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.
All users that can “view” apps can also view all completions and export them to PDF.
|QA-T100||Record Placeholders : 06 - 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 - LDAP Signature Widgets should accept a correct username/password pair|
|QA-T134||Record Placeholders : 08 - Delete Record Placeholder|
|QA-T207||Analytics - Completion Data can 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|
|QA-T569||Dev Mode - Completions are not Saved|
|QA-T651||Signature Step : 07 / LDAP Signature Widgets should reject wrong/empty passwords|
|249||Provide the ability to print the material history record|
|259||Ability to scan and read auto-id codes generated or used by other other systems and capture their data into the material history record.|
|267||All process execution activities have to be recorded in history log and include the ID of user that is performing the activity and date-time stamp|
|292||Ability for Apps to record completion of a process step with all related information|
|293||Track process execution of the Production Models by Apps|
|348||All material tracking history will include context of the operator performing the activities|
|349||All material tracking history will include context of equipment used in processing|
|380||Ability to manage and track multiple users as working on the same process step. Ie. process execution of work order, batch, lot, material, etc.|
|813||All data shall be Attributable; data must be identified to the person who did the data collection. Records shall include information about how the data was acquired, action/activity performed, where and and when|