App Approval
An App Approval is an instance of an Approval Type that has been assigned to a specific app.
An App Approval can have one or many approvers assigned to it.
After an App Approval has been created, only one approver must sign in order to complete the approval of the next published version of the app.
So, if the “Quality” Approval Type is assigned to an app, and there are 3 approvers assigned within this App Approval, then only one of these approvers needs to sign the App Approval on every future version of the app.
The number of Approval Types within the Tulip Account limits the number of App Approvals that can be assigned to an individual app.
By default, there are no App Approvals assigned to Apps. An App Owner must assign App Approvals to each app that they create.
Common examples of App Approvals include “Quality” and “Compliance”.
Fields
| Name | Description |
| Name | The name of the Approval Type assigned to the App |
| Description | The description of the Approval Type assigned to the App |
| Approver List | The list of all Tulip users that can sign as the approver for this App Approval on all future published versions of the app |
| Enabled | A boolean value that indicates whether this App Approval will be used for future published versions of the app |
Tests
| ID | Name |
|---|---|
| QA-T329 | Apps Page : 08 - App Approvals Setup |
| QA-T330 | Apps Page : 09 - App Approvals during Publishing |
| QA-T386 | Apps Page : 10 - App Testing during Approvals |
| QA-T523 | Apps Page : 11 - Multiple Approvals for Apps |
Requirements
| ID | Requirement |
|---|---|
| 11 | Provide a configurable workflow for approval of new or modified content (including connectors, components, tables) |
| 15 | Provide ability to apply status to managed content. E.g. Development, In Review, Released, Published, etc. |
| 25 | Material history records must include exception approval log. |
| 52 | Content must have configurable workflow to require a review and approval by people with appropriate authority before they are published for use in production. |
| 248 | Ability to define and maintain batch record documentation for regulatory compliance (electronic batch record) |
| 461 | Only approved content can be used for production execution activities |
| 820 | Electronic signatures have to be secured and not allowed to be falsified. They can only be used by their genuine owners. |