|
| 1 | +<?xml version="1.0" encoding="UTF-8"?><record_update table="scan_table_check"> |
| 2 | + <scan_table_check action="INSERT_OR_UPDATE"> |
| 3 | + <active>true</active> |
| 4 | + <advanced>true</advanced> |
| 5 | + <category>manageability</category> |
| 6 | + <conditions table="sys_update_set">state=in progress^ORstate=complete^EQ<item display_value="In progress" endquery="false" field="state" goto="false" newquery="false" operator="=" or="false" value="in progress"/> |
| 7 | + <item display_value="Complete" endquery="false" field="state" goto="false" newquery="false" operator="=" or="true" value="complete"/> |
| 8 | + <item endquery="true" field="" goto="false" newquery="false" operator="=" or="false" value=""/> |
| 9 | + </conditions> |
| 10 | + <description>Usually, developers mark an updatesets as Ignore if the work done is not required to be promoted or incorrect or irrelavent or due to any other reasons. |
| 11 | +However, at times, some of the developers may use the ignored set for any active work instead of creating new one by updating the state from Ignore to In-Progress. It is not a good practice to do the same. It may case the deployment issues and also makes the troubleshooting process cumbersome. |
| 12 | +It may also impact the deployment and cause issues in case if the state is changed to In-Progress/Completed for the potential ignored sets.</description> |
| 13 | + <documentation_url/> |
| 14 | + <finding_type>scan_finding</finding_type> |
| 15 | + <name>Update set In Progress/Completed previously Ignored</name> |
| 16 | + <priority>3</priority> |
| 17 | + <resolution_details>It is always good and recommended to create a new updateset instead of using already Ignored updatesets by changing the state from Ignore to In-Progress/Completed.</resolution_details> |
| 18 | + <run_condition/> |
| 19 | + <score_max>100</score_max> |
| 20 | + <score_min>0</score_min> |
| 21 | + <score_scale>1</score_scale> |
| 22 | + <script><![CDATA[(function (finding, current) { |
| 23 | +
|
| 24 | + var usSysId = current.getUniqueValue(); |
| 25 | + var audit = new GlideRecord('sys_audit'); |
| 26 | + audit.addEncodedQuery('fieldname=state^tablename=sys_update_set^oldvalue=ignore^newvalue=in progress^ORnewvalue=complete'); |
| 27 | + audit.addQuery('documentkey', usSysId); |
| 28 | + audit.setLimit(1); |
| 29 | + audit.query(); |
| 30 | + |
| 31 | + if(audit.hasNext()){ |
| 32 | + finding.increment(); |
| 33 | + } |
| 34 | +
|
| 35 | +})(finding, current);]]></script> |
| 36 | + <short_description>Already Ignored Update Set shouldn't be set back to In Pogress/Completed.</short_description> |
| 37 | + <sys_class_name>scan_table_check</sys_class_name> |
| 38 | + <sys_created_by>admin</sys_created_by> |
| 39 | + <sys_created_on>2024-10-30 19:28:34</sys_created_on> |
| 40 | + <sys_id>01c1c08ec3a19610afa6fc84e401310d</sys_id> |
| 41 | + <sys_mod_count>0</sys_mod_count> |
| 42 | + <sys_name>Update set In Progress/Completed previously Ignored</sys_name> |
| 43 | + <sys_package display_value="Example Instance Checks" source="x_appe_exa_checks">ca8467c41b9abc10ce0f62c3b24bcbaa</sys_package> |
| 44 | + <sys_policy/> |
| 45 | + <sys_scope display_value="Example Instance Checks">ca8467c41b9abc10ce0f62c3b24bcbaa</sys_scope> |
| 46 | + <sys_update_name>scan_table_check_01c1c08ec3a19610afa6fc84e401310d</sys_update_name> |
| 47 | + <sys_updated_by>admin</sys_updated_by> |
| 48 | + <sys_updated_on>2024-10-30 19:28:34</sys_updated_on> |
| 49 | + <table>sys_update_set</table> |
| 50 | + <use_manifest>false</use_manifest> |
| 51 | + </scan_table_check> |
| 52 | +</record_update> |
0 commit comments