<?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 How to find and propose a workaround for the restriction where &amp;quot;Open by&amp;quot; and &amp;quot;Open for&amp;quot; ER HRSD in HRSD forum</title>
    <link>https://www.servicenow.com/community/hrsd-forum/how-to-find-and-propose-a-workaround-for-the-restriction-where/m-p/3228122#M40913</link>
    <description>&lt;P class="" data-start="103" data-end="233"&gt;&lt;STRONG data-start="103" data-end="231"&gt;How to find and propose a workaround for the restriction where "Open by" and "Open for" cannot be the same in the ER module?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P class="" data-start="235" data-end="609"&gt;In the ER module, the system does not allow the "Open by" and "Open for" fields to have the same value. This restriction creates challenges for us where the ER team often needs to bulk raise cases and track them throughout their lifecycle without adding the end user. Has anyone found a workaround or best practice to handle this scenario?&lt;/P&gt;
&lt;H3 class="" data-start="611" data-end="633"&gt;&amp;nbsp;&lt;/H3&gt;
&lt;P class="" data-start="704" data-end="1171"&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 04 Apr 2025 11:12:38 GMT</pubDate>
    <dc:creator>Victor Val Mas</dc:creator>
    <dc:date>2025-04-04T11:12:38Z</dc:date>
    <item>
      <title>How to find and propose a workaround for the restriction where "Open by" and "Open for" ER HRSD</title>
      <link>https://www.servicenow.com/community/hrsd-forum/how-to-find-and-propose-a-workaround-for-the-restriction-where/m-p/3228122#M40913</link>
      <description>&lt;P class="" data-start="103" data-end="233"&gt;&lt;STRONG data-start="103" data-end="231"&gt;How to find and propose a workaround for the restriction where "Open by" and "Open for" cannot be the same in the ER module?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P class="" data-start="235" data-end="609"&gt;In the ER module, the system does not allow the "Open by" and "Open for" fields to have the same value. This restriction creates challenges for us where the ER team often needs to bulk raise cases and track them throughout their lifecycle without adding the end user. Has anyone found a workaround or best practice to handle this scenario?&lt;/P&gt;
&lt;H3 class="" data-start="611" data-end="633"&gt;&amp;nbsp;&lt;/H3&gt;
&lt;P class="" data-start="704" data-end="1171"&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Apr 2025 11:12:38 GMT</pubDate>
      <guid>https://www.servicenow.com/community/hrsd-forum/how-to-find-and-propose-a-workaround-for-the-restriction-where/m-p/3228122#M40913</guid>
      <dc:creator>Victor Val Mas</dc:creator>
      <dc:date>2025-04-04T11:12:38Z</dc:date>
    </item>
    <item>
      <title>Re: How to find and propose a workaround for the restriction where "Open by" and "Ope</title>
      <link>https://www.servicenow.com/community/hrsd-forum/how-to-find-and-propose-a-workaround-for-the-restriction-where/m-p/3228135#M40914</link>
      <description>&lt;P&gt;&lt;a href="https://www.servicenow.com/community/user/viewprofilepage/user-id/1478"&gt;@Victor Val Mas&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;how is that restriction applied? did you check that script etc?&lt;/P&gt;
&lt;P&gt;If my response helped please mark it correct and close the thread so that it benefits future readers.&lt;/P&gt;</description>
      <pubDate>Fri, 04 Apr 2025 11:27:39 GMT</pubDate>
      <guid>https://www.servicenow.com/community/hrsd-forum/how-to-find-and-propose-a-workaround-for-the-restriction-where/m-p/3228135#M40914</guid>
      <dc:creator>Ankur Bawiskar</dc:creator>
      <dc:date>2025-04-04T11:27:39Z</dc:date>
    </item>
  </channel>
</rss>

