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

Question

Question

Rename workflow's 'business process' starting rule

asked on August 25, 2021

Hi - we'd like to be able to rename a workflow's business process starting rule. Specifically so that we can change the text that appears in the menu for business processes when a user selects them in the Web Client. 

The use case:

  • A user selects a document in the repository (web client), right clicks on it, and then chooses a Business Process - which in turn runs a workflow that launches a Forms process (they also use the Business Process tab etc, but same issue is there):

 

  • At the moment we have to make this the Workflow Name - but note that in workflow it's possible to rename a 'Schedule' or 'Condition' workflow starting rule:

 

  • So we can rename the Condition or Schedule starting rule; but not the Business Process starting rule (which we presume is what gets displayed in the Web Client menu?)

 

As per shot above, there's nowhere to 'rename' the Business Process starting rule.

Am I missing something here? Do I have to change the name of the ovrall workflow to change the name in the Web Client user menu for the Business Process starting rule?

If that is the case - we'd love a Feature Request to be able to rename the Business Process starting rule so that it allows us to customise the text to launch it in the Web Client menu, without having to rename the workflow itself.

Thanks,

Duncan

0 0

Answer

SELECTED ANSWER
replied on August 26, 2021

There's no separate name for business process rules. The workflow itself is the business process, so its name is what is displayed in the business process list in the client applications.

Event starting rules have separate names because you can have more than one on the same workflow. There is only business process rule for any given workflow.

2 0
replied on August 26, 2021

Hi Miruna. Ok thanks for that.

Then we would like to add that as a feature request please: the ability to customise the text displayed in the Web Client menu for launching a workflow business process.

The reason is because (as in this case) a workflow may have a generic name that covers a group of conditional paths - whereas the business process context from the Web Client only goes down one of those paths due to the file metadata (so the overall workflow name doesn't make sense and is confusing for the user). We don't want to have to create an independent workflow with a unique name.

Now we've started using this, we can think of quite a few situations where this would be useful.

0 0

Replies

replied on August 27, 2021

How about creating a workflow with the name you want that then does an "Invoke Workflow" activity on the one you need.

2 0
replied on August 29, 2021

Yep - that would work and keep the overall workflow maintenance simpler. Great idea thanks!

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

Sign in to reply to this post.