Skip to main content
swapnar6405
swapnar6405
February 2, 2023
Solved

Nagivation (Lightweight) pattern control

  • February 2, 2023
  • 9 replies
  • 0 views

Hi,

I am using a Navigation (Lightweight) pattern.

When the user clicks on the left menu for example 2nd menu item, I am able to load the respective page. But, when I try to save the data on the 2nd menu item page, after saving it is loading the first menu item page. It is not staying in the same page.

Any advises here please.

Best answer by konduruc733182

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.

9 replies

konduruc733182
konduruc733182
February 3, 2023

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.

    swapnar6405
    swapnar6405Author
    February 6, 2023

    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.

    yanaln6436
    yanaln6436
    February 6, 2023

    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()
    ),

    Terms & ConditionsAccessibility statement