Auto Config Profiles

PLEASE NOTE: AUTO CONFIG PROFILES IS AN EXTENSION OF THE AUTO CONFIG FEATURE AND IS RESTRICTED AND ONLY AVAILABLE AS BETA THROUGH OUR EARLY ACCESS PROGRAM. PLEASE FILL OUT THE REGISTRATION FORM TO APPLY.

The Auto Config Profiles enable you to define configurations on MARK and PG Connect (profiles) through a new web-based configuration tool, export / import them into PG Connect and control them through SDK or Intent API level functions. Once released, the feature will deprecate the AutoConfig as it provides the same and much more functionality.

What is a profile?

  • A profiles is a wrapper which encapsulate PG Connect and MARK configuration. Each profile contains MARK configurations and PG Connect Settings (Integration Path and Workflow Rules). A profile is defined inside a *.proconfig file.

When are configurations of Profile 0 applied?

  • Profile 0 is the default profile. It will be triggered implicitly by pairing MARK with PG Connect.

What is the *.proconfig file format?

  • The *.proconfig configuration file consists of one default profile and up to 69 custom profiles
  • The *.proconfig configuration file is not compatible with the *.pgconf file from the AutoConfig
  • The *.proconfig configuration identifies a profile with a unique profile name (id).
  • In order to create a *.proconfig file you require accesss to a new web-based configuration tool in order to export a *.proconfig configuration file (available through early access programme)

What is the Profile 0? When is it applied?

  • Profile 0 is the default profile.
  • The MARK settings will be triggered implicitly by pairing MARK with PG Connect
  • PG Connect Setting are also applied from the default profile when a MARK is paired.

Please note: The last active profile is not triggered automatically but only the deault one

How to import Your Configuration via MDM?

To import the *.proconfig file exported from the web-base, push it to /sdcard/Android/data/de.proglove.connect/files/ProGlove.proconfig (using this location usually does NOT require setting the storage permission through the MDM beforehand). Please make sure your config file has the exact name ProGlove.proconfig. After the file has been added to the correct location, it will be automatically imported by the app, even if it is already running.

Implicit and explicit triggering of a profile

Only one profile can be active at a time. Profiles trigger in two ways:

  • By pairing with MARK (implicitly)
  • By activating it via Intent/SDK (explicitly, using profile id)

Only the default profile is triggered implicitly. This happens every time the MARK pairs. This doesn't happen when connection is lost and re-established again, but only with new connections. Every profile can be triggered explicitly.

Please note: Explicit activation is only successful if profile with the specified id exists in the configuration file and the MARK device is connected when using the SDK Integration Path and there is no MARK connected to Android, an error is thrown. When using Intent integration Path, compared to the SDK there is no possibility to throw an error. Please check for a connection state with MARK before applying your desired profile.

Configuration lifecycle

MARK configuration is persistent. This means that, once the MARK is configured during the profile activation, the configuration remains on the MARK until new profile is activated. If the MARK disconnects, the configuration from the last active profile will remain on it. If it connects again, it will be configured with the configuration from default profile. If another profile gets activated via Intent/SDK, it will be configured with the configuration from that profile.

So, only profile activation can change the configuration on MARK. Putting it on a charger, rebooting or connecting it with an Access Point will not change its configuration.

Please note: Please do not use MARK with PG Connect and the Access Point One S in parallel unless you know what you do

Auto Config Profile and PG Work View

Workflow Rules and Integration Paths are disabled in PG Connect UI as long as the *.proconfig configuration file exists. Changing Workflow Rules through UI is disabled as long as the *.proconfig configuration file exists and has a valid name. If the MARK disconnects and connects again, the Workflow Rules from default profile will be set. If another profile gets activated via Intent/SDK, the Workflow Rules from that profile will be set.

So, when *.proconfig configuration file exists, only profile activation can change the Workflow Rules.