Micro Focus Content Manager

Modified on Fri, 23 Feb 2024 at 03:21 PM

Micro Focus CM Integration


Integration with Micro Focus CM is one of the available submission events for Productivity Suite forms.

This has been done to integrate with local councils TRIM backend systems.


Prerequisites


The following items need to be setup before the submission event can be configured. The submission event configuration will request information from the CM instance and this will fail if the prerequisites have not been set up:

  • An account/password must be assigned
  • Basic Authentication needs to be enabled
  • The following domains need to be whitelisted by adding them to the Access-Control-Allow-Origin 

Here is an example of what your CORS configuration should look like:


<configuration>
  
  <system.webServer>
    <httpProtocol>
      <customHeaders>
        <add name="Access-Control-Allow-Origin" value="https://console.oneblink.io" />
        <add name="Access-Control-Allow-Headers" value="Content-Type,Authorization" />
        <add name="Access-Control-Allow-Credentials" value="true" />
        <add name="Access-Control-Allow-Methods" value="POST,GET,OPTIONS" />
        <add name="Access-Control-Max-Age" value="86400" />
      </customHeaders>
    </httpProtocol>
    
  </system.webServer>
</configuration>



Depending on the IIS configuration, the submission event queries may fail with a 401 due to the browser sending a preflight OPTIONS request without the authorisation header. You will need to implement a solution to return a 200 response as documented CORS with Basic or Windows Authentication


Configure Integration


Navigate to the integration page and on the Micro Focus CM card select Setup Integration.


URL - Your organisation's Micro Focus Service API URL (e.g. https://council.state.gov.au/HPECMServiceApi)

Username - You will need to provide a username of an account that has access to the service

Password -  You will also need to provide the password for the username



Configure Submission Event


To configure the Micro Focus CM submission event open the form that you wish to be capturing, and navigate to the Submission Event tab.


From here you can select ‘ADD SUBMISSION EVENT’ and select Micro Focus CM from the ‘Event Type’ drop down.

This will open up a series of configurations that will need to be set.



Record Type -  You will need to set the record type (e.g. correspondence in, invoice, policy document). A list of record types will automatically be retrieved from the API after typing the first 3 letters. 

Container - Select the container where the record will be placed.

Action Definitions - Select an action to assign to the record for the submission in the Content Manager

Location - Select a location usually a person or a group for the action.


More Options

You also have the option to set the Record Title. 


Record Title - The title of the record for how it will appear in the Micro Focus CM. From here you can customise the record title with data from the form submission. For example {FORM_NAME} - {ELEMENT:Name}, this will set the Record title to be the name of the form - the input data from the ‘Name’ Element. This can allow users to easily identify what was submitted to the Content Manager based on the record title.

Click the ‘CUSTOM VALUES’ button for more information.


Retry on failure - If this switch is enabled then the submission will be automatically retried 5 time. If all 5 of the retries fail then a notification email will be sent to the app sending email address. 


Once these settings have been configured, click the ‘SAVE’ button, and any submission of the form will be posted to your specified container. 



Get Help


If you have any question or would like assistance with setting up your Micro Focus CM integration please contact us via this support portal or email support@oneblink.io. We are happy to assist in any way we can.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article