Related terms
A Federated Case Management Repository (FCMR) serves as a centralized repository for cases and work performed by users in a federation. The FCMR consolidates work items and makes them available to all users in the federation.
Users in a federation work in their local application portal, which can display cases and assignments from other applications in the federation. Each local application processes and maintains its own cases and data, and publishes data to the FCMR.
The FCMR contains class tables for federated versions of key classes, such as Work-Federated and Assign-Worklist-Federated. Instances of the federated classes serve as lightweight pointers to class instances residing in a federation’s local application databases.
Federated classes in the repository contain no BLOB fields, only a handful of key properties such as ID and status needed to identify and open each case in its local application. The full data for a case resides in only one place, its local application database, and all processing for that case occurs within its local application, even when that processing is being done by a user within a remote application portal.
Local applications update the FCMR whenever case and assignment data change. If the FCMR is unavailable for updates, the applications queue the changes to the FCMR agents: FCMRSave, FCMRSaveAssignWorkList, and FCMRSaveAssignWorkBasket. These agents update the FCMR when it is available to ensure that the application data and FCMR is always in sync.
Caution:
Disabling the FCMR queue agents might result in data loss.