pub struct PendingUserTask {Show 19 fields
pub instance_id: Uuid,
pub workspace_id: String,
pub element_id: String,
pub name: Option<Option<String>>,
pub bpmn_flow_path: Option<Option<String>>,
pub bpmn_version: Option<Option<i64>>,
pub instance_created_at: String,
pub instance_created_by: String,
pub parked_at: Option<Option<String>>,
pub assignee: Option<Option<String>>,
pub owner: Option<Option<String>>,
pub candidate_users: Option<Vec<String>>,
pub candidate_groups: Option<Vec<String>>,
pub assignment_unresolved: Option<bool>,
pub due_date: Option<Option<String>>,
pub priority: Option<Option<String>>,
pub form_key: Option<Option<String>>,
pub form_fields: Option<Vec<BpmnUserTaskFormField>>,
pub form_validation_disabled: Option<bool>,
}Expand description
PendingUserTask : One <userTask> parked awaiting a human, with the process context needed to act on it (#1104). Every field is read off the persisted process status or the compiled user-task model – there is no claim ledger and no claimed_by, because the engine records no such thing.
Fields§
§instance_id: Uuidthe process instance – the id path segment of the completion operation
workspace_id: String§element_id: Stringthe <userTask> element id – the user_task_id path segment of the completion operation
name: Option<Option<String>><userTask name=\"...\">, the label an author wrote for a human
bpmn_flow_path: Option<Option<String>>§bpmn_version: Option<Option<i64>>§instance_created_at: String§instance_created_by: String§parked_at: Option<Option<String>>When the token arrived at this element, from the engine’s own bounded history. Null for a park older than the retained history.
assignee: Option<Option<String>>flowable:assignee / <humanPerformer>, when written as a literal
owner: Option<Option<String>>§candidate_users: Option<Vec<String>>§candidate_groups: Option<Vec<String>>§assignment_unresolved: Option<bool>The task declares an assignment written as an expression, which this path cannot evaluate. The task is still listed (hiding it would make it unreachable, which is the defect #1104 is about) but a client must not present it as unassigned.
due_date: Option<Option<String>>presentational only – nothing schedules on it
priority: Option<Option<String>>§form_key: Option<Option<String>>flowable:formKey, reported but never resolved (#705 phase 4)
form_fields: Option<Vec<BpmnUserTaskFormField>>§form_validation_disabled: Option<bool>the model set flowable:formFieldValidation=\"false\", so the server will not validate the payload
Implementations§
Source§impl PendingUserTask
impl PendingUserTask
Sourcepub fn new(
instance_id: Uuid,
workspace_id: String,
element_id: String,
instance_created_at: String,
instance_created_by: String,
) -> PendingUserTask
pub fn new( instance_id: Uuid, workspace_id: String, element_id: String, instance_created_at: String, instance_created_by: String, ) -> PendingUserTask
One <userTask> parked awaiting a human, with the process context needed to act on it (#1104). Every field is read off the persisted process status or the compiled user-task model – there is no claim ledger and no claimed_by, because the engine records no such thing.
Trait Implementations§
Source§impl Clone for PendingUserTask
impl Clone for PendingUserTask
Source§fn clone(&self) -> PendingUserTask
fn clone(&self) -> PendingUserTask
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more