data type save

RE: data type save

BeckettHayes — Thu, 09 Jan 2025 10:14:15 GMT

Thank you so much for answering, you saved my day.

RE: data type save

G Nithisha — Mon, 06 Jan 2025 19:14:10 GMT

If you want to save value after clicking on button or else choosing option in dropdown will use a!save() function.
simply it saves the value in target.

if you want to save same value whatever user provided/selected you can use a!save(local!test,save!value)
or else you want to save different value after clicking on the submit button.

saveInto:{ri!button,

a!save(local!test,null)

}
it means local variable test updated with null value user clicks on the submit button.

RE: data type save

Stefan Helzle — Mon, 06 Jan 2025 10:39:30 GMT

Because I can then pass a list of a!save() to that parameter to allow reacting on events from outside of the component. That what makes this customizable.

RE: data type save

Soma — Mon, 06 Jan 2025 06:46:14 GMT

There will be cases where you need to manipulate or conditionally handle some operations based on the input. Instead of using an additional variable to save the value and handle it based on that, you can use save!value.

It simplifies the process of saving or manipulating the user input in the interface by providing direct access to the value.

Example:

a!save(local!email, if(isnull(save!value), "No Email Provided", save!value))

RE: data type save

Raúl Gómez Moya — Sun, 05 Jan 2025 20:07:28 GMT

I still don't understand its use, why not use a variable of the specific type that is expected to be stored in ri!saveInto instead of using the save data type?

RE: data type save

Stefan Helzle — Sun, 05 Jan 2025 19:34:33 GMT

I use the "save" datatype when I want to expose a functionality like the Appian default components in the saveInto parameter.

Find an example in my blog post: https://appian.rocks/2023/12/04/the-master-of-email-address-fields/