AME Role / Responsibility assignment to a user


Functional Setup

For setting up standard attributes, users need to have AME responsibilities. Below are steps to do the same.

 

I) From System Administrator

1. Login as System Administrator user

2. Select the responsibility “User Management”.

3. Select “Users” menu option

4. Search for the user to whom you wish to grant AME roles and click on ‘update’ icon

5. In the update user page, user details can be seen along with a list of roles available to user. Click on

‘Assign Roles’ button

6. Search for ‘Approval%Man%’ and it will give list of roles available.

7. Select Roles: 1) Approvals Management Administrator 2) Approvals Management business Analyst

8. Specify justification and relevant dates for the newly assigned roles, and click Apply to assign the

Roles to the user.

 

II) From Personal Login

  1. Navigate to the Personal Home Page.
  2. Select Functional Administrator Responsibility
  3. From the Grants page, press on the Create Grant button

4. Create a grant with the following information:

· Name <specify a descriptive name>

· Grantee Type = Specific User

· Grantee = <The user which you just created>

· Object = AME Transaction Types

5. Click next and select the Object Data Context

· Data Context Type = All Rows

6. Click Next to define the object parameters and Select Set

· Set = AME Calling Applications

7. Click Next, review the setups and then finish the process.

Now, User should be able to see ‘Approval Management Business Analyst’ responsibility in his/her home page. If not, please ‘Clear Cache’ from Functional Administrator Responsibility.

 

Pre-Requisites

Below are two Standard Attributes that need to be setup:

  1. The profile option AME: Installed should be ‘Yes’ either at the application or site level.
  2. Worklist is enabled for the users to receive notifications in the Application Worklist.
  3. Any Standard Attribute setup list ‘Allow Empty Approval Group’, ‘At least one rule must apply’ etc. need to be setup with required value as per requirements, before migrating Rules (If AME rules are planned to migrate through ldt files)