Data Variables are not available in data painter for decision table columns

book

Article ID: 143164

calendar_today

Updated On:

Products

CA Agile Requirements Designer

Issue/Introduction

ARD 3.0.1.9

We have noticed that anytime we copy a Decision Table from one flow into a new flow, and save the flow into the TDM Repository, the variables related to the Decision Table are not seen in Data Painter. Therefore, we are unable to use the variables when naming the Test Cases.

Note: This issue is not seen if the Data used to create the Decision Table is imported. The problem is only seen when working with a copy of an existing Decision Table.

 

Steps used to recreate the issue:Create a DT in Excel

  1. Create a new Model in ARD.
  2. Use the "Import - Decision Table" option to import the options.xlsx file to create the Decision Table in the flow.
  3. Connect the Start and End Blocks to the Decision Table.
  4. Save the flow to a project in the TDM Repository.
  5. Go to Path Explorer and Generate Test Cases.
  6. When saving Test cases, launch Data Painter and notice the variables from the Decision Table are available for use.
  7. Create a New Model in ARD.
  8. Make a copy of the Decision Table from the previous flow, and paste it into the new flow.
  9. Connect the Start and End blocks to the Decision Table.
  10. Save the new flow to a project in the TDM Repository.
  11. Go to Path Explorer and Generate Test Cases.
  12. When saving Test cases, launch Data Painter and notice the variables from the Decision Table are NOT available for use.

As a test, we went back to the Decision Table in the second flow, where the problem was seen, and opened that Decision Table for edit. Then re-imported the data from the Excel Spreadsheet (.xlsx file), regenerated the Test Cases, and now the variables available in Data Painter. The issue was only seen for the Decision Table created from a copy. 

 

Environment

Release : 3.0

Component : CA Agile Requirements Designer

Resolution

Engineering reviewed and confirmed this is a defect. A fix has already been implemented and will be available in the 3.1 release, which is targeted for March 2020.