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

Question

Question

Assigning Global Date Token to Custom-made Stamp not working

asked on June 4, 2014

Hi Everyone:

 

So I am attempting to create a new Stamp, and this stamp has the Date as a value. (the "%(DATE)" token.)

 

When I apply the stamp manually, that is, clicking on the stamp and applying it to a document it works just fine. It will assign todays date. However, when I have workflow assign it, it just returns the syntax "%(DATE)". Has anyone encountered a similar problem? It looks like all of my workflow config is correct.

 

Tony

 

 

2 0

Answer

APPROVED ANSWER
replied on June 4, 2014

Please review the Workflow help file pertaining to stamps. Under the Stamp Options section, there is a note that states

 

Note: This activity can only use public stamps that do not include Laserfiche tokens (e.g., %(Parent)). You cannot use custom stamps that include one or more tokens nor create a custom stamp with this activity. More information. You also cannot use private stamps, even if the stamps are owned by the Workflow User.

1 0
replied on June 4, 2014

As a possible alternative, you can use the Add Text Box activity in Workflow to place a text box containing the %(Date) onto a specific location on your document image

3 0
replied on June 5, 2014

Thanks for the suggestion. I'll give this a whirl and let you know how it goes.

 

Tony

0 0
replied on June 6, 2014

this worked like a charm, thanks Aaron.

 

Tony

0 0
replied on June 23, 2014

This would work in an application I need but is there a way to lock the text box so no changes can be made to it?

 

0 0
replied on June 23, 2014

If you mark the Text Box as "protected" in the Workflow activity, the text box will only be able to be modified by the user that created the text box (in this case the Workflow user) or by the document owner.

 

2 0
replied on June 24, 2014

Thank you Aaron that worked great for our use.

0 0

Replies

You are not allowed to follow up in this post.

Sign in to reply to this post.