We have a requirement to change the type of one the field from Integer to Text f

RE: We have a requirement to change the type of one the field from Integer to Text f

karlam — Wed, 24 Feb 2016 19:08:36 GMT

Curious if you found a solution to your issue. I need to update a CDT and I'm just in the development phase and I've already experienced issues with the different versions.

RE: We have a requirement to change the type of one the field from Integer to Text f

RAMASESHU RAVEPATI — Fri, 20 Nov 2015 20:45:53 GMT

Abhi, we have problems with older instances not the newer instances.

how to take care of those older Processes Instances without manually updating the old pv types in the older instances?
or
Is there a way we can do before deploying the application to rectify these errors?

RE: We have a requirement to change the type of one the field from Integer to Text f

abhi.jana — Fri, 20 Nov 2015 02:39:06 GMT

The old instances reference a ^1 which is considered a different type CDT than the original, so process upgrade wouldn't be useful in this scenario. Creating a new pv and replacing the old pv in the original model would work for the upgrade.

RE: We have a requirement to change the type of one the field from Integer to Text f

RAMASESHU RAVEPATI — Thu, 19 Nov 2015 20:03:13 GMT

CDT's with ^1 version doesn't exist in the data types as all the CDT's are deleted. Some how it's the old running processes instances retaining them and throwing an exception!!

RE: We have a requirement to change the type of one the field from Integer to Text f

abhi.jana — Thu, 19 Nov 2015 08:35:02 GMT

It seems process upgrade does not update the type of a pv and does not work when the pv type is different for the process and the target model. I reckon the way to address this would be to create a new pv of the CDT type, replace the ^1 pv with this new pv everywhere in the model and then run the upgrade. The ^1 pv remains but this way you can ensure that it is not used.

RE: We have a requirement to change the type of one the field from Integer to Text f

RAMASESHU RAVEPATI — Wed, 18 Nov 2015 22:00:55 GMT

Attached file is the Log File with Errors

Issue Log.txt

RE: We have a requirement to change the type of one the field from Integer to Text f

RAMASESHU RAVEPATI — Wed, 18 Nov 2015 21:53:49 GMT

Thank you Abhi, Your advice resolved the new functionality and process variable issues to UI.
We are facing another issue which we are yet to resolve,
Issue: 1. When we deployed the application from DEV to Test with the changes in existing CDT's, the application failed to deploy with error log attached.
2. So we deleted the Existing old CDT's from Test Environment and redeployed the application again, which in turn resolved the deployment issue.
3. Running Processes in the TEST started using the older version of CDT's with "^version" (EX: Root as Root^1).
4. Process upgrade smart service is not handling the CDT changes with ^ versions.
All these CDT's are consumed by the Webservices, So the option of changing the Name of CDT's is not viable for us.
Please advice,
thank you
Rama

First Notice Of Loss.import-log.txt

RE: We have a requirement to change the type of one the field from Integer to Text f

abhi.jana — Wed, 18 Nov 2015 02:43:00 GMT

Existing processes reference the previous version of the model and will not be updated automatically after impact analysis. You can run forum.appian.com/.../Process_Upgrade.html for this purpose.

RE: We have a requirement to change the type of one the field from Integer to Text f

RAMASESHU RAVEPATI — Wed, 18 Nov 2015 00:45:04 GMT

Thank you Nick,
We are on 7.10 right now. I updated the outdated dependents, but the older running processes instances have ^versions to them. For Example, Cdt with name ROOT got updated with ROOT^1.

RE: We have a requirement to change the type of one the field from Integer to Text f

Nick Vigilante — Tue, 17 Nov 2015 23:31:55 GMT

I tested this out in 7.11 and was unable to reproduce the issue. What version are you testing this in? Did you make sure all outdated dependents were updated appropriately? Can you please provide screenshots demonstrating the behavior you're experiencing?