Skip to content
Support
  • There are no suggestions because the search field is empty.

Groups in VXL Live

VXL Live ensures that workflow execution is a seamless and intuitive process, enhancing the overall user experience. Execute workflows efficiently and stay informed about the status in real-time, making workflow management a breeze.

Introduction

Groups created in Vince Live should seamlessly integrate and be reflected in VXL Live. This document outlines the functionalities, behavior, and permissions related to groups and workflows in VXL Live.

Group Functionality

General Behavior

  1. Reflection in VXL Live
    • Groups created in Vince Live will be available in VXL Live.
  2. Multiple Workflows in Groups
    • A group can consist of multiple workflows.
    • Users can search and select a group in VXL Live.
  3. Workflow Display After Group Selection
    • Upon selecting a group, all workflows within the group will be displayed.
    • For admin users, all Groups and all workflows in the group will be visible.
    • For regular users, only workflows they have permissions for (Read, Write, or Full Access) will be displayed.
  4. Group Visibility
    • Groups will only be visible to users with access to those groups.

Workflow Environment and Execution

Environment Selection

  1. Environment Access for Workflows
    • If a group contains workflows linked to multiple environments (e.g., TST, PRD), a user’s environment access dictates visibility and execution.
    • Example:

      • Workflow 1 (WF1) linked to TST.

      • Workflow 2 (WF2) linked to PRD.

      • If a user has access only to TST, only TST will be displayed in the environment list for the group, and WF1 will be executable.

      • Attempting to execute WF2 will result in an error message:

        "The selected environment is not linked to the current workflow. Please choose a valid environment."

Connection Permissions

  1. Execution Linked to Connections
    • Each environment is linked to a connection.
    • If a user has environment access but lacks connection access, the Run button will be disabled.
  2. Example
    • TST environment linked to the Testing connection.
    • PRD environment linked to the Production connection.
    • User permissions:
      • Access to TST and PRD environments.
      • Permission for the Testing connection only.
    • Behavior:
      • Selecting TST: Run button enabled.
      • Selecting PRD: Run button disabled.
  3. Environment Switching
    • Users can switch environments they have permission for.
    • Run button behavior will update dynamically based on connection permissions.
  4. Environment-Specific Run Button Colors
    • Colors for environments can be configured during environment creation.
    • The Run button’s color updates based on the selected environment.

Workflow Input Fields and UI Behavior

Date Input Field

  1. Calendar Display
    • If a workflow includes an input field with data type as date, clicking on the field will display a calendar.
    • The calendar should align with the UI design and not disrupt the layout.
  2. Default Values
    • If an input field is configured with a default value, the value should be displayed when the workflow is selected.