Integrations Hub
Jadu Content Portal has many frameworks and tool sets for integration into back office systems. In many cases, this is where data from a form is pushed to an ERP (to update an ERP record) or an ECM system (to push files and documents to a file repository or Document Imaging System).
Within Content Portal these are referred to as "Actions". Actions, once configured in the software (usually through and existing integration or through a custom integration) can be triggered by ‘Rules’ which fire when a user submits a form, or reaches the end of a form.
The integrations hub is where integration between Content Portal and other line of business systems are configured, such as Perceptive Content, Hyland OnBase, Office 365, Google, and Ellucian.
In the example of ‘Perceptive Content’ an option in the Integration Hub will be used to configure Jadu Content Portal with your Perceptive Content system (see above).
In some cases, to integrate with other on-premise systems and applications (Hub Integration Server also known as HubIS) will need to be installed on-premise (NOTE: Jadu HubIS is a separately purchased subscription based product).
It is via this software that Jadu Content Portal can be integrated securely to multiple business systems if required.
With any integrations either via the Integration Hub or via Hub Integration Server or other such middleware, an integration with a new system or a new version of an existing system, the customer is responsible for the following tasks:
- Provision of API and business process documentation for Line of Business systems to be integrated with
- Provision of APIs to both Test and Live instances of Line of Business systems.
- Test data for integration testing
- Management of line of business solutions
- Providing Jadu with at least 60 days notice when integrated line of business systems are upgraded (both partner and/or customer to provide advanced notice).
- Remote access to Line of Business Systems
In many cases, an ECM system will have a separate module or product that enables interactions and secure messaging - such as ‘Hyland Perceptive Integration Server’ which has a ‘apps’ license that enables unlimited, secure messages to and from Jadu Content Portal.
You may also want to pull data into a form (to validate data or to allow your users to verify something stored in a back office system or pick from a list of items). Within Content Portal these are referred to as ‘Integrated Components’.
Implementing AssureSign Digital Signatures
Jadu has partnered with AssureSign to deliver legal electronic signatures when your users are completed forms.
Configuring AssureSign integration
Jadu does not send a signed document directly to an ECM system - but rather enables a form to be electronically signed whilst transferring the data and any attachments (PDF and/or images) to the ECM system.
A copy of the digitally signed document is available to access from AssureSign’s control panel for evidence that a document has been electronically signed.
AssureSign to Hyland eAuthorize connection details
You will need to record access details for AssureSign when using with Hyland eAuthorize - a middleware product from Hyland Software that enables AssureSign to integrate with Perceptive Content.
| Information | Detailed Examples |
|---|---|
| UserName | Demo(perceptivecontent)@jadu.net |
| Password | ********** |
| API URL | https://sb.assuresign.net/api/documentnow/v2/wsdl |
| Context Identifier | 21ae3673-c4d3-2d2d-bb33-93955036d70e |
| Template Tag | This needs to be provided after you have set up AssureSign specifically for your implementation - See: AssureSign Tags |
AssureSign Integrated Forms
- On the AssureSign Administration Tab, open Notifications and click DocumentTRAK.
- In Completed Document Transmission section, copy the eAuthorizeExternalDocUpload
- Select Edit for the “General Information” section
- Enter a name for the web notification in the “Design Name” box
- In the Service Endpoint (URL) box, replace “[Server IP]” with this value then click next:
http://{Connect Runtime host name}:<port>/ws/SignatureEndpoint - Select EditRawXML and click Next
- Replace the original text in the XML with the following highlighted text by performing the following substeps:
- Select the existing text in the code in place of the highlighted text and click the exact parameter name enclosed in brackets in the Request XML Editing box.
- In the <field1>, <field2>, <field3>, <field4>, and <field5> tags, enter the appropriate index values for the signed document when it comes into ImageNow
- Note the values above can be static text (no brackets) or could contain the name of an AssureSign jotblock within brackets ([JotBlockName]). If any field value is empty, the corresponding field in ImageNow appears empty.
- In the <documentType> tag, enter the document type value that you want the signed document to contain
<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:esig="http://www.perceptivesoftware.com/asq/esignature">
<soapenv:Header/>
<soapenv:Body>
<esig:UploadSignedDocument>
<DOC_ID>[Document ID]</DOC_ID>
<DOC_AUTH_TOKEN>[Document AuthToken]</DOC_AUTH_TOKEN>
<DOC_ORDER_ID>[Order ID]</DOC_ORDER_ID>
<drawer>default</drawer>
<name>[Document Name]</name>
<field1>[Document Name] Field 1</field1>
<field2>[Document Name] Field 2</field2>
<field3>[Document Name] Field 3</field3>
<field4>[Document Name] Field 4</field4>
<field5>[Document Name] Field 5</field5>
<documentType>AssureSign External Default</documentType>
<DOCUMENT>[Completed Document]</DOCUMENT>
<EXTERNAL_DOCUMENT_QUEUE>SignatureComplete</EXTERNAL_DOCUMENT_QUEUE>
</esig:UploadSignedDocument>
</soapenv:Body>
</soapenv:Envelope>
Additional AssureSign Notes
- Ensure that the document keys contain unique values for signed documents. This restricts ImageNow from appending a signed third-party document.
- Provide the queue name for the EXTERNAL_DOCUMENT_QUEUE parameter to download the signed document in that queue in ImageNow.
- If you do not provide a document name for the name parameter, ImageNow uses the document ID as the default document name.
- Select Compare response to expected XML string and click Next.
- Select Edit Raw XML and click Next.
- Verify the XML looks like the following example. Create a template for document transmission. For details,see the AssureSign Quick Reference Guide for instructions to create a template.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:UploadSignedDocumentResponse
xmlns:ns2="http://www.perceptivesoftware.com/asq/esignature">
<Return>true</Return>
</ns2:UploadSignedDocumentResponse>
</soap:Body>
</soap:Envelope>
- In Workflow Template, for Web Notifications, ensure that no notifications are selected for any of the stages.
- For Document Transmission, select the design name added in step 2.
Implementing Hyland OnBase
Jadu's integration with Hyland OnBase comprises of a suite of Homepage widgets and Form functionality, allowing data to be surfaced from, and pushed into OnBase.
The integration makes use of both OnBase API Server and Hyland IdP, and requires either OnBase version of EP3 (20.3.15.1000), EP5, or above. Relevant functionality has not been back-ported to EP4.
Additionally, OnBase Quick Access Viewer whilst not a mandatory component, unlocks additional functionality for portal administrators.
Configuring Hyland OnBase integration