Question
Handle Parallel Development for Data Tables
Hi,
We have multiple releases and there is a chance that data table attribute/structure might get changed release wise. Since development of these release may overlap each other, is there any way to handle a single data table to support parallel development without affecting the development work of previous release? We don't want to create new table release wise.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
If you mean that two versions of your app on different Pega instances are going to be viewing the same external data records, then both will certainly need both to be prepared to understand the one data record configuration.