EDC introduces a new dimension to rule execution. When EDC is not used, data management during Decision Service execution is relatively straight-forward: incoming data contained in the request payload is modified by rules and the resulting updated state for all objects is returned in the response.
However, when EDC is used, data management becomes more complicated. How is data in the database synchronized with the data contained in the request payload and data produced or updated by Decision Service execution? Using several scenarios, this section describes the algorithms used by Corticon Server to perform this synchronization. All scenarios use the familiar Cargo.ecore, which was connected to a database in the Corticon EDC: Enterprise Data Connector guide. If you have not reviewed that guide, we highly recommend doing so before continuing, as this section builds on the concepts introduced there.
Figure 322. Cargo.ecore with Database Connection and Mappings
The sample Rulesheet we will use is defined as shown:
Figure 323. Sample Rulesheet for Synchronization Examples
Note: The RDBMS data in this section was established in the EDC Tutorial into a Microsoft SQL Server 2014 installation. The data was extended in the "Testing the Rulesheet with Database Access enabled" topic in the Rule Modeling Guide to add and populate the data that is described in this chapter's topics.
