After CPG to Patterns Migration Cloud Discovery still launches CAPI Orders, causing performance impact - Known Error

After CPG to Patterns Migration Cloud Discovery still launches CAPI Orders, causing performance impact Description Relevant Compatible Versions:

Family release: Tokyo and above Discovery and Service Mapping Patterns: March Summary of reason for Update Set:

After CPG to Patterns Migration Cloud Discovery still launches CAPI Orders, causing performance impact

This issue is in two Update Sets

3-Azure Discovery-CS5988126 - OOM Fix for Launching non-LP patterns 4-Azure Discovery-CS5988126 - OOM Fix for Launching non-LP patterns v2

PRB, DEF, or STRY (If Exists):

PRB1633842

Maintenance Steps (What to do when OOB Release):

Revert the files below:

sys_script_include_941dd5d5eba32200979aa5115206fe61 (In some situations this file may already be reverted)

sys_script_include_2feee4ba8725115077e0dcec3fbb358e sys_script_fd3d85401ba7d114e1366c46604bcba5

Target Release Data (If Known)

Washington DC

List of Files Affected:

sys_script_include_941dd5d5eba32200979aa5115206fe61

sys_script_include_2feee4ba8725115077e0dcec3fbb358e sys_script_fd3d85401ba7d114e1366c46604bcba5

Steps to Reproduce

> Migrate CPG to Patterns > Run AWS or Azure Cloud Discovery > Check sn_cmp_order, many entries are created

Workaround Apply both update sets attached, one is in CPG Scope and other in Global.

sys_remote_update_set_bceec739498f3950f87764ad5fdeab60.xml sys_remote_update_set_441f4ff5498f3950f87764ad5fdeabac.xml

Please note this workaround is a before query business rule on the sn_cmp_rb_resourceblock table that essentially forces the query to return 0 results when the query is coming from OrderServiceImpl.submitOrder. It checks the source of the query by forcing a stack track using “throw new Packages.java.lang.Throwable()”.

The code fix for this needs to be implemented in the Java layer in the fix release in PRB1633842.