Process an Outlier

When a suspect product with local license is removed on a follow-up, the case remains a Local PRPT Case (Local Potential Reportable Case) until the corresponding nullification/downgrade local reports is generated.

If a customer wants to change Local Reports configuration data after being in production with this release, it is recommended that customers ensure that cases/reports under processing be completed before changing configuration data to avoid unpredictable results. Note that if a customer changes the Local Reports configuration data mid-way where the reports are mid-way processing (e.g., scheduled), the reports will be determined as local/global based on what type it was at the time when the report was scheduled and will be completed processing that way irrespective of current configuration even if inconsistent with the configuration. Also note that presence of local reports will determine that the case is local case.

It is also recommended that customers ensure that cases/reports under processing be completed before up taking the Local Locking feature and (thereby) installing the local lock configuration data (refer to Activate Local Locking in Oracle Argus Safety). Note that if the case was mid-way processing (e.g., case was open in data entry workflow) when customer up took the Local Locking feature, a subsequent case save will determine if the case is local or global.