Hi,
Is it possible to map work, history_work and some other application specific data classes to different database table in a different database ? If it is not, can we map them to different database table in different schema under same database? I assume it is not possible to separate common tables like assignments, operators etc. So, if we have multiple application for different organizations, at least can we map application specific tables to different schema in a different database?
Thanks.
Multiple database/schema instances specific to application ?
@EngincanY
We don't think Pega's Enterprise architecture works this way. And also pega does not recommend having custom schema for our needs. Even though we have multiple applications in an instance, reports can always be specialized based on the application or any custom need.
If your requirement is purely for reporting purposes, then you can use the Reports database option available in the database rule. We can configure our Report Definition rule to fetch details from the Reports database instead of the actual database.
Let us know if this answers your question or get us some clarity on your need.
ospteam Thank you for your response. My question is actually for storing application specific case data in a separate schema/database. For example, in case of we have different applications for different organizations/division. But anyway, you response is quite helpful for me to understand this.