|
| 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>false</advanced> |
| 5 | + <category>performance</category> |
| 6 | + <conditions table="sys_transform_map">run_business_rules!=true^EQ<item endquery="false" field="run_business_rules" goto="false" newquery="false" operator="!=" or="false" value="true"/> |
| 7 | + <item endquery="true" field="" goto="false" newquery="false" operator="=" or="false" value=""/> |
| 8 | + </conditions> |
| 9 | + <description>Business rules validation directly on fields in Transform Maps is generally not considered a best practice, and instead, it is recommended to leverage other methods like Field Map Scripts or onBefore Transform Scripts for handling field-level data manipulation. |
| 10 | +Transform Maps usually deal with bulk data imports. Using business rules (which fire on each insert/update) during a data import can negatively impact performance, as business rules execute for every individual record transformation, which can slow down processing.</description> |
| 11 | + <documentation_url/> |
| 12 | + <finding_type>scan_finding</finding_type> |
| 13 | + <name>Transform Map Run Business Rule</name> |
| 14 | + <priority>3</priority> |
| 15 | + <resolution_details>Disable “Run Business Rules” |
| 16 | + |
| 17 | +Unless needed, the “Run Business Rules” checkbox should be unchecked as Post import additional business logic may leads to run via existing business rules, but this can increase |
| 18 | +import/processing times. |
| 19 | + |
| 20 | +Disabling this option will will stop the execution of the following and prevent the potential performance issue |
| 21 | +– Business Rules |
| 22 | +– Script engines (Approval Engine, Assignment rule Engine, Data policy Engine Field normalization Engine (CMDB), Role Engine, Execution Plan Engine, Workflow Engine, text Indexing Engine, Update Sync Engine(Update Set), Data Lookup Engine, Email notification) |
| 23 | +– Auditing</resolution_details> |
| 24 | + <run_condition/> |
| 25 | + <score_max>100</score_max> |
| 26 | + <score_min>0</score_min> |
| 27 | + <score_scale>1</score_scale> |
| 28 | + <script><![CDATA[(function (engine) { |
| 29 | +
|
| 30 | + // Add your code here |
| 31 | +
|
| 32 | +})(engine);]]></script> |
| 33 | + <short_description>Disable 'Run Business Rule' on Transform Map[sys_transform_map]</short_description> |
| 34 | + <sys_class_name>scan_table_check</sys_class_name> |
| 35 | + <sys_created_by>a.pandey</sys_created_by> |
| 36 | + <sys_created_on>2024-10-03 08:17:34</sys_created_on> |
| 37 | + <sys_id>f9f026c983cd92100283b955eeaad323</sys_id> |
| 38 | + <sys_mod_count>0</sys_mod_count> |
| 39 | + <sys_name>Transform Map Run Business Rule</sys_name> |
| 40 | + <sys_package display_value="Example Instance Checks" source="x_appe_exa_checks">ca8467c41b9abc10ce0f62c3b24bcbaa</sys_package> |
| 41 | + <sys_policy/> |
| 42 | + <sys_scope display_value="Example Instance Checks">ca8467c41b9abc10ce0f62c3b24bcbaa</sys_scope> |
| 43 | + <sys_update_name>scan_table_check_f9f026c983cd92100283b955eeaad323</sys_update_name> |
| 44 | + <sys_updated_by>a.pandey</sys_updated_by> |
| 45 | + <sys_updated_on>2024-10-03 08:17:34</sys_updated_on> |
| 46 | + <table>sys_transform_map</table> |
| 47 | + <use_manifest>false</use_manifest> |
| 48 | + </scan_table_check> |
| 49 | + <sys_translated_text action="delete_multiple" query="documentkey=f9f026c983cd92100283b955eeaad323"/> |
| 50 | +</record_update> |
0 commit comments