Important Update: Community URLs redirect issues are partially resolved. Learn More. .
on 2022-03-31 11:35 AM
The legacy Operational Risk Management (ORM) Custom Control available in the Archer Operational Risk Management use case has been retired as of Archer Release 6.11. Organizations who have not updated their Archer Operational Risk Management Use Case to the latest version - Release 6.9 SP2 (6.9.2) - leveraging the new ORM Report Object and who wish to take advantage of the Release 6.11 platform enhancements will not have access to the Self-Assessment Application upon migration to Release 6.11. Organizations must package install the new ORM use case (6.9.2) to access the Self-Assessment application on the Release 6.11 platform.
In Archer Release 6.11, the legacy Operational Risk Management (ORM) Custom Control within the Archer Operational Risk Management use case has been retired. The ORM Custom Control was replaced with a Report Object in version 6.9.2 in April 2021. With the retirement of the ORM Custom Control, customers with active licenses for the Operational Risk Management use case will be required to upgrade their use case to the latest version in order to take advantage of the Release 6.11 Archer Platform updates. Customers who have already taken advantage of the updated 6.9.2 ORM use case will not be affected by the Custom Control retirement.
Customers who are unsure if they are still using the ORM Custom Control, and not yet upgraded to the ORM Report Object, can verify their use case version by contacting their Archer Administrator or by accessing the Self-Assessment application within the Operational Risk Management use case.
Customers on the legacy version of the ORM use case will see the Custom Control. Note that customer specific configurations may alter the Self-Assessment record page from the out of the box application.
Customers on the updated 6.9.2 ORM use case will see a Report Object. Note that customer specific configurations may alter the Self-Assessment record page from the out of the box application.
For customers who upgrade to Release 6.11 but have not upgrade their ORM use cases to Release 6.9.2, the Custom Control within the Self-Assessment application will be unavailable.
For end users accessing the Self-Assessment application, there will be no on-screen error messages or indicators of the unavailability of the deprecated Custom Control. Instead, when general users attempt to load a record within Self-Assessment application, their browser will redirect them to their home screen.
For administrators accessing the Self-Assessment application, the Archer Log will indicate the deprecated and removed ORM Custom Control code. Likewise, the Application Builder will highlight that the feature is no longer available.
SaaS & Hosted Customers:
SaaS and Hosted customers can expect standard upgrade timelines for the latest platform release. Therefore, SaaS and Hosted customers are encouraged to take the ORM use case upgrade to Release 6.9.2 as soon as possible in order to continue uninterrupted use of the Self-Assessment application. For SaaS and Hosted customers already using the latest ORM Report Object, no changes are needed; the upgrade will have no effects on the ORM Report Object.
SaaS and Hosted customers still on the legacy version of the ORM use case, using the Custom Control are encouraged to take the Release 6.9.2 use case package updates as soon as possible. There are two options SaaS and Hosted customers can follow. Customers can upgrade their ORM use case by taking the latest ORM use case package either before or after their platform updates to Release 6.11. Applying the new use case package prior to the Release 6.11 platform upgrade will ensure there is no disrupted access to the Self-Assessment application. For customers who upgrade their use case version after the Release 6.11 platform update, there will be no loss of data, but access to the Self-Assessment record page interface will be disrupted until the new use case package is applied.
When installing the use case package, Archer Administrators are reminded to override the default layout option in the final steps of the ORM installation and select “Override Layout” to ensure proper display of the ORM Report Object.
On Premises Customers:
On Premises customers using the legacy ORM use case (pre-6.9.2 release) are required to upgrade their use case version to use the new ORM Report Object if they wish to use the platform enhancements available in Release 6.11. On Premises customers currently on a platform version of Release 6.9.2 or higher can upgrade their ORM use case to Release 6.9.2 prior to taking the Release 6.11 platform update to ensure there is no loss of access to the Self-Assessment user interface. If customers chose to upgrade their platform to Release 6.11 prior to taking the ORM use case package updates, the Self-Assessment application record page will not load until the new package is applied. Once the new use case package is applied, the user interface will be available. Note that no date is lost with the deprecation of the ORM Custom Control.
For On Premises customers on a platform version prior to Release 6.9.2 that wish to maintain access to the Self-Assessment application throughout their migration must upgrade their platform to a release between Releases 6.9.2 and 6.10, apply the new ORM use case package, and then upgrade their platform to Release 6.11. Customers can also upgrade directly to Release 6.11 and then apply the ORM use case package, but the ORM Self-Assessment application will not load until the new use case package is applied.
When installing the use case package, Archer Administrators are reminded to override the default layout option in the final steps of the ORM installation and select “Override Layout” to ensure proper display of the ORM Report Object.
10.Click Install and Click “Ok”
Note: Upon successful package installation, the ORM Custom Control will be moved off the layout within the Application Builder and replaced with the Report Object.