A recent white paper has been published - IG1332 "How to use ODA using Engagement Management to Realize UI Orchestration".
This document refers to the new concept of UI Markup Language (AML, UI-BML, UI-OML) to "simplify and enhance the creation of interactive and dynamic web applications". It refers to new ODA-Cs called "Navigation Management", "Content Management" and "Channel Management". It also provides sequence diagrams showing the interaction between the EGM block and other ODA functional blocks. However, there is no reference to the Approach B (SoR steer the process) decoupling of the EGM from the other ODA blocks (described in IG1228), which consumes the TMF701 Process Flow API and TMF688 Event Management API. Has this approach B been abandoned now and if so, what is the reasoning behind this?
IG1332 is in a very early phase of its lifespan. It is not yet complete and should be taken as indicative. Our agile sprint approach to deliverables encourages us to distribute content as soon as possible and acquire feedback from the wider membership.
The 701/688 pattern is a wider event mechanism rather than engagement management decoupling, and is intended for business process observability and management. The engagement journey control would build upon the generic SoR flow to personalise the experience. So, we would expect the two mechanisms to work together to provide the final experience.
We will add your concern to our backlog, and find a position upon it.
The engagement call is on a Wednesday, 10am Central European time, and the call details are available from the project calendar page.
Thanks for the reply.