Introduction: In the ever-evolving world of IT, user interface (UI) design has undergone various transformations. One of these trends involved making desktop interfaces resemble mobile interfaces. However, this trend eventually reverted to the idea that mobile and desktop UIs should be distinct. During the era of mobile-like UIs, a concept called UI actions emerged. This lesson delves into UI actions, their significance, and how they influence navigation within EmpowerID systems.

1. UI Actions: An Overview

UI actions, short for user interface actions, are dynamic elements within EmpowerID designed to facilitate navigation. They offer flexibility in constructing menu systems without the need for hardcoded menus, allowing for diverse navigation paths. UI actions are deeply rooted in the concepts of nouns, verbs, and actions, akin to a linguistic model.

2. Functionality of UI Actions

UI actions primarily serve as links pointing to various resources or workflows. These resources can include web pages, protected resource pages, objects, etc. The key to differentiating UI actions is how they generate these links based on specific parameters and permissions.

3. Security and UI Actions

UI actions are security-trimmed, meaning users only see actions they have permission to use. In a system with thousands of UI actions, users will only encounter those relevant to their permissions, reducing clutter and complexity.

4. Display Locations

UI actions can be displayed in various parts of an IT system, depending on the context. These locations include mobile interfaces, bot interactions, find pages, and microservices. Each context may present UI actions differently, aligning with its specific purpose.

Open

Find Pages

Open

Microservice

 

5. Practical Example: Implementing a UI Action

Let's illustrate how to create a UI action using a real-world scenario. Suppose you want to provide users with access to a Manage Person workflow. Here are the steps:

• Begin by defining the UI action with a name, description, and optional localization.

• Select the appropriate noun (e.g., "person") for this UI action.

• Choose an appropriate verb based on the context and workflow.

• Specify whether the UI action is contextual or non-contextual, depending on its display requirements.

• Indicate the action type, whether it's a page or a workflow.

• Save the UI action configuration.

Once created, the UI action dynamically appears in the interface, but only for users with the necessary permissions to execute the linked workflow.

6. Extending UI Actions

Organizations can extend UI actions by defining custom nouns, verbs, and actions tailored to their specific needs. For example, you can create custom UI actions for industry-specific workflows or operations unique to your business.

Conclusion: UI actions are essential tools for enhancing user navigation within IT systems. They offer dynamic, customizable menu options while maintaining security and user-specific relevance. By understanding UI actions and their flexibility, organizations can streamline their interfaces and improve user experiences in an ever-evolving IT landscape.

DEMO

1. We want our workflow to appear in this Actions Pane.

2. In order to do that navigate to Admin → Miscellaneous → Noun Verb Action Navigation

3. I already have the Noun and Verb, and that page already exists. I just want to define the UIAction.

4. Click on the + button and fill out the form.

5. This is how we link the workflow with the UI Action and determine where it should appear. For example, if you wanted to show it under the IAM Shop Microservice, you would have selected the IAM Shop Microservice from the Noun dropdown. Similarly, if you wanted it to appear under the Business Role, you would have selected the Business Role from the verb dropdown. It depends on where you want it to appear. See the image below for reference.

6. Click on the save button.

7. Now go to the Find/Person page and there in the Actions menu you can see it. Click on it and it will run your workflow.