Button

Hi aliciam,

welcome in the community:

1.) try to use the insert code function below yourt textfield. it makes it way easier to read code.

a!buttonArrayLayout(
    buttons: {
        a!buttonWidget(
            label: "Atras",
            size: "SMALL",
            width: "FILL",
            style: "NORMAL",
            value: local!currentStep - 1,
            saveInto: local!currentStep,
            showWhen: or( local!currentStep = {1,3} )
        )
    },
    align: "START"
)

if the first screen is another form, you need to submit your current form and build a loop in your process.

Hi aliciam,

welcome in the community:

1.) try to use the insert code function below yourt textfield. it makes it way easier to read code.

a!buttonArrayLayout(
    buttons: {
        a!buttonWidget(
            label: "Atras",
            size: "SMALL",
            width: "FILL",
            style: "NORMAL",
            value: local!currentStep - 1,
            saveInto: local!currentStep,
            showWhen: or( local!currentStep = {1,3} )
        )
    },
    align: "START"
)

if the first screen is another form, you need to submit your current form and build a loop in your process.

Note that if you use a!formLayout() - which comes with navigation buttons bundled into it - you can also use the 'Allow users to step back to this node from the next chained activity.' setting (on the 'Other' tab) on the User Interface nodes where Appian will automatically add a 'Go Back' navigation button for you.

You can build a simple screen flow if there is not much processing need to happen between two screens, and use buttons as necessary to move forward and back and submit. Appian provides all the functionalities to facilitate this behaviour.

yes, i often forget about that function. valuable comment :)

I find this less and less used given you can simulate this kind of activity within a single SAIL form...but I guess there maybe reasons when you need to inject functionality between two "forms" which would be better placed in the process, so it's always worth having this in your toolkit