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.
The following Pages must be properly configured before this Page will work properly:
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
|QA-T267||User Roles : 08 - Viewers should be unable to modify data in Tulip|
|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|
|13||Provide visibility to approvals or tasks by user, group, role.|
|19||Provide the ability to configure an e-signature requirement for any master data definition or model's status transition in the approval workflow|
|461||Only approved content can be used for production execution activities|