I'm using a basic form interface to gather some data for an order approval. All of the relevant data is being stored in a CDT entry, a rule input called newOrderInput. The interface is used as the form for a user input task, and I'm trying to configure it to output to a process variable for storage in my data entity. I'm attempting to access it using ac!newOrderInput but it gives me an error, saying variable is improperly scoped. What can I change to access the rule input?
Discussion posts and replies are publicly visible
Have you configured this input on forms tab of user input task?
Hi, to configure the output values we simply need to pass them in saveInto of the input variables and if you want to pass something into the task you can pass through values.
Yes, but it appears that that only affects input into the task.
I tried this but it looks like it saves that value as soon as the task begins. I need to wait until submission before the correct values are in my output.
josephh1345 said:I tried this but it looks like it saves that value as soon as the task begins.
I don't understand what you mean by this but the data which the user inputs into the form is saved to process variables only when the user submits it.
What exactly do you want to have?
Your solution does save my rule input, but the value passed into my process variable is null. My interface saves data into the rule input when I hit the submit button.
Hi let me explain whatever we pass in the values in the input section goes to our interface and whatever we change in our interface gets saved into our process variables on submit button.
can you share a screenshot of your user input tasks data tab
This is the way to do that. I had the same problem and i solved using this method. i think you have configured issue, make sure the process variable will be a parameter.
Could it be that you configured the saveInto for that same variable on the data inputs tab as well? If yes, I suggest to remove the custom output and just use the configuration on the input tab.
The reason is, that all save operations, and that includes the saveIntos defined on the data input tab, will evaluate at the same time. This leads to a race condition.