Nagivation (Lightweight) pattern control

Hello swapnar6405,

If you are using a record action or related action this behavior is expected. Because it will refresh your local variables that is storing the current page identifier. The only work around I am aware to achieve your requirement is using the a!writeToDataStoreEntity() function to perform your saves.

I had a similar issue sometime back.

Hi Chaitanya,

I am not using record action or related action. I am using WriteToDataStoreEntity smart service.

But, still not got a clue to fix this.

I'm not entirely sure what's going on in ur interface with the limited info,
but if ur using the lightweight navigation pattern, try using a dummy refresh local, and make it so that the selected navigation system wont change unless this refresh is changed or if u directly saved to it.
I think the problem lies elsewhere tho, but this might fix ur problem.

  a!localVariables(
    local!refresh: 1,
    /* The selected navigation section */
    local!activeLightweightNavSection: a!refreshVariable(
      value: 1,
      refreshOnVarChange: local!refresh,
      refreshOnReferencedVarChange: false()
    ),

When the user selects Holidays or Attorneys and after submitting the respective page submit button, Admin page is reloading to initial "Viewers" page. Please find the below details.

lightweight navigation pattern:

Could it be that you use this interface as a startform in a process which you added to a site? If yes, the reason for that behaviour is that the form gets submitted and starts the process when clicking the "SAVE" button and returns to the freshly initialized interface.

Yes, I have a site with a Menu item where I have selected Type as "Action" and Content as "Admin Process Model"

In the Admin process mode I have used the Process Start Form as "Admin Home Page".

I thought of selecting Type as "Interface", but I am getting an error message "An interface with rule inputs cannot be saved as a site page" due to rule inputs.

So, not sure how to fix the issue.

There is no issue. You need to decide what you want to achieve and use the Appian features as required. A process is for starting an action, and an interface is just to display things.

Chaitanya,

I have updated with my code here. Do you have any sample code here from your end. Thanks.

Hello, Can you check what is the value that is being saved in local!selection and ri!page at each stage. I couldn't figure out what else might be the reason for that behavior. Where is this form displayed. are you using in a process model or using it in a start form? In case if it is a start form you will face this issue. try to replace your rule inputs with locals since you are planning to use a!writeToDataStoreEntity(). If you do not want to change your variables to locals may be you can use neted interfaces and then use locals.