For the complete documentation index, see llms.txt. This page is also available as Markdown.

Case Repository - use in low-code

Low-code integration with Case Repository

The functionality for adding new entries to Case Repository is available for scripts (scriptService) and script tasks (scriptTask).

Low-Code API for Case Repository

Eximee Case Repository serves as the central repository of customer cases, aggregating information from many channels and systems into a unified data model. In the context of the low-code platform, the API enables standardized integration of processes, forms, and services with the case repository so that status and event data are consistent, up-to-date, and available across applications.

The integration is based on an event-driven model, which allows data to be published and updated in real time, regardless of where the process is initiated. This makes it possible to build a unified customer case view (omnichannel), support automation, and ensure service continuity across customer and internal channels.

This section describes how to use the low-code API to communicate with Case Repository, including data publication rules, object model requirements Case.

Detailed description of the role, architecture, and data model Eximee Case Repository is found in the document describing the assumptions Case Repository.

Creating a new case status

Method create creates a new case status entry in Case Repository.

Required fields:

  • caseType - case type,

  • client - customer identifier,

  • clientType - customer identifier type,

  • status - current case status.

Field statusDescription is optional and is used to extend the status description.

Field caseId is optional and is used to manually assign a case identifier. The value can be any string, however due to the uniqueness requirement it is recommended to use Random.uuid(). If we do not fill in the field caseId, the system will generate a unique identifier automatically.

Field source is filled by default with the value "eximee" for all entries created from the low-code platform. Field caseType is filled by default with the application name for all entries created from the low-code platform.

Example:

Modifying an existing case status

Method update updates the status of an existing case. The request should include only the fields to be changed. The operation modifies all statuses assigned to the given case.

Example of updating the status and description:

Deleting a case status

Method delete removes all statuses assigned to the given case. The operation is irreversible.

Retrieving the current case status

Method get retrieves the current case status.

Sample response:

Searching for a case status

Method search allows searching for case statuses based on the provided filters. Filters can be combined freely, and the results are paginated. A logical product (AND) is used between different filter fields, which means that only records meeting all the specified conditions are returned.

Example usage:

Sample response:

Last updated

Was this helpful?