This enhancement request is made for CJEU which is implementing large and complex case management system. ER is filed on customer request to be consider for Pega as feature potential to be implemented in platform in future versions.

Context:   

In the context of the SIGA program, we have many platforms and tools that manage data and metadata in their repositories (e.g., MDM, PEGA, MuleSoft AnyPoint, DWH, Pentaho, Qlik Sense, Exalead).  

• A few of these share metadata with other platforms. For example, MDM shares data and metadata via MuleSoft AnyPoint API Interfaces. 
• Additionally, we have the databases for the legacy applications that will be migrated to the PEGA platform and the rest that will not be migrated. The databases that will be migrated contain essential data and metadata, which are very useful for data migration activities in providing the provenance and lineage information for this process. 
• The documentation for different data models and metadata models is also spread in various tools (SAP PowerDesigner), platforms (Confluence), and documents stored on disk (Excel, PowerPoint, Word, Visio, Drawio, PDF documents). 
• All these points above lead to the impossibility of having a 360-degree view of the data, especially of the metadata information. Also, maintaining all this information to prevent duplication, redundancy, consistency, and quality will come with a considerable governance resource effort. 

Below are the metadata requirements for the features/capabilities needed in Pega platform

• As an architect/developer, I need to access (get) the data models metadata for all PEGA applications (at least the conceptual and logical models) via the API services interface preferable. 
• As an architect/developer, I need to have all the data model changes (creates, updates, deletes) propagated automatically via the API services interface, preferably. 
• As an architect/developer, I want to be able to create/update/delete a PEGA data model via metadata API interfaces (advanced). 

Scope: 

• Manage metadata at the unified level via federation, and peer-to-peer, shared exchange, with the option to centralize it physically. 
• This will help us to be much more flexible in defining, developing, and testing different capabilities, functions, and scenarios in this phase. It will help us to structure the requirements for a future metadata management solution at the enterprise level.