We get a lot of questions from the ecosystem about the Common Application / Common Data model. So we have an upcoming webinar planned for the User Experience Expert Circle where you can Ask the Experts.
We plan to cover some basics like:
What is it? What’s its intent? What value? Real life implementations? Who is using it?
When would i use it? Why would I use? How do i begin using it?
Lessons learnt
Where do you get more information?
Ask the experts
Please reply to this thread if you would like to ask a question about the Common Application that you would like to see answered by our panel of experts.
I’d like to ask the panel how we enable delegation using Common Application entities and data structures. This is a recurring requirement in strategic applications, where customers seek granular control over their visibility and access.
Could we have documentation/explanation on the correct way of overriding the OOTB data pages for entities particularly when we would connect to external API(not REST) to source our data only for a few entities. For instance, there is OOTB data page of D_Entity_Search that actually looks generalized to search many entities. In our case, we want to connect to an external API to source our contact information. We have no need to store our contact in the common LDM contact class, and no need to be strongly tied to pyGUID as our contacts have a different unique identifier. The Search and select patterns and the subsequent data pages look to be very strongly tied to Entity class,pyGUID and the way to go ahead in our situation isnt easy to understand. Advise on approach would be much appreciated. We want to override how we source lets say only contacts and account, but have no need/use of the other entities . In such a situation what would you advise as an approach.
Some organization have developed their in house Data models over the years and they do not align with the Common data model. What would be the advise for them? Considering they have invested heavily and developed multiple applications using their data model, trying to either expand the common data model to fit their needs or trying to change their existing data model to fit into the common data model both looks to be significant amount of work.
I have another question for the panel. In case all my CRUD operations on entity is managed via integration, how does Common Application supports saving the data back to the integrating system. Is there a placeholder to configure save plan ?
@MarcCheong Most of the common app documentation says this disclaimer “As a reminder, using the Common Application is not mandatory when building applications directly on Platform. For strategic applications (for example, Customer Service) that are built using the Common Application, please refer to the respective application’s instructions for mandatory uses.” e.g. Pegasystems Documentation. However the product documentation doesn’t call out anything about common application in CS - Pegasystems Documentation
How are we supposed to make decisions whether to use common application or not for CS constellation implementation ? of course we found dependencies for d_entity_search and adopted it but having a clear documentation increases the adoption rate.
After adopting CDM for CS implementation, now, there is no clear documentation about CDM when clients want to use SORs to fetch the data. E.g. D_Account, D_Account_List, which is over 90% of the implementations. Of course we figured out and used Account_SOR condition, but we are building new apps based on assumptions rather than a trustworthy product documentation. Please help us with fixing the documentation problems to reduce our build cycles, and to increase the adoption rates for CDM.
@ravi9779 this is an old conversation, asking for questions before our Webinar in September. The replay can be found here:
I’ll pass your feedback on, from above to make sure it gets attention.
if you have new questions, please raise a new conversation on our Expert Circle to ensure it gets visibility, it is more likely to be viewed by our members on our home page as only those who liked or commented on this one will be notified about this post.