# Workaround created for properties.xsl issue

- Reference: PBI 344134
- Compliance Impacts: This defect is not a compliance or regulatory issue.
- Documentation: No document impact.

## Issue

An issue was identified in our hosted solution that caused an incorrect properties.xsl to be used; this resulted in erratic formatting issues in the documents. After further investigation, the following files were also identified as potentially having the issue:

- WKFS_StyleGuide.xsl
- FontScaling.xsl
- table.xsl

## Solution

A temporary solution has been implemented to use a unique name for these files.

Utilize the UpdatePropertiesStylesheet utility to change the .xsl files to have their own unique identifier. See "How and when to run the UpdatePropertiesStylesheetUtility.docx" for detailed information.

After running the UpdatePropertiesStylesheet utility on the Document Generation Services Management Tool, the following files and their references within the files are updated accordingly:

Original .xls file | Example of updated .xsl file name
--- | ---
WKFS_StyleGuide.xsl | WKFS_StyleGuide635780724639423381.xsl
Properties.xsl | properties635780724639423381.xsl
FontScaling.xsl | fontScaling635780724639423381.xsl
table.xsl | table635780724639423381.xsl

## Implementation Notes

Users can access these files at https://connect.wolterskluwer.com/sites/dept-pmoportal/BankingInvestmentProducts/expereie/Lists/General%20Discussion/Subject.aspx.

Note the following:

- If deploying content from sprint 27 or before, you must run the utility on the content after it has been deployed to the Document Generation Services environment before using the content.
- Submit a SN ticket to ASM and include the "How and when to run the UpdatePropertiesStylesheetUtility.docx" document and the zip file stating you need the UpdatePropertiesStylesheet utility ran for a specific environment.
- If you need to deploy more than one library, deploy all libraries before submitting one ASM ticket.
- Running the utility will cover all libraries that have been deployed to that environment.
- After deploying content, do not use/ping/test the library for any reason until after ASM runs the utility; we will be at risk for this error to occur again.
- You can run this utility any time after the library has been deployed.
- There are no dependencies on aliases or permissions being completed prior to running the utility.