You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.

Introduction

In DCM2, the DCM Lists Service is providing overviews of cases and tasks to the Runtime. If, for some reason, the DCM Lists Service lost data, it can be fixed by using the "Restore dcm-lists service" functionality in the DCM Maintenance App. The Maintenance App can restore all cases at once or single case as well. Under the hood, the DCM Maintenance App will send an HTTP request to Case Engine, which will trigger each known case to restore itself in the DCM Lists Service. 

Prerequisites

Before using the "Restore dcm-lists service," ensure the following prerequisites are met:

  • The user that uses DCM Maintenance App, needs to have the Role "owner".
  • The Case Engine needs to have indexing enabled. You can find more information on initial indexing here: Initial indexing.
  • Make sure that the Runtime isn't currently used by users.

Triggering "Restore dcm-lists Service"

All cases

To trigger the "Restore dcm-lists Service" for all cases, open "General" tab in the DCM Maintenance App and click the "Restore dcm-lists for all cases" button.

This action restores all cases in the DCM-Lists service. The data of each single case will be retrieved and sent to the DCM Lists service. This may lead to a high system load when there are many cases in the database. The system might be busy for a while, possibly leading to a delay in other actions.

Single case

To trigger a single case:

  • Open the "Cases" tab.
  • Find the specific case.
  • Scroll down to "Actions" section.
  • Push the button "Restore dcm-lists for this case".



Didn't find the answer you were looking for? Try the advanced search!