<?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>topic Feature Request: Preference Option to Restrict Zones/Objects to Only Existing When Building Policies in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/feature-request-preference-option-to-restrict-zones-objects-to/m-p/247977#M70548</link>
    <description>&lt;P&gt;The current PAN-OS GUI makes adding objects and zones on the fly very easy while building policies.&lt;/P&gt;&lt;P&gt;Unfortunately this sometimes casues unwanted side effects:&lt;/P&gt;&lt;P&gt;As an example, when building a security policy including the zone "Admin" I started typing "admin" in the zone add field as a search and pressed enter. Instead of choosing the already-built "Admin" zone, this caused a new zone "admin" to be created with no associated type, interfaces, etc., which obviously caused commit errors.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The on-the-fly addition is handy in some cases, but I would like to be able to toggle this function on and off. Once the majority of the objects and zones are built I would prefer the GUI to only pick existing objects from the drop-down unless I explicitly click the "+" add button.&lt;/P&gt;</description>
    <pubDate>Tue, 29 Jan 2019 15:04:11 GMT</pubDate>
    <dc:creator>bgolub</dc:creator>
    <dc:date>2019-01-29T15:04:11Z</dc:date>
    <item>
      <title>Feature Request: Preference Option to Restrict Zones/Objects to Only Existing When Building Policies</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/feature-request-preference-option-to-restrict-zones-objects-to/m-p/247977#M70548</link>
      <description>&lt;P&gt;The current PAN-OS GUI makes adding objects and zones on the fly very easy while building policies.&lt;/P&gt;&lt;P&gt;Unfortunately this sometimes casues unwanted side effects:&lt;/P&gt;&lt;P&gt;As an example, when building a security policy including the zone "Admin" I started typing "admin" in the zone add field as a search and pressed enter. Instead of choosing the already-built "Admin" zone, this caused a new zone "admin" to be created with no associated type, interfaces, etc., which obviously caused commit errors.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The on-the-fly addition is handy in some cases, but I would like to be able to toggle this function on and off. Once the majority of the objects and zones are built I would prefer the GUI to only pick existing objects from the drop-down unless I explicitly click the "+" add button.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jan 2019 15:04:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/feature-request-preference-option-to-restrict-zones-objects-to/m-p/247977#M70548</guid>
      <dc:creator>bgolub</dc:creator>
      <dc:date>2019-01-29T15:04:11Z</dc:date>
    </item>
    <item>
      <title>Re: Feature Request: Preference Option to Restrict Zones/Objects to Only Existing When Building Poli</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/feature-request-preference-option-to-restrict-zones-objects-to/m-p/247985#M70549</link>
      <description>&lt;P&gt;An FYI...while it's great you posted this FRs don't get tracked via the community or accepted from posting in the community.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That said there's a thread on submitted FRs.&amp;nbsp; If you search for "feature request" I'm sure you'll find it.&amp;nbsp; To officially have your FR accepted you need to talk to your SE.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jan 2019 15:12:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/feature-request-preference-option-to-restrict-zones-objects-to/m-p/247985#M70549</guid>
      <dc:creator>Brandon_Wertz</dc:creator>
      <dc:date>2019-01-29T15:12:34Z</dc:date>
    </item>
  </channel>
</rss>

