Follow these guidelines for choosing an appropriate application ID
while registering application connection for use by native MBO, workflow, or Online Data
Proxy clients. Failure to specify the correct application ID would result in failure when
the client tries to activate itself even though the user name and activation code do
match.
| Registration Type |
Application ID Guidelines |
|---|
| Workflow client |
- 2.0.1 or earlier
– leave the application ID empty.
- 2.1 or later
– use preexisting "HWC" template, or, if using your
own template, make sure that "HWC" is set as the
application ID in the template.
- iOS Sample container 2.1
or
later – use the template you have
created. The application ID used by the iOS sample
container should match the application ID specified
in registration.
|
| Native MBO application |
- Previous to 2.1.2 – leave the
application ID empty. This applies to native
messaging-based application
clients.
- 2.1.2 or later – (recommended) use the
application connection template that is automatically
created for the application. Otherwise, ensure you
register application connection with the correct
template by verifying that application id matches, and
that the correct security configuration and domain are
selected. Also, if using replication synchronization,
set other template properties (such as
synchronization-related properties in Connection
category) as required. For Android native MBO
application, this recommendation applies starting with
2.1.1.
|
| Online Data Proxy
client |
Register application connection using the
template created for the application. Existing templates can
be found in the tab.
|