Transferring a local variable in an interface into a process variable

RE: Transferring a local variable in an interface into a process variable

Stewart Burchell — Thu, 27 Jun 2019 07:56:42 GMT

Unless you're intending to use the local!userToTransferTo for something else you could simply point your a!pickerFieldUsers component directly at the rule input:

a!pickerFieldUsers(
label: "New Owner",
labelPosition: "ABOVE",
saveInto: ri!userToTransferTo,
value: ri!userToTransferTo,
required: true,
validations: {},
placeholder: "--Start typing officer name--"
),

RE: Transferring a local variable in an interface into a process variable

davidb545 — Thu, 27 Jun 2019 07:45:53 GMT

Thanks heaps - that's got it....

created a rule input for the form "RIUserToTransferTo" and changed my save code to:

a!save(
ri!RIUserToTransferTo,
local!userToTransferTo
)

which seems to be accepted.

cheers :-)

RE: Transferring a local variable in an interface into a process variable

nareshs427 — Thu, 27 Jun 2019 06:20:49 GMT

Hi David,

You cannot save any value into process variable as part of saveInto in an Interface. As Jose mentioned above, the values should be transferred to a variable based on the variable context.

In your case, it is a start form and in order to save the users value in the process variable, create a rule input in the interface and save the value in that rule input. While configuring interface, map the rule input with the process variable you would like to save the values in the 'Process Start Form' as shown in the below snapshot. Please note the process variables should be selected as parameter in order to appear in the mappings in Process Start Form.

Hope this helps. Cheers!

RE: Transferring a local variable in an interface into a process variable

josep — Thu, 27 Jun 2019 03:42:55 GMT

Hello David,

It is important to understand the execution context, when you are in the process context(domain) you have access to the process variables pv!. When you are in a smart service or process node you are on the activity class context ac! (domain) and when you are on a rule ( expression, interface, or so) you are on the rule context (domain) where you have rule inputs so you have ri!.

You should map the values between the context you create a node data input variable ac! That you will map and set up the value that comes from the process and later you have a rule input (the same type always, that will receive the activity class variable.

pv! -> ac! -> ri!

And you have to do the same when you want to receive a value from the interface.

ri! -> ac! -> pv!

The rrror you are experiencing is that you are trying to access a process variable that is not visible on the interface just because you are not in the context.

Here you can find a discussion about the same

community.appian.com/.../passing-process-variable-to-interface-records-tutorial

Hope this helps

Jose