specs/models/M_APP_VER_COMP
App Version Completion
A completion log is an append-only list of all "completion" events that occured 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 occured. |
| 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 occured at the time it occured. |
| Station ID | The unique ID of the station where the completion occured |
| Comments | Any comments added to the completion. |
| Step Time | How long was spent on each individual step. |
| Step List | A list of all steps and step groups in the app at the time of completion |
| Version | The version of the App for which the completion occured. |
| 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 completion log. |
| Application Name | The name of the application at the time that the app was completed |
| Application ID | The unique of the ID of the application where the completion was registered |
| Execution ID | The unique ID of the completion |
| 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. |
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-T389 | Completions - Parallel Players have separate Completions |
| QA-T651 | Signature Step : 07 / LDAP Signature Widgets should reject wrong/empty passwords |
Requirements
| ID | Requirement |
|---|---|
| PLAT-8775 (62) | Data from integrations is historized, stored for use in trending and analysis |
| PLAT-8865 (800) | All records shall be Contemporaneous. Data captured should include the date and time of the activity/action |