I recently updated a CDT, which is referenced in a process model subprocess. The

danielh366 over 11 years ago

I recently updated a CDT, which is referenced in a process model subprocess. The CDT is passed by reference to the subprocess.

Existing processes on my development server are now broken because they can't call the subprocess with the older version of the CDT. The error message reads: "The following process process parameters were of the incorrect type: ...". The newer version has minimal changes: I just updated the VARCHAR size of a text field.

I have never had issues like this before, even when adding new fields to a CDT. I am very concerned about pushing this build to our production server. Is this a problem with Appian 7.2? Is there any way I can fix the broken processes?...

Discussion posts and replies are publicly visible

Parents

0 danielh366 over 11 years ago

I just tried the following:
1. Start a process (A) with one version of CDT with VARCHAR 1000 set for a field
2. Update the CDT to VARCHAR 2000 for that field
3. Run a sub-process from process A to get the error
4. Start another process (B) with the updated CDT
5. Change the CDT back to VARCHAR 1000 for the field
6. Run a sub-process from Process B to get the error
7. Re-run sub-process from Process A to see what happens

No dice: even with the original VARCHAR setting, Process A fails. It doesn't matter if the CDT specification matches exactly.

My last hope, before facing a production nightmare, is to omit the CDT's from the application export, in hopes that on import to production, both the updated process models and existing processes will reference the unchanged CDT's in production.

We have no staging server, so I'll have to try to test this out on Dev first.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 danielh366 over 11 years ago

I just tried the following:
1. Start a process (A) with one version of CDT with VARCHAR 1000 set for a field
2. Update the CDT to VARCHAR 2000 for that field
3. Run a sub-process from process A to get the error
4. Start another process (B) with the updated CDT
5. Change the CDT back to VARCHAR 1000 for the field
6. Run a sub-process from Process B to get the error
7. Re-run sub-process from Process A to see what happens

No dice: even with the original VARCHAR setting, Process A fails. It doesn't matter if the CDT specification matches exactly.

My last hope, before facing a production nightmare, is to omit the CDT's from the application export, in hopes that on import to production, both the updated process models and existing processes will reference the unchanged CDT's in production.

We have no staging server, so I'll have to try to test this out on Dev first.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data