Handle Aged Updates, schema change in deployment using prpcServiceUtils
In Pega 7.2.2, when we use prpcServiceUtils for deployment, aged updates are going in and replacing newer rules. Is there a way to handle that from command line? And we have no chance to skip any Schema Change, then after the import we must change it manually, it hindert our release automation process.
Is there any possibilty to check the product content when we use the prpcserviceutil.sh?
i have still a question about the setting "import.existingInstances=skip". This property was set as "skip" by default, it means Skip instances that already exist in different rulesets or versions. But how could the aged updates be verified/handelt? Or it means the aged update would not be imported with this settings?