---
alias: uipagecontext-st
description: "This documentation details a table for resolving UI actions within a specific context"
---

# UIPageContext

## Description

Used to resolve UIPage Exceptions for UI Actions (e.g. Material.Trackin for a specific context)

## Fields

The **UIPageContext** table has the following fields:

| Field | Description | Key | Mandatory | Comments |
| --- | ----- | -- | -- | ---- |
| **Action** |  | Yes | Yes | |
| **PrimaryRole** |  | Yes | No | |
| **Facility** |  | Yes | No | |
| **Area** |  | Yes | No | |
| **Step** |  | Yes | No | |
| **Resource** |  | Yes | No | |
| **ResourceProcessingType** |  | Yes | No | |
| **Page** |  | No | No | |
| **BusinessRule** |  | No | No | |

Table: UIPageContext fields

Some specific actions are pointing to predetermined UI Pages by default:

| Action                  |    UI Page    |
|-------------------------|:---------:|
| MyWorkgroup.**MyWorkgroup** |    `MyWorkgroupView_Cluster`    |
| FabExplorer.**ResourceView** |    `ResourceView_Cluster`    |
| FabExplorer.**StepView** |    `StepView_Cluster`    |
| FabExplorer.**AreaView** |    `AreaView`    |

Table: Predefined UI Page Contexts

To override this default behavior, it is possible to use indirection by adding entries on the smart table using `{ACTION_NAME}.View` as an action identifier. For example, adding:

| Action                  |    UI Page    |
|-------------------------|:---------:|
| `FabExplorer.ResourceView`**.View** |    `CustomResourceView01`    |
| `FabExplorer.AreaView`**.View** |    `CustomAreaView01`    |

Table: Indirection in UIPageContext

The first entry will override the navigation to the `CustomResourceView01` UI Page instead of `ResourceView_Cluster`. Note that you can also override action `FabExplorer.ResourceView` directly, however this indirection will **NOT** take into account the Resource Processing Type and all other UI Pages that are included in the defined ResourceView would redirect always to the defined UI Page instead of `ResourceStorageView` or `ResourceConsumableFeedsView`. In light of this, new virtual actions suffixed with **.View** were added for these 3 special cases.

## Precedence Keys

The search precedence rules are the following:

1. Action, Resource
2. Action, PrimaryRole, Area, ResourceProcessingType
3. Action, PrimaryRole, Facility, ResourceProcessingType
4. Action, Area, ResourceProcessingType
5. Action, Facility, ResourceProcessingType
6. Action, PrimaryRole, ResourceProcessingType
7. Action, ResourceProcessingType
8. Action, PrimaryRole, Step
9. Action, PrimaryRole, Facility
10. Action, PrimaryRole
11. Action, Area
12. Action, Facility
13. Action