Stamp Annotation issues

asked on September 26, 2014 • Show version history

I am facing below mentioned issues with the stamp:

1) Image stamp can not contains metadata field value or other tokens

My Requirement: stamp with image and by default with username and DateTime

2) custom text stamps can not be validated by stamp conditions in workflow because it contains tokens

Image Stamps are validated by stamp workflow conditions but custom text stamps are not validated, why?

http://www.laserfiche.com/support/webhelp/workflow/9.1/en-us/LFWorkflow.htm#cshid=Resources/Activities/Using%20Condition%20Editors.htm

3) protected stamps are not movable

My Requirement: stamp should not be editable but it should be movable

4) "workflow" user will be the owner of stamps if applied by workflow

I need the stamp owner (not document owner) should be the user who has initiated the workflow

5) stamp color can not be fixed/assigned by user

My Requirement: Recently used stamp can apply the stamp color, but I need to fix the stamp color when I create the stamp

6) there is no option to create stamps from admin, we need to use client for that

Stamp should be created from Admin console actually. If I login from client using admin user into LF client then I need atleast one document to open in document viewer and then I can create the stamp. When I can create stamp from any system and it is available to any other user then why can't we create it from admin.

7) there is no option to edit the image/custom text stamp by its creator

my requirement: User will stamp the document by image/custom text stamp and then add information like "Material Received", "Inward", "SAP GR No." or any other information that user would like to write on stamp. Only stamp owner should modify the details and it is read only for rest of the users.

0 0

replied on October 2, 2014

Hi Ashish,

Thank you for the feature requests - the points you mentioned are expected Laserfiche behaviour so thank you for the feature requests - if you could provide us with the use case scenario, this would help us better understand why the features are required.

I have a few suggestions that may help with the issues you are having:

Point 1 and 6 - Create a "stamp" metadata field that contains a list of stamps available for users. When the field is updated, a workflow is triggered to apply the stamp to the document and update a "history" field to contain information about the workflow initiator and date/time the workflow started.
Point 2 and 7 - Use a metadata field instead - set the default values with the tokens needed. The information can then be validated by Workflow.

For points 3,4 and 5, if you can provide a use case scenario of why this is needed then we may be able to provide you with possible workarounds.

Cathy

0 0

replied on October 5, 2014 • Show version history

2) custom stamp only have predefined tokens, not a list of fields

3) protected stamps are not movable

Document will have 5-10 stamps, due to that information will not be properly visible to user, so user will just move the stamp

User1: will apply image stamp or custom stamp (can also by textbox) which is protected

User2: will able to view that stamp but not able to edit

my requirement: user2 should not able to edit the content of stamp but should able to move.

4) "workflow" user will be the owner of stamps if applied by workflow

Auto Stamp will use workflow initiator as a stamp owner. We are configuring workflow execution by "workflow" user which has full admin rights.

I don't want to change document owner name but I need stamp owner.

I need the stamp owner (not document owner) should be the user who has initiated the workflow

5) stamp color can not be fixed/assigned by user

When I create the stamp it should following information:

- stamp color

- stamp security (like public, protected, private), if protected then it should ask for the username (multivalue)

- Do you need to include username in stamp?

- Do you need to include date in stamp?

- Do you need to include time in stamp?

- font settings for different text

0 0

replied on June 26, 2019

Has this feature request been addressed. I am currently running into the same issue where I need the metadata to be included and ID number and I am unable to do this?

Thanks

Bev

0 0

Question

Question

Replies

Sign in to reply to this post.