How to know which button was selected by the end user

RE: How to know which button was selected by the end user

susana197 — Tue, 02 Oct 2018 16:11:09 GMT

Thanks Mike,

This solution worked like a charm!

Have a nice day.

RE: How to know which button was selected by the end user

mitchellg942045 — Tue, 02 Oct 2018 14:26:57 GMT

As others have stated, if you pass in a pv for the button action as a rule input and save the button text on submit i.e:

a!buttonWidget(
label: "Cancel",
value: "Cancel",
saveInto:ri!buttonClicked,
submit: true
),
a!buttonWidget(
label: "Proceed",
value: "Proceed",
saveInto:ri!buttonClicked,
submit: true
)

From there you can have a script task in the process model to update any needed values in the process based on the selected button or throw it right to an XOR gate. Hope that helps!

RE: How to know which button was selected by the end user

charlesm492 — Tue, 02 Oct 2018 14:12:43 GMT

For the first question, as others have said you just need to use the value and saveInto properties of your buttons to save the different values into a rule inputs. As a best practice, these values that you are saving should be constants.

For your second question, you would just need to mark the required property of your comment field as true and mark the skipValidation property of your Proceed button as true so that only the other two buttons cause the required validation on the comment field to fire.

RE: How to know which button was selected by the end user

Larry Nguyen — Tue, 02 Oct 2018 14:08:51 GMT

I think you can achieve this by having a ri!button (or any rule input variable) and for your buttonWidget saveInto the ri!button. Have the buttonWidget value field equal to a constant or value that identifies the buttons as the Cancel, Re-Work, or Proceed button. Map the rule input to the acp and have the acp save into the pv! variable.

For the validation, you can setup a validationGroup for the comment text field and buttonWidgets you want to fire off that validation for that comment text field. A good example of this is here:

docs.appian.com/.../recipe_configure_buttons_with_conditional_requiredness.html

RE: How to know which button was selected by the end user

hrishikeshd997 — Tue, 02 Oct 2018 13:52:07 GMT

To update a process variable, the interface needs to have rule inputs. Use this rule input into the saveInto attribute in a!buttonWidget.
eg:
a!buttonWidget(
label: "Cancel",
value: "Cancel",
saveInto:ri!buttonClicked,
submit: true
),
a!buttonWidget(
label: "Proceed",
value: "Proceed",
saveInto:ri!buttonClicked,
submit: true
)

This will mean if Cancel is clicked ri!buttonClicked will have value as "Cancel", if proceed button is clicked it will have value as "Proceed".
Then map this to a process variable in the Data -> Inputs tab in a User Input Task activity in which your SAIL interface is called. The rule inputs of the interface will be the activity class parameters (Data Inputs) and these can be mapped to a process variable.

For your second query you can use validation groups. Refer to this SAIL recipe - docs.appian.com/.../recipe_configure_buttons_with_conditional_requiredness.html

RE: How to know which button was selected by the end user

Andrew Zysk — Tue, 02 Oct 2018 13:49:26 GMT

Hi Susan,

1.
Typically, you can use an interface rule input of type Text (I usually name it "button_text"), and save the unique value of the button into that variable before submitting.

For example, clicking the Cancel button should save "Cancel" into ri!button_text. In your process, you should have a button_text process variable that the form saves into.

"I thought I would add an a!save function in the buttonWidget" - this is possible! :) Make sure you are using the "saveInto" field on the buttonWidget. These saves are executed before the form is submitted.

2.
To make a text field required only for certain buttons, it sounds like you might want to look at the "validate" and "submit" fields on each of your buttons - you can alter the logic of whether or not the button should trigger required fields.

RE: How to know which button was selected by the end user

Carlos Santander — Tue, 02 Oct 2018 13:41:40 GMT

For the first question, you need give a different value to each button, and then have each button save into the same rule input.

For the second question, you can make use of validation groups. Take a look at the following recipe for an example: docs.appian.com/.../recipe_configure_buttons_with_conditional_requiredness.html

RE: How to know which button was selected by the end user

gianninol — Tue, 02 Oct 2018 13:41:03 GMT

It should be perfectly possible to add an a!save function in the saveInto field of the buttonWidget. Can you be more specific when you say that SAIL doesn't like it?

As for making it required only when those specific buttons are pressed, you can make use of the validationGroup parameter on the buttons and the field. Link to example here: docs.appian.com/.../recipe_use_validation_group_for_buttons_with_multiple_validation_rules.html

I believe you can add multiple validation groups to the field by having a space between each validation group you want it to belong to.

RE: How to know which button was selected by the end user

Mike Lasutschinkow — Tue, 02 Oct 2018 13:40:46 GMT

Yes, you can add a save into the saveInto of the button (and this is the most sensible way to capture which button was pressed).

Your code would look something like the following:

a!buttonWidgetASubmit(
    label: cons!BUTTON_LABEL_TEXT, /* your constants here */
    value: cons!BUTTON_LABEL_TEXT,
    saveInto: {
        ri!buttonClicked /* text rule input to save into process variable */
    }
)