AME Part Five – Defining a Dynamic Approval Group

One of the most recent search terms that I’ve seen for my blog here was “AME dynamic approval group example” – so in this post, I’m going to go through the steps required to create a dynamic approval group and provide an example.  This example continues on from part four, since we will be replacing the static approval group with a simple dynamic one.

Using the “Approvals Management Business Analyst” responsibility, in the “Approval Process Setup” panel on the right hand side of the dashboard, choose the “iRecruitment Vacancy Approval” transaction type again:

Define Process for the Transaction Type

Click on the “Approver Groups” link, and we will modify the existing group from static to dynamic.  Click on the “Update” icon for the Approver Group we created earlier, and then change the usage type from Static to Dynamic.  As soon as the change is made, you will be shown a warning, indicating that the static approvers will be removed from the group:

Warning when changing usage

Since we are going to be redefining the group completely, this is fine, so click on the “Yes” button and you will be returned to the group definition with no static approvers shown.

As a simple example, my approver group requires approval from two people – the user MATT and the HR person Tim Cleary.  The SQL code required to retrieve the two records in the same query is

SELECT 'user_id:'||user_id
FROM   fnd_user
WHERE  user_name = 'MATT'
SELECT 'person_id:'||person_id
FROM   per_all_people_f  papf
WHERE  papf.full_name = 'Cleary, Mr. Timothy'

In the SQL above, we need to tell AME exactly what kind of approver we are retrieving – by prefixing the user record with “user_id:” and prefixing the person record with “person_id:”, AME then knows where the records are being retrieved from.  Enter the SQL into the Query box, and then hit the Apply button. You can also use the Validate button, which checks that the query is structurally sound, but does not seem to check much more than that (for example, if you prefix the user record with “usssssser_id:”, it is still classed as a valid query).

That’s all there is to it – if we now go and create a new vacancy (using the same BJOSPEH user that we did in the last post), when we review the vacancy, we see that AME has added the two approvers to the bottom of the approval list:

Additional Approvers are generated by AME

2 thoughts on “AME Part Five – Defining a Dynamic Approval Group

  1. Hi,

    do you know if there is any way to get the approval group name in the approval list to display the actual person that the notification is going to?

    Currently if you define an approval group called

    Another Group
    which contains 1 member
    Another Member

    the Workflow shows that the next step on the notifications trail it to go to “Another Group”. is there any way that we can make that Description say its going to “Another Member”
    rather than “Another Group”

Comments are closed.

By continuing to use the site, you agree to the use of cookies. more information

In common with almost all professionally run websites, this website logs the IP address of each visitor in order to keep it running reliably. This is also essential for protecting the website and its visitors from malicious attacks, including infection with malware.

This website provides information as a service to visitors such as yourself, and to do this reliably and efficiently, it sometimes places small amounts of information on your computer or device (e.g. mobile phone). This includes small files known as cookies. The cookies stored by this website cannot be used to identify you personally.

We use cookies to understand what pages and information visitors find useful, and to detect problems such as broken links, or pages which are taking a long time to load.

We sometimes use cookies to remember a choice you make on one page, when you have moved to another page if that information can be used to make the website work better. For example:
- avoiding the need to ask for the same information several times during a session (e.g. when filling in forms), or
- remembering that you have logged in, so that you don’t have to re-enter your username and password on every page.

You can prevent the setting of cookies by adjusting the settings on your browser (see your browser Help for how to do this). Be aware that disabling cookies will affect the functionality of this and many other websites that you visit.