Author: Derek Leung

Product version: 2024.2+


Need

Customer needs to trigger workflow task to Data Steward to review record in error immediately after an import workflow to avoid unnecessary clicks.



Summarized Solution

Solution leverages new data-driven workflows in xDM. 


Detailed Solution

1. You need to define 2 workflows: The first workflow is a standard 2-step-approval workflow (i.e. Business User to Data Steward), but remember to enable “Multi Record” for the Entity’s Cardinality.


The first workflow must have Submit Data Automation, please note the Integration Job name will be used in the second workflow.


 

A screenshot of a computer

AI-generated content may be incorrect.


2. For the second workflow, the Start event’s Context Type should be “Start from Completed Batch”, based on the Integration Job name in the first workflow.  Choose Record Type as “Source Authoring Data with Errors”.  Assume IT will be doing the manual review of the error records.
A screenshot of a computer

AI-generated content may be incorrect.


3. Now let’s kick start the first workflow as the Business User, perform the Import
A screenshot of a computer

AI-generated content may be incorrect.


4. Importing 2 products, one is correct, another one with wrong Family value
A screenshot of a computer

AI-generated content may be incorrect.


5. After clicking “Send to Review”, the stepper will prompt a prompt with error as WARNING, but still you can click “Proceed Anyway”, Then fill-in the comment and send to the Approver.


   A screenshot of a computer 
AI-generated content may be incorrect. 

 A screenshot of a computer

AI-generated content may be incorrect.


6. The Data Steward will receive an approval task, Start the task
A screenshot of a computer

AI-generated content may be incorrect.


7. The Data Steward clicks the button “Save to xDM” to commit the records
A screenshot of a computer

AI-generated content may be incorrect.


8. The same Warning will appear, he can click “Proceed Anyway”
A screenshot of a computer

AI-generated content may be incorrect.


9. Leave a comment and press OK


10. Now if you examine the “Latest Integration Batches” in Application Builder Management, you’ll see that the integration job “ALL” has been completed but with errors.  Good records will go into the GD table.  Bad records will go into the AE table.
A screenshot of a computer

AI-generated content may be incorrect.


11. You can search the Good record from the Application
A screenshot of a computer

AI-generated content may be incorrect.


12. In the IT’s My Tasks, he/she will see a Review Error Product task
A screenshot of a computer

AI-generated content may be incorrect.

If you open the task, it highlights the error values
A screenshot of a computer

AI-generated content may be incorrect. 



Currently this approach is valid only for Source Authoring Data With Errors (AE).  You can refer to the documentation of the “Records to Checkout” Property for more details.