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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Introduction

In DCM2, DCM Lists Service is providing information to DCM Dashboard about Cases. For some reason, DCM Lists can lose data, which can be fixed by using "Restore dcm-lists service" functionality. DCM Lists can have all Cases restored at once or single case can be restored as well. Under the hood, Maintenance App will send 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:

  • User that uses DCM Maintenance App, needs to have the Role "owner"
  • Case Engine needs to have indexing enabled - more information in https://my.blueriq.com/x/BwKLCw page

Triggering "Restore dcm-lists Service"

All cases

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

The 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 single case:

  • open "Cases" tab
  • look for specific case
  • scroll down to "Actions" section
  • Push button "Restore dcm-lists for this case"



  • No labels