Understanding Navigation Flow Status after Import

When you import a snapshot containing an active navigation flow into an environment containing an active navigation flow of the same category (role, group, or global), then the new navigation flow being imported is deactivated.

For example, the following navigation flows are currently active on your system:

• NF Sales Q2 (Sales group)

• NF Administrator (Service Administrator role)

• NF Custom Default (global)

Let's say you import a navigation flow called NF Sales Q3, which uses the same Sales group as NF Sales Q2. The NF Sales Q3 navigation flow will be imported as inactive and the existing NF Sales Q2 will remain active for the Sales group. If you want the new NF Sales Q3 to be active, you must manually activate it (which will inactivate the old NF Sales Q2). We deactivate the imported Q3 navigation flow because the import might occur ahead of the Q3 start date, and we want to ensure the Q3 navigation flow isn't activated before the Q3 start date.

If a new application is created from a Migration snapshot that includes an active custom global navigation flow (for example, NF Custom), the NF Custom global navigation flow will become inactive after Migration import. The same is true if the application is cloned. The Default global navigation flow will become the active global navigation flow and you'll need to ensure you activate the global NF Custom navigation flow after the new application is created. If all users are using the NF Custom global navigation flow, they might experience a service interruption until the NF Custom navigation flow is activated.

When designing navigation flows:

• Create navigation flows for specific groups or classes of users. Then associate the navigation flow to corresponding user groups.

• Avoid creating one global navigation flow for all users.