Step 4: Store the Skipped Customer record

Once all the skipped customer records are stored in the list, and the ETL pipeline has been executed, the β€œOn Completed” function is executed.

This exercise defines actions in the β€œOn Completed” function to store the deleted records details in a target entity.

  • To define the Actions to be executed once the ETL pipeline run is completed, go to the Code tab>On Completed function. To define the actions, add an β€œAction box” by clicking the [+ Action box] button.

  • To traverse the list of skipped records, add and define the following action in the β€œCode” tab:

    1. Select Action as β€œTraverse List”.

    2. Select Target Value as β€œskippedRecordsList”.

    3. The Variable β€œitem” is created.

  • To create the entity record for the skipped records detail from the traversed item, add and define an action in the Traverse List action as follows:

    1. Select Action as β€œCreate Entity record”.

    2. Create the JXPResponse variable β€œResult” by clicking the [+] button.

    3. The Entity variable β€œitem” is created.

  • To save the ETL pipeline, click [Save].

  • To publish the ETL pipeline, click [Publish].

  • Ensure the ETL pipeline is enabled.

  • Click the [Run] button.

  • The Run ETL pipeline dialog box displays. To add a parameter (to add value for StartupParameters) click the [+ Parameter] button. Add three (3) parameters.

  • To skip records with Customer_ID as β€œ3”, β€œ5”, and β€œ7”, enter the StartupParameters as per the image below. These values will be traversed to match with the Customer_ID to skip creating relevant records. To run the ETL pipeline, click the [Run] button.

  • For a list of Customer IDs ranging between 1 and 17 (odd numbers), the records with Customer_D β€œ3”, β€œ5”, and β€œ7” are skipped in the target destination.

Last updated