Security Duty Properties [AX 2012]
Updated: August 9, 2011
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
In Microsoft Dynamics AX, security permissions are combined into privileges, and privileges are combined into duties. Duties are defined as a group of related privileges that provide a user with access to a specific business function. In the application object tree (AOT), these privileges are organized into the nodes of a duty.
This section describes the best practice rules for duties.
-
All duties should be assigned to a role.
-
All duties should be part of a process cycle.
-
Because a duty represents a specific business function the name of the duty should rarely or never change. For example, your company pays bills. The details of how you pay bills may change but the essential function of paying bills will not change. Instead of creating a new duty you should change the privilege subnodes of the duty.
-
The name of a process cycle should rarely or never change.
This section describes the properties for the AOT node at Security > Duties > YourDuty.
|
Property |
Required |
Description |
|---|---|---|
|
Name |
Yes |
Name of the duty. |
|
Label |
Yes |
Text that appears on the user interface for the duty. |
|
Description |
Yes |
Description of the duty. |
|
Enabled |
Yes |
The enable value. The value can be one of the following:
|
This section describes the properties for the AOT node at Security > Duties > YourDuty > Privileges > YourPrivilege.
|
Property |
Required |
Description |
|---|---|---|
|
Name |
Yes |
The name of the privilege. |
|
Enabled |
Yes |
The enable value. The value can be one of the following:
|
Announcements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. Get your copy at the MS Press Store.