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

Question

Question

Starting business process from repository

asked on March 1, 2018

Good morning,

We have a workflow, which we have converted into a business process so that it can be initialized from the repository's Web Client. During the set up of the Business Process Rule, there is a tab that allows you to set a condition for the process to be able to start.

We set up a condition that if the path is XYZ to then allow the business process to start. This works fine, except that I'm looking for a way to hide the business process from the user's view if they are in a different path. Currently it shows the 'Start" button and when you try to start it, it just throws an error.

I was looking more into the conditions but couldn't figure out how to adjust that part. 

Can anyone provide guidance on what to adjust?

Thank you,

Raul Gonzalez

 

BPRules.PNG
EntryPathBPStart.png
BPRules.PNG (13.83 KB)
1 0

Answer

SELECTED ANSWER
replied on March 2, 2018

I filed it based on the behavior described in your initial post. It hasn't been added to the known issues list. I don't currently have a target release date for it.

0 0

Replies

replied on March 2, 2018

"somepath" should start with a "\".

1 0
replied on March 2, 2018

Miruna,

 

I'm sorry, that was just a mere example. In a real scenario we are trying something like "\some\path\here"

Our issue is that we still see the Start button to start the process from Web Access. It's just that if you start it from anywhere that is not "\some\path\here", it gives the error below, which is helpful, but we are looking for a way to not show the Start button until you are actually on "\some\path\here"

0 0
replied on March 2, 2018

That's actually a Web Access bug (reference number #75484).

0 0
replied on March 2, 2018

Thanks Miruna,

Do you have a link to the #75484 bug reference? We'd like to bring this to our Laserfiche contacts to see if they can help us further.

0 0
SELECTED ANSWER
replied on March 2, 2018

I filed it based on the behavior described in your initial post. It hasn't been added to the known issues list. I don't currently have a target release date for it.

0 0
replied on March 2, 2018

Oh I understand. Thanks Miruna and please keep us posted if you find any workaround.

Thank you,

Raul Gonzalez

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

Sign in to reply to this post.