which is Efficient way

RE: which is Efficient way

Stefan Helzle — Thu, 14 Nov 2024 14:02:26 GMT

Sure, but you can also just pass the rule input.

RE: which is Efficient way

Dinesh Arumugam — Thu, 14 Nov 2024 13:51:09 GMT

im storing it to pass in multiple places in my UI

RE: which is Efficient way

Stefan Helzle — Thu, 14 Nov 2024 13:31:21 GMT

Storing a rule input value into a local for no specific purpose makes no sense and is not required.

RE: which is Efficient way

Dinesh Arumugam — Thu, 14 Nov 2024 12:20:04 GMT

it is coming form RI as a record type

RE: which is Efficient way

Dinesh Arumugam — Thu, 14 Nov 2024 12:18:22 GMT

compute means - doing some operations and getting some value

yes we use the first approach, but it consume memory right ,that why i raised this question

RE: which is Efficient way

Stefan Helzle — Thu, 14 Nov 2024 11:59:02 GMT

Well, a value that is not computed is a static value. If this is needed in multiple places, creating a constant for it might be a good idea.

RE: which is Efficient way

venkatrea696188 — Thu, 14 Nov 2024 11:51:41 GMT

[quote userid="289184" url="~/discussions/f/best-practices/37960/which-is-efficient-way"]if so i need to call index,whereconains in many places right dont it consume memory[/quote]

This what compute means in your case. We generally go with first approach it's best practice not only in Appian but in other coding languages too

RE: which is Efficient way

Dinesh Arumugam — Thu, 14 Nov 2024 11:40:35 GMT

if no need of compute ?

RE: which is Efficient way

Stefan Helzle — Thu, 14 Nov 2024 11:33:18 GMT

If I need a computed value multiple times, I use local variables to reduce the evaluation time.