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.
|Record Placeholders : 06 - Table Data Tab
|Signature Step : 03 - Signature form should allow any user to submit it when configured so
|Signature Step : 04 - Signature form should allow only the current user to submit it when configured so
|Signature Step : 05 - Signature forms should only be submittable a single time per process run
|Signature Step : 06 - Signature forms should display the user name and timestamp of submission in data exports
|Signature Step : 07 - Signature widgets should accept username and password in LDAP mode
|Record Placeholders : 08 - Delete Record Placeholder
|Analytics - Completion Data can be Ignored by Analytics
|User Roles : 08 - Viewers should be unable to modify data in Tulip
|Apps Page : 06 - App Completions Export Data
|Form Step - Running the Form Step
|App Editor Misc - Player Menu
|Completions - Parallel Players have separate Completions
|Dev Mode - Completions are not Saved
|Provide the ability to print the material history record
|Ability to scan and read auto-id codes generated or used by other other systems and capture their data into the material history record.
|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
|Ability for Apps to record completion of a process step with all related information
|Track process execution of the Production Models by Apps
|All material tracking history will include context of the operator performing the activities
|All material tracking history will include context of equipment used in processing
|Ability to manage and track multiple users as working on the same process step. Ie. process execution of work order, batch, lot, material, etc.
|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