Table of Contents
Overview
It is important for the end user to have an easy way of forcing a TMS Update. Although ChipDNA Mobile requires that the integrator performs a TMS update at least every 45 days, at times the user may need to carry out a forced update in order to download recently changed TMS properties when an update is not yet required by the SDK.
For example, if something has changed on the TMS, such as enablement of tipping, or change of maximum transaction limit, the end user then needs to force a TMS Update in order to download these new properties immediately, rather than waiting until the next required update time.
For more information on Terminal Managment System (TMS), please see our website.
*We mandate integrators add a "Force TMS Update" button in their application's settings page to provide the end user with an easy way to update their terminal when needed.
How to force a TMS update
Android:
To force a TMS Update, call
CardEaseMobile.getInstance().updateFromTms(ITmsUpdateListener tmsUpdateListener, boolean force, boolean full);
with the following parameters:
boolean force = true;
boolean full = false;
Calling this method with these parameters will force a TMS update immediately and download any new properties/settings.
*A full update will download all settings from the TMS server, including the settings which did not change since the previous update, and it is a more time-consuming update.
iOS:
To force a TMS Update, call
[[CardEaseMobile sharedInstance] updateFromTms:self force:true full:false error:&error];
with the following parameters:
BOOL force = TRUE;
BOOL full = FALSE;
Calling this method with these parameters will force a TMS update immediately and download any new properties/settings.
*A full update will download all settings from the TMS server, including the settings which did not change since the previous update, and it is a more time-consuming update.