How can I create an ATF test step for a field that has a dependency (i.e., another field).

[Community Alums]

When creating a manual test step for a Service Catalog item (Create a New Incident), the records of a reference field on the form depend upon the selected value of a drop down on the same form.  In ATF this cannot be performed when filling out variable values for a record producer.  When attempting to create the step for ATF, no records are displayed in the pop-up window list and any manual entry is an Invalid Input considering the window has no records.

Side note:  ATF steps using a reference field are able to be created successfully when there isn't a dependency.

Is there a work around to this issue?

[Daren Kline]

Has anybody answered this? I am experiencing the same issue.

[Carolien]

Badly need this too, has anyone found a workaround?

[codycotulla]

Hi,

You can use parameters for this.

Create a parameter of the type you need to set the value, often a string or a document ID or Reference. Then in the step where you need to set the value, put in the "data pill" for the parameter.

You may need to have two Value setting steps. For example, if there is a group/user dependency on a form, you might need to set the group in one Set Field Values step, and the user in another Set Field Values step.

Hope this helps.

Let me know if you have any questions.

Thanks,

Cody

[Carolien]

Hi Cody,

Thanks for your advice, I can indeed reference the parameters set in the ATF set values step.

One issue though, I can enter a new variable in the Variables Choice List within a Parameter Variable in my own developer instance, but in the developer instance that we use at work, the Variables Choice List doesn't appear, even though I am using the same kind of variables (String) and the same options.

Could this be caused by e.g. options within an update set? Or some other restriction?

Thanks,

Carolien