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

Question

Question

personal stamp in workflow

asked on July 10, 2013

Dears,

 

Why it is not possible to get a personal stamp in workflow, specifically if the personal stamp is created by the workflow user (Connection Profile User)?

 

 Our scenario is to be able to assign a personal stamp with the workflow at each approval level of the users (by digital signature), while these users cannot use the personal stamps used by the workflow.

 

Please, clarify why public stamps are only available there?

 

Thanks,

Dory

 

2 0

Answer

APPROVED ANSWER
replied on July 12, 2013

Hi Dory,

 

The ability to use personal stamps, even as the Workflow user, has been purposefully omitted from Workflow.  At best, the stamps on a document are visual aids that carry no legal weight.  At worst, a user could gain access to the Workflow account and forge a stamp.  Because stamps are insecure and largely meaningless, we've opted to not tacitly endorse their use as a method of formal approval.

 

That said, if you're set on using private stamps, it would be very easy to do so with a custom script smiley

4 0

Replies

replied on July 10, 2013 Show version history

I've wanted more stamp capabilities like that too because anytime the customer wants to explore using them in this way I always have to shut them down.

 

However there is one neat trick you can use for this one - I had a project where I had to look for certain people to stamp a personal approved stamp in workflow as part of an approval process. We had each of the users create a personal stamp named ApprovalStamp and I used a search that looked for {LF:AnnStampName="ApprovalStamp", owner="User"}

 

But since this is a public stamp you can't search on who placed that there - Directly

 

There is a way that you can sort of search - you can do this:

 

{LF:AnnCreator="User"} & {LF:AnnStampName="StampName"}

 

Personally I'd love to see one of these:

 

Security for stamps

Ability to see who placed a stamp or annotation and being able to reference placed stamps or annotations in workflow. 

 

If we had those two we wouldn't need to worry about Public vs Private. Heck if we just had the ability to see who placed a stamp or other annotation it would be better.

 

As it stands now there is a delete annotation function in workflow but it's only good in cases where you placed the annotation earlier within the same workflow. There is no find annotation function to locate annotations for it to delete. As I've learned to break my workflows apart for better management (especially with the new token passing in 9.0.2) this is becoming less useful than it already was.

 

 

0 0
replied on November 4, 2013 Show version history

I think this was not covered, but you can add a users personal connection profile to the workflow and then use that as the connection profile used for a custom script for private stamps.

 

With that type of solution, you would need to have the user republish/update their connection profile each time they change there password. It may be best to have the user install the workflow designer on there personal machine so the connection profile only resides there and the workflow would need to be re-published from that machine after any re-publish done from any other machine that does not contain that connection profile.

 

The script is fairly easy to comile as most of it is already built in the help files for the SDK Script activity.

0 0
replied on November 4, 2013

Kenneth,

 

This is not a setup recommended by Laserfiche. For one thing, it would only work with Laserfiche users, not domain accounts. But more importantly, the connection profile is saved and published with the workflow definition. So anybody with editor rights could download the workflow and modify it to do other actions as that user. Yes, you can secure them to the individual users, and changing workflow definitions is audited, but like Brett mentioned above, they wouldn't carry any legal weight since they'd be relatively easy to forge.

 

Miruna Babatie

 

Software Test Engineer

Laserfiche

1 0
replied on November 5, 2013

Miruna,

 

That is interesting. I was informed by Presales that the connection profiles are saved locally, and would become invalidated if you publish a workflow with a connection profile you do not have in your machines workflow designer. Thanks for setting that straight

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

Sign in to reply to this post.