mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-08-06 09:26:52 +01:00
- Introduced guidelines for using the "CMFRT" prefix in object names, fields, and procedures to avoid naming collisions and ensure clarity. - Established rules for object ID ranges to prevent conflicts with other extensions and maintain historical integrity. - Documented best practices and anti-patterns for various coding patterns, including case statements, interface injection, label usage, and validation methods. - Implemented a standards review skill to evaluate AL source changes against CMFRT company standards, ensuring compliance with naming, permissions, and architectural patterns.
32 lines
864 B
AL
32 lines
864 B
AL
table 55008 "CMFRT AQ Setup"
|
|
{
|
|
fields
|
|
{
|
|
field(55011; "CMFRT AQ FS Jnl. Template Name"; Code[10])
|
|
{
|
|
Caption = 'CMFRT AQ FS Journal Template Name';
|
|
ToolTip = 'Specifies the Job Journal Template used for material lines created by the Field Service API.';
|
|
DataClassification = CustomerContent;
|
|
}
|
|
}
|
|
}
|
|
|
|
page 55020 "CMFRT AQ Setup"
|
|
{
|
|
layout
|
|
{
|
|
area(Content)
|
|
{
|
|
field("CMFRT AQ FS Jnl. Template Name"; Rec."CMFRT AQ FS Jnl. Template Name")
|
|
{
|
|
ApplicationArea = All; // Caption and ToolTip inherited from the table field
|
|
}
|
|
}
|
|
}
|
|
}
|
|
|
|
enum 55040 "CMFRT AQ Buffer Status"
|
|
{
|
|
value(55000; "CMFRT AQ Pending") { Caption = 'CMFRT AQ Pending'; }
|
|
value(55001; "CMFRT AQ Processed") { Caption = 'CMFRT AQ Processed'; }
|
|
}
|