Feature #2669
closed
Add rejection reason to approval task
Added by Vladimír Kotýnek almost 4 years ago.
Updated over 3 years ago.
Description
Please add rejection reason to role approval tasks.
When the approver disapprove role assignment he/she should be able to fill reason of the dissapprovement. In IDM configuration this field might be set as mandatory.
- Priority changed from Normal to High
- Target version set to 11.1.0
- Assignee changed from Vít Švanda to Ondrej Husník
- Status changed from New to In Progress
- % Done changed from 0 to 60
- Status changed from In Progress to Needs feedback
- Assignee changed from Ondrej Husník to Vít Švanda
- % Done changed from 60 to 90
- Status changed from Needs feedback to In Progress
- Assignee changed from Vít Švanda to Ondrej Husník
- % Done changed from 90 to 100
I did review and tested it. Works awesome, thanks for that.
Review notes:
- DynamicTaskDetail:122 "this.setState({reasonRequired: decision.reasonRequired});". Please call rest of block as callback in setState method. (Maybe "reasonRequired" may not be a state.)
- Only "approve" and "reject" variants are now supported in the application configuration. This can be done more dynamically with any decision button name (in connfiguration key). This is not important because user can now modify a WF definition for it.
- Please modify wiki documentation as we told.
- Status changed from In Progress to Needs feedback
- Assignee changed from Ondrej Husník to Vít Švanda
- Status changed from Needs feedback to Resolved
- Assignee changed from Vít Švanda to Ondrej Husník
I made rereview, thnaks for that.
- Status changed from Resolved to Closed
Also available in: Atom
PDF