Below are the issues to be aware of in Service Portal after Rome upgrade:
- After upgrading to Rome, whenever a category is selected in the Service Portal, the list of catalog items displayed is not updated, despite the URL being updated to the sys_id of the catalog.
Refer Article for cause & solution: Service Portal: Changing categories does not update category items displayed after Rome upgrade
- Catalog UI Policies not working in Service Portal after Rome upgrade, when the variable internal name is not matching the one in the Catalog UI policy action.
Refer Article for cause & solution: [Rome] Catalog UI Policies not working in Service Portal
- Service Portal: Catalog UI Policy conditions doesn't work if the condition contains question choice that has a value with more than 5 characters in 'UPPER CASE' in condition builder
Refer Article for cause & workaround: Catalog UI Policy conditions doesn't work if the condition contains question choice that has a value...
- After Rome Upgrade, Many forms doesn't have variables visible on the portal
Cause & Solution: Check the Catalog UI Policies for corrupted conditions
Valid format: <catalog_conditions>IO:8bd5114413e8e600c2783d27d144b00f=205b848113bcea044de43598d144b03c^EQ</catalog_conditions>
InValid formats: (contains OR123TEXTQUERY321 or does not have IO:<sys_id> for variable name)
<catalog_conditions>catalog_item=205b848113bcea044de43598d144b03c^EQ</catalog_conditions><catalog_conditions>IO:b9f927a90f1d0200ea6c8fcce1050e6a=true^OR123TEXTQUERY321=true^ORIO:09f927a90f1d0200ea6c8fcce1050e53=true^EQ</catalog_conditions>
The corrupted format seemed to be working without any issues until Quebec version, but due to the enhancements and fixing many other bugs in Rome, this points out this corruption and breaks form, expecting the catalog ui policies to be corrected. After in-depth analysis, evaluation logic in Rome has been changed slightly to offer better performance. In that process, there is some internal casting that happens on the UI policy automatically and system expects the right version/format of the catalog ui policies going further starting Rome.
To resolve the issue, please correct the catalog condition in the UI Policies by
De-activating and activating affected Catalog UI Policies.
[OR]
Just saving the affected Catalog UI Policies.
