When to set values of a rule input which are hidden to a user?

RE: When to set values of a rule input which are hidden to a user?

Peter Lewis — Fri, 23 Apr 2021 13:04:24 GMT

You can also save as many fields as you need to using an array. For instance,

a!buttonWidget(
  label: "Submit",
  submit: true,
  style: "PRIMARY",
  saveInto: {
    a!save(
      target: ri!customer.updatedOn,
      value: now()
    ),
    a!save(
      target: ri!customer.updatedBy,
      value: loggedInUser()
    ),
    a!save(
      target: ri!cancel,
      value: false
    )
  }
)

I always prefer using this method of saving data on the button because you can guarantee that all the other data has been entered - otherwise, the user wouldn't be able to submit the form!

RE: When to set values of a rule input which are hidden to a user?

Stefan Helzle — Fri, 23 Apr 2021 13:00:57 GMT

Adding to that, I recommend to keep to the best practice of using keyword syntax.

saveInto: a!save(target: ri!abc, value: "abc"),

RE: When to set values of a rule input which are hidden to a user?

Arun Dubey — Fri, 23 Apr 2021 11:43:26 GMT

Hi ,

As per your requirement you can try this code

a!buttonWidget(
label: "Submit",

saveInto: a!save(ri!abc,"abc"),
submit: true,
style: "PRIMARY"
)

thanks,

RE: When to set values of a rule input which are hidden to a user?

fgrl — Fri, 23 Apr 2021 11:06:08 GMT

I am still not sure how exactly: May you share some code, please? Inside the saveInto() ?

RE: When to set values of a rule input which are hidden to a user?

Stefan Helzle — Fri, 23 Apr 2021 10:59:34 GMT

I do that in the submit button. Have very good experience with it.