Build NUX pages with different structured models on same page without cross contamination

jtkerlin

When having different structured models added to the same NUX page there are cross contamination issues. NUX page seems to only reference/use the system id codes and does not include the type of model.

Example/Situation: Two models - HUB and Spoke - entirely different structure. Both have 3 modules, of which one has the same system ID code of 1000000001, the others are different. Additionally, you have 5 actions/processes in both models, of these 2 have the identical system ID codes of 10000000060 and 10000000065. In the HUB those actions relate to importing data from a flat file into HUB, two different files 1) Client, 2) Department. In the Spoke those actions relate to delete actions/processes 1) Deletes all Actual Transactions, 2) Deletes Forecast.

NUX Page has the following set up:

HUB

process 10000000060 process 10000000065

module 10000000001

Spoke

module 10000000001 module 1000000022

When you select HUB, the three top items should be enabled and only those, HOWEVER, since the module code is identical the Spoke one is enabled as well. Not necessarily a problem for this example (but could be); however when you change the model to Spoke the two processes at the top are enabled, which is a problem - especially if you have a user who is not paying attention. If you/they run those processes you end up having items deleted in the Spoke, which is unexpected and a bad result.

Preferred Functionality

Preferred functionality would be that when modules, processes, etc. are added from a specific model, it includes something that denotes the type of model. That way this issue would not occur.

Current workarounds not ideal

The current workarounds are okay, but lack the expected flexibility and functionality of having two differently structured models on the same NUX page.

1. Use the set up above, but make it VERY noticeable that they are not interchangable. This requires users who are paying attention and could still result in bad result.
2. Keep different structured models separate on NUX Pages. Only HUB models go on Hub pages, only Spoke models go on Spoke pages.