The App Completions page allows users to view historical data created by a given application, as generated by the execution of an app completion.
Completion data is viewed as a table that can be filtered by date range or version of the application.
The App Completions page also permits users to export completion data as a CSV or print the page as a PDF.
View
Edit
All users that can “view” apps can also view all completions and export them to PDF.
ID | Name |
---|---|
QA-T100 | Record Placeholders : 00 - Table Data Tab |
QA-T108 | Signature Step : 03 - Signature form should allow any user to submit it when configured so |
QA-T109 | Signature Step : 04 - Signature form should allow only the current user to submit it when configured so |
QA-T110 | Signature Step : 05 - Signature forms should only be submittable a single time per process run |
QA-T111 | Signature Step : 06 - Signature forms should display the user name and timestamp of submission in data exports |
QA-T112 | Signature Step : 07 - Signature widgets should accept username and password in LDAP mode |
QA-T134 | Record Placeholders : 00 - Delete Record Placeholder |
QA-T207 | Completion Data can be set to be Ignored by Analytics |
QA-T267 | User Roles : 08 - Viewers should be unable to modify data in Tulip |
QA-T328 | Apps Page : 06 - App Completions Export Data |
QA-T347 | Form Step - Running the Form Step |
QA-T349 | App Editor Misc - Player Menu |
QA-T389 | Completions - Parallel Players have separate Completions |