<?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>post Required field on catalog task submission in ITSM articles</title>
    <link>https://www.servicenow.com/community/itsm-articles/required-field-on-catalog-task-submission/ta-p/2313618</link>
    <description>&lt;P&gt;I have read numerous posts about making variables visible and even required on Catalog Tasks, but not on Requested Items.&lt;BR /&gt;Based on various answers and potential solutions I have designed two options that we use&lt;/P&gt;
&lt;H4&gt;Option 1 - create variable on RITM level&lt;/H4&gt;
&lt;P&gt;First step is to create a variable on RITM level and define its visibility using UI Policy&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="find_real_file.png"&gt;&lt;img src="https://www.servicenow.com/community/image/serverpage/image-id/135325iE9E937ACA98AECAD/image-size/large?v=v2&amp;amp;px=999" role="button" title="find_real_file.png" alt="find_real_file.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Next, a client script (onSubmit) has been applied on a catalog task. One of the conditions is catalog task short description (not best practice, probably task sys_id could be used). By using short description field in script conditions, we can apply this rule to any task regardless on its order in a workflow; i.e., Task 2 instead on Task 1.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="find_real_file.png"&gt;&lt;img src="https://www.servicenow.com/community/image/serverpage/image-id/135345i5C7D38B11A3DB4C2/image-size/large?v=v2&amp;amp;px=999" role="button" title="find_real_file.png" alt="find_real_file.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Finally, in the workflow we added this variable to selected variables on catalog task where we want to make this variable visible.&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;Option 2 - create variable on Catalog task level&lt;/H4&gt;
&lt;P&gt;This approach creates variable on the workflow and it is visible on the RITM form if there is no defined any UI Policy.&lt;BR /&gt;First step is to go to workflow/edit workflow variables and add a new variable. Create new variable and add it to catalog task, or preferred catalog task if there are more than one.&amp;nbsp;&lt;BR /&gt;In this approach onSubmit script is created on catalog task level (can be created from any catalog task).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="find_real_file.png"&gt;&lt;img src="https://www.servicenow.com/community/image/serverpage/image-id/135335i133B63E5AD737148/image-size/large?v=v2&amp;amp;px=999" role="button" title="find_real_file.png" alt="find_real_file.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 04 May 2018 15:37:40 GMT</pubDate>
    <dc:creator>Vladi1</dc:creator>
    <dc:date>2018-05-04T15:37:40Z</dc:date>
    <item>
      <title>Required field on catalog task submission</title>
      <link>https://www.servicenow.com/community/itsm-articles/required-field-on-catalog-task-submission/ta-p/2313618</link>
      <description>&lt;P&gt;I have read numerous posts about making variables visible and even required on Catalog Tasks, but not on Requested Items.&lt;BR /&gt;Based on various answers and potential solutions I have designed two options that we use&lt;/P&gt;
&lt;H4&gt;Option 1 - create variable on RITM level&lt;/H4&gt;
&lt;P&gt;First step is to create a variable on RITM level and define its visibility using UI Policy&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="find_real_file.png"&gt;&lt;img src="https://www.servicenow.com/community/image/serverpage/image-id/135325iE9E937ACA98AECAD/image-size/large?v=v2&amp;amp;px=999" role="button" title="find_real_file.png" alt="find_real_file.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Next, a client script (onSubmit) has been applied on a catalog task. One of the conditions is catalog task short description (not best practice, probably task sys_id could be used). By using short description field in script conditions, we can apply this rule to any task regardless on its order in a workflow; i.e., Task 2 instead on Task 1.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="find_real_file.png"&gt;&lt;img src="https://www.servicenow.com/community/image/serverpage/image-id/135345i5C7D38B11A3DB4C2/image-size/large?v=v2&amp;amp;px=999" role="button" title="find_real_file.png" alt="find_real_file.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Finally, in the workflow we added this variable to selected variables on catalog task where we want to make this variable visible.&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;Option 2 - create variable on Catalog task level&lt;/H4&gt;
&lt;P&gt;This approach creates variable on the workflow and it is visible on the RITM form if there is no defined any UI Policy.&lt;BR /&gt;First step is to go to workflow/edit workflow variables and add a new variable. Create new variable and add it to catalog task, or preferred catalog task if there are more than one.&amp;nbsp;&lt;BR /&gt;In this approach onSubmit script is created on catalog task level (can be created from any catalog task).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="find_real_file.png"&gt;&lt;img src="https://www.servicenow.com/community/image/serverpage/image-id/135335i133B63E5AD737148/image-size/large?v=v2&amp;amp;px=999" role="button" title="find_real_file.png" alt="find_real_file.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 04 May 2018 15:37:40 GMT</pubDate>
      <guid>https://www.servicenow.com/community/itsm-articles/required-field-on-catalog-task-submission/ta-p/2313618</guid>
      <dc:creator>Vladi1</dc:creator>
      <dc:date>2018-05-04T15:37:40Z</dc:date>
    </item>
  </channel>
</rss>

