Bug 1267164 - Make Task admin configurable
Summary: Make Task admin configurable
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Core
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Alessandro Lazarotti
QA Contact: Radovan Synek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-29 08:12 UTC by Anton Giertli
Modified: 2020-03-27 20:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:07:46 UTC
Type: Enhancement
Embargoed:


Attachments (Terms of Use)

Description Anton Giertli 2015-09-29 08:12:56 UTC
Description of problem:

Currently the Task admin is set by default to value "Administrator".

It is possible to change this value to a different one, but only for one Task at a time - via Task input parameter
https://github.com/droolsjbpm/jbpm/blob/6.2.x/jbpm-human-task/jbpm-human-task-workitems/src/main/java/org/jbpm/services/task/wih/util/PeopleAssignmentHelper.java#L108


Version-Release number of selected component (if applicable):

6.1.x
How reproducible:
always

Steps to Reproduce:
1. Try to change Task admin to a different value for:

 -- whole process
 -- whole project (deployment)
 -- globally for whole business-central


Actual results:
It is not possible to change Task admin value for a whole process / project / business-central (users have to do it manually for every task)

Expected results:
It is possible to configure Task admin for a whole process / project / business-central via some config option - i.e. kie-deployment-descriptor.xml or System property


Additional info:
There is a workaround for this issue - drop similar DRL file under workbench/WEB-INF/classes
https://github.com/droolsjbpm/jbpm/blob/master/jbpm-human-task/jbpm-human-task-core/src/test/resources/simple-add-task-rules.drl#L47

This will change the Task admin globally for whole business-central - this approach is not very user friendly, hence this should be considered only as a workaround.


Note You need to log in before you can comment on or make changes to this bug.