Databases Reference
In-Depth Information
11.5.2.
Data approval process
Logical modeling takes the pragmatic approval processes
in order to make clear their specifications by taking into
account the retained workflow tool. It can be a workflow
available in the MDM system or a generic exterior workflow.
This modeling is reduced and is limited to configuration
rules in the workflow.
11.5.3.
Administrative object
The logical modeling of data follows the same rules as
those retained by semantic modeling (see Chapter 10).
11.5.4.
Transaction
For operations that require a bespoke transactional scope,
it is necessary to foresee the following mechanisms:
− piloting of transactional opening and closure (begin,
commit) by a simple operation configuration. When an
operation fails, then the rollback is automatically
pronounced. In other words, each operation has meta-data
that enables it to decide, depending on the requirements of
its transactional behavior. Therefore, the same operation can
be transactional in an MDM execution context, and not in
another context;
− management of nested transactions. In order to manage
transactions on a scope going beyond a simple CRUD applied
to a single business object, it is necessary to configure the
master/slave functioning of nested transactional operations.
For example, the update operation of a product is master vis-
a-vis other guarantee update operations which are then
slaves. In other words, the beginning and the end of the
transaction is carried by the first operation; the others called
upon during its execution do not open up the transaction.
