Servicenow recommendation :
Audit the Lookup rule and ensure that lookup target is set to CI and target table is set to Scanned Applications.
I understand the recommendation to use Scanned Applications as the target table. However, third party data has already been loaded into Discovered Applications, and the CI association information, including the direct CI information is already available to me in the payload. Could you clarify whether it is mandatory to load the same application records into Scanned Applications as well for the lookup rule to function correctly, despite already having the required CI reference? and I can set that CI directly in the processor script instead of lookup rules to work in this case.
