In general Pega uses Org/Div/Unit level hierarchy while building a App using Application Express Wizard.But Pega has provided a Separate Landing Page for Operational Structure and Taxonomy,what is importance and advantages of this Landing Pages in the CLM.
And during a Application Development Phase where should we take this Piece of work.
Note:I mean at Foundational level or after a few releases into Prod.
Hi Dileep, the Operational Structure landing page is provided to support the way PFFS and CLM have extended the purpose of the Org/Div/Unit structures to facilitate a flexible and scalable structure that consuming applications (like CLM) can make use of for work routing and other purposes.
For example in CLM, the application uses the Country and Booking Entity parts of the Operational Structure to filter down the Product Matrix so that operators are only presented with the products that they are allowed to work with.
Another example is how the routing logic is implemented on the each Assignment. CLM ships with a set of specific router rules that interrogate the Operational Structure to dynamically work out how to route each assignment.
The advantage for CLM is that it makes the application very flexible and agile for purposes like global roll-outs, operational change and so on.
It also gives the business a very visual landing page to see their operation.
The Operational Structure should be considered very early on in any CLM implementation project, as a well designed taxonomy and populated structure will give the system a level of resilience to planned and unplanned operational change going forward.