orvanta-api 4.1.0

No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

# CmmnCaseSummary

## Properties

Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**id** | [**uuid::Uuid**](uuid::Uuid.md) |  | 
**workspace_id** | **String** |  | 
**cmmn_case_path** | Option<**String**> | The *current* path of the pinned model, resolved through `cmmn_case_model_version`. Reading the value denormalised at start time alone would name the path the case was started at, which a later rename has moved on from. | [optional]
**cmmn_version** | Option<**i64**> | the `cmmn_case_model_version.id` this case resolves its model from | [optional]
**business_key** | Option<**String**> |  | [optional]
**created_at** | **String** |  | 
**created_by** | **String** |  | 
**started_at** | Option<**String**> |  | [optional]
**completed_at** | Option<**String**> |  | [optional]
**job_status** | Option<**String**> |  | [optional]
**canceled_by** | Option<**String**> |  | [optional]
**lifecycle** | Option<**String**> | `case_status.lifecycle`'s tagged `type`, or `null` when the engine has not picked the job up yet. | [optional]
**case_state** | Option<[**models::CmmnCaseState**](CmmnCaseState.md)> | The case's own CMMN state, which can legitimately disagree with `lifecycle` --- an `active` case may carry an `incident`. Both are reported because the badge is derived from both. | [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)