Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
17 replies
Subscribers
6 subscribers
Views
8842 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
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?...
OriginalPostID-71541
OriginalPostID-71541
Discussion posts and replies are publicly visible
Parents
0
danielh366
over 11 years ago
I did notice in the XSD for the updated CDT, that besides the updated VARCHAR length there was a differing <xsd:schema/> parameter.
Instead of reading "xmlns:types1=..." like on the DEV server, it reads: "xmlns:types2=..." on PROD.
But all the CDT's seem to have similar variations.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
danielh366
over 11 years ago
I did notice in the XSD for the updated CDT, that besides the updated VARCHAR length there was a differing <xsd:schema/> parameter.
Instead of reading "xmlns:types1=..." like on the DEV server, it reads: "xmlns:types2=..." on PROD.
But all the CDT's seem to have similar variations.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data