It’s been some time since my last post and I decided to post a new one. I have reviewed Cloud Readiness / Oracle Oracle HCM Cloud What’s New documents for the 20C update and would like to admit some of them definitely deserve attention.
Of course, the full list is quite long but I tried to outline those that I personally had in my wishlist.
A full list you can review here.
1. Actions Framework Improvements
Now you can configure country and/or role-specific action and action reasons that extend flexibility on filtering out lists of actions and reasons based on specific roles or countries.
Also, you can make assignment statuses country-specific and what was the most requested is to set a default assignment status based on the action selected. It might be useful if you use actions to register long-term absences with no eligibility for payroll during the absence period. It was quite a challenge to teach users to not forget changing assignment status for that kind of action. Now you can accommodate it to ensure consistency of transactions.
Pay attention that all action framework improvements work only in responsive pages.
2. Automation of accrual plan enrollment and plan balances copy during local/global employee transfers
Below is the Oracle explanation:
The automation will be delivered as a phased approach across releases. If you as an employee are eligible for the same plan in the new entity when transferred, all your active absence plans in the old organization will be end dated. Your enrollment into the same plan will be automated in the new entity and the initial plan balance will be re-instated. Currently, this automation is available for front-loaded and incremental accrual plans with carryover options enabled. Copying of plan balance for accrual plans with vesting, waiting period and rollover options is not included in this release yet.
It definitely improves user satisfaction avoiding manual movement plan enrollments and balances in the new assignments.
3. Individual compensation approval notifications now can show element input values
Now you can include any input values to the BIP notification template other than a primary input value that makes approval transaction more clear to understand what needs to be approved. The point is that Manage Personal Contribution, Individual Compensation transactions often are accommodated for registering some events related to payments (overtimes, etc.), and to make it clear for approver we were forced to provide clear clarifications in approval comments that are not stored alongside with individual compensation transactions. Now you can set up input values to put all needed information for approvers.
4. Salary range validation configuration
Before the system only raised a warning message without preventing saving a change salary transaction.
I remember I came up with a workaround described in my previous post: https://hcmcloudhub.com/2019/06/10/how-to-restrict-for-users-to-enter-a-salary-amount-outside-a-grade-range/
Now it is not needed anymore as it becomes a standard configuration.
You can now specify whether to allow, warn, or disallow proposed salaries that violate the salary range. For example, you don’t let anyone propose salaries that are under or over the specified salary range. Or, you warn people when their proposed salaries are under or over the specified salary range.
5. Migrating Security Definitions
This is a huge improvement for security implementation consultants.
Not sure it is exactly related to 20C update as it is already in place in my POD that is 20B. Anyway, it’s been a challenge to migrate custom job roles, duties, data security policies before this improvement, and it will definitely save a lot of time to migrate security between DEV-TEST-PROD environments. Now you can migrate all security-related artifacts such as job roles, duties, data roles, data security policies, security profiles, role provisioning rules, etc.
The easiest way to migrate security artifacts in bulk using Export / Import feature in a functional area.
You can narrow a scope to pick only a set of the custom roles you want to migrate:
Once the process finishes, download a zip file and import it into a target environment.
You don’t need to submit a regenerate grants ESS job as it is done behind the scene as a final step of the import process.
Of course, you can migrate one or more custom roles (without security profiles) using export options for the following FSM tasks:
Export business objects for these tasks
– Manage Job Roles / Manage Duties
– Manage Data Security Policies
I hope you will find it useful.