Are you facing the issue for any specific workflow or for all workflows you are observing this behavior? Also, are you using out-of-the-box workflows or any custom workflow you have created and facing this issue?
okay, just make sure that for your custom workflow, the workflow task that you have defined in the workflow model is having parent as bpm:workflowTask. Also, hoping that you are using bpmriority property in the share-config-custom.xml to display the priority value in the workflow task form.
I checked all configurations and it seems good everywhere. I also checked the OOTB behavior and it is showing priority as value as expected. I am not getting the difference between bpmriority and wfriority. Does it affect priority property..?
In the bpmModel.xml where the core content modeling for any workflow resides, bpmriority property under the bpm:task content type is the one which holds the value for the workflow priority. I am not sure about wfriority field as I have not seen it in any of the out-of-the-box workflows, it looks like it is a new field you may have added for your custom workflow. Is that correct?
In the workflow task configuration in share-config-custom.xml, I am not sure which value you are using to show the workflow priority field. However, if you are using bpmriority field then it should have been displayed having your workflow task defined in workflow model is having parent as bpm:workflowTask. Is there anything specific you have done in order to display the priority value using a different field?
For Default Start Task <type name="bpm:startTask"> <parent>bpm:workflowTask</parent>
<properties>
<!– Description for the workflow as a whole –> <property name="bpm:workflowDescription"> <type>d:text</type> <constraints> <constraint ref="bpm:allowedDescriptionLength"/> </constraints> </property>
<!– Due date for the workflow as a whole –> <property name="bpm:workflowDueDate"> <type>d:date</type> <mandatory>true</mandatory> </property>
<!– Priority for the workflow as a whole –> <property name="bpm:workflowPriority"> <type>d:int</type> <default>2</default> <constraints> <constraint ref="bpm:allowedPriority" /> </constraints> </property>
While, <!– –> <!– The base for all Tasks assigned via a Workflow –> <!– –>
<!– List of "hidden" transitions to consider masking from user –> <property name="bpm:hiddenTransitions"> <type>d:text</type> <multiple>true</multiple> <default></default> </property> <!– Flag to determine whether the owner can reassign their task –> <property name="bpm:reassignable"> <type>d:boolean</type> <default>true</default> </property> </properties>