Important Update: Community URLs redirect issues are partially resolved. Learn More. .
2023-07-13 02:08 PM - edited 2023-07-13 02:11 PM
If you did not upgrade to 6.13 or 6.13 Patch 1 (i.e., You upgraded to 6.13 Patch 1 Hotfix 2 or higher), you do not need to use this script.
Archer Platform versions 6.13 and 6.13 Patch 1 (6.13.0.1) contain a defect which removed data values from text boxes and other Application Builder areas where the data had no characters present outside of HTML markup (e.g., only an image was present). The following components were altered:
• Section Panel Text
• Section Help Text
• Layout Object Description
• Workspace Description
• Field Description (includes Text Box content)
• Field Help
To recover this data, a script must be run against a pre-upgrade, restored instance backup. The results of this script are SQL Commands which can be run against the post-upgrade database to restore the data.
Archer determined that a reported defect might adversely affect customers running Archer 6.13. Archer removed the 6.13 and 6.13 Patch 1 releases from myRSA and stopped the in-progress upgrade to the SaaS production environments while investigating the issue.
The defect is related to a previous fix for a translation issue related to non-presenting HTML tags for help text fields and sections of layout builder. The defect does not impact any data on the record page in text area fields. The defect resulted in the following:
• Lost links to images in Text Boxes containing only an image and no text in the field. The images are still present in the Company Files folder, but they are no longer referenced properly.
• Lost HTML Style markup that appear within HTML tags
• Lost Application Builder links and other HTML that does not render on the Record page.
Archer has created a script to detect the changes this defect made on a system when it was upgraded to 6.13 or 6.13 Patch 1. The fix script only addresses changes, if no additional changes have been made to the text area.
SaaS and Hosted customers - No action is needed.
The Archer SaaS Operations team will perform this work for all SaaS and Hosted customers. Archer will issue a Service Advisory detailing when the work will be performed.
On-prem customers who installed Archer Platform 6.13 or 6.13 Patch 1 must run the Discovery script against a restored, pre-upgrade instance database, and then run the Update script against an upgraded database to regain the identified information.
IMPORTANT: Archer recommends you upgrade any systems running versions of 6.13 prior to 6.13 Patch 1 Hotfix 3 to this version or greater.
1. Download the zip file attached to this Technical Advisory.
2. Unzip the file.
The Discovery Script is named CE-120284DataRecoveryOnPrem.sql.
Run the Discovery Script provided in CE-120284DataRecovery.sql against a restored, pre-upgrade backup (an Archer instance database backup created prior to upgrading to Archer 6.13 or 6.13 Patch 1).
Note: The Discovery Script assumes that the instance database name is the same in the restored environment and in the “regular” (upgraded) environment.
1. Using SQL Server Management Studio (SSMS), execute the provided Discovery Script.
2. On the Results tab, review the generated Update statements. These statements outline the recommended fixes for this impacted environment.
3. Select all rows in the Results tab second panel “(No column name)” and save them as a SQL file to be run against the current, upgraded instance database.
Deploy Fixes (Execute Update Statements)
1. Using SQL Server Management Studio (SSMS), open the Results file generated in step 3 above.
2. Execute the collection of Update statements.
Note: If the database name in the target (post-upgrade) environment does not match the name from the source (pre-upgrade) environment, the statements will fail.
Packages generated within an environment upgraded to 6.13 or 6.13 Patch 1 could contain configurations which are missing affected data.
In this situation, Archer recommends you delete any packages generated prior to performing remediation steps above.
Re-generate the packages after performing remediation in the upstream environment and then re-deploy the new packages to the downstream environments.
IMPORTANT: If you have made additional changes in the downstream environments, those changes should be reflected into the upstream environments prior to regenerating packages.