The various dates (and any associated intervals) can be adjusted using the call described below.
If a field is missing or set to NULL it will be skipped.
The Update method here is preferred to the Update method on the DatesController.
The following models are used:
| Name | Type | Description | Optional |
|---|---|---|---|
| OrderId | String | Order Id | |
| Steps | List<StepsStepModel> | Start-/EndDate changes for individual steps. | yes |
| Name | Type | Description | Optional |
|---|---|---|---|
| StepNumber | Int | Step number. Please note that the step number is 0-based. The first step is called 0, the second is called 1 and so forth. | |
| StartDate | DateTime | The start date of this step. Please note that only the date part will be used. The time part will be zeroed. | yes |
| EndDate | DateTime | The end date of this step. Please note that only the date part will be used. The time part will be zeroed. | yes |
| ReminderDate | DateTime | The first/next reminder of this step. Please note that only the date part will be used. The time part will be zeroed. | yes |
| ReminderInterval | Int | Number of days to next and subsequent reminders for this step. | yes |
| RequiredToSign | Int | Number of signers on this step required to sign. 0 - all. | yes |
| SignerGroups | Dictionary<SignerGroupModel> | Update Signer Groups - overrides RequiredToSign. | yes |
Update dates, associated intervals and/or RequiredToSign on the steps of the order.
POST api.esignatur.dk/Steps/Update
{
"OrderId": "bf63812e-0297-4494-9726-cfe0d5ff84a2",
"Steps": [
{
"StepNumber": 0,
"EndDate": "2023-06-07T02:33:11.4894266+02:00",
"RequiredToSign": 2
}
]
}