How to Understand Terminal Application Update Scenarios in TMS: Difference between revisions

From wizarPOS
No edit summary
No edit summary
Line 1: Line 1:
== Execution scenario ==
== Execution scenario ==
 
The update of applications on terminals from TMS is triggered under specific scenarios as follows:
{| class="wikitable"
{| class="wikitable"
|-
|-
! Scenario !! Description
! Scenario !! Description
|-
|-
| bootstrap || This operation is performed when the terminal is connected to the network for the first time after the terminal is turned on.
| Bootstrap Scenario || This update occurs when the terminal connects to the network for the first time after being powered on.
|-
|-
| Every six hours || Update every six hours, time begin counting from terminal switch on.
| Scheduled Updates Every Six Hours || Terminals are set to check for and perform updates every six hours.
|-
|-
| Click Apply push || After clicking the "Push Apps" button on WizarView, if the terminal is online, it will perform the application update. But If the app is configured in a group, and click "Push Apps" button for the the group, some of online terminals can update immediately, some of online terminals can not update correctly because of the network limitation, so the Wizarview will continue to push several times to the terminals. Terminals that are not online, will update when in '''Scenario bootstrap''' or '''Scenario 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.

Revision as of 19:04, 12 January 2024

Execution scenario

The update of applications on terminals from TMS is triggered under specific scenarios as follows:

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.

Note:

  • 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.