AVIO Consulting

Oracle ACM 11g – A look into Title, Priority, and Category

Mar 31, 2014 | ACM, BPM, Oracle

In Oracle BPM 11g PS6, BPM Studio (JDeveloper) is the design-time environment for Oracle Adaptive Case Management (ACM). The first thing that you notice when you create your Case Management project in JDeveloper is the Case artifact itself. The top most tab in the Case artifact is the ‘General’ tab. The first three elements on this tab are Title, Priority, and Category. It was not obvious to me as to what values should be used in these three elements when I created my first ACM project. It is only after I deployed it and browsed through the Case UI on the BPM Workspace that I was able to get a better idea of what values to use. In this blog we will cover what these three elements define in a Case and the different options that are available to set the values for them.

The first element is Title. This element defines the name of each Case that will be created. The default option for this element is a non-dynamic value. There is a very high probability that you don’t want to give the same name to all your Cases and hence you will not want to you use this. You will want to set a dynamic value so that every Case has a unique name to identify it with. Follow these steps to set dynamic value for your Title:

1) Select ‘Translation’ from the drop-down for the Title.

2) Once you select ‘Translation’, a circular globe icon appears next to the Title value field, click on it.

3) Click on the + button to ‘Create a new Key’ and give it an appropriate name. Use curly brackets and consecutive numbers for arguments, as shown below. Click Ok.

4) Now you will map your arguments to some values. To map your values to the Case related metadata for each Case, you should have your Case Data already defined. To do that, click Ok to exit out of the Translation and click on the ‘Data & Documents’ tab and add it using the + button. See image below.

5) Switch back to the ‘General’ tab and click on the ‘Translation’ circular globe icon.

6) For {0}, click on […] button. An Expression Builder opens up. In the Variables section you see 2 things, (1) you see your Case variable and (2) you see your Data variable(s). Select an appropriate variable attribute. Use the ‘Insert into Expression’ button, do not type the XPath. See image below.

6) Do the same for {1}. See image below.

7) Your finished Translation will look as shown below. Click Ok.

The second element is Priority. This element defines a Priority that is set for each Case that is created. In JDeveloper, you can set the default value for all the Cases from the drop-down (1 thru 5). When a new Case is created via the ACM ‘StartCase’ operation, the Priority for the Case can be defined as part of the payload. If the Priority is not set as part of the payload, ACM applies the default value set in JDeveloper as the Priority.

The third element is Category. This element defines a Category, or in other words, a group that each Case belongs to. For example, you could have some Cases go into a “Platinum Customer” group, while other Cases go into a “Gold Customer” group. Similar to the Title, the default option is a non-dynamic value. If you are going to use Category, there would be no reason to assign the same Category to all your Cases. Hence, you don’t want to use a non-dynamic value. The steps to set a dynamic value for the Category are the same as for Title.

1) Select ‘Translation’ from the drop-down for the Category.

2) Once you select ‘Translation’, a circular globe icon appears next to the Category value field, click on it.

3) The rest of the steps are the same as that of setting a dynamic value for Title.

For more reading on Oracle ACM, please have a look at the articles published by the Oracle A-team. Also, have a look at this other AVIO blog – 5 Scenarios for Using Adaptive Case Management published by Kris Nelson.

Please feel free to leave me any comments or questions.