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
3 replies
Subscribers
4 subscribers
Views
1485 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Hello to all, This is a question I was meaning to ask for some time n
nikolaosm
over 8 years ago
Hello to all,
This is a question I was meaning to ask for some time now. When monitoring a running instance of a process you have the option in Appian to modify the process variables values of the instance.
However, if the process variable you are examining is a CDT, you do not have the option in the monitor UI to modify the process variable value. At least this is the case in version 7.8 that we are using.
What is the way to solve problems that arise when you need to modify the value of the CDT?
Regards,
Nikos
OriginalPostID-168743
OriginalPostID-168743
Discussion posts and replies are publicly visible
Parents
0
ryanh
over 8 years ago
I agree that it would be nice to have that functionality in place. We haven't used the component Eduardo references (I'll have to read up on it). We do however frequently have to use his first suggestion. We edit the individually running/broken process and add a new script task. We set individual values in the CDT in the data output tab and then map the node to run the 'broken' node next. Save the edited version, close it, open the process and cancel the invalid node and restart the process on the new script node.
There are a few issues with this solution, but it works for most cases: nodes with MNI, crashes with XORs (because adding the new node that calls the XOR causes multiple input paths to the XOR, use a dummy node first before XORs if possible or have the new node call the one before the XOR), funky logic that you may not want to run twice, etc. (i.e. if the node that broke already altered data that shouldn't be altered twice). This helps us solve the majority of our invalid CDT values in prod when they occur.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
ryanh
over 8 years ago
I agree that it would be nice to have that functionality in place. We haven't used the component Eduardo references (I'll have to read up on it). We do however frequently have to use his first suggestion. We edit the individually running/broken process and add a new script task. We set individual values in the CDT in the data output tab and then map the node to run the 'broken' node next. Save the edited version, close it, open the process and cancel the invalid node and restart the process on the new script node.
There are a few issues with this solution, but it works for most cases: nodes with MNI, crashes with XORs (because adding the new node that calls the XOR causes multiple input paths to the XOR, use a dummy node first before XORs if possible or have the new node call the one before the XOR), funky logic that you may not want to run twice, etc. (i.e. if the node that broke already altered data that shouldn't be altered twice). This helps us solve the majority of our invalid CDT values in prod when they occur.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data