When creating a self service tile in the TDM Portal, you will be using Agile Requirements Designer (ARD) to assist with the creation of the workflow. The publishing of specific data pools will happen behind the scenes, without user involvement. This knowledge article will assist with a common issue that users run into with the self service catalog when different versions of data pools are used.
When I publishing test data from the self service catalog, I am not seeing the variables that I was publishing with when I publish the datapool directly in Datamaker. How can I troubleshoot this problem?
When you created the link in ARD to publish a data pool from Datamaker, you will be able to see the data pool's level ID by viewing the process block in your ARD as shown below.
<Please see attached file for image>src="/servlet/servlet.FileDownload?file=0150c000004AKZ1AAO" alt="screenshot_398.png" width="823" height="234">
In this example, the data pool called JoeDP is using an level ID of 7533 that ARD is referencing back in Datamaker.
The next step is to check that the datapool you are publishing in Datamaker has the same level ID as the one in your ARD flow. If you don't have level IDs visible in the Maintain Projects view in Datamaker, you can enable it from the menu by selecting Settings|Show Level ID. If this is checked, then the level ID will be visible.
Once you have enabled the setting in Datamaker, refresh the project tree, and you should now see the level IDs next to the data pools as shown in the screenshot below.
<Please see attached file for image>src="/servlet/servlet.FileDownload?file=0150c000004AKZ3AAO" alt="screenshot_4000.png" width="289" height="193">
In this case, the data pool is showing the same level ID as the one referenced in the ARD flow. If the values are different, you will need to re-select the correct version of the data pool that you want to publish for the self service catalog.
When you create a new version of a data pool, that can cause a change in the level ID for the data pool. The self service flows will not know about new versions of your data pools, so if you want the flow to use your new version, you will need to update the flow to point to the new version.