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
6 replies
Subscribers
6 subscribers
Views
2227 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Hello, I am wondering if it is possible to populate a CDT in the Inpu
issamd
over 10 years ago
Hello,
I am wondering if it is possible to populate a CDT in the Input tab and then populate one field in that CDT in the Output tab.
For example: Let's say I have a CDT called Employee and I use a query rule to populate the employee name in Input. In output I want to populate Employee.Nickname using an expression. How can I do this?...
OriginalPostID-121975
OriginalPostID-121975
Discussion posts and replies are publicly visible
0
elizabeth.epstein
over 10 years ago
You can reference Node Inputs as ac!myInputName in the Node Outputs.
So if your Node Input is called Employee, then in Node Outputs you can use =someExpression(ac!Employee.name) and save to just the Nickname field of an Employee type PV.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Ricardo Galvan
Appian Employee
over 10 years ago
Please see the following reference to know the difference between the two tabs:
forum.appian.com/.../Data_Tab.html
This will help you understand the difference in concepts and aid you in the example you have provided
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
issamd
over 10 years ago
I've attached a screenshot of the expression and that it saves into the correct PV. When I run the process it still does not populate the PV in the output.
Also, thank you for that reference, Ricardo. I understand the difference between the two but I can't seem to populate a CDT that I just populated in the same script task.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Terri McCormick
Appian Employee
over 10 years ago
A common mistake I see is populating the inputs at the parent level and the outputs at the individual attribute level. This creates a race condition. You must either populate the entire CDT from ac!myCTD to pv!myCDT (typically on the inputs) or populate the pieces: ac!myCDT.name to pv!myCDT.name which can be on inputs or outputs.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
elizabeth.epstein
over 10 years ago
Terri is right. If you are *also* saving your input directly to a PV, you can't try to save the outputs to that same PV (or fields within it.)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
issamd
over 10 years ago
I see, this answers my question, thanks everyone!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel