-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
AT
- Annotations are
- editable in Runtime incidents (can be edited and cleared via RuntimeService API)
- propagated to the corresponding historic incident immediately
- require the same rights that the resolution of incidents does, so any of
- UPDATE permission on resource "Process Instance"
- UPDATE_INSTANCE permission on resource "Process Definition"
- retrieved by querying the (historic) incident itself
- there is a new column ANNOTATION_ of type VARCHAR(4000) for incident and historic incident
- User Operation Log entries are written when annotations are modified
Hints
- Keep this consistent with
CAM-9556
This is the controller panel for Smart Panels app
[CAM-13060] In Java API, I can add/edit/delete an annotation for an incident
| Description |
New:
*AT*
* Annotations are ** editable in Runtime incidents ** propagated to the corresponding historic incident immediately ** require the same rights that the resolution of incidents does, so any of *** UPDATE permission on resource "Process Instance" *** UPDATE_INSTANCE permission on resource "Process Definition" * retrieved by querying the (historic) incident itself * there is a new column ANNOTATION_ of type VARCHAR(4000) for incident and historic incident |
| Mentioned Roles |
| Mentioned Groups |
| Status | Original: Open [ 1 ] | New: Ready [ 10005 ] |
| Description |
Original:
*AT*
* Annotations are ** editable in Runtime incidents ** propagated to the corresponding historic incident immediately ** require the same rights that the resolution of incidents does, so any of *** UPDATE permission on resource "Process Instance" *** UPDATE_INSTANCE permission on resource "Process Definition" * retrieved by querying the (historic) incident itself * there is a new column ANNOTATION_ of type VARCHAR(4000) for incident and historic incident |
New:
*AT*
* Annotations are ** editable in Runtime incidents (can be edited and cleared via {{RuntimeService}} API) ** propagated to the corresponding historic incident immediately ** require the same rights that the resolution of incidents does, so any of *** UPDATE permission on resource "Process Instance" *** UPDATE_INSTANCE permission on resource "Process Definition" * retrieved by querying the (historic) incident itself * there is a new column ANNOTATION_ of type VARCHAR(4000) for incident and historic incident |
| Mentioned Roles |
| Mentioned Groups |
| Description |
Original:
*AT*
* Annotations are ** editable in Runtime incidents (can be edited and cleared via {{RuntimeService}} API) ** propagated to the corresponding historic incident immediately ** require the same rights that the resolution of incidents does, so any of *** UPDATE permission on resource "Process Instance" *** UPDATE_INSTANCE permission on resource "Process Definition" * retrieved by querying the (historic) incident itself * there is a new column ANNOTATION_ of type VARCHAR(4000) for incident and historic incident |
New:
*AT*
* Annotations are ** editable in Runtime incidents (can be edited and cleared via {{RuntimeService}} API) ** propagated to the corresponding historic incident immediately ** require the same rights that the resolution of incidents does, so any of *** UPDATE permission on resource "Process Instance" *** UPDATE_INSTANCE permission on resource "Process Definition" * retrieved by querying the (historic) incident itself * there is a new column ANNOTATION_ of type VARCHAR(4000) for incident and historic incident *Hint* * Stay as consistent as possible to |
| Mentioned Roles |
| Mentioned Groups |