specs/models/M_APP_VER_COMP
App Version Completion
A completion log is an append-only list of all "completion" events that occurred for a given Tulip App. Each completion contains base fields ( Start Time, End Time, Duration, Logged in User, Station Name, Comments, Step Time, Version) as well fields that change from App to App depending on the steps, variables, and records defined for that App.
Fields
Each completion log contains the following fields:
| Name | Description |
|---|---|
| Start Time | The time the App began running. |
| End Time | The time when the "Complete" event occurred. |
| Duration | The total time between the start and end time. |
| Logged in User | The user that was logged in at the station as the App was running. |
| Station Name | The name of the station where the completion occurred at the time it occurred. |
| Comments | Any comments added to the completion. |
| Version | The version of the App for which the completion occurred. |
| Canceled | Indicates whether the app was "canceled" in other words, halted before completion after being started. If a run of the app is cancesled, it is not considered in Analyses. |
| Execution ID | The unique ID of the completion |
| Included in Analytics | Allows the user to exclude specific rows from analytics. Typically this is used to exclude test/development completion data from appearing in production analytics. |
| Last Viewed Step Name | The name of the step that was visible when the app was completed |
| Variables | The value, at the time of the completion, for each variable in the App. Each value results in a distinct entry in the completion log. |
| Records | The value, at the time of the completion, for each record in the App. Each record results in a distinct entry in the completi |
Tests
| ID | Name |
|---|---|
| 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-T207 | Analytics - Completion Data can be Ignored by Analytics |
| QA-T328 | Apps Page : 06 - App Completions Export Data |
| QA-T651 | Signature Step : 07 / LDAP Signature Widgets should reject wrong/empty passwords |
| QA-T823 | Completions - Null Values in Completions |
| QA-T824 | Completions - All Variable Types in Completions |
| QA-T825 | Completions - Arrays in Completions |
| QA-T961 | Analytics - Completion Data can be Ignored by Analytics (cloned) |
| QA-T1044 | Completions - Table Records in Record Placeholders are captured |
Requirements
| ID | Requirement |
|---|---|
| PLAT-8865 (800) | All records shall be Contemporaneous. Data captured should include the date and time of the activity/action. |
| PLAT-8872 (830) | All data changes must be captured in audit trail. Audit trail can be turned off or on for GxP needs. This may only be performed by an administrator; it cannot be performed by a user executing an APP. |
| PLAT-8891 (816) | The manifestation of an electronic signature should contain the user's full name, date & time, meaning of signature human readable format; the record itself should contain these elements. |
| PLAT-8915 (804) | All records shall be Complete. Records shall include all data related to activity with no deletion or overwriting. |
| PLAT-8920 (802) | All records shall be Original; all originally recorded data shall be maintained. |
| PLAT-8946 (806) | All records shall be Enduring, ie. stored, managed, accessible and unalterable for the full retention period. |