Upgrading from any release prior to Kingston can result in Restricted Caller
Access (RCA) errors in certain HR functionality. For example, when submitting requests from the
Employee Service Center (ESC) or HR service portal.
Changes to RCA configuration on upgrade
Errors can occur if you have customizations that reference script includes.
Script includes prior to the upgrade are Caller Access = None. This
setting prevents affecting current functionality when you install the Scoped Application
Restricted Caller Access [com.glide.scope.access.restricted_caller] plugin.
The next upgrade and any subsequent upgrades you take, it’s possible some of your script
includes can have their Caller Access set to Caller Restriction. Some of these potential RCA
errors can affect submitting requests from the ESC or HR service portal.
- Actions
- If you are on Madrid or greater, you can run the Automated Test Framework (Quick Start
Tests). These tests identify any affected script includes and to ensure that basic
functionality is intact.
- For flagged issues:
- Add the RCA privilege files to your configuration.
Note: For script includes that
are not causing issues, keep Caller Access = Caller
Restriction. This setting prevents outside code from accessing these
scripts.
- Or, reset your script includes that are causing errors because of these changes to
Caller Access = None.
Note: This setting customizes the
script include and makes it more difficult to receive future base system fixes and
features that affect the script.
- Upgrading could affect these script includes:
Script includes |
Script includes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|