#1037: refresh "priority" when either "impact" or "urgency" changes.

git-svn-id: http://svn.code.sf.net/p/itop/code/trunk@3463 a333f486-631f-4898-b8df-5754b55c2be0

datamodels/2.x/itop-incident-mgmt-itil/datamodel.itop-incident-mgmt-itil.xml

@@ -81,6 +81,10 @@
             <value id="3">3</value>
             <value id="4">4</value>
           </values>
+          <dependencies>
+            <attribute id="impact"/>
+            <attribute id="urgency"/>
+          </dependencies>
           <sql>priority</sql>
           <default_value>4</default_value>
           <is_null_allowed>false</is_null_allowed>

datamodels/2.x/itop-request-mgmt-itil/datamodel.itop-request-mgmt-itil.xml

@@ -92,6 +92,10 @@
             <value id="3">3</value>
             <value id="4">4</value>
           </values>
+          <dependencies>
+            <attribute id="impact"/>
+            <attribute id="urgency"/>
+          </dependencies>
           <sql>priority</sql>
           <default_value>4</default_value>
           <is_null_allowed>false</is_null_allowed>

datamodels/2.x/itop-request-mgmt/datamodel.itop-request-mgmt.xml

@@ -92,6 +92,10 @@
             <value id="3">3</value>
             <value id="4">4</value>
           </values>
+          <dependencies>
+            <attribute id="impact"/>
+            <attribute id="urgency"/>
+          </dependencies>
           <sql>priority</sql>
           <default_value>4</default_value>
           <is_null_allowed>false</is_null_allowed>