|
|
| (One intermediate revision by one other user not shown) |
| Line 1: |
Line 1: |
| == Execution scenario ==
| | {{Migrating|https://smartpossdk.gitbook.io/cloudpossdk/faq/tms-wizarview/understand-update-scenarios}} |
| The update of applications on terminals from TMS is triggered under specific scenarios as follows:
| |
| {| class="wikitable" | |
| |-
| |
| ! Scenario !! Description
| |
| |-
| |
| | Bootstrap Scenario || This update occurs when the terminal connects to the network for the first time after being powered on.
| |
| |-
| |
| | Scheduled Updates Every Six Hours || Terminals are set to check for and perform updates every six hours.
| |
| |-
| |
| | Manual 'Push Apps' Activatio || When the "Push Apps" button is clicked on WizarView:
| |
| * If the terminal is online, it will immediately begin the application update process.
| |
| * For terminals configured within a group and receiving a group-wide push, some may update instantly while others might face delays or issues due to network limitations. WizarView will make several attempts to push the update to these terminals.
| |
| * Terminals that are not online during the push will receive the update in the next '''bootstrap scenario''' or during the '''Scheduled Updates Every Six Hours'''.
| |
| |}
| |
| ==== <big>Note:</big> ====
| |
| * '''Network Dependency:''' The success of immediate updates (especially in the case of manual pushes) is dependent on the network status of the terminals. Offline terminals will adhere to the bootstrap or scheduled update scenarios.
| |
| * '''Continual Push by WizarView:''' For terminals experiencing network issues or other update barriers, WizarView will continue attempting to push the update until successful.
| |
Latest revision as of 05:05, 8 April 2024
