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
5 replies
Subscribers
7 subscribers
Views
2269 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
User Interface
My organization and I are relatively new to Appian and are working on building o
isaace
Certified Associate Developer
over 9 years ago
My organization and I are relatively new to Appian and are working on building our first SAIL interfaces. We have a business need for users to be able to complete tables of varying lengths. I started with the SAIL recipe for an Inline Editable Grid and I have no problems creating the table and it's supporting expression, ucItemRowEach.
However, I am running into difficulties writing the data in that table to my process. The instructions from the recipe include creating a CDT "for items with the same fields as in the example" as well as replacing the local!items with an ri!items. I have not been able to persist data from the table to the "main interface" ri!items and thus to my process. Could someone provide an example of a ucItemRowEach expression and a "main interface" expression that has been modified with the intention of writing to process?
I am still uncertain as to whether the data will come from the "main interface" ri!items or from the ucItemR...
OriginalPostID-146157
OriginalPostID-146157
Discussion posts and replies are publicly visible
Parents
0
Jin Pheh
Certified Associate Developer
over 9 years ago
the "main interface" in this case refers to the parent SAIL rule which calls row building rule you created.
In order to get information from the row level rule to the parent you have to pass the information via a rule input. The same mechanism is used to get information from the main interface rule to the process model - when you configure the user input node with the main interface rule you have to provide rule inputs to that rule - once the user submits the form the rule inputs you specified will be populated with your information.
Be sure that when you configure the form node with the rule and arguments that you use Activity Parameters which save to Process Variables - a form expression cannot save directly to a process variable so the intermediate Activity Parameter step is needed.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Jin Pheh
Certified Associate Developer
over 9 years ago
the "main interface" in this case refers to the parent SAIL rule which calls row building rule you created.
In order to get information from the row level rule to the parent you have to pass the information via a rule input. The same mechanism is used to get information from the main interface rule to the process model - when you configure the user input node with the main interface rule you have to provide rule inputs to that rule - once the user submits the form the rule inputs you specified will be populated with your information.
Be sure that when you configure the form node with the rule and arguments that you use Activity Parameters which save to Process Variables - a form expression cannot save directly to a process variable so the intermediate Activity Parameter step is needed.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data