It is worth mentioning that the questions on the Form do not have to be a 1:1 representation of the Attribute values used to create the Asset. Form values can be modified or ignored entirely, and attribute values can be provided statically within the Automation Rule. A bit of planning is still in order, though.
Examples:
While configuring and testing the Rule, it can be helpful to build one step at a time and use the Log Action component to check values.
The Web Request component is used multiple times to capture the data provided on the Form using the Forms REST API.
Requirements:
The Get Form Index resource provides details regarding the Forms attached to the provided Issue.
Note: This example assumes that only one Form is attached to the Issue during this operation. If multiple Forms are attached, it would be necessary to iterate over the Forms data to identify the desired ID value.
The Get Form Simplified Answers resource provides a user-friendly means for accessing the Form data. Storing the answers in a variable clarifies the following steps of the process.
If there is a large number of answers to process, consider using the Create Lookup Table component to provide additional clarity going forward. This allows you to define Keys for each answer. Individual Values can be captured by using a smart value to iterate over the form Data variable created in the last step.
{