> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/workflows/designing-workflows/processes/shape-repository/service-task/delegates/assessment-delegates.md).

# Assessment delegates

{% hint style="warning" %}
Assessment delegates use the Assessments Java API v1, which is deprecated. For new workflow implementations, use the [Collibra API Task](/workflows/designing-workflows/processes/shape-repository/collibra-api-task.md) instead.
{% endhint %}

Assessment delegates are service task delegates that connect a workflow process to the assessments service. They let a workflow request that an assessment be started or retrieved for a given use case, and read back the assessment answers as process variables.

## ConductAssessmentDelegate

Starts or requests the start of an assessment for a use case. Place this delegate on a service task where the process needs to hand off to the assessments service so a steward or reviewer can complete an assessment for the use case asset currently in scope.

### Properties

| Property       | Value                                                                         |
| -------------- | ----------------------------------------------------------------------------- |
| Type           | Service Task                                                                  |
| Java class     | `com.collibra.assessments.api.v1.workflow.delegate.ConductAssessmentDelegate` |
| Implementation | `org.flowable.engine.delegate.JavaDelegate`                                   |

### Input parameters

| Field name       | Type   | Required | Description                                                                                                                                                                                                                                                                             | Example                                  |
| ---------------- | ------ | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- |
| `useCaseOwnerId` | String | Yes      | The ID of the use case owner the assessment is assigned to or conducted on behalf of. If not set, the workflow user is assigned as the assessment owner. Always set this variable explicitly before the process reaches this task to ensure the intended user is assigned as the owner. | `"a1b2c3d4-0000-4a4a-8b8b-000000000001"` |
| `useCaseAssetId` | String | Yes      | The ID of the use case asset the assessment applies to.                                                                                                                                                                                                                                 | `"f1e2d3c4-0000-4a4a-8b8b-000000000002"` |

Both variables are read from the execution as-is. The delegate does not validate their presence or type, so upstream tasks in the process must set them before this service task is reached.

### Output

None. This delegate does not set any process variables. It sends a notification to the assessments service to start the assessment. The resulting assessment is later retrieved via a separate delegate once it has been completed: [GetAssessmentDelegate](#getassessmentdelegate).

### Usage

Ensure `useCaseOwnerId` and `useCaseAssetId` are already set on the execution, typically by a preceding script task or form submission, before the process reaches this task.

## GetAssessmentDelegate

`GetAssessmentDelegate` is the counterpart read delegate to `ConductAssessmentDelegate`. Where `ConductAssessmentDelegate` pushes a request to start an assessment, `GetAssessmentDelegate` pulls back the answers from a completed assessment, including template, content, and linked asset, into a result process variable for the process to branch on or persist.

### Properties

| Property       | Value                                                                     |
| -------------- | ------------------------------------------------------------------------- |
| Type           | Service Task                                                              |
| Java class     | `com.collibra.assessments.api.v1.workflow.delegate.GetAssessmentDelegate` |
| Implementation | `org.flowable.engine.delegate.JavaDelegate`                               |

### Input parameters

| Field name       | Type   | Required | Description                                             | Example                                  |
| ---------------- | ------ | -------- | ------------------------------------------------------- | ---------------------------------------- |
| `useCaseAssetId` | String | Yes      | The ID of the use case asset the assessment applies to. | `"f1e2d3c4-0000-4a4a-8b8b-000000000002"` |

### Output

Sets the `result` process variable containing the completed assessment data, including the assessment template, content, and linked asset. Use this variable in subsequent tasks to branch the process or persist the results.

### Usage

Place this delegate on a service task that follows the user task or intermediate event where the assessment is completed. Ensure the assessment initiated by `ConductAssessmentDelegate` has been completed before the token reaches this task.

```xml
<serviceTask id="getAssessment"
             name="Get assessment"
             flowable:delegateExpression="${getAssessmentDelegate}" />
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.collibra.com/workflows/designing-workflows/processes/shape-repository/service-task/delegates/assessment-delegates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.