specs/routes/R_APPA

App Approvals

Overview

The App Approvals page allows users to assign Approval Types to a specific App.

Users must also assign at least one “Approver” within the Approval Type when it is added to the app.

After an Approval Type is assigned to an app, all future versions of the app will require an approver from the specified approval type. Approval Types can be removed, and this means that a certain approval type will no longer be required.

Model/Page Connections

Approval Types

View

  • A user can view all possible Approval Types on this Page

App

Edit

  • A user can edit the list of all approvals needed for all future versions of the app by toggling “on” individual approval types on the right side of the screen

App Approvals

Create

  • A user can create a new App Approval after pressing the toggle to turn “on” a specific Approval Type on the right side of the screen. They must choose at least one Approver.

Edit

  • A user can edit the list of approvers by pressing the “pencil” symbol next to the user icons within the Approval Type

View

  • A user can view all possible App Approvals on this Page

Delete

  • A user can remove an App Approval after pressing the toggle to turn “off” a specific Approval Type on the right side of the screen

User

View

  • A user can view a list of all possible approvers after pressing the toggle to turn “on” a specific Approval Type on the right side of the screen

Pages

The following Pages must be properly configured before this Page will work properly:

User Permissions

A user with “create” permissions for the app can view, edit, create and delete approvals.

A user with “view” permissions for the app can view all approvals

Tests

IDName
QA-T267User Roles : 08 - Viewers should be unable to modify data in Tulip
QA-T329Apps Page : 08 - App Approvals Setup
QA-T330Apps Page : 09 - App Approvals during Publishing
QA-T386Apps Page : 10 - App Testing during Approvals
QA-T523Apps Page : 11 - Multiple Approvals for Apps

Requirements

IDRequirement
13Provide visibility to approvals or tasks by user, group, role.
19Provide the ability to configure an e-signature requirement for any master data definition or model's status transition in the approval workflow
461Only approved content can be used for production execution activities