User Picker isn't saving my selection

Question

I added a User Picker to my Interface. 
 I have defined "Selected Users" as ri!selectedUsers (which is an array of type User) 
 I have defined "Save Into" as ri!selectedUsers 
 When I select user, the selection is not saved in the component. I have seen some advice regarding a!save, and using load and local variables, but I am missing something and can't seem to find it explicitly explained in videos or the documentation. 
 Any suggestions? 
 Thanks, 
 Rob

Mike Schmitt · Accepted Answer

It's fairly straightforward luckily - basically you create an input variable on the user input task's Data tab matching the type you need (list of users in your case), then switch over to the "Forms" tab and find the rule input and set it to the newly-created ACP.

Mike Schmitt · Answer

As a preliminary piece of advice: when entering a comment, use the menu "Insert -> Code" to insert a Code box which will both retain your formatting as well as not making your comment 5 pages long. You should be able to do this also if you edit an existing comment. I'll take a glance at your code as soon as I can and see if I can spot anything. 
 Meanwhile it might help you to reduce the case to something absurdly simple and get that working at least - I banged out the following code in the last minute which works just fine for me: 
 a!pickerFieldUsers(
 value: ri!selectedUsers,
 saveInto: ri!selectedUsers,
 maxSelections: 3
) 
 and the expected result, which works fine:

Mike Schmitt · Answer

Shoot, I was actually about to ask you before whether it was only breaking in a process, but I forgot to. 
 So, yes this is expected behavior when the Task setup is incomplete. When saving a variable into a ri! variable in a SAIL form used on a task in a process, the rule input on the User Input Task node MUST map to an ACP (ac!) variable defined in that task. You might think it would just save a "temporary" copy on the SAIL form without this, but it doesn't. I'd be pretty surprised if this wasn't the root of your issue.

Mike Schmitt · Answer

If I understand your question correctly, then the answer luckily is that it's a lot easier than you're making it. You can have the user picker field store into a text field - when a user is cast as text, the resulting text value is just the username. So for example, you could just point your user picker field at ri!flight.firstOfficer instead of using an intermediary field. 
 Another approach would be to continue using the separate field, and then in a script task after the user input task, save the username value into the CDT property. This adds steps but also potentially adds flexibility to do different things if needed.

User Picker isn't saving my selection

Top Replies