Created a new instance scan check (Table Check) & Updated the README.…

…md document. (#180)

* Created a new instance scan checks (Table Check).

* Update README.md

---------

Co-authored-by: Astrid Sapphire <59789839+SapphicFire@users.noreply.github.com>

README.md

@@ -179,6 +179,11 @@ Tickets from tables such as Incident, Change Request, Problem, and other task-re
 ### Check Inactive Business Rules over 90 days
 Inactive Business Rules which are not updated for more than 90 days and not created by glide.maint and not updated by admin should be identified to remove unnecessary overhead.
 
+### Update set In Progress/Completed previously Ignored
+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. 
+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.
+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.
+
 ## Category: Upgradability
 
 ### Call GlideRecord using new

ca8467c41b9abc10ce0f62c3b24bcbaa/checksum.txt

@@ -1 +1 @@
-g3fOXFKd_SJhY9hj5S6s3duX-d8QXo-aSq9DmLRSggO5QMR75a3S7veyxd7UW-55ROSZ3KZjkORvxDYC4eAoUw8hM5sBWzpif0rXl-I8pW_VUCIh6epUd3BCmn83iXPR1-OT_yZ9dFtlQN97LDs2GL0KQjct68x8NHekh9tYbFUjuQUBI_KuJJ0K9Vb1BgVtLHwuTloIyflunbMQLgcrSSCxSC_INduOiWNzlFF2AFYjlcv8I4JjPpaFDCHCcaPGYHUmAVfsjTiBx3owim2ZBkmIBrQmCDl3m8sqmnfrGXsU-FDAXaMghtw5gFVdQt1vsqnZmW16o7TGnwo6I7w4q8h37ATVhuwgCA_rUAI6ckPtO9uBWYLC7AJX3X2P2emhszEC2sQwmy17Ul9guViUL4LIA4LpeuG6virKuq8nUJne6mrzciepOadDXUVYriNwLjTWy9qlIhIgpaD1wv0MckKAJ1vx_io6bROOgr3xgI3p717PF6RYfnUoS57_l5IuKfCVaFNHDA0VO0x8o9_B0aq3HHJksOnbeLFNSEdIm5_dK32KOcxzWKa5NYIqDimQqQvAvTnhqucdsENG6K8G3Olw1auQYgIu5J3s0RHxY52Nn3Zx7wCFFJXSLpKeU6T-E3M9JHF_nAa3s-FUWwuvCZL_38uyxhcKSBCFDOsN_Rg
+uEH-MVj5358yRx1qNhQZQDDN5DRl_EHSvw3CQ3-uqkJ_UjcZdANraoCdU5KL_mwp7x_66jQSj054ighy53LegM7d6xp8_kOx-SoZTIBBtdf3RE1OwevZASv1Xl2dR1lp0CM5i8lVq4rGQFmN2RkUv1xgprPYKTBCZ4CamesJX89wF4nSGzRdUqPHkH_e73S8Jgwmmm4BxHZ0ow4yyQ3QJbAu90kHsbyehFpjxnzDPjiml_OPVkwylOkpqn4QviJ4UAcgb-00eYvr7RSYX2blyPTisybSLuK2ty0jsylJC8xzt5ZuO5ronXCrqPIwN2P9yXqU-nP3xnCZJJXnSGV2xUU-5OkcoMrfEht5HOM39kIOxzzJvGAOXs6wGA7OqEDdoZHQeZL3eR9m6lq_nHMCHPYjl8nFUedj10VV3oF6YETA4MX0MGNrybGVxIFfibgbqAzLnwiUnfKRtdvF3kRpcIBn8WGEiiSSzDDXovB4gY1b8Fhkk8SNhAM8a9518wFfJRbCWj4kwIJRbbKOKmOf1PY31VjHy8tQ0FH8xALm4sbGHfDTgGdo-Cjy3Velkrr3nqFJJOpdpqB1-I4_fXl8clJPYUou8CdxBhc9bhuZbkJvggMU-8Ne18HimH3K9cn2OLyRe7gRi8-nfG8c-pzvY_gW6iYdD3Yvdfqtirxs6gw

ca8467c41b9abc10ce0f62c3b24bcbaa/update/scan_table_check_01c1c08ec3a19610afa6fc84e401310d.xml

@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="UTF-8"?><record_update table="scan_table_check">
+    <scan_table_check action="INSERT_OR_UPDATE">
+        <active>true</active>
+        <advanced>true</advanced>
+        <category>manageability</category>
+        <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"/>
+            <item display_value="Complete" endquery="false" field="state" goto="false" newquery="false" operator="=" or="true" value="complete"/>
+            <item endquery="true" field="" goto="false" newquery="false" operator="=" or="false" value=""/>
+        </conditions>
+        <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. 
+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.
+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>
+        <documentation_url/>
+        <finding_type>scan_finding</finding_type>
+        <name>Update set In Progress/Completed previously Ignored</name>
+        <priority>3</priority>
+        <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>
+        <run_condition/>
+        <score_max>100</score_max>
+        <score_min>0</score_min>
+        <score_scale>1</score_scale>
+        <script><![CDATA[(function (finding, current) {
+
+	var usSysId = current.getUniqueValue();
+	var audit = new GlideRecord('sys_audit');
+	audit.addEncodedQuery('fieldname=state^tablename=sys_update_set^oldvalue=ignore^newvalue=in progress^ORnewvalue=complete');
+	audit.addQuery('documentkey', usSysId);
+	audit.setLimit(1);
+	audit.query();
+	
+	if(audit.hasNext()){
+		finding.increment();
+	}
+
+})(finding, current);]]></script>
+        <short_description>Already Ignored  Update Set shouldn't be set back to In Pogress/Completed.</short_description>
+        <sys_class_name>scan_table_check</sys_class_name>
+        <sys_created_by>admin</sys_created_by>
+        <sys_created_on>2024-10-30 19:28:34</sys_created_on>
+        <sys_id>01c1c08ec3a19610afa6fc84e401310d</sys_id>
+        <sys_mod_count>0</sys_mod_count>
+        <sys_name>Update set In Progress/Completed previously Ignored</sys_name>
+        <sys_package display_value="Example Instance Checks" source="x_appe_exa_checks">ca8467c41b9abc10ce0f62c3b24bcbaa</sys_package>
+        <sys_policy/>
+        <sys_scope display_value="Example Instance Checks">ca8467c41b9abc10ce0f62c3b24bcbaa</sys_scope>
+        <sys_update_name>scan_table_check_01c1c08ec3a19610afa6fc84e401310d</sys_update_name>
+        <sys_updated_by>admin</sys_updated_by>
+        <sys_updated_on>2024-10-30 19:28:34</sys_updated_on>
+        <table>sys_update_set</table>
+        <use_manifest>false</use_manifest>
+    </scan_table_check>
+</record_update>