Question

Using task name as a token

Forms

Updated June 9, 2017

asked on June 8, 2017

Is there any way to use the task name as a token in the "save to repository" document name path? Or is there a way to capture the action?

I have a form that HR can either save as a completed form, or save as a rejected form. I want to identify which form was rejected once it saves in laserfiche. If i could use the task name it would work or if i could use the action identified from the button HR uses on the form it would work also. Otherwise i can't figure out any other way to get the word "rejected" as part of document name.

I use version 10, and i'm not especially good with coding - so any help would be appreciated!

0 0

Replies

replied on June 8, 2017 • Show version history

Joanne,

When setting up the "Save To Repository" task, you should be able to add the user action into the folder path, document name, etc.

However, it would match whatever the action is called so you might get "Approve" or "Reject" instead of "Approved" or "Rejected" depending on how you label the buttons.

If you absolutely need it to say "Approved" or "Rejected" then the simplest option is make that the actual button text (not especially clean on the user side).

Or you could use JavaScript to populate a hidden field and use that value instead (this is what I do on some of my forms but I'm guessing you want to avoid coding).

OR you could create a decision branch (exclusive gateway) in the business process, with two different "Save to Repository" tasks: one with Rejected in the name, and the other with Approved. Then, use the "Last User Action" value in the Path Conditions (outflows) for determining which one to use.

A follow up question, what do you need to do with the identified documents? If this is for an automated process, a better option might be to put the Approved/Rejected value into a separate field, or use it to determine what folder they end up in rather than putting it in the name.

0 0

replied on June 9, 2017

Oh my gosh that was it. I didn't realize action was tied to the actual name on that action. I had branched the process already anticipating it would be the right thing, but just couldn't get the name to go on right.

Sometimes the problems that give me the most grief are the simplest to answer. Thank you so much!

0 0

You are not allowed to follow up in this post.

Question

Question

Using task name as a token

Replies

Sign in to reply to this post.