Copy the Boilerplate End Points
The boilerplate form calls a set of end points, which should be copied and renamed to match your new task.
First create a new end point group at
Find the end points at

Copy all of the end points in this group into your new group.

Update the getTaskConfig
Your copy of the
taskType - this must match thetaskTypeId abovetaskName - change this to something meaningful for your tasktitleConf - these titles will appear in the Self Service template when users are claiming tasks
For example:
var response = {
success: false,
taskType: "timboilerplate"
};
try {
var configVars = {
"taskConf": {
"taskName": {
"en": "Tim's Boilerplate Task",
"cy": "Tasg Enghraifft"
}
},
"titleConf": {
"timboilerplate": {
"en": "{{caseTaskSummary}}",
"cy": "{{caseTaskSummary}}",
}
},
"formConf": {
"maxFileCountCitizen": 3,
"maxFileCountStaff": 10,
"maxFileSizeCitizen": 3000000,
"maxFileSizeStaff": 5000000,
"maxFileTextCitizen": "3MB",
"maxFileTextStaff": "5MB"
}
};
response.vars = configVars;
response.success = true;
}
End Points Overview
The end points do the following.
| Name | Description |
|---|---|
| addAttachment | Adds an attachment to a caseTask
|
| endTask | This endpoint is called once a task types workflow has been completed
|
| getTaskConfig | Provides the task configuration |
| getTaskData | Returns all of the data relevant to the task which can be used by the task forms. This end point can be edited to retrieve additional data |
| performClaimChangeActions | Updates the case whenever the task is claimed or unclaimed by the task officer |
| removeAttachment | Remove an attachment from a caseTask
|
| startTask | This endpoint is called as part of the initiation phase of the workflow
|
| writeToTaskHistory | Writes updates entered by the task officer into both the case task notes child entities and the case note child entity |
