We have categorization information in a framework for use by multiple applications. This information includes structure such as the associated Data Types, Data Pages, Data Transforms, etc., as well as the actual data itself (currently stored in Pega tables, could be placed externally if needed).
What we want is for the data to be versioned with the framework so that applications that use the framework only see changes to the data when they adopt the new version of the framework. As far as we understand Pega's data management, the reality is that changes to the data will be immediately seen by applications using the framework.
Our current approach is for applications using the framework to only access the data via versioned rules and those rules will select a versioned dataset based on the version of the rule or framework. The versioning of the dataset will be managed manually and new versions will be generated infrequently so the data management is not a significant burden.
I am curious if anyone else has dealt with scenarios like this before and what approaches they may have tried.
Currently the data is not versioned. Conceptually, it will be a simple V1, V2, V3, etc. ID values will be maintained between versions as much as possible. With each version there would be a change log that downstream developers can use to identify possible changes they need to make to their own implementations to use the new version of the data set.