If your solution depends on using checksums for validating DeficiencyPop URLs, as of OnBase 18, you are required to configure a unique checksum key value, which is used to create the checksum value added to the URL.
If your solution did not previously use a unique string value to create checksum values, you must take the following actions in order for any previously created DeficiencyPop URLs to validate:
-
In the DeficiencyPop web.config file:
-
Within the Hyland.Web.HealthcarePop element, enter a unique checksum key value in the checksum setting for DeficiencyPop.
-
Set the EnableLegacyChecksumFallback setting to true.
-
Setting the EnableLegacyChecksumFallback setting to true should be considered a temporary method of validating legacy checksums until you can recreate and replace the Pop integration URLs using the unique string value as the checksum key.
If your solution was already using a unique string value to create checksum values, any DeficiencyPop URLs that were previously created will continue to validate with no additional action needed.