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

Question

Question

Wrestling with Shortcuts and Workflow

asked on April 28, 2017 Show version history

We have a situation where we are looking to distribute one daily report across a groups of users.  This can easily be done via Workflow routing to groups, as it will put a shortcut in each user folder.

Then when each user reads or opens the document we want to be able to remove their shortcut.  

Ideally, we would be able to key off an open document event, but none exists.

Manually deleting the shortcut would work, but we don't let them delete from these folders, and access rights do not let us differentiate between shortcuts and documents.  

Any other action impacts the source document which might be shared by as many as 20 users.

We'd be OK with creation multiple copies of the document for each user's folder, but that is not an option for the Route to Group task.

Short of hacking the audit trail tables, is there a way to let us remove these shortcuts as each user opens the item?

Thanks in advance - 

 

0 0

Replies

replied on April 30, 2017

You said "Manually deleting the shortcut would work, but we don't let them delete from these folders, and access rights do not let us differentiate between shortcuts and documents."

If you're not opposed to a manual event, maybe build a simple business process workflow that verifies the item is an appropriately named shortcut and if so, deletes it.  If they try to start the business process on any other document that that doesn't meet your criteria, it refuses to delete the item.  Now you didn't have to give them delete privilege, but made sure they can "request deletion" of authorized items.

1 0
replied on May 1, 2017 Show version history

Thanks Ege -

That is why I was thinking about popping into the Audit Trail tables.

 

And thanks Matthew -

That is a very clever idea!

Bill

1 0
replied on April 29, 2017

We brought this up before. Unfortunately there isn't a way to detect when a user opens a document. My understanding is that LF Server does not broadcast an event that WF Subscriber can pick up on.

In our situation, we want to track how long it takes for a user to open a document that is assigned to them, so that we can compare it with how long it takes them to process that document. There isn't a way to do that though, which prevents us from optimizing our processes further.

Hopefully the next version will offer some answers.

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

Sign in to reply to this post.