-
Bug
-
Resolution: Unresolved
-
Medium
-
4
-
Severity 3 - Minor
-
148
-
Issue Summary
When admin using the automation configuration that was imported from production to sandbox , the lookupobject action still referring to the production Insight schema. The same applies when admin copy the imported configuration. This is also applicable when an automation is exported and imported between 2 production instances.
Steps to Reproduce
- In production, create a Insight schema called Schema A. ( If its a new instance , create a different object schema first , this is to assure the id will not match when we import it to Sandbox)
- Then , create an object type and objects
- Then, create automation and use lookupobject actions to search object in Schema A. Can us Name="xxx" iql. Add Log action to check the response value.
- Now create sandbox instance.
- Create Schema A in Insight and import the same data from production to Sandbox.
- Now , export the automation from production and import it to Sandbox.
- Execute the automation and monitor the log response.
Expected Results
It should return a different object key , based on Sandbox
Actual Results
Return the objectKey from Production insight.
Workaround
Open the imported automation configured , in the "Lookup Object" action , select a different schema and change it back to the original schema.
[JSDCLOUD-15091] Insights Automation: Imported automation configuration from production to sandbox/production , the lookupobject action still refering to the production schema
When you export the rule from A4J it contains all the information needed to execute the rule. In the lookupObjects case it contains the workspaceId:
"value": { "workspaceId": "f1668d0c-828c-470c-b7d1-8c4f48cd345a", "schemaName": "Human Resources", "schemaId": "1", "customSmartValue": { "id": "_customsmartvalue_id_1629155285558", "name": { "type": "FREE", "value": "lookupObjects" }, "type": "IQL", "query": { "type": "SMART", "value": "objectType == Employee" }, "lazy": false } },
The sandbox instance and the prod instance have different workspaceIds (how it routes to Insight). Does this behaviour work correctly with Issue based automation rules? If anything I would have expected the rule to not run.
Am I looking at this wrong or has this issue been outstanding since August 2021?!