Many of you probably know about an Application Composer. This is a powerful tool to extend certain cloud applications (such as CX, ERP, SCM Cloud Applications) by creating fields, objects, and relationships between objects.
Here are some of the changes you can make using this tool:
• Modify objects by adding new fields or create entirely new objects.
• Create foreign key-based relationships between two objects.
• Modify user interface pages by exposing your newly created fields for an object or create an entirely new work area for your custom objects.
• Expose object relationships on pages in the form of subtabs.
• Write application logic, such as triggers and validation rules, for an object or for use across multiple objects.
• Implement functional and data-level security for custom objects.
• Enable custom objects for reporting by creating custom subject areas.
I got some experience with the Application Composer while was working with the Oracle HR helpdesk module.
Unfortunately, it is not applicable to Oracle HCM Cloud business objects and pages.
To tailor a user experience Oracle offers the Page Composer and HCM Experience Design Studio for the HCM product family. We are looking forward to getting a new powerful feature “Autocomplete Rules” inside HCM Experience Design Studio that has already been announced but still under controlled availability. According to Oracle statements, we will be able to get much more flexibility with object defaulting rules, object validation, rules, field validation, and modification rules. That’s going to be terrific improvements.
But few of you know that it is possible to write application logic with Groovy, such as triggers and validation rules, for HCM objects too in the current Oracle HCM Cloud version.
Let me outline this ability on the following use case: while creating a Position it is required to populate default values for BU, Department, and Location from the logged-in user employee’s assignment who is creating a position and set a default value for Hiring Status as Approved.
Below are configuration steps to achieve this:
1. Enable HCM Business Objects Configuration at the enterprise level.
2. Activate a sandbox.
3. Go to the Configure Objects page.
4. Create a post-create a trigger
5. Come up with a Groovy script. You can learn more about using Groovy in Oracle Cloud Applications here: https://docs.oracle.com/en/cloud/saas/applications-common/20b/oacex/groovy-scripts.html#OACEX576000
Below is a short video that demonstrates the above steps:
I hope you find this helpful.
Very nice article. Thank you for sharing. I have question about the VO. Where can we get the list of the VO?
thank you for the great Article, Could you give more info about how to find the VO name? for example, I need the VO name Business Unit object, Value set object.
Could you also give an example of using CommonLookup VO in HCM?