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

Question

Question

Forms- Save to Repository {/_currentuser_display} token showing up as Anonymous User

asked on January 10, 2017 Show version history

I have a form that I am starting from Workflow and passing to an approver in Forms.  I am using a signature field in which the current user's display name (token- {/_currentuser_display}) is added to the text above the field.  In the forms module when I approve the form the display name shows correctly- after I save the form to Laserfiche the text above the field shows "Anonymous User" (This is not a public form).  Does anyone have any clue what could be causing this?  I am currently using Laserfiche Forms Version 10.1.0.642.

0 0

Replies

replied on January 11, 2017

This is the expected behavior as the token used in text above the field is parsed every time the form is opened and the value won't the saved. So if the approver open the form it will show the approver's display name. But when save to repository service task open the form to generate the pdf/tiff, it open it as anonymous user so it will show "Anonymous User". If you want the value to be fixed after approver approve the form, you can use a field with {/_currentuser_display} as default value instead. Then the value will be kept after approve.

0 1
replied on September 17, 2020

Using {/_currentuser_display} does not work.  It shows Anonymous User when attaching the form (as PDF) to email as next step in workflow process.

0 0
replied on September 22, 2020

Did you use it as default value for a field and check the value when the approver open the form? If the form is not opened by the approver and you just use it as attachment in email service task, it is expected behavior to show it as "Anonymous User" as there is no current user for email service task.

0 0
replied on September 23, 2020

We found a solution by adding a hidden field populated with {/_currentuser_display} value and use to display below the signature and it shows up in email attachment.

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

Sign in to reply to this post.