Adding a reliant entity using plugin Compliance Workspace Compliance Workspace version 19.1.1 ERROR

szabb27
Tera Contributor

Will summarize the issue we've encountered with adding a reliant entity on Compliance Workspace.

The problem appeared following the installation of a plugin update to Compliance Workspace version 19.1.1.

This update has not impacted the configuration of the workspace and the button itself but a subsequent table within a critical component called "client action."

 

For context, we have a button labeled "Add from existing control." As you can see in the configuration, we're using a client action that defines all aspects of our pop-up window. This client action is designed for a related list, which is correct given the button's use within a related list.

szabb27_0-1733233812626.png

 

szabb27_1-1733233812631.png

 

 

However, upon closer inspection of the related list configuration, we've noticed a change from the older version of Compliance Workspace 19.0.1.

Previously, we could see  the application scope on the form. This leads to believe that something has changed in the latest release. Examining the table configuration for the related list reveals that this table is now missing several columns. I've included images for comparison:

szabb27_2-1733233812640.png

 

szabb27_3-1733233812650.png

Since no coding changes have been made in the Compliance Workspace to the button configuration, it appears that the button's functionality is affected by the change in the columns available in teh above highlighetd table 

4 REPLIES 4

Connor Levien
ServiceNow Employee
ServiceNow Employee

@szabb27 I have checked in on of my instances that has the 19.1.1 version installed and can confirm the fields are there, so it doesnt look the issue is related to the version. I suspect potentially someone in your instance has deleted the field potentially, I would suggest to raise a support ticket to get some support with this one

szabb27
Tera Contributor

Feedback much appreciated Connor!

Raised a support ticket in which i provided my feedback with the ServiceNow HI team around 3 weeks ago and your response is the first helpful information (FYI. the HI Case number CS7770173) 

Connor Levien
ServiceNow Employee
ServiceNow Employee

@szabb27 I will try to get the case moving from my side but would also suggest reaching out to you account team to get support as they can get visibility of the case

szabb27
Tera Contributor

Would be highly appreciated!