Implementing Oracle Search - Do’s and Don’ts

Do's	Don'ts
Run the ‘Compute Users ACL with parameter User Population = All Users’ ESS job only ONCE after the new module(s) have been ingested for additional product implementation in OS.	DO NOT re-run the Initiate ACL Ingestion job set for any additional product OS implementations. This is done only once at initial implementation. This is a job set which creates empty ACL index first and follows with the computation of ACL for all users. This may cause users of existing implementation not being able to view results in secured searches until this job is completed. DO NOT schedule the ‘Compute Users ACL with parameter User Population = All Users’, as this could cause performance issues.
Review if the ACL refresh jobs are scheduled on your application. This is important to ensure searches apply the up-to-date data security policies.	The process Compute Users ACL with parameter User Population = All users should not be run periodically and should not be scheduled.
Review if the ACL refresh jobs are scheduled on your application. This is important to ensure searches apply the up-to-date data security policies.	Don’t schedule the ingestion of functional indices. It’s not necessary and will only consume system resources.
Run periodical health checks of functional index ingestions with diagnostic reports to identify ingestion issues. There are reports for person, journeys, work structures, and so on. Run Compute Users ACL with population = All Users after P2T (on the target environment).	Don’t run initial ingestion of functional indices (such as fa-hcm-person or fa-hcm-position) as part of the release upgrade. There is an automated ingestion process implemented, which will re-ingest indices that require full re-ingestion upon release upgrade.

Best Practices for Scenario-based Use Cases

Case	Key Points	ACL process to run	ACL Frequency	When to run
Update of a security role where majority of users are impacted	If a role that impacts majority of the population like employee or line manager role has been modified and some new privileges have been added or removed, execute ACL process for all users	Stop Business As Usual Incremental jobs.) Compute Users ACL (Parameter - All Users) ,	Once	To be run in off business hours or cut-off period
Update of a security role where only a handful of users are impacted	If a role impacting a handful of population like an admin role has been modified for which only a small population of support and admin users have been assigned.	Individual ACLs can be computed for a user using the Regenerate ACL action available in the “Preview HCM Data Security.”	Once per user	Can be run during business hours
Major re-org within enterprise. (including mergers and acquisitions).	Execute the ACL process for all users. ACL index will be updated, and it will be run for all users.	Pause the incremental schedule, run Compute Users ACL (Parameter - All Users) only once, and then resume the incremental schedule.	Once	To be run in off business hours or cut-off period

Case

Key Points

ACL process to run

ACL Frequency

When to run

Update of a security role where majority of users are impacted

If a role that impacts majority of the population like employee or line manager role has been modified and some new privileges have been added or removed, execute ACL process for all users

Stop Business As Usual Incremental jobs.)

Compute Users ACL (Parameter - All Users)

Once

To be run in off business hours or cut-off period

Update of a security role where only a handful of users are impacted

If a role impacting a handful of population like an admin role has been modified for which only a small population of support and admin users have been assigned.

Individual ACLs can be computed for a user using the Regenerate ACL action available in the “Preview HCM Data Security.”

Once per user

Can be run during business hours

Major re-org within enterprise. (including mergers and acquisitions).

Execute the ACL process for all users. ACL index will be updated, and it will be run for all users.

Pause the incremental schedule, run Compute Users ACL (Parameter - All Users) only once, and then resume the incremental schedule.

Once

To be run in off business hours or cut-off period