Pattern "Azure Application Gateway TD (LBS)" is failing to retrieve Azure Application gateways during Top-Down discovery - Known Error

Pattern "Azure Application Gateway TD (LBS)" is failing to retrieve Azure Application gateways during Top-Down discovery Description Pattern "Azure Application Gateway TD (LBS)" in identification section: "Azure Application Gateway TD (LBS)" is able to get Azure application gateways, but is failing to process the received result in pattern step "14. Parse Application Gateway services attributes" Output of operation is not containing expected list of retrieved application gateways, instead, it is an empty variable. Due this pattern is not able to identify azure application gateways during Top-Down discovery.

Steps to Reproduce

- Open pattern "Azure Application Gateway TD (LBS)" and "Application Gateway service identification" identification https://instance.service-now.com/sa_pattern_list.do?sysparm_query=nameSTARTSWITHAVI%20Load%20Balancer%20VIP&sysparm_view=

- Pattern "Azure Application Gateway TD (LBS)" in identification section: "Azure Application Gateway TD (LBS)" is able to get Azure application gateways, but is failing to process the received result in pattern step "14. Parse Application Gateway services attributes"

Workaround - PFA update set which needs to be imported into the instance

- Here is the summary of changes made in the update-set : The response from this method was in the form of array result = cloudcall.arrayListExecute(${service_account}, null, api_url, null, 'GET', null, 'true', CTX ); It is iterated over the array and formed the proper JSON, so that Step 14 : " Parse Application Gateway services attributes" works as expected.