Question
Kavileswar
IN
Last activity: 4 Oct 2018 13:54 EDT
Type change for existing property
Pega 7.1.9 Platform - Suppose there is one property <GroupNumber> is created with integer data type in 01-01-01 version and assume code moved to QA env too.
Now my current running version is 01-01-04, as per latest changes, need to change the data type to Text. It won’t allow us to change the data type even withdrawn in 01-01-04 version and try to create a new one with same name .
It allows us to create a new one with the same name if we withdrawn in current version and create in super class or next immediate class.
Is there any feasible solution for this to change the data type of existing property
***Updated by moderator: Lochan to add Categories***
**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.
Pegasystems Inc.
IN
Hi,
If you want to change the property type in 01-01-04, you must withdraw the property in lower versions such as 01-01-03.
As you want to save the property in the same class as before, you can withdraw the property in lower version.
Ex: 01-01-03 Withdraw
01-01-04 New Type
or
01-01-04 Withdraw
01-01-05 New Type
Pegasystems Inc.
IN
One word of caution here. This can prove a little trickyy , for reasons of backward compatibility. The change could affect the schema datatype and potentially require data conversion. If the property is referenced in activities and other rules, at least some of those rules may depend on the type of the property, producing different results for different types.
Additionally, if the property is referenced in Java code, the code may malfunction as a result of the type change.
If you are sure that no processing is using the property, you can delete the property or skim to your version that contains the correct property type However, if you have a version in production, and think you need to make a change to a property type, it is usually better to create a new property (with a distinct name) of the new type and transition to the new property.
Kavileswar
IN
Pega7.1.9 does not allow to create a property with the same name and apply to class,even if we withdraw in 01-01-03 and try to create in 01-01-04
This prop being refered in many places
Pegasystems Inc.
IN
Hi There,
What happens when you create a new Report Definition including those properties.
In case it works fine you may have to re-save and validate the old Report.
Thanks,
Ujjwal
Sopra Steria Group
FR
Hi, I have the same problem as well, in version 7.3.1, on an abstract class (the problem with converting existing data doesn't apply here.)