Release history

Last updated: September 2020

Overview

Key features and benefits

This integration eliminates functional silos by integrating with existing enterprise systems across Archer and CLM functions thereby improving collaboration and alignment. With this integration in place, a user does not have to be a SirionLabs CLM user to create a Contract Draft Request in SirionLabs CLM from an Archer Contract.

Key points:

• The mandatory values of an Archer Contract need to be populated with necessary details to create a CDR (Contract Draft Request) in SirionLabs CLM. The Third Party associated with the contract should be specified and exist in the SirionLabs CLM environment.

• Contact a SirionLabs CLM representative to assist with setting up the integration.

Prerequisites

Components	Recommended Software
Archer Solution	Archer Third Party Governance
Archer Use Case	Archer Third Party Catalog
Archer Application	Contracts
Uses Custom Application	No
Requires On – Demand License	No

SirionLabs CLM components

Architecture diagram

Architectural approach is to abstract data layer from the logic and layout. There is a common API substrate (or a gateway) that takes care of authentication, metering, monitoring and analytics.

Configuring Archer

Note: The integration should have the access to the SMTP server where Archer triggers the notification for contract creation. You will need the integration package from the Archer Exchange – this contains XML files holding values for the custom SirionLabs CLM Values List fields.

Task 1: Configuring the Contracts application – Create new fields based on SirionLabs CLM requirements

1. Go to Application Builder Contracts to add the new fields to the Contract application.

2. Click Add New to add the fields.

3. Add the following fields to the Contracts application and set to mandatory:

Field Name	Field Type
Agreement Type	Values List
Contract Category	Values List
Paper Type	Values List
TCV	Text

4. To add the values in the Values List field, the XML files from the integration package must be imported accordingly.

5. Add all four of the created fields to the necessary Contract layouts (Creation and the Approval forms).

6. Also, add the Tracking ID field to the Contract Layout as this ID is necessary for kicking off the integration.

7. Click Save/Apply.

Task 2: Configuring the Archer XML notification

1. Click and expand the Notifications tab.

2. Click the XML Notifications option. The Manage XML Notifications page appears.

3. Click Add New to add a new notification. The Add New XML Notifications page appears.

4. Select Contracts from the Available Applications dropdown.

5. Click  OK. The Manage XML Notifications page appears.

6. Enter the Name for the XML Notification.

7. Under the Content tab, in the body, add any necessary fields from the Contract application that needs to be sent to SirionLabs CLM in the notification.

8. Enter the subject line as: “RSA Archer: Tracking ID(#[Field:Tracking ID]) is created for Contract([Field:Contract ID])”. Please note that the subject line might vary according to the client in the production version of the integration.

9. In the Delivery tab, enter the From Address. The mail will be sent from this mentioned address to the recipient via SMTP server.

   1. Configure the From Address in the Archer Control Panel.

   2. In the subsequent section (Task 3), a detailed description is available on how to setup the Archer with a Mail server.

   3. Ignore, if it is already setup.

10. For the recipient’s mail address:

    1. Contact your SirionLabs CLM representative for the integration configuration. A recipient email address will be assigned.

11. The current integration is configured for the creation of a Contract Draft Request within SirionLabs CLM, so the Filter Criteria is applied here to notify SirionLabs CLM when an RSA Archer Contract is created.

12. Click Apply/Save once the filter criteria tab is set up as below:

Task 3: Email Server Configuration in Archer Control Panel (Optional)

If the Archer instance is not configured with a mail server, follow the below steps to setup Notifications in the Archer Control Panel:

1. Open Archer Control Panel and find the Notification section under Instance Management.

2. Enter the mail server address in Server Address along with Port and Authentication information.

3. Click the Test Connection to verify the connectivity.

4. After successful connectivity, ensure the Archer Job Engine is running in the background.

   1. In Windows, you can verify that by opening Services

Using the Integration

Swimlane diagram

Task 1: SirionLabs CLM instance setup

User:

1. Integration configuration requires a SirionLabs CLM instance, the integration will be pushing newly created Archer contracts into the SirionLabs CLM environment.

2. Contact your SirionLabs CLM representative for the application setup.

3. After step 2, the integration will configure the required changes to add this integration into the SirionLabs CLM ecosystem.

Task 2: Archer Contract creation

After the SirionLabs CLM Instance is setup, verify the integration by performing below steps:

User:

1. Navigate to the Contracts application in Archer:

   1. Click the horizontal ellipsis, then click New Record to create a contract.

   2. Populate the mandatory fields and click Save and Close to create the Archer contract (other fields are optional).

2. Once the Archer contract is created, the integration will pull the Contract information and create a Contract Draft Request in SirionLabs CLM.

3. Once the integration is successful, the Archer contracts will be updated in the Contract Requests (CDR) module of SirionLabs CLM as per client defined configurations. User can view Archer specific metadata fields, such as, Contract Name, Contract Amount, and Contract Id in SirionLabs CLM Contract Requests module.

Certification environment

Date tested: September 2020

Product Name	Version Information	Operating System
Archer	6.8	Windows
SirionLabs CLM	2.x	Cloud (AWS) using Linux (Ubuntu) WMs