Rule Input setting to null after refresh after interface gets refreshed

RE: Rule Input setting to null after refresh after interface gets refreshed

Abhay Dalsaniya — Mon, 05 Feb 2024 17:46:29 GMT

On page refresh the RI gets reset to it's original value, E.g. if you are calling an interface from another source, the supplied value from the parent will take in effect.

RE: Rule Input setting to null after refresh after interface gets refreshed

Harshit Bumb (Appyzie) — Mon, 05 Feb 2024 05:50:08 GMT

amikb0002 I assume this clientName is a filter on the interface. You can use the below code as a sample to understand.

a!localVariables(
  local!clientName,
  rule!getDataFromProcessReport(
    clientName: local!clientName
  )
)

RE: Rule Input setting to null after refresh after interface gets refreshed

Konduru Chaitanya — Mon, 05 Feb 2024 04:14:05 GMT

Could you please share your complete updated code, it would help all of us understand the issue better and provide you an accurate answer.

RE: Rule Input setting to null after refresh after interface gets refreshed

amikb0002 — Mon, 05 Feb 2024 03:46:17 GMT

I have tried this code already but did not work.

a!localvariable( local!test: a!refeshVariable( value: ri!abc, refreshOnReferenceVarChange: false())

RE: Rule Input setting to null after refresh after interface gets refreshed

Harshit Bumb (Appyzie) — Sun, 04 Feb 2024 19:35:16 GMT

Rule inputs are used to exchange values between objects like Interface and Expression, interface and Process Model, etc. But they don't have a memory of their own. You will have to use local variables for this.

amikb0002 You can take a look at this documentation for better clarity - docs.appian.com/.../Local_Variables.html

RE: Rule Input setting to null after refresh after interface gets refreshed

Stefan Helzle — Sun, 04 Feb 2024 18:16:42 GMT

The value of the rule input is controlled only by the parent interface passing the value.

If you, for whatever reason, need/want to store a copy, assign it to a local variable using a!refreshVariables() to set refreshOnReferencedVariables to false.

RE: Rule Input setting to null after refresh after interface gets refreshed

amikb0002 — Sun, 04 Feb 2024 16:10:47 GMT

Here is the snippet.

data: a!queryProcessAnalytics(
report: cons!WLRD_PROCESS_REPORT_POINTER,
contextProcessModels: cons!WLRD_PROCESS_MODEL_POINTER,
query: a!query(
filter: a!queryFilter(
field: "c17",
operator: "=",
value: ri!clientName,

When page gets refreshed ( for now I am manually refreshing the page) , rule input becomes null and it throws below error.

Could not display interface. Please check definition and inputs. Interface Definition: Expression evaluation error at function a!gridField [line 43]: The a!queryFilter function has an invalid value for the "value" parameter. When the value of "operator" is "=" "value" must not be null or empty

I would like to keep the rule input value intact when it is passed at the first time so after page gets refreshed, I will use it for filter. Any suggestion? TIA

Note- I will handle null later in my code.

RE: Rule Input setting to null after refresh after interface gets refreshed

Stefan Helzle — Sun, 04 Feb 2024 09:07:08 GMT

When data in a rule input is set to null, there is nothing you can do about it. Maybe you could create a copy of that rule input, but that might break the UX on the parent UI.

RE: Rule Input setting to null after refresh after interface gets refreshed

Harshit Bumb (Appyzie) — Sat, 03 Feb 2024 06:01:12 GMT

This is difficult to debug as we don't know what is happening, or how the refresh happens.

Can you add your code or better clarity?

RE: Rule Input setting to null after refresh after interface gets refreshed

amikb0002 — Sat, 03 Feb 2024 05:34:26 GMT

Hi Kiran-

There is a separate UI, from there, customer name is passed as parameter to this interface. This interface shows all the business elements which are used during execution of the process model. Also it shows the user input task name with task link through which user can take action on user input task. User input task name changes as soon as workflow moves further.

The issue is, once the interface (based on process analytics) loads the data based on that customer which is being passed as a parameter to this interface from another interface and user task link is clicked, it opens up a user input form where user can take action, also the interface page should be refreshed as soon as the user input task is actioned to show the next user input task. currently I did not implement refresh feature. I manually refreshed the page but the customer name which is passed as rule input is getting set to null and the interface is showing no data due to this.

RE: Rule Input setting to null after refresh after interface gets refreshed

Niranjan79 — Sat, 03 Feb 2024 04:52:01 GMT

Hi amikb0002 ,

'interface page gets refresh", are you reloading the interface or how it is getting refreshed?

and from where the rule input value is getting?