150 likes | 410 Views
AX 2012 Development Training. Presented by Vishy Grandhi. Training Outline. Lesson 1: Role based security Lesson 2: Setup new user Recipes. Role based security : Objectives. At the end of this lesson you will have an understanding about Role based security Roles assignment to users.
E N D
AX 2012 Development Training Presented by Vishy Grandhi
Training Outline • Lesson 1: Role based security • Lesson 2: Setup new user • Recipes
Role based security: Objectives • At the end of this lesson you will have an understanding about • Role based security • Roles assignment to users
Role based security : Definitions • Entry Points • Permissions • Privileges • Duties • Roles
Role based security : Entry Points • Menu items • Web content items • Service operations • SSRS reports
Role based security : Process Cycles • Process cycles are used in rich client to make it easier for a system administrator to view and find related duties when setting up security. • Conversion cycle • Cost accounting cycle • Expenditure cycle • Human capital management cycle • Information Technology cycle • Revenue cycle
Setup new user: Objectives • At the end of this lesson you would have a good understanding of the following • Setup a new user • Assign the user appropriate role • Modify roles, duties and privileges
Recipes: List of recipes • The following recipes are included in this presentation 4a. Create a new privilege and duty for your form 4b. Assign your duty to a process cycle and role 4c. Create a new user 4d. Assign role to a user
Recipe 4a: Create a new privilege and duty for your form • Start • Let’s assume you created a new form called SpeciesForm and a new display menu item called SpeciesMenuItem • Open Microsoft Dynamics AX development workspace (Ctrl + Shift + W) • Right-Click on AOT->Security->Privileges and select New Privilege menu • Rename your privilege SpeciesPrivilege • Right-click the node Menu Items->Display->SpeciesMenuItemand select Open New Window • Drag the menu item SpeciesMenuItem to the Entry Point node under your privilege SpeciesPrivilege • You should have an entry under the Entry Point node called SpeciesPrivilege. Select this nodeand check properties (F4) • In the Properties Window select the property AccessLevel and change the value to Delete • Right-Click on AOT->Security->Duties and select New Duty • Rename your duty to SpeciesMaintain • Drag your privilege SpeciesPrivilege to the Privileges node under your dutySpeciesMaintain • Finish
Recipe 4b: Assign your duty to a process cycle and role • Start • Let’s assume you created a new duty SpeciesMaintain • Open Microsoft Dynamics AX development workspace (Ctrl + Shift + W) • Right-Click on AOT->Security->Duties->SpeciesMaintainduty and select Open New Window • Expand the Process Cycles node (Under AOT->Security) and select the process cycle to which you want to add your duty. • Drag the duty SpeciesMaintain to the Duties node under your process cycle • Expand the Rolesnode (Under AOT->Security) and select the Role to which you want to add your duty. • Drag the duty SpeciesMaintain to the Duties node under your role • Finish
Recipe 4c: Create a new user • Start • Open the Microsoft Dynamics AX client. • Open the Users form. System Administration > Common > Users > Users. • Click New > Import in the Action Pane. • Click Next. • Select the domain name contoso.com. • Enter Vishyfor the first name. • Click Next. • Click Select all. • Click Next. • Click Next. • Select only System User and Employee roles. • Click Next. • Select Accounts receivable administrator profile in Same profile in all companies. This defines Vishy'srole center. • Click Next. • Click Finish
Recipe 4d: Assign role to a user • Open the Microsoft Dynamics AX client. • Go to System Administration > Common > Users > Users. • Double-click VishyGrandhi in the grid to edit his record. • Click Assign roles in the User's role section of the form. • Select Accounts receivable manager and click OK. • Finish.
Summary of Training • We have looked at Role based security in AX • We explored the different security elements • Finally we created a new user and assigned him/her roles