bcquality/custom/knowledge/security/cmfrt-three-permissionset-pattern.good.al
BeytullahCengiz88 afb1fa2883 Add CMFRT naming conventions, object ID ranges, and patterns documentation
- 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.
2026-07-14 14:09:04 +02:00

35 lines
1.1 KiB
AL

// Step 1: Objects set — owns all AL objects with execute access.
permissionset 2045222 "CMFRT GD Objects"
{
Assignable = true;
Caption = 'CMFRT GD Geodynamics - Objects';
Permissions =
table "CMFRT GD POI" = X,
table "CMFRT GD Setup" = X,
page "CMFRT GD POI" = X,
page "CMFRT GD Setup" = X,
codeunit "CMFRT GD IGeodynamics" = X,
codeunit "CMFRT GD IGeodynamics Impl" = X;
}
// Step 2: Read set — inherits object access, adds tabledata read.
permissionset 2045221 "CMFRT GD Read"
{
Assignable = true;
Caption = 'CMFRT GD Geodynamics - Read';
IncludedPermissionSets = "CMFRT GD Objects";
Permissions =
tabledata "CMFRT GD POI" = R,
tabledata "CMFRT GD Setup" = R;
}
// Step 3: Edit set — inherits Read, adds insert/modify/delete.
permissionset 2045226 "CMFRT GD Edit"
{
Assignable = true;
Caption = 'CMFRT GD Geodynamics - Edit';
IncludedPermissionSets = "CMFRT GD Read";
Permissions =
tabledata "CMFRT GD POI" = IMD,
tabledata "CMFRT GD Setup" = IMD;
}