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...

Discussion posts and replies are publicly visible

Parents

0 Jonathan Katora
Appian Employee
over 9 years ago

Isaac, glad to see that you are using editable grids. I am not sure about your specific process, but I've created two expressions (see attached) to help you understand how to take the recipe from local variables (in the SAIL recipe) to rule inputs of a CDT data type (for process use). I will refer to them as the parent rule and support rule (support rule= ucItemRowEach).

To test this grid out:
1.) Create a CDT called "CDT_editableGrid" and add 4 elements: id (num(int)), sampleText (text), sampleInteger (num(Int)), sampleDate (date).
2.)Copy the expression in the support...txt file into an interface. Add the rule inputs from the SAIL recipes page. save the rule as uc_itemRowEach (you can name it whatever just make sure to change the name in the parent).
3.) Copy the expression in the parent...txt into another interface and create a rule input called "sampleCDT" of Any Type data type. You should be able to see the data from these (see picture)

In terms of getting this to work with your CDTs, you need to modify the dot notation names for the value/saveInto parameters in the support rule to match your CDT element names. Also make sure in the parent to set the linkField value parameter to your CDT type by using type!YOUR_CDT_NAME()

Hope this helps. Good luck!
Parent Editable Grid with CDT.txt
Parent Editable Grid with CDT.txt
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Jonathan Katora
Appian Employee
over 9 years ago

Isaac, glad to see that you are using editable grids. I am not sure about your specific process, but I've created two expressions (see attached) to help you understand how to take the recipe from local variables (in the SAIL recipe) to rule inputs of a CDT data type (for process use). I will refer to them as the parent rule and support rule (support rule= ucItemRowEach).

To test this grid out:
1.) Create a CDT called "CDT_editableGrid" and add 4 elements: id (num(int)), sampleText (text), sampleInteger (num(Int)), sampleDate (date).
2.)Copy the expression in the support...txt file into an interface. Add the rule inputs from the SAIL recipes page. save the rule as uc_itemRowEach (you can name it whatever just make sure to change the name in the parent).
3.) Copy the expression in the parent...txt into another interface and create a rule input called "sampleCDT" of Any Type data type. You should be able to see the data from these (see picture)

In terms of getting this to work with your CDTs, you need to modify the dot notation names for the value/saveInto parameters in the support rule to match your CDT element names. Also make sure in the parent to set the linkField value parameter to your CDT type by using type!YOUR_CDT_NAME()

Hope this helps. Good luck!
Parent Editable Grid with CDT.txt
Parent Editable Grid with CDT.txt
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data