Which is best practice of the location of class for external database - Int or Data
Hi,
Let's say we have a class for CIF (Customer Information File) which resides outside of Pega. We do mapping between table outside and class in Pega. This is very typical use case but which is correct or best practice - MyCo-Data-CIF or MyCo-Int-CIF. I know both works without any issue and makes no difference but for standardization purpose I want to know what is standard, and the reasons behind.
***Updated by moderator: Lochan to update platform capability***
Thanks,g
Hi,
It is very surprising because my expectation was Int. The external database class mapping wizard (see below) creates class under MyCo-Int class so I thought that is Pega's standard way. If Data is standard, why doesn't product make a class under MyCo-Data class?
Thanks,
Anyone has any comment? A comment from product management team is much appreciated.
Thanks,
Hi There,
I think "data" would be the better option. The int is used for keeping integration artifacts and this is no integration. Pega CRM used external marketing data and they also keep it in "-data-". So, keeping in data is more appropriate and convincing.