We observed that the number of attributes in the response payload of “Container” service rest, differs between the clone environment and our regular environment. Several attributes are missing in the clone environment, and a few examples are listed below for reference.
During our high-level analysis, we identified that the TransformSROutput_V4 Data Transformation (DT) in the previous version contained a larger set of attributes, whereas the current version includes fewer attributes in the payload.
To move forward, we need your guidance on the following to finalize the better approach.
Should we continue with the attributes present in new RSV, considering they are no longer present in the latest version?
Or should these attributes be added back into the extension DT to maintain compatibility with the earlier payload structure?
Additionally, we will need to cascade this information to all downstream teams/systems to ensure alignment.
Requesting your inputs so we can proceed with the right approach.
Thank you for your response.
We have created this clone environment as part of pega version upgrade activity.
yes, it is a clone of regular stage environment in 25.1.2 version.
Understood from the previous replies that you are cloning the environment as as part of upgrade. Can i check if the upgrade is done in the cloned environment post which you are noticing the changes in DT mentioned in the new RSV? If this is the case, i would recommend to check the release notes of new version you are upgrading to know if there are known changes to be incorporated. I would also recommend to create a support request to debug this while the community will also support with their experience.
We are upgrading from 24.1.3 version to 25.1.2
Yes, all our environments are in sync. Recently, we cloned our Stage environment to version 25.1.2 in order to validate whether the upgrade introduces any issues or impacts existing functionalities.
Recently, we cloned our Stage environment to version 25.1.2 in order to validate whether the upgrade introduces any issues or impacts existing functionalities. During validation we noticed couple of attributes are missing in the response payload of Container service.
Yes, it seems like a known change. TransformSROutput_V4 Data Transformation (DT) in the previous version contained a larger set of attributes, whereas the current version includes fewer attributes in the payload. Hence couple of attributes are missed.
Hi Debasis, is the v4 version of Container used prior to upgrade as well? I have checked inernally and this change has been part of the 23.1 release, which is not a change introduced in 25.1
Thank you for your Response.
If we compare TransformSROutput_V4 DT in PegaMKT-Engine:08-24-01 RSV with PegaMKT-Engine:08-24-51, we will get couple of mappings are removed in the latest version.
PegaMKT-Engine:08-24-51, this RSV is introduced as part of upgrade.
The V4 of the Container services introduced the ability to return SR properties back to the calling channel application based on the calling Channel. The properties that you identified are specific to Agent assisted channels like the Call Center or Retail branch locations. What is the channel you are using for your Container calls in this case?
There is an extension point in the data transform which allows you to add additional properties based on your channels.