Sequence of data pool is changing after publishing the data pool In TDM Portal

book

Article ID: 224083

calendar_today

Updated On:

Products

CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

We have created three data pools in Datamaker (DataPool1, DataPool2, and DataPool3), and designed a Self-service Tile, taken from the ARD Flow, that references the three data pools in the sequence of DataPool1, DataPool2, and DataPool3.

When executing the publish job in TDM Portal, we see the data pools are getting executed in the wrong sequence: DataPool2, DataPool1, DataPool3

 

 

Environment

Release : 4.9.1

Component : Web Portal - Publishing

Resolution

 

the "TDM Job Submission Order" is set in the Flow Properties - General Properties dialog, at the bottom of the screen, as shown below:

https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=+ejos9O7MTDp21jzxIzGCA==

Looking at the copy of the ARD flow you provided, I see the "TDM Job Submission Order" has been configured as "Calculate Job Submission Order", which according to the ARD documentation, could change the sequence order of execution. See: https://techdocs.broadcom.com/us/en/ca-enterprise-software/devops/agile-requirements-designer/3-1/requirements-modeling/visual-flows.html

  • Submit as Encountered in VTF Logic — CA TDM uses the exact same order of blocks as defined in the ARD flow file. This is the default.
  • Calculate Job Submission Order —  Let CA TDM calculate the order of Publishes. This order can differ from the order of blocks in the ARD flow file.
  • Use Override Sequence — You define an override sequence in CA TDM. This order can differ from the order of blocks in the ARD flow file

I recommend setting this back to the default setting: "Submit as Encountered in VTF Logic", and save to the TDM Repository, and see if this corrects the behavior you are seeing for the publish jobs

 

The "TDM Job Submission Order" is set in the Flow Properties - General Properties dialog, at the bottom of the screen, as shown below:

https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=+ejos9O7MTDp21jzxIzGCA==

Looking at the copy of the ARD flow you provided, I see the "TDM Job Submission Order" has been configured as "Calculate Job Submission Order", which tells TDM to ignore the order set by the ARD Flow (VTF logic), and to calculate the order based on the tables "parent to child" relationships. TDM will execute the parent first and then the child, as a result, this could change the sequence order of execution to be different from what is defined in ARD.

See: https://techdocs.broadcom.com/us/en/ca-enterprise-software/devops/agile-requirements-designer/3-1/requirements-modeling/visual-flows.html

  • Submit as Encountered in VTF Logic — CA TDM uses the exact same order of blocks as defined in the ARD flow file. This is the default.
  • Calculate Job Submission Order —  Let CA TDM calculate the order of Publishes based on the Parent-Child relationships of the tables. This order can differ from the order of blocks in the ARD flow file.
  • Use Override Sequence — You define an override sequence in CA TDM. This order can differ from the order of blocks in the ARD flow file

It's recommended to set this back to the default setting: "Submit as Encountered in VTF Logic", and save to the TDM Repository, and see if this corrects the behavior you are seeing for the publish jobs.