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

From wizarPOS
No edit summary
(Replaced content with "{{Migrating|https://smartpossdk.gitbook.io/cloudpossdk/faq/tms-wizarview/understand-update-scenarios}}")
Tag: Replaced
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
== Execution scenario ==
{{Migrating|https://smartpossdk.gitbook.io/cloudpossdk/faq/tms-wizarview/understand-update-scenarios}}
 
{| class="wikitable"
|-
! 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.
|-
| Every six hours || Update every six hours, time begin counting from terminal switch on.
|-
| 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'''.
|}

Latest revision as of 05:05, 8 April 2024

Please visit new link of same subject:

https://smartpossdk.gitbook.io/cloudpossdk/faq/tms-wizarview/understand-update-scenarios

We're making a move! Our site's content is migrating to a new URL, to provide you with an enhanced browsing experience. Please update your bookmarks accordingly. Thank you for your continuous support!