I have two questions according to the "Financial Services -> Operational Structure" wizard, which creates operational model of organization-division-unit in CLM/KYC Strategic Applications.
1. Why organization created from operational structure wizard doesn't allow for reuse of existing standard organization created in different application, not built on Pega FS? We have a Customer Service implementation, where standard organization was created, but CLM application requires different one, with extra properties in a BLOB added by wizard, which developer is not able to set from Designer Studio.
2. Why workgroup/workbasket created in operational structure wizard has to contain organization structure in the description and ID e.g. CIT_Commercial_US_Bank_Customer Onboarding?
With regards to reusing orgs created outside of the operational structure landing page that is something that is currently not supported. This functionality is owned by the Pega Foundation for Financial Services (PFFS) team and exists as a backlog item. It have been explored in the past, but hasn’t made it to a high enough priority to get built.
can you help in understanding the importance of the operating structure in Pega CLM. we have already defined our Organisation /div/unit while creating Application using App wizard.But when trying to include in operational landing page its throwing error saying it already exists in system.
so is good to skip using the operational structure.
The problem is, that you can’t reuse it. You need to create a new one e.g. with suffix FS. Organization created by this wizard has a lot of of extra properties in a BLOB, used later on by CLM, so you need to have one created by this wizard to be able to see portal and to create a new case. This is a problem, which I addressed to the product team, as reuse of the standard Pega organization is not possible and it’s a design of Pega for Financial Services strategic app.