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

Question

Question

BP Requirement: A shortcut in a specific path has to be selected

asked on April 20, 2015 Show version history

I'm trying to set up a rule for a business process such that it is enabled only for shortcuts in a specific folder. I'm using a combination of document type and entry path, but this doesn't seem to work because the entry paths of shortcuts point to the main entry, as opposed to the location of the shortcut.

My folder structure looks like this:

  • Folder 1
    • Subfolder A (contains documents)
    • Subfolder B (contains documents)
  • Folder 2 (contains shortcuts for the docs in Subfolder A)
  • Folder 3 (contains shortcuts for the docs in Subfolder B)

 

I need to make it so that the BP is enabled only for the shortcuts inside Folder 2, and not for Folder 2 itself or any of the other folders or the entries in them.

Is there a way to do this?

0 0

Replies

replied on April 20, 2015
 
 

Hi Ege,

 

Instead of using path, use Parent Name. This allowed it to only be an option for shortcuts in Folder 2 and disabled for all the other folders/entries.

 

 

Cheers,

Carl

 
0 0
replied on April 23, 2015

Are you sure that's correct? I set it up exactly like that and it didn't work. The BP is still grayed out when I select the shortcut in Folder 2.

0 0
replied on April 23, 2015

Carl's rule works for me. What versions of Laserfiche Server and Workflow are you using?

0 0
replied on April 23, 2015

LFS 9.2.0.343

WF 9.1.1.365

0 0
replied on April 23, 2015

Hm, I'm not seeing anything changed since then (I'm using WF 9.2 and LFS/Client 9.2.1). There was a bug fixed for WF 9.2 where the shortcuts' metadata was not properly processed, but the Client is processing the rules on its side to enable/disable the buttons.

Probably worth opening a support case if upgrading is not an option. At least please patch Workflow to the latest hotfix for 9.1.1.

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

Sign in to reply to this post.