You are viewing limited content. For full access, please sign in.

Question

Question

Does the previous submitter variable work for a reassigned user?

asked on October 6, 2023

I tried using the Previous User Submitter (/_fs_submitter) variable in the AP Clerk task, but the process was suspended, indicating that the variable didn't have a value.  The last submitter had actually been reassigned by the original submitter, so I'm wondering how or if this would work?  In the diagram below, you can see that the task for AP Process is initially assigned to Vicki, but she reassigns to Kim.  Kim works the AP Process task and it routes to Create Voucher.  After Create Voucher I want it to go back to Kim.  Which variable should I use?

 

0 0

Answer

SELECTED ANSWER
replied on October 18, 2023 Show version history

Yes, you can use '/_initiator' for the AP Clerk task. The procedure looks like the picture below when using '/_initiator'  in the provided simplified process.

0 0

Replies

replied on October 10, 2023 Show version history

Could you please provide us the process or more detailed settings of each task? So we can better investigating why the variable didn't have a value and find a solution.

0 0
replied on October 10, 2023 Show version history

Hi Zhipeng.  The xml file is attached as a txt file.

 

0 0
replied on October 10, 2023

Please change the file extension from XML to TXT before uploading.

0 0
replied on October 15, 2023 Show version history

Hi Mike. I've noticed that you are using a variable value in the task. I created a simplified process like below (also attached), in which the workflow task did nothing but delay one minute.  It works fine for me: the value of variable '/Submitter_ID' in 'User Task' is the submitter of task 'Approval' and no instance suspends.

So I am wondering that whether the Workflow task changed the variable value?

0 0
replied on October 16, 2023

The workflow task does not change the /Submitter_ID variable.  It retrieves variables from the Forms process and passes those values to a SQL query, which returns a Response value back to the Forms process.  The task that follows the workflow, AP Clerk, is set up to go to the /Submitter_ID, which hopefully is the person who just submitted the form and not the original submitter that started the Forms process. 

0 0
replied on October 16, 2023

I have noticed that you are using the variable in multiple forms. Because the default value is only filled in when the variable has no value, this field would not be updated when used in multiple forms.

You can try to use process variable instead of field variable. And I tried to use '/_initiator' which works fine in my process.

0 0
replied on October 17, 2023

I'm using '/_initiator' for the AP Process; when that person reassigns to another person, how is the other person identified?  Are they now identifiable as '/_initiator' or are they now the {/_currentuser}?  Are you suggesting I can use '/_initiator' for the AP Clerk task?

0 0
SELECTED ANSWER
replied on October 18, 2023 Show version history

Yes, you can use '/_initiator' for the AP Clerk task. The procedure looks like the picture below when using '/_initiator'  in the provided simplified process.

0 0
replied on October 23, 2023

Ok, thanks...I think that will work for me. 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.