Validation not refreshing when navigating interfaces

RE: Validation not refreshing when navigating interfaces

rainier_albario — Mon, 07 Jun 2021 15:22:22 GMT

Yeah, I thought it only revolves in the interface section since its mostly a design and validation handling, never knew process model is also connected to this. Again, thank you for the insight.

RE: Validation not refreshing when navigating interfaces

Mike Schmitt — Mon, 07 Jun 2021 14:55:56 GMT

A process model is required for most processing beyond simple database writes. And it's often a good idea to use one anyway (unless you have specific reasons to avoid doing so) since it makes for easier debugging and troubleshooting.

RE: Validation not refreshing when navigating interfaces

rainier_albario — Mon, 07 Jun 2021 14:32:19 GMT

This issue has been resolved using this method. Thank you!

RE: Validation not refreshing when navigating interfaces

Stefan Helzle — Mon, 07 Jun 2021 06:50:36 GMT

A note here: This is not "go back". You have a global scope defined by that main interface and validation happens in this scope. Showing or hiding any parts does not change that global scope nor validation. Once triggered it stays triggered as long as you submit the form.

RE: Validation not refreshing when navigating interfaces

Stefan Helzle — Mon, 07 Jun 2021 06:46:44 GMT

Yes.

Have a look at https://docs.appian.com/suite/help/21.2/record-actions.html

Basically it is: "Use a process for user actions."

I know there is always a way to not need a process model and I do that myself if, and only if, there is a benefit. But this is a topic for later in your learning path.

RE: Validation not refreshing when navigating interfaces

rainier_albario — Mon, 07 Jun 2021 06:44:08 GMT

I have two interface I have ri!action on both interface. I'll show the userManagement if the value of ri!action is "userManagement" and "add" for userRegistration. so when I clicked cancel i change the ri!action value to "userManagement" to go back to the previous interface.

RE: Validation not refreshing when navigating interfaces

vamsi krishna — Mon, 07 Jun 2021 06:37:02 GMT

You are using same showWhen parameter for "Create User" button and "Submit" button?

RE: Validation not refreshing when navigating interfaces

rainier_albario — Mon, 07 Jun 2021 06:30:54 GMT

Hello, Thank you for your response. However, I already tried it changing the showWhen value to false when I click cancel. However, when I go back to userRegistration form the validation will be removed. But when I add ri!ShowWhen then change it back to true after clicking the "Create User" button the validation is still there.

RE: Validation not refreshing when navigating interfaces

vamsi krishna — Mon, 07 Jun 2021 06:21:17 GMT

If you are not submitting the form on cancel button, then you can try this

a!localVariables(
  local!amount,
  local!buttonValue,
  local!showWhen:and(local!buttonValue,isnull(local!amount)),
  a!formLayout(
    contents: {
      a!textField(
        label: "Amount",
        value: local!amount,
        saveInto: local!amount
      )
    },
    buttons: {
      a!buttonArrayLayout(
        buttons: {
          a!buttonWidget(
            label: "Submit",
            style: "PRIMARY",
            submit: true,
            saveInto: {
              a!save(local!buttonValue,true)
            }
          ),
          a!buttonWidget(
            label: "cancel",
            saveInto: {
              a!save(local!buttonValue,false)
            }
          )
        }
      )
    },
    validations: a!validationMessage(
      message: "Is required",
      validateAfter: "SUBMIT",
      showWhen: local!showWhen
    )
  )
)

RE: Validation not refreshing when navigating interfaces

rainier_albario — Mon, 07 Jun 2021 03:30:16 GMT

Hello, sorry I'm not using any process model for navigating interfaces.

So you're saying I need to create a process model to do that?

RE: Validation not refreshing when navigating interfaces

Mike Schmitt — Mon, 07 Jun 2021 02:41:45 GMT

After any validation has been triggered for a particular instance of a form, it will stay triggered until the form is exited (like via a submit button click). If you want your user to be able to press "cancel" and go back to a default state, you should have the cancel click submit from the current form and chain the user into a new instance of the same task - to the user this will happen seamlessly.

If the task in question is a start form, then it's a little trickier, but should still be possible - i.e. have the "cancel" button start the process then chain the user into a User Input Task that has the same interface set as its form. Honestly though at this point you may as well ditch the Start Form setup and instead just have the process contain that task, and an XOR gateway could check what button was clicked and if it was "cancel", loop the user back to the same form again, otherwise move on in the process.

RE: Validation not refreshing when navigating interfaces

rainier_albario — Mon, 07 Jun 2021 01:24:59 GMT

Hello, still not resolve

RE: Validation not refreshing when navigating interfaces

Stefan Helzle — Sun, 06 Jun 2021 09:04:00 GMT

I know that you have two interfaces. The way of how to implement this kind of things is just different with Appian. The basic idea is that you have data (Appian Records), UI to display this data and processes to allow a fine grained interaction with the user. These processes are not meant to be another abstract way of manipulating data in DB but a way to express a functional business process.

In your case it could be: Create user, send email to user, add user to groups assign task to users supervisor to assign application roles and permissions.

RE: Validation not refreshing when navigating interfaces

rainier_albario — Sat, 05 Jun 2021 19:06:22 GMT

I'm already using two interface btw. One is user management and one is for the registration form. The user management form has a create user button that will navigate to the user management interface. I just want the navigation dissappear whenever I go back again to the user form

RE: Validation not refreshing when navigating interfaces

Stefan Helzle — Sat, 05 Jun 2021 18:43:05 GMT

I understand. Try to decouple your functionality. Create a separate interface to create a new user. Make it the start form of a process. Then start that process via a startProcessLink.

I do not know your background, but wrapping your head around Appian might take a bit.

RE: Validation not refreshing when navigating interfaces

rainier_albario — Sat, 05 Jun 2021 18:34:14 GMT

I'm using startProcessLink on my submit button. Whenever I try to save data to the database. Can you explain to me how startProcessLink can resolve the issue of removing the validation message when navigating interface? Sorry, I'm fairly new to appian.

RE: Validation not refreshing when navigating interfaces

Stefan Helzle — Sat, 05 Jun 2021 18:29:20 GMT

Is there a reason for not using a process and a startProcessLink? Doing this kind of things just in an interface can become tricky.

RE: Validation not refreshing when navigating interfaces

rainier_albario — Sat, 05 Jun 2021 18:08:18 GMT

Here the validation message is not removed when I go back to this form after clicking the cancel button.

RE: Validation not refreshing when navigating interfaces

rainier_albario — Sat, 05 Jun 2021 17:58:27 GMT

Hello, thank you for answering.

Yes, it's just a sub interface. The way I navigate is by declaring rule input called action. I have a dashboard called "user management" and then I have "user registration", there is a button under user management called Create User, whenever I clicked that I used the showWhen. I'll show the user management if the value of ri!action is userManagement and show user form if the value is "addform" that's how I navigate interfaces.

RE: Validation not refreshing when navigating interfaces

Stefan Helzle — Sat, 05 Jun 2021 17:51:36 GMT

Please explain how you are doing this "back to the form" and "click the cancel button" interaction. My any chance, could it be that you embed this as a sub interface into another one?

With proper usage of related actions or startProcessLink this does not happen.