Invalid Value on Update error being thrown on Agent Workspace when a UI Action is clickedIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Invalid Value on Update error being thrown on Agent Workspace when a UI Action is clicked Created a custom UI Action called that calls a subflow. When this is clicked on the UI16 platform there are no issues. When clicking this on Agent Workspace it will throw the Invalid value on Update error and it won't create the subflow Steps to reproduce:1. Go to Agent Workspace and click on All Cases and submit a case2. Click on the case just submitted and click the on the custom UI action3. The error should be seen: => Invalid Value on Update errorRelease<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Generic Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The UI action was created to the table _TABLE_A_ not to another table and also it has calls inside to that table: _TABLE_A_.On the platform (Where the UI does not have any issue), the URL used is under table _TABLE_A_ ===>>>> That UI action is under table _TABLE_A_ not under sctask/task tableOn workspace, when the direct record is called, it goes to the same table again _TABLE_A_ and that UI action works as the UI action is defined on that table (_TABLE_A_) and all the internal calls are based on that tableNow, when it is called from the parent record, the URL generated is under task table not under _TABLE_A_ table That's why the UI action is failing. The UI action was created to be used on table _TABLE_A_ not on sctask/task and internally on the code there are calls to point to table _TABLE_A_ as well. Now. 1. When going to the parent tab=> All of those subtabs are under the same parent tab which is related to table _TABLE_A_ and the UI action is under that table==>> Results: UI action works fine2. If you open the record directly from the list, that will open a big/parent tab related to table _TABLE_A_=> The details information is under same parent tab which is related to table _TABLE_A_ and the UI action is under that table==>> Results: UI action works fine3. Now, where the issue is:If you go first for the CSTASK record and then open the record the big/parent tab related is under task table=> All of those subtabs are under the parent tab CSTASK which is related to table task and not under _TABLE_A_. That's why if you trigger the UI from here, that will fail because the UI action was not created under that task table and under that table there are not the info used on _TABLE_A_.==>> Results: UI action failsResolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } There are three options 1. If the UI action is needed to be used from sctask/task - parent record, the UI action needs to be re-design to be sure all the calls provided on the UI action are also valid from scatsk/task and _TABLE_A_ tables2. You can create logic to not show the UI action when it is called from the parent record, only from _TABLE_A_3. You can create another UI action only for sctask/task table to do the same and hide the existing one when it is called from sctask/task record - parent record.