Dynamic interfaces using grids

RE: Dynamic interfaces using grids

Domen Jemec — Wed, 31 Oct 2018 16:01:13 GMT

Hi Eric,
Unless multiple dependent smart service calls or complex data processing needs to be done between drill in - out, the load variable method allows for a simpler solution to this issue. Consider using Choose() instead of nested ifs to create a frameworks that can rapidly scale simply.

For user experience, there are a few different guides outlined in the US design guide
docs.appian.com/.../ux_in_place_drill_down.html
docs.appian.com/.../ux_master_detail.html

Ex Sail

Load(
local!interfaceSelection: 1,
choose(
local!interfaceSelection,
rule!gridInterface(),
rule!drillInInterface()
)

)

RE: Dynamic interfaces using grids

erics171 — Tue, 30 Oct 2018 14:08:02 GMT

Many thanks, is is good to know there is this method in Appian. For this particular interface I have decided to use the interface itself and some local variables

RE: Dynamic interfaces using grids

erics171 — Tue, 30 Oct 2018 14:07:07 GMT

Many thanks, I did something similar to achieve this!

RE: Dynamic interfaces using grids

viveku3486 — Mon, 29 Oct 2018 11:05:17 GMT

Hi Eric,

1) For back button, you have to follow below steps inside process model

- Click on properties for main interface input task node and click on others tab

- At the bottom you can see an option "Allow Users to step back to this node from next chained activity". Click on that and this will be provide a default Go Back button on the very next interface which will redirect to this main interface when user clicks on Go Back button

2) For saving the data you can store those data into mysql table and maybe you provide a simple interface containing a richtext message like

"Your data submitted successfull" or "There was some issue in previous operation. Try again"

with submit button. This will help user to understand whether their operation was successful or not and simply end the process when they click submit button

RE: Dynamic interfaces using grids

prashantm963 — Mon, 29 Oct 2018 10:37:34 GMT

Hi Eric,

You can create one local variable in the screen and you can save a button's value in it and you can show the screens for certain values of the button.

for ex.

load(
local!a,
local!b,
if(
local!a=back,
rule!screen1 ,
if(
local!b="save",
a!writetodb()
,"")
,"")
)