Marmind integration

Prerequisites

• You need to be on Censhare Cloud

• You need to become a Marmind customer

Please reach out to your project manager to learn how to fulfil these requirements.

Steps to start with Marmind

Once the prerequisites are met, you will need to:

• Obtain the license

• Wait for the integration to be deployed

• Opt., configure the SSO (default is done by the Censhare IT, detailed instructions can be found in the partner documentation, login required)

• Enable the Marmind module in the Censhare Admin Client (to be done by the Censhare IT)

• Opt., configure the Marmind APIs as described below (default is done by the Censhare IT)

Marmind module configuration in the Admin Client

Marmind integration comes pre-configured and enabled in the Admin Client. Usually, those default settings never need to be changed and we do not recommend changing them.

Public and Sync APIs

Marmind configuration can be found under Configuration → Modules → Entirely Integration → Marmind Integration (Public API)/(Sync API). For now, some settings are the same as in the HCMS server module configuration, with the same logic.

For the Marmind integration, you have two configurations, for two different APIs.

• Public API acts on behalf of the user in the Marmind UI when browsing or adding assets as explained here

• Sync API keeps data in sync between two systems when assets are edited

Their settings are identical, except the authentication.

Public API requires an authorization as a proper Censhare user and uses that user’s permissions. It is called, e.g., when the user browses Censhare assets while staying in the Marmind UI for the purpose of adding them to a Marmind object.

Sync API uses a system user and enalbes a background synchronization. Changes done on the assets in one system are propagated to the other using this API.

Asset filter

By default, the integration only refers to the current version of the asset. It is recommended to leave this filter as-is. In case of changes, the entire logic of the integration may change. This needs to be planned carefully.

The same applies to adding any new filters. It may only make sense to filter out the assets that are checked out to avoid confusion when two users edit the same asset but from the different system.

Known issues

Censhare Web Client has a known issue with the session timeout: after 25 minutes of an inactive session, the application will enforce a user log out. Unfortunately, this issue also influences the behaviour of the Marmind web client.

In the Marmind web client, after 25 minutes of inactivity on the assets, you won’t be able to perform any actions on them. You will be able to use the rest of the Marmind interface normally. In such cases, you need to log out and log in again.