Micro Focus Content Manager Locations Connector

Overview

The Micro Focus Content Manager Locations connector is a reading, writing, and deleting connector provided by UNIFYBroker/Micro Focus Content Manager.

This connector encapsulates the attributes in Micro Focus Content Manager locations and is typically implemented in conjunction with an associations and child connector to describe all location data.

Technical Requirements

The Micro Focus Content Manager Locations connector has no additional requirements following the listed connector prerequisites.

Usage

This connector encapsulates the attributes in Micro Focus Content Manager locations of one Micro Focus Content Manager instance.

Reading Yes
Writing Yes
Deleting Yes
Polling Yes
NOTE: Polling operations are only supported by agents configured for REST endpoints.

Schema

Fields in a Micro Focus Content Manager Locations connector refer to individual location attributes of the same name.

The schema provider for this connector will request all known attributes from the location object from the target Micro Focus Content Manager instance.

Special Cases

LocationSortNameThe name of location, is a required field for all location types except 'User'. User locations have this value set by Content Manager to be a concatenation of the various name fields. The Content Manager API dictates this field must be set, however for User locations, the value provided is ignored.
LocationSurnameA composite of the LocationSurnamePrefix and LocationSurnameNoPrefix fields. Cannot be assigned a value by UNIFYBroker.

Configuration

A Micro Focus Content Manager Location connector maintains the following configuration:

Name Description
Collection Size Requests made to the source instance are batched. This size describes the number of entities that will be processed per batch.

Filter Query

The Location connector allows the filtering of locations retrieved from Micro Focus Content Manager with a API query. For information on how to write a query, see Filtering Connectors with an API Query.

Is this article helpful for you?