# PendingUserTask
## Properties
**instance_id** | [**uuid::Uuid**](uuid::Uuid.md) | the process instance -- the `id` path segment of the completion operation |
**workspace_id** | **String** | |
**element_id** | **String** | the `<userTask>` element id -- the `user_task_id` path segment of the completion operation |
**token_id** | [**uuid::Uuid**](uuid::Uuid.md) | The parked token -- the park itself, and what a claim is taken on (#1123). A multi-instance or parallel-branch task parks several tokens at one element, each with its own resolved identity and its own claim, so `(instance_id, element_id)` does not identify one of them. Pass this as `token_id` to the claim and release operations when an element holds more than one park. |
**name** | Option<**String**> | `<userTask name=\"...\">`, the label an author wrote for a human | [optional]
**bpmn_flow_path** | Option<**String**> | | [optional]
**bpmn_version** | Option<**i64**> | | [optional]
**instance_created_at** | **String** | |
**instance_created_by** | **String** | |
**parked_at** | 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. | [optional]
**assignee** | Option<**String**> | `flowable:assignee` / `<humanPerformer>` -- the name the engine resolved at park time when the assignment was written as an expression, the declared literal otherwise (#1123). | [optional]
**owner** | Option<**String**> | `flowable:owner`, same rule as `assignee` | [optional]
**candidate_users** | Option<**Vec<String>**> | | [optional]
**candidate_groups** | Option<**Vec<String>**> | | [optional]
**assignment_unresolved** | Option<**bool**> | The task declares an assignment that could **not** be turned into a name -- an expression the engine's park-time resolution refused, or a task whose token parked before #1123 shipped. 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. An expression the engine *did* resolve is not flagged: the identity fields above carry the answer. | [optional]
**unresolved_assignments** | Option<[**Vec<models::BpmnUnresolvedAssignment>**](BpmnUnresolvedAssignment.md)> | Each refused expression with the reason it could not be read, so a client can say *why* rather than only *that*. Empty when there is nothing to refuse, and for a token parked before #1123 shipped (which carries no resolution record at all). | [optional]
**identity_resolved_at** | Option<**String**> | When the engine decided this task's identity. Present exactly when a park-time resolution record exists; absent means the identity was read from the static model, which for a literal assignment is the same answer arrived at a different way. | [optional]
**claimed_by** | Option<**String**> | Who has taken responsibility for this park (#1123). Absent means unclaimed, which is the ordinary state -- claiming is optional and an unclaimed task is completable by anyone in its audience. A claimed task is still listed for everyone in its audience, so they can see it is taken; only its holder and admins may complete it. | [optional]
**claimed_at** | Option<**String**> | | [optional]
**due_date** | Option<**String**> | presentational only -- nothing schedules on it | [optional]
**priority** | Option<**String**> | | [optional]
**form_key** | Option<**String**> | `flowable:formKey` -- the key exactly as the model wrote it, always reported so a client can name the external form whether or not it resolved. Before 6.0.0 a resolved key (via a `bpmn_form_binding` row) or `orvanta:formRef` could each name an Orvanta app to render in place of `form_fields`, surfaced as `resolved_form_ref` / `form_ref`. Apps were removed (#1720) and both fields with them (#1759): a key now only ever falls back to `form_fields`. | [optional]
**form_fields** | Option<[**Vec<models::BpmnUserTaskFormField>**](BpmnUserTaskFormField.md)> | | [optional]
**form_validation_disabled** | Option<**bool**> | the model set `flowable:formFieldValidation=\"false\"`, so the server will not validate the payload | [optional]
[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)