A user has activated but has not received any Data

Data loads are not always automatically invoked whenever a user activates, it is controlled using the system key: perform.initload.process

If this key is set to Nil, a load will not begin after activation and must manually be invoked.  To manually invoke a load:

  1. Open the Swift MEAP™ Admin Console
  2. Navigate to the Users page by selecting Users in the left menu
  3. Locate your user in the list and place a mark in the check box next to their details
  4. Select: Data Load->Initload

A new data load will be sent to your user.

Setting the value of the perform.initload.process key in Administrator -> System Keys will control future behavior.

 

You also need to check if a load is in progress, ready or completed for the user.   Once a load has been initialized and the device polls the server, the 'Data Load' screen is displayed on the device and the application cannot be used until the load completes.  The user may believe that the load begins immediately, but the device is locked even when no data is being downloaded.  This is done to prevent the user altering data while new data is being downloaded.

As the load process can take some time, do not assume the device is stuck until the load progress has been checked in the server.  To check the load progress:

  1. Log into the Swift MEAP™ Admin Console
  2. Open the Queues->Initload Summary menu. 
  3. Search for your user and check the status of the load.

Is the load READY or FAILED, are there any errors displayed?  If the load is IN PROGRESS, please be patient, the server is still processing data received from your data source.  The client will not attempt to retrieve part of the load until the entire load is READY.

User not received data - follow up actions

If all of the above has been checked and the issue has not been resolved, please provide your configuration, client logs, server logs and user details to support.

Please also provide information on the dates/times that activation took place and a full summary of the issue.  Note: Logs are required for the period in which activation / data load was attempted.