Possible to edit workflow priority?

[katarinahallber]

Hi,
we are running Alfresco 4.0.e Community, Share.

When a workflow is created, the user creating the workflow can set the priority of the workflow (Low, Medium or High). As far as we can see there is no way to change the workflow priority later? Or is there?

If not, is there a way to make it possible to change the priority after the workflow has been created?

Regards
Katarina Hallberg

[parzgnat]

The forms that you see when submitting workflow and acting on workflow tasks are controlled by the share-workflow-config.xml file.  This file is located at $ALFRESCO_HOME/tomcat/webapps/share/WEB-INF/classes/alfresco.  There are separate form configurations for each of the out-of-the-box workflow tempates (Adhoc, Group Review and Approve, Parallel Review and Approve, etc.).  You'll also see different forms for Activiti and JBPM workflows.  You'll have to find the forms for the specific workflow that you're trying to change.  There will be separate forms for each workflow for when the workflow is being initiated, and other forms for when a workflow task is being acted on after the workflow has started.

In your case, you'll want to look for the form for when a task is being acted on after the workflow has started.  In that form, you'll see that the bpm:workflowPriority attribute is set to read-only.  If you change it to not be read-only, it should allow you to modify the priority while the workflow is in progress.

A good tutorial for working with Alfresco workflows can be round here:  http://ecmarchitect.com/images/articles/alfresco-workflow/advanced-workflow-article-2ed.pdf

[douglascrp]

Hey.

I tried this idea of exposing the bpm:workflowPriority instead of bpmriority into the user task, setting it as NO read-only, but changing it seems to be not reflected to the workflow.

[douglascrp]

Hey, it's me again.

Please, take a look at this post if you have the time https://forums.alfresco.com/forum/developer-discussions/workflow/javalangclasscastexception-javalang...

It's related with the running workflow's priority change.

Thank you