http://www.workflowfaq.

com/roles-grants-for-ame By default, the “Approvals Management Administrator” and “Approvals Management Business Analyst” responsibilities do not have any functions associated with them, because their access is restricted by Role Based Access Control (RBAC). In this section, I will detail the steps needed to add functions so that we can get into using AME. Firstly, we’ll create a new user for this demonstration, and assign them the two responsibilities, thus:

If I now log into the eBusiness Suite as that user and try to switch to either of those responsibilities, the system indicates that there are no functions available for the user (see screenshot below). As I said above, this is because role based access control ensures that only users with the right roles as well as responsibilities can access the functions.

So, now we need to modify the user to give them the right roles to administer AME properly. As a system administrator, open the “User Management” responsibility, as shown below.

you now have functions associated with the two responsibilities: . Once you have entered the justification. then you will need to use the SYSADMIN user and assign the “Security Administrator” role to your user. where you should search for all Roles beginning “Approval”: You are then returned to the user screen. you should then hit the Apply button. Search for the user that you want to add the functions to (in my case.If you do not have any functions assigned to the responsibility. the AMEADMIN user I created earlier). where you should complete a justification for granting the roles to the user – if you don’t then the screen will prevent you from continuing. and when you log in as the AME user. Select the “Users” option to continue. open the user details and then click on the “Assign Roles” button. Log out as this user. You are then presented with a search window.

thus: . In this example. The main principle behind this is to enable organizations to split the Transaction Type maintenance between different roles – for example to allow HR Super Users to maintain only the HR rules. we will create a specific grant for the AMEADMIN user. the data is still protected and cannot be viewed: Again. we need to grant some RBAC roles to allow the user to access the different transaction types. however in the real world it is more likely that you will create the grant for a group of users. Using a different user. RBAC means that when we open the Dashboard. However.Now that we have granted the roles to the user. they can access the functions correctly. navigate to the Functional Administrator responsibility and click on the “Create Grant” button to create the new grant. The Object is set to “AME Transaction Types”.

Log out of this user and log back in as the AMEADMIN user. now flush the cache by clicking on the “Core Services” tab then choose the “Caching Framework” sub-menu. and navigate to one of the AME responsibilities – you are now given a list of the AME Transaction Types that are configured in the system: . accept the default data context type of “All Rows” and continue to the third step. Define the “Set” to be “AME Calling Applications” as shown in the following screenshot: Finally. You will be presented with a warning message (see below) which you can ignore and click on the “Yes” button.In the second step. Choose “Global Configuration” from the sidebar and then click on the “Clear All Cache” button. In order to ensure that the changes are replicated. review the settings that you have entered and click on the “Finish” button.

I’ll be providing a practical example of customizing AME within iRecruitment.In the next blog post. .

Sign up to vote on this title
UsefulNot useful