Last modified on 18 August 2016, at 11:49

Client

Revision as of 11:49, 18 August 2016 by KNO (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Why are my changes of ACM objects not deployed to the mobile device?

If you modify the ACM objects (Application, Context, Context Scope) you will need to re-create and deploy the new configuration. See the Release MetaDefinitions article how to do that.

What are Metaio ID-Markers and how can I use them?

Check the informatoin on the Metaio site about ID-Markers.

Images can not be opened although I can see the according UBIK® object (and thumbnails). Why?

The UBIK® Client synchronizes and displays objects delivered by the ACM. As a document in UBIK® actually consists of two parts, the internal document object AND the physical file document, the system always delivers the internal document object to the client.

If it happens that the account configured for running the UBIK® web service can not access the physical document, e.g. due to missing permissions, we find the following situation:

  • The client displays the internal document object, as its synchronisation is basically independent of the physical document
  • But openening the document will fail as the web service can not access (load and deliver) the file content

The client shows a wrong icon for an object, although the MetaClass does have a specific one! What is wrong?

The icon is sent to the client within the meta defintions, which are created based on the linked MetaClasses in the MetaClass scopes. Consequently, a specific icon of a MetaClass requires that a scope exists for exactely this MetaClass (and e.g. not for the inherit parent).

Do I need to reinstall the certificate after I de-/installed the application itself?

No, the certificate is placed in a global certificate store and remains valid.

Can I use the same LLA Markers for UBIK.WinX and UBIK.Android?

No, as we are not using the (proprietary) Metaio format in the Windows version. The new kind of markers for relocating devices to different positions are basically QR-Codes with a special notation. If you want to create one you simply have to create a QR-Code (e.g. with GoQR) with the following notation:

<UBIK>
    <LLA>Latitude;Longitude;Altitude</LLA>
</UBIK>