Apliqo UX navigation - specific screens for elements

Apliqo UX
1

Hi,

In Apliqo UX, is it possible to specify different navigation screens for different elements in a view. For example, the hyperlink on the sales account would take me to one screen, where as the hyperlink on the labour account would take me to another screen?

Thanks.

2

You can define multiple views in the targetView array. If the user clicks the cell then the first view will be navigated to by default. On right-click > navigate to … pops up a list of the defined array and the user can select where to navigate to.

To answer your question is there a way to automatically and flexibly change the 1st element in the array depending on the context of the row. Not really. You would need to let the user decide on right-click where to navigate to.

However, the “not really” is actually a kind of via creating an attribute called “targetView” on the row dimension and storing there the ID of the app to navigate to (e.g. “a1.f1.v1”). This isn’t really flexible as the attribute name can’t be defined per view but it will definately work and fulfill your requirement of different target view navigation depending on the row context. So maybe it is actually a qualified “yes”.

Note that you can combine both the targetView attribute and the normal hardcoded targetView options within a view. The attribute will control the default or left click navigetion, but the user will still have the option to right-click and select from the array defined in the options. Also note as there is only one targetView attribute per dimension if you don’t want that navigation to apply in other screens then you need to add “targetViewAttributeOverride”: false to the advanced options json of the subview or widget.

Just be aware (as this isn’t documented anywhere!) that the syntax of the app ID stored in the targetView attribute is different from what is needed in the standard advanced options json.

targetView attribute syntax:

{
  "targetView": {
    "appName": "a1",
    "view": "a1.v13",
    "viewType": "Dashboard"
  }
}

E.g.

image
image1204Ă—658 65.8 KB

Versus the standard advanced options json syntax:

  "targetView": [
    {
      "view": "a1.v13",
      "viewType": "Dashboard"
    },
    {
      "view": "a14.f1.v1",
      "viewType": "Dashboard"
    }
  ]
1 Like
3

Wanted to revive this old thread since we are having trouble getting targetview to work properly when trying to navigate to a wizard substep. Years back, I remember that it didn’t work with wizards but the Adv Option targetview now does work:

  "targetView": [
    {
      "view": "a18.f2.z1.t1.v3",
      "viewType": "Wizard"
    }
  ],

However, when we try to apply the same logic to the “targetView” attribute (even after converting the “[” to “{”, it doesn’t work.

{"targetView":{"appName":"a18","view":"a18.f2.z1.t1.v3","viewType":"Wizard"}}

Not sure if there’s any other tricks to getting it to navigate? We tried using href directly in the attribute value (which works purely for navigation) bu thatt doesn’t pass the current page’s filter values over via the settings service.