Hi,
I am using 18.1 and trying records tutorial by following https://docs.appian.com/suite/help/18.1/Records_Tutorial.html
I was stuck at Add a Related Action point 4 where we need to pass process variable to query rule. I know its not in very detailed but generic steps . As a newbie, I need guidance in proceeding further in the tutorial.
step 4: For the User Input activity, assign the task to "=pp!initiator", and create a form titled "Update Phone Number" with one text field called "New Phone Number" that has a default value of rule!getEmployeeById(pv!employeeId).phoneNumberand saves into ac!newPhoneNumber. ac!newPhoneNumber should then be saved into a process variable so that it can be accessed by other nodes later in the process.
rule!getEmployeeById(pv!employeeId).phoneNumber
ac!newPhoneNumber
Here text field for new Phone Number that i am creating.
a!textField( label: "New Phone Number", labelPosition: "ABOVE", value: rule!getEmployeeById(pv!employeeId).phoneNumber, saveInto: {ac!newPhoneNumber}, refreshAfter: "UNFOCUS", validations: {} )
The error i am getting in interface is "Could not display interface. Please check definition and inputs. Interface Definition: Expression evaluation error: Invalid variable(s) found: pv!employeeId,ac!newPhoneNumber."
I would like to know how do i create activity class variable ac!newPhoneNumber and pass it to another process variable? Any help would be appreciated.
Attaching screen shots for process variable declaration and query rule that i created
Thanks.
Discussion posts and replies are publicly visible
Thanks for the inputs. I was able to create activity variable and able to save update phone number in the database as per the tutorial
1. I created employeeId and newPhoneNumber process variables
2. user input task>forms>create interface> with rule inputs as follows
3. input task>forms> update rule inputs with query rule
4. assign ac! variable to pv!variable
Hi krisk, You can directly use activity class parameters and process variables into interface rule, but in that case you will only be able to test that interface at run time. you will not be able to test interface as separate object, it will throw an error as it is showing to you. Thanks, Prashant