20B Action/Action Reason Enhancement Q&A

Tuesday, May 12, 2020 5:40 PM

1. We are getting errors when clicking on action and action reason. Is this an issue with a missing privilege on a custom role?

The privileges below are already given to users with seeded HR Specialist and Line Manager role. For custom role, confirm the y have below privileges, if
not add them, regenerate the roles, and re-test.

2. We have our approval rules configured to route the approval notification based on the Action/Action Reason entered for a transaction. Will making this
customization have any impact on how these transactions are routed for approval?

No, this will not have any impact on transaction approval rules.

3. Can we change/limit the list of values that we wish to display in the Action Reason field for MSS/ESS workflows?

No, you cannot limit what is shown in the list of values. These options displayed here depend on the action type selected. You will see all action reasons
created for the given action type.

4. With this enhancement, are there any additional changes to security that need to be updated?

Nothing needs to be updated for security. This enhancement only impacts customizations that were done to these fields.

5. Can we speak more about what/how is impacted? We do not have time to regression test every single customization in 3 days.

The changes were only done to the Action/Action Reason and Direct Report Action/Action Reason fields. These are the only fou r fields that will be
impacted by this enhancement so you won’t have to review all customizations done after upgrading to 20B.

6. How do you customize the Change Assignment workflow if we already have a rule that is grayed out?

Unless the rule is seeded, you can change/edit the rule. If there is an issue with a custom rule being grayed out, the sugge stion would be to log an SR with
Support to look into that issue further.

7. Once the patch is applied to Production, will we have to reapply the customization even after the fix?

Yes. Since the component of these fields have been changed in 20B, the customization will need to be recreated from either t he Design Studio or Page
Composer.

8. If there are no customizations on the Action or Action Reason fields, then nothing needs to be fixed?

Correct. The 20B enhancement changed the component of these fields which causes the old customizations to this field to no l onger work. If there were
never any customizations done to these fields, then no action needs to be taken.

9. When attempting to terminate an employee, I am encountering the error “You must enter a valid value for the Action ID field (PER-1530231).” This did not
appear until this component changed. How should I proceed as the action and reasons are active with end date of 12/31/4712?

This issue would not be related to the 20B enhancement. The recommendation would be to log an SR with Support to investigate this further.

10. Is long term goal to get rid of Page Composer and move everything to the Design Studio?

Yes. After analyzing the common customizations done by our customers, we found that the many customizations were done to mak e fields show as
visible or required. We have started this migration by allowing these simple customizations to be done in the Design Studio. Over time, more complex
customizations will be possible from the Design Studio.

11. We have not gone live yet but are getting ready to add our customizations to our Production environment which is scheduled to upgrade to 20B next week.
What is the recommended action plan with respect to the customizations that need to be added?

Trainings Page 1
 If you have not done any customizations yet in Production, then you should wait for the 20B upgrade before entering the neces sary customizations.

12. Our Production pod is scheduled to upgrade to 20B in June. Will the patch for this issue be applied automatically at that time?

Yes, the patch for this issue will be included.

13. Prior to the patch, we had to follow the workaround of downloading the customization XML file, delete a certain line, and re-upload the XML file. Do we need to
follow this process again after the patch is applied?

No, you do not need to follow the workaround again after the patch has been applied. The recommendation is to recreate the r ule in the Design Studio
after upgrading so that the customizations to the Action/Action Reason fields are shown again.

14. Is it possible to make the action field mandatory from the Design Studio?

The Action field is delivered as mandatory so there is no property to set as required/not required. The only option in the D esign Studio is to set it as either
visible or not visible.

15. Does this mean that the 20B enhancement essentially removes the old customizations to these fields?

Yes, the upgrade to 20B essentially removes the customizations to the Action, Action Reason, Direct Report Action, & Direct R eport Action Reason. These
will need to be added back after upgrading to 20B.

Trainings Page 2