<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Write on Embedded Variable in Workplace Case in Developer forum</title>
    <link>https://www.servicenow.com/community/developer-forum/write-on-embedded-variable-in-workplace-case/m-p/3515178#M1251514</link>
    <description>&lt;P&gt;Hi Will,&lt;/P&gt;&lt;P&gt;Yeah — this is one of those Workspace limitations that catches a lot of people.&lt;/P&gt;&lt;P&gt;What you’re seeing is expected: &lt;STRONG&gt;embedded variables (question_answer records) are rendered as read-only in Workspace&lt;/STRONG&gt;, even if:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;You update variable permissions&lt;/LI&gt;&lt;LI&gt;Use UI Policies&lt;/LI&gt;&lt;LI&gt;Try &lt;CODE&gt;g_form.setReadOnly()&lt;/CODE&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Those approaches only work in the &lt;STRONG&gt;classic UI&lt;/STRONG&gt;, not in Workspace.&lt;/P&gt;&lt;HR /&gt;&lt;H3&gt;Why this happens&lt;/H3&gt;&lt;P&gt;In Workspace, variables are not handled like normal form fields. They’re rendered through &lt;STRONG&gt;Now Experience components&lt;/STRONG&gt;, and:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;They don’t respect traditional UI Policies or client scripts&lt;/LI&gt;&lt;LI&gt;Read/write behavior is controlled differently (and mostly locked down OOTB)&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;&lt;H3&gt;What actually works&lt;/H3&gt;&lt;H4&gt;1. Use a real field on the table (recommended)&lt;/H4&gt;&lt;P&gt;If the agent needs to edit &lt;CODE&gt;meeting_date&lt;/CODE&gt;, the cleanest approach is:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Create a field on the Workplace Case table (e.g., &lt;CODE&gt;u_meeting_date&lt;/CODE&gt;)&lt;/LI&gt;&lt;LI&gt;Make it editable in Workspace&lt;/LI&gt;&lt;LI&gt;Sync it with the variable (optional via Business Rule)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;This is the most reliable and supported approach.&lt;/P&gt;&lt;HR /&gt;&lt;H4&gt;2. Sync variable ↔ field (if you must keep variable)&lt;/H4&gt;&lt;P&gt;You can:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;On load → copy variable value to the field&lt;/LI&gt;&lt;LI&gt;On update → write back to &lt;CODE&gt;question_answer&lt;/CODE&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Handled via Business Rules or Flow.&lt;/P&gt;&lt;HR /&gt;&lt;H4&gt;3. Custom component (advanced)&lt;/H4&gt;&lt;P&gt;Technically possible, but:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Requires Workspace / UI Builder customization&lt;/LI&gt;&lt;LI&gt;You’d need to override how variables are rendered&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Not recommended unless you’re already doing heavy UI customization.&lt;/P&gt;&lt;HR /&gt;&lt;H3&gt;What will NOT work&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;UI Policies (Workspace)&lt;/LI&gt;&lt;LI&gt;Client scripts (&lt;CODE&gt;g_form&lt;/CODE&gt;)&lt;/LI&gt;&lt;LI&gt;Variable write roles alone&lt;/LI&gt;&lt;LI&gt;ACL tweaks on &lt;CODE&gt;question_answer&lt;/CODE&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Thu, 26 Mar 2026 10:12:17 GMT</pubDate>
    <dc:creator>pr8172510</dc:creator>
    <dc:date>2026-03-26T10:12:17Z</dc:date>
    <item>
      <title>Write on Embedded Variable in Workplace Case</title>
      <link>https://www.servicenow.com/community/developer-forum/write-on-embedded-variable-in-workplace-case/m-p/3515166#M1251511</link>
      <description>&lt;P&gt;We have an ask where Workplace Agents are able to update an embedded variable on a submitted case within the Workplace Workspace.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The variable (meeting_date) is currently read-only, and needs to be able to be amended by the agent working on the case, and just this field.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2026-03-26 10_01_47-_terry6666@godaddy.com.txt - Notepad.png" style="width: 390px;"&gt;&lt;img src="https://www.servicenow.com/community/image/serverpage/image-id/507777iBDAD3C169A7F5DD0/image-dimensions/390x266?v=v2" width="390" height="266" role="button" title="2026-03-26 10_01_47-_terry6666@godaddy.com.txt - Notepad.png" alt="2026-03-26 10_01_47-_terry6666@godaddy.com.txt - Notepad.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;What I have tried so far:&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Added the roles ot the Write and Read roles on the Variable and Container records (Unsuccessful)&lt;/LI&gt;&lt;LI&gt;Created UI Policy to make variable writable (Works in classic UI, not Workspace)&lt;/LI&gt;&lt;LI&gt;g_form.setReadOnly() doesn't work on Workspaces, tried and works on the Classic, not Workspace&lt;/LI&gt;&lt;LI&gt;Checked ACLS on the Case table and the question_answer table. Even with correct roles, editing is not possible.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Is this just not possible, or is there something I am missing?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for any help provided.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Mar 2026 10:07:42 GMT</pubDate>
      <guid>https://www.servicenow.com/community/developer-forum/write-on-embedded-variable-in-workplace-case/m-p/3515166#M1251511</guid>
      <dc:creator>Will Wood</dc:creator>
      <dc:date>2026-03-26T10:07:42Z</dc:date>
    </item>
    <item>
      <title>Re: Write on Embedded Variable in Workplace Case</title>
      <link>https://www.servicenow.com/community/developer-forum/write-on-embedded-variable-in-workplace-case/m-p/3515178#M1251514</link>
      <description>&lt;P&gt;Hi Will,&lt;/P&gt;&lt;P&gt;Yeah — this is one of those Workspace limitations that catches a lot of people.&lt;/P&gt;&lt;P&gt;What you’re seeing is expected: &lt;STRONG&gt;embedded variables (question_answer records) are rendered as read-only in Workspace&lt;/STRONG&gt;, even if:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;You update variable permissions&lt;/LI&gt;&lt;LI&gt;Use UI Policies&lt;/LI&gt;&lt;LI&gt;Try &lt;CODE&gt;g_form.setReadOnly()&lt;/CODE&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Those approaches only work in the &lt;STRONG&gt;classic UI&lt;/STRONG&gt;, not in Workspace.&lt;/P&gt;&lt;HR /&gt;&lt;H3&gt;Why this happens&lt;/H3&gt;&lt;P&gt;In Workspace, variables are not handled like normal form fields. They’re rendered through &lt;STRONG&gt;Now Experience components&lt;/STRONG&gt;, and:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;They don’t respect traditional UI Policies or client scripts&lt;/LI&gt;&lt;LI&gt;Read/write behavior is controlled differently (and mostly locked down OOTB)&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;&lt;H3&gt;What actually works&lt;/H3&gt;&lt;H4&gt;1. Use a real field on the table (recommended)&lt;/H4&gt;&lt;P&gt;If the agent needs to edit &lt;CODE&gt;meeting_date&lt;/CODE&gt;, the cleanest approach is:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Create a field on the Workplace Case table (e.g., &lt;CODE&gt;u_meeting_date&lt;/CODE&gt;)&lt;/LI&gt;&lt;LI&gt;Make it editable in Workspace&lt;/LI&gt;&lt;LI&gt;Sync it with the variable (optional via Business Rule)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;This is the most reliable and supported approach.&lt;/P&gt;&lt;HR /&gt;&lt;H4&gt;2. Sync variable ↔ field (if you must keep variable)&lt;/H4&gt;&lt;P&gt;You can:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;On load → copy variable value to the field&lt;/LI&gt;&lt;LI&gt;On update → write back to &lt;CODE&gt;question_answer&lt;/CODE&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Handled via Business Rules or Flow.&lt;/P&gt;&lt;HR /&gt;&lt;H4&gt;3. Custom component (advanced)&lt;/H4&gt;&lt;P&gt;Technically possible, but:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Requires Workspace / UI Builder customization&lt;/LI&gt;&lt;LI&gt;You’d need to override how variables are rendered&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Not recommended unless you’re already doing heavy UI customization.&lt;/P&gt;&lt;HR /&gt;&lt;H3&gt;What will NOT work&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;UI Policies (Workspace)&lt;/LI&gt;&lt;LI&gt;Client scripts (&lt;CODE&gt;g_form&lt;/CODE&gt;)&lt;/LI&gt;&lt;LI&gt;Variable write roles alone&lt;/LI&gt;&lt;LI&gt;ACL tweaks on &lt;CODE&gt;question_answer&lt;/CODE&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Thu, 26 Mar 2026 10:12:17 GMT</pubDate>
      <guid>https://www.servicenow.com/community/developer-forum/write-on-embedded-variable-in-workplace-case/m-p/3515178#M1251514</guid>
      <dc:creator>pr8172510</dc:creator>
      <dc:date>2026-03-26T10:12:17Z</dc:date>
    </item>
    <item>
      <title>Re: Write on Embedded Variable in Workplace Case</title>
      <link>https://www.servicenow.com/community/developer-forum/write-on-embedded-variable-in-workplace-case/m-p/3515179#M1251515</link>
      <description>&lt;P&gt;&lt;a href="https://www.servicenow.com/community/user/viewprofilepage/user-id/12958"&gt;@Will Wood&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;is it editable by admin?&lt;/P&gt;</description>
      <pubDate>Thu, 26 Mar 2026 10:12:33 GMT</pubDate>
      <guid>https://www.servicenow.com/community/developer-forum/write-on-embedded-variable-in-workplace-case/m-p/3515179#M1251515</guid>
      <dc:creator>Ankur Bawiskar</dc:creator>
      <dc:date>2026-03-26T10:12:33Z</dc:date>
    </item>
    <item>
      <title>Re: Write on Embedded Variable in Workplace Case</title>
      <link>https://www.servicenow.com/community/developer-forum/write-on-embedded-variable-in-workplace-case/m-p/3515180#M1251516</link>
      <description>&lt;P&gt;Nope!&lt;/P&gt;</description>
      <pubDate>Thu, 26 Mar 2026 10:13:57 GMT</pubDate>
      <guid>https://www.servicenow.com/community/developer-forum/write-on-embedded-variable-in-workplace-case/m-p/3515180#M1251516</guid>
      <dc:creator>Will Wood</dc:creator>
      <dc:date>2026-03-26T10:13:57Z</dc:date>
    </item>
  </channel>
</rss>

