Skip to content

FAQ

Why can’t I store the settings on my Xesar 3 installation?! The most likely issue is, that you need to change the pin code for the Xesar Tablet before you can save the settings. This has been changed in newer versions of Xesar 3.

How can I obtain the identifiers for the new entity metadata? Currently if you have not acquired the identifiers for the metadata you cannot set them on new entities you create through the interface.

Unfortunately there is no query for listing these, so the only viable option is to cause a PartitionChanged(https://integrations.api.xesar.evva.com/#operation-subscribe-xs3/1/ces/PartitionChanged-message) Event that will give you the definitions.

You can do that for example by using a SetDailySchedulerExecutionTimeMapi call. Once you have the identifiers, you can set the right metadata fields when creating a new entity.

How can I clear the authorization profile for a user? You can set the authorization profile using SetDefaultAuthorizationProfileForPersonMapi.

The value for the key defaultAuthorizationProfile needs to be null as a token (as defined by JSON grammar) and not as a string.

How can I set the default for the validity when adding a smartphone? When you add a new smartphone using the AddSmartphoneToInstallationMapi you can omit the key validityDuration (i.e. don’t add this property). This way you will get the default from XS3 configuration.

What is the meaning of the LOCKED_INSECURE and LOCKED_SECURE states on my mobile phones? LOCKED_INSECURE means the blacklist was not yet distributed to all components the identification medium had access to, so there may still be access.

LOCKED_SECURE means that the blacklist was distributed to all components the identification medium had access to, so there is no access any more. Alternatively it might also be that it can no longer be valid, so it was marked as secure in the backend.

Why can’t I remove a locked identification medium or mobile phone? There is currently no way to delete any identification media.

The historic reason for this is simple to explain:

  1. if it is broken, you cannot know if it is the right one you were given back
  2. the access system is always required to keep and correlate all the records

A way to make them less visible is in the queue (kind of a Schrödinger’s State). For mobile phones the design decision was to make them exactly like RFID media, so that’s what it is now.

Will revoking a smartphone cause blacklisting? Yes, a revoke will cause blacklisting.

How do I acquire the information to confirm the revocation of a smartphone using ConfirmSmartphoneRevokeMapi?
  1. Xesar will emit the event SmartphoneRevokePending whenever a smartphone is revoked.
  2. Your service (middleware) should know what to do with it’s supported app and then send a ConfirmSmartphoneRevokeMapi with the corresponding parameters from (1).
  3. Xesar will emit a ‘SmartphoneRevokeConfirmed’

What if the service missed ‘SmartphoneRevokePending’? If your service misses the SmartphoneRevokePending and looses track of the transaction IDs or state of the Smartphone, you can query the identification-media-access-data resource via xs3/1/q. This resource is also filterable by the state field - here REVOKED - if you need to find Smartphones in a specific transaction state. e.g.:

{
  "requestId": "dc9b0595-eaf6-4c81-b4e0-995be7e1c76d",
  "token": "<Your token>",
  "resource": "persons",
  "params": {
    "pageOffset":0,
    "pageLimit":50,
    "filters":[
      {
        "type": "eq",
        "field": "identifier",
        "value": "2133"
      }
    ]
  }
}

You can then re-issue a RevokeSmartphoneMapi and Xesar 3 will emit the event SmartphoneRevokePending and you can proceed with steps 2) and 3) from “How do I acquire the information to confirm the revocation of a smartphone using ConfirmSmartphoneRevokeMapi?”