LexisNexis Regulatory Compliance

The Archer LexisNexis Regulatory Compliance integration allows you to automatically import regulatory compliance data directly into the Archer Policy Program Management and Corporate Obligations Management use cases. The enhancements made to the solutions allows users view the regulatory alerts linked to the regulatory obligations. Archer Corporate Obligations Management then delivers the tools you need to analyze regulatory news, automatically notify responsible personnel, and proactively address issues before they impact your organization.  Additionally, Archer produces real-time reports and user-specific dashboards to view regulatory news, type, and impact to your organization, and to monitor the overall status of your regulatory change management program.

On this page

Release notes

Release Version

Release Date

Notes

Archer 6.6

August 2019

Initial Release

Archer 6.8

November 2020

Offering Updated:

  • Allow customer to ingest Historical Notes content through the Obligations/Sub Obligations JST data feed.

  • The LexisNexis JavaScript file was updated for improved performance for data feeds.

  • The XSLT in the data feeds was updated to use the Date format DD/MM/YYYY.

  • Package Version: The Tools ODA package has been updated to 6.8

Archer 6.8

December 2020

The LexisNexis JavaScript file was updated to capture features/functionality from the Enhanced Content modules.

Archer 6.8

December 2021

Re-Signed JavaScript file.

Archer 6.8

November 2022

Archer has removed the old xmldom library. JS file has been updated to use @xmldom/xmldom library.
Data Feed Manager JavaScript Transporter Scripts Require Update - Archer Community - 683320 (archerirm.community)

Archer 6.12

March 2023

Offering Updated:

  • The LexisNexis JavaScript file was updated to fix the issue related to initial full load of Mandates.

  • The Regulatory Compliance and Enhanced Content Implementation guides have been combined into a single document.

Archer 6.12

August 2023

  • Obligations data feed was processing only the first page content instead of all pages. The LexisNexis JavaScript file was updated to fix the issue related to processing of all page content in Obligations feed.

  • The XSLT code in Alerts data feed has been updated: Module Name can be used instead of Module ID now for mapping.

  • The Source Definition content in Mandates data feed has been updated: Level 1 to Level 4 has been renamed to Source, Topic, Section and Sub-Section to match Authoritative Sources levels naming conventions.

Archer 6.12

June 2024

Re-Signed JavaScript file.
Archer 6.12 January 2025 Bug fix: If a Section moves from one Topic to another, because the data feed is mapping the Section to the Topic, this update is not being applied as the differential data feed is set to append not replace.

Solution: The data feed is now split into 4 data feeds targeting each level replacing it's parent.

Known issues / Limitations

Component

Description

Mandates Content

The Mandates data feed are mapped to the 4 levels in the Authoritative Sources application. If users need > 4 levels (Based on LexisNexis Content Subscription) mapping, then users need to reconfigure Authoritative Sources to accommodate them. Refer Appendix II for more information.

Overview

The Archer LexisNexis Regulatory Compliance Enhanced Content integration allows you to automatically import regulatory data directly into the Archer Policy Program Management use case. The enhancements made to the solutions allows users view the regulation (mandate) and the designated regulator linked back to the regulatory obligations. Archer produces real-time reports and user-specific dashboards to view the mandates tied to specific regulations and the compliance of those mandates as tested through the Controls Assurance solution. This integration builds on the LexisNexis Regulatory Compliance integration which pulls in the Obligation/Sub Obligation, Tools, and Regulatory Alerts.

Key features and requirements

Key benefits

LexisNexis Regulatory Compliance integration with Archer enables organizations to:

  • Consolidate information from multiple regulatory bodies.

  • Be alerted to changes or references to these regulatory obligations.

  • Document the impact and sustain a repeatable auditable regulatory change program.

  • Report on activities related to regulatory issue remediation.

  • Implement a consistent and repeatable regulatory change management process.

  • Centrally manage Regulations, Laws and Requirements and map them to Regulators, Obligations and Policies.

  • Report on overall compliance of the Regulation within the organization.

Requirements

Components

Requirement

Archer Solution

Regulatory & Corporate Compliance Management

Archer Use Case(s)

The following use cases can take advantage of the information provided by the LexisNexis Regulatory Compliance integration:

  • Archer Policy Program Management

  • Archer Corporate Obligations Management

Archer Applications

Leverages the following applications:

  • Control Standards

  • Regulatory Intelligence Items

  • Authoritative Sources

Uses Custom Application

One (1) - Two (2) On-Demand Application is required.

  • Tools

  • Regulators

Requires On-Demand License

Yes

Archer Requirements

Archer release 6.12 or later

LexisNexis Requirements

Valid LexisNexis Regulatory Compliance license is required for Obligations Alerts and Tools content.

Valid LexisNexis Enhanced Content license is required for Mandates and Regulators content.

Supported Platform Version

This offering has been developed for and validated on Archer Platform release 6.12 

 

LexisNexis offers various type of content.

  • Regulatory Compliance data feeds. Content is delivered via Control Standards, Regulatory Intelligence Items and Tools (ODA).

  • Enhanced Content data feeds is an Add-on to the existing LexisNexis Regulatory Compliance. Content is delivered via Authoritative Sources and Regulators (ODA).

Customers need to configure and install the necessary components based on their LexisNexis content subscription. The Archer Package supports Obligations / Sub-Obligations, Alerts, Tools, Mandates and Regulators content from LexisNexis.

Integration flow

The following diagram provides an overview of interaction between LexisNexis Regulatory Compliance and Archer.

The integration process follows the following flow:

  1. The Archer data feed for the LexisNexis Regulatory Compliance Integration pulls the data from the source: LexisNexis Regulatory Compliance API URL and imports the data into Target: Control Standards, Regulatory Intelligence Items Application and Tools ODA.

  2. When the user logins into the LexisNexis Regulatory Compliance URL, a list of all the obligations, sub-obligations, alerts/notifications, and tools available are visible.

The following diagram provides an overview of interaction between LexisNexis Regulatory Compliance - Enhanced Content and Archer.

Graphical user interface Description automatically generated

The integration process follows the following flow:

  1. The Archer data feed for the LexisNexis Regulatory Compliance Enhanced Content Integration pulls the data from the source: LexisNexis Regulatory Compliance Enhanced Content API URL and imports the data into Target: Authoritative Sources application and Regulators ODA.

  2. When the user logins into the LexisNexis Regulatory Compliance Enhanced Content URL, a list of all the Mandates and Regulators available are visible.

Configure LexisNexis Regulatory Compliance

Before you begin 

This section provides instructions for configuring the LexisNexis Regulatory Compliance offering with the Archer Platform.  This document is not intended to suggest optimum installations or configurations. 

It is assumed that the reader has both working knowledge of all products involved, and the ability to perform the tasks outlined in this section. Administrators should have access to the product documentation for all products to install the required components.

All LexisNexis Regulatory Compliance links must be working prior to the integration. Perform the necessary tests to confirm that this is true before proceeding. 

Important: The integration described in this guide is being provided as a reference implementation for evaluation and testing purposes.  It may or may not meet the needs and use cases for your organization.  If additional customizations or enhancements are needed, it is recommended that customers contact Professional Services for assistance.

Configuring Archer

Before you import the LexisNexis Regulatory Compliance data feeds, complete the following tasks. First, install Archer LexisNexis Tools 6.12 Install Package.zip in your Archer environment, Version 6.12 or above. Then configure Control Standard and Regulatory Intelligence Items applications for the LexisNexis Regulatory Compliance Integration.

Before you import the LexisNexis Regulatory Compliance Enhanced Content data feeds, complete the following tasks. First, install Archer LexisNexis Regulators 6.12 Install Package.zip in your Archer environment, Version 6.12 or above. Then configure Authoritative Sources application for the LexisNexis Regulatory Compliance Enhanced Content Integration.

Installing the package

The following tasks detail how to import and install the Archer LexisNexis Tools 6.12 Install Package.zip.

Step 1: Back up your database

There is no Undo function for a package installation. Packaging is a powerful feature that can make significant changes to an instance. strongly recommends backing up the instance database before installing a package. This process enables a full restoration if necessary.

An alternate method for undoing a package installation is to create a package of the affected objects in the target instance before installing the new package. This package provides a snapshot of the instance before the new package is installed, which can be used to help undo the changes made by the package installation. New objects created by the package installation must be manually deleted.

Step 2: Import the package

  1. Go to the Install Packages page.

    1. From the menu bar, click .

    2. Under Application Builder, click Install Packages.

  2. In the Available Packages section, click Import.

  3. Click Add New, then locate and select the package file that you want to import.

  4. Click OK.

The package file is displayed in the Available Packages section and is ready for installation.

Step 3: Map objects in the package

  1. In the Available Packages section, select the package you want to map.

  2. In the Actions column, click Analyze for that package.

    The analyzer runs and examines the information in the package. The analyzer automatically matches the system IDs of the objects in the package with the objects in the target instances and identifies objects from the package that are successfully mapped to objects in the target instance, objects that are new or exist but are not mapped, and objects that do not exist (the object is in the target but not in the source).

    Note: This process can take several minutes or more, especially if the package is large, and may time out after 60 minutes. This time-out setting temporarily overrides any IIS time-out settings set to less than 60 minutes.

    When the analyzer is complete, the Advanced Package Mapping page lists the objects in the package file and corresponding objects in the target instance. The objects are divided into tabs, depending on whether they are found within Applications, Solutions, Access Roles, Groups, Sub- forms, or Questionnaires.

  3. On each tab of the Advanced Mapping Page, review the icons that are displayed next to each object name to determine which objects require you to map them manually.

The following table describes the icons.

Icon

Name

Description

Awaiting mapping review

 

 

 

Awaiting Mapping Review

Indicates that the system could not automatically match the object or children of the object to a corresponding object in the target instance.

Objects marked with this symbol must be mapped manually through the mapping process.

Important: New objects should not be mapped. This icon should remain visible. The mapping process can proceed without mapping all the objects.

Note: You can execute the mapping process without mapping all the objects. The Awaiting mapping review icon is for informational purposes only.

Checkmark

 

 

 

Mapping Completed

Indicates that the object and all child objects are mapped to an object in the target instance. Nothing more needs to be done with these objects in Advanced Package Mapping.

Missing objects

 

 

Do Not Map

Indicates that the object does not exist in the target instance or the object was not mapped through the Do Not Map option. These objects will not be mapped through Advanced Package Mapping and must be remedied manually.

 

 

Undo

Indicates that a mapped object can be unmapped. This icon is displayed in the Actions column of a mapped object or object flagged as Do Not Map.

  1. For each object that requires remediation, do one of the following:

    • To map each item individually, on the Target column, select the object in the target instance to which you want to map the source object. If an object is new or if you do not want to map an object, select Do Not Map from the drop-down list.

      Important: Ensure that you map all objects to their lowest level. When objects have child or related objects, a drill-down link is provided on the parent object. Child objects must be mapped before parent objects are mapped. For more details, see " Parent and Child Object Mapping " in the Archer Online Documentation.

    • To automatically map all objects in a tab that have different system IDs but the same object name as an object in the target instance, do the following:

    1. In the toolbar, click Auto Map.

    2. Select an option for mapping objects by name.

The following table describes the options.

Option

Description

Ignore case

Select this option to match objects with similar names regardless of the case of the characters in the object names.

Ignore spaces

Select this option to match objects with similar names regardless of whether spaces exist in the object names.

c. Click OK.

The Confirmation dialog box opens with the total number of mappings performed. These mappings have not been committed to the database yet and can be modified in the Advanced Package Mapping page.

d. Click OK.

  • To set all objects in the tab to Do Not Map, in the toolbar, click Do Not Map.

    Note: To undo the mapping settings for any individual object, click in the Actions column.

    When all objects are mapped, the Checkmark icon is displayed in the tab title. The Missing objects icon is displayed next to the object to indicate that the object will not be mapped.

  1. Verify that all other objects are mapped correctly.

  2. (Optional) To save your mapping settings so that you can resume working later, see "Exporting and Importing Mapping Settings" in the Archer Platform Help.

  3. Once you have reviewed and mapped all objects, click .

  4. Select I understand the implications of performing this operation and click OK.

The Advanced Package Mapping process updates the system IDs of the objects in the target instance as defined on the Advanced Package Mapping page. When the mapping is complete, the Import and Install Packages page is displayed.

Important: Advanced Package Mapping modifies the system IDs in the target instance. Any Data Feeds and Web Service APIs that use these objects will need to be updated with the new system IDs.

Step 4: Install the package

All objects from the source instance are installed in the target instance unless the object cannot be found or is flagged to not be installed in the target instance. A list of conditions that may cause objects not to be installed is provided in the Log Messages section. A log entry is displayed in the Package Installation Log section.

  1. Go to the Install Packages page.

    1. From the menu bar, click .

    2. Under Application Builder, click Install Packages.

  2. In the Available Packages section, do the following:

    1. Locate the package file you want to install.

    2. In the Actions column, click Twin gears.

  3. In the Selected Components section, select the components of the package that you want to install.

    • To select all components, select the top-level checkbox.

    • To install only specific global reports in an already installed application, select the checkbox associated with each report that you want to install.

      Note: Items in the package that do not match an existing item in the target instance are selected by default.

  4. Click Lookup.

  5. For each component section, do the following:

    Note: To move onto another component section, click Continue or select a component section in the Jump To drop-down menu.

    1. In the Install Method drop-down menu, select an install method for each selected component.

      Note: If you have any existing components that you do not want to modify, select Create New Only. You may have to modify those components after installing the package to use the changes made by the package.

    2. In the Install Option drop-down menu, select an install option for each selected component.

      Note: If you have any custom fields or formatting in a component that you do not want to lose, select Do Not Override Layout. You may have to modify the layout after installing the package to use the changes made by the package.

  6. Click OK.

  7. To deactivate target fields and data-driven events that are not in the package, in the Post-Install Actions section, select the Deactivate target fields and data-driven events that are not in the package checkbox. To rename the deactivated target fields and data-driven events with a user-defined prefix, select the Apply a prefix to all deactivated objects checkbox, and enter a prefix. This can help you identify any fields or data-driven events that you may want to review for cleanup post-install.

  8. Click Install.

  9. Click OK.

Step 5: Review the package installation log

  1. Go to the Package Installation Log tab of the Install Packages page.

    1. From the menu bar, click .

    2. Under Application Builder, click Install Packages.

    3. Click the Package Installation Log tab.

  2. Click the package that you want to view.

  3. In the Package Installation Log page, in the Object Details section, click View All Errors.

    For a list of packaging installation log messages and remediation information for common messages, see “Package Installation Log Messages” in the Archer Platform Help.

Step 6: Adding tools ODA to Regulatory and Corporate Compliance workspace

  1. Go to the Workspaces page.

    1. From the menu bar, click .

    2. Under Workspaces and Dashboards, click Workspaces.

  2. Select Regulatory and Corporate Compliance.

  3. Go to Workspaces Menu tab.

  4. Search Lexis Nexis Compliance and add to the list.

  5. Click Save.

Enhanced Content package installation

Refer Steps 1 to 5 from Installing the Package to import and install the Archer LexisNexis Regulators 6.12 Install Package.zip.

Step 7: Adding regulators ODA to Regulatory and Corporate Compliance workspace

  1. Go to the Workspaces page.

    1. From the menu bar, click .

    2. Under Workspaces and Dashboards, click Workspaces.

  2. Select Regulatory and Corporate Compliance.

  3. Go to Workspaces Menu tab.

  4. Search Lexis Nexis Compliance and add to the list as shown below:

Graphical user interface, application Description automatically generated

  1. Click Save.

Configure control standards application

Task 1:  Add fields to the control standard application

  1. Navigate to Applications by clicking the Administration dropdown menu and selecting Applications under Application Builder.

  2. Select the Control Standards application and navigate to the Fields tab.

  3. Edit the Content Source Values List field and Add a new value “LexisNexis”.

  4. In the Fields tab. Add the following fields:

    1. Obligation Type

      1. Type: Value List (Field Specific)

      2. Display options: Dropdown

      3. Values:

        1. Obligation

        2. Sub-Obligation

    2. Jurisdiction

      1. Type: Value List (Field Specific) 

      2. Display Option: Values Popup; Maximum Selection=No Maximum

    3. Sub-Obligations

      1. Type: Cross-Reference

      2. Available Reference: Control Standards

      3. Display Control: Grid

      4. Record Lookup Configuration/Grid Display Properties Display Fields: Standard Name, Statement, Jurisdiction

    4. Parent Obligations: After creating the above cross-reference field, find and rename the field Control Standards (Sub-Obligations) to Parent Obligations

      1. Type: Related Records

      2. Available Reference: Control Standards

      3. Display Control: Grid

      4. Record Lookup Configuration/Grid Display Properties Display Fields: Standard Name, Statement, Jurisdiction

    5. Number Of Sub-Obligations: Numeric (Calculated field)

      1. Type: Numeric

      2. Options: Calculated Field

      3. Formula:

      4. IF(NOT(ISEMPTY([Sub-Obligations])), COUNTA([Sub-Obligations]), NOVALUE())

    6. Historical note

      1. Type: Text

      2. Display Control: Text Area

  5. Navigate to Layout -> Designer tab -> Add New Layout Object.

  6. Add Tab Set named “LexisNexis Content”. Add the following tabs under it:

    1. General Information

    2. Practical Guidance

    3. Consequence

    4. Remedial Action

    5. Content Source

  7. Add Section named “LexisNexis Content” under “General Information” tab.

  8. Add Section named “Historical Note” under “General Information” tab.

  9. Place all the above created fields in “General Information” and “Historical Note” sections as shown in the screenshot below

Graphical user interface, application Description automatically generated

  1. Click Apply.

  2. Navigate to Fields tab. Add the following fields:

    1. Practical Guidance

    1. Type: Text

    2. Display Control: Text Area

  3. Navigate to Layout -> Designer Tab -> Add New Layout Object

  4. Add Section named “Practical Guidance” under “Practical Guidance” tab.

  5. Add above created field to “Practical Guidance” section as shown in the screenshot below.

Background pattern Description automatically generated

  1. Click Apply.

  2. Navigate to the Fields tab. Add the following fields:

  1. Consequence

  1. Type: Text

  2. Display Control: Text Area

  1. Navigate to Layout -> Designer Tab -> Add New Layout Object. Add Section named “Consequence” under “Consequence” tab.

  2. Add the above created field to “Consequence” section as shown in the screenshot below.

Graphical user interface Description automatically generated with low confidence

  1. Click Apply.

    1. Remedial Action

      1. Type: Text

      2. Display Control: Text Area

    2. Description – Directional

      1. Type: Text

      2. Display Control: Text Area

    3. Description – Questional

      1. Type: Text

      2. Display Control: Text Area

  2. Navigate to the Fields tab. Add the following fields:

  3. Navigate to Layout -> Designer Tab -> Add New Layout Object. Add Section named “Remedial Action” under “Remedial Action” tab.

  4. Add the above created fields to “Remedial Action” section as shown in the screenshot below.

Graphical user interface, application Description automatically generated

  1. Click Apply.

    1. Compliance Source

      1. Type: Text

    2. Module

      1. Type: Value List (Field Specific)

      2. Display Options: Dropdown

    3. Topic

      1. Type: Text

    4. Sequence

      1. Type: Text

    5. Last Content Update Date

      1. Type: Date

  2. Navigate to the Fields tab. Add the following fields:

  3. Navigate to Layout -> Designer Tab -> Add New Layout Object. Add Section named “Content Source” under “Content Source” tab.

  4. Add the above created fields to “Content Source” section as shown in the screenshot below.

Graphical user interface, application Description automatically generated

  1. Click Apply.

Task 2: Add DDEs to account for new layout changes

Rule 1: Hide LexisNexis Content Tabs

  1. Navigate to the Layout -> Rules tab for the following steps.

  2. Create New Rule from scratch:

    1. Name:  Content Source Does Not Contain LexisNexis

    2. Criteria:

      1. Content Source Does Not Contain LexisNexis

  3. Click Add New in the Linked Actions section.

  4. Select Apply Conditional Layout and click OK.

    1. Name:  Hide LexisNexis Content tabs.

    2. Hide all sections in LexisNexis Content tab set. Below is the list of sections under LexisNexis Content tab set:

      1. General Information Tab -> LexisNexis Content Section and Historical Note Section: Do Not Display

      2. Practical Guidance Tab > Practical Guidance Section: Do Not Display

      3. Consequence Tab > Consequence Section: Do Not Display

      4. Remedial Action Tab > Remedial Action Section: Do Not Display

      5. Content Source Tab > Content Source Section: Do Not Display

    3. Set Qualified Users/Groups to Everyone.

    4. Save Action.

  5. Save rule.

Rule 2: Do not display Sub-Obligations

  1. Navigate to the Layout > Rules tab for the following steps.

  2. Create new rule from scratch:

    1. Name: Obligation Type Equals subobligation

    2. Criteria:

      1. Obligation Type Equals subobligation

  3. Click Add New in the Linked Actions section.

  4. Select Apply Conditional Layout and click OK.

    1. Name – Do Not Display Sub Obligations

    2. Set the following sections/fields to “Do Not Display”.

      1. LexisNexis Content Tab Set -> General Information Tab -> LexisNexis Content Section: Sub-Obligations and Number Of Sub-Obligations Field Do Not Display

    3. Set Qualified Users/Groups to Everyone.

    4. Save Action.

  5. Save Rule

Rule 3: Do not display Parent Obligations

  1. Navigate to the Layout > Rules tab for the following steps.

  2. Create new rule from scratch:

    1. Name: Obligation Type Equals to Obligation

    2. Criteria:

      1. Obligation Type Equals to Obligation

  3. Click Add New in the Linked Actions section.

  4. Select Apply Conditional Layout and click OK.

    1. Name: Do Not Display Parent Obligation Field

    2. Set the following fields/sections to “Do Not Display”

      1. LexisNexis Content Tab Set > General Information Tab > LexisNexis Content Section: Parent Obligations field Do Not Display

    3. Set Qualified Users/Groups to Everyone.

    4. Save Action

  5. Save Rule.

Configure regulatory intelligence items application

Task 1: Add fields to the regulatory intelligence items application

  1. Navigate to Applications by clicking the Administration dropdown menu and select Applications under Application Builder.

  2. Select the Regulatory Intelligence Items application and navigate to the Fields tab.

  3. Edit the Source Values List field and Add a new value “LexisNexis”.

    1. Compliance Source

      1. Type: Text

    2. Impact

      1. Type: Text

      2. Display Control: Text Area

    3. Impacted Obligation

      1. Type: Cross - Reference

      2. Available Reference: Control Standards

      3. Display Control: Grid

      4. Record Lookup Configuration/Grid Display Properties Display Fields: Standard Name, Statement, Jurisdiction

    4. Impacted Sub-Obligations

      1. Type: Cross- Reference

      2. Available Reference: Control Standards

      3. Display Control: Grid

      4. Record Lookup Configuration/Grid Display Properties Display Fields: Standard Name, Statement, Jurisdiction

    5. Type

      1. Type: Value List (Field Specific)

      2. Display Options – Dropdown

    6. Effective Date

      1. Type: Text

        Note: Effective Date is coming as text from LexisNexis Source so make the field Text and Not Date.

    7. LN ID

      1. Type – Text

    8. LN Date Created

      1. Type – Date

    9. Archived

      1. Type: Value List (Field Specific)

      2. Display Options – Dropdown

    10. LN Date Changed

      1. Type: Date

  4. In the Fields tab. Add the following fields:

  5. Navigate to Layout > Designer Tab > Add New Layout Object. Add New Sections named “LexisNexis Information” and “LexisNexis Reference Information”

  6. Add the above created fields to these sections as shown in the screenshot below.

Graphical user interface, text, application, email Description automatically generated

  1. Click Save.

Task 2: Add DDEs to account for new layout changes

  1. Navigate to the Layout > Rules tab for the following steps.

  2. Create new rule from scratch:

    1. Name:  Source Does Not Contain LexisNexis

    2. Criteria:

      1. Source Does Not Contain LexisNexis

  3. Click Add New in the Linked Actions section.

  4. Select Apply Conditional Layout and click OK.

    1. Name: Hide LexisNexis Information and LexisNexis reference Information Section.

    2. Set the LexisNexis Information and LexisNexis Reference Information sections to “Do Not Display”.

    3. Set Qualified Users/Groups to Everyone.

    4. Save Action

  5. Save Rule.

Configuring authoritative sources application

Task 1:  Add fields to the authoritative sources application

  1. Click and navigate to Applications. Under the Application Builder dropdown, select Applications.

  2. Select the Authoritative Sources application and navigate to the Fields tab.

  1. Edit the Content Source Values List field and Add a new value “LexisNexis”.

    1. Country

      1. Type: Value List (Field Specific)

      2. Display Options: Values Popup

      3. Configuration: Maximum Selection=No Maximum

    2. Date Archived

      1. Type: Date

      2. Display Options: Date/Time

    3. Date Changed

      1. Type: Date

      2. Display Options: Date/Time

    4. LN Date Created

      1. Type: Date

      2. Display Options: Date/Time

    5. Is Archived?

      1. Type: Values List (Field Specific)

      2. Display Option: Drop Down

    6. Is Government?

      1. Type: Values List (Field Specific)

      2. Display Option: Drop Down

    7. Level

      1. Type: Values List (Field Specific)

      2. Display Options: Values Popup

      3. Configuration: Maximum Selection=No Maximum

    8. Source ID

      1. Type: Text

    9. State

      1. Type: Values List (Field Specific)

      2. Display Options: Values Popup

      3. Configuration: Maximum Selection=No Maximum

    10. URL

      1. Type: External Link

    11. Rename the field Regulator (Authoritative Sources) to “Regulators”

      1. Type: Related Records

      2. Display Control: Single Column

    12. Create New / Rename existing Control Standards field to “Obligations”

      1. Type: Cross-Reference/ Related Records

      2. Available Reference: Control Standards

      3. Display Control: Grid

      4. Record Lookup Configuration/Grid Display Properties Display Fields: Standard ID, Standard Name, Statement.

    13. Sub-Obligations

      1. Type: Cross-Reference/ Related Records

      2. Available Reference: Control Standards

      3. Display Control: Grid

      4. Record Lookup Configuration/Grid Display Properties Display Fields: Standard ID, Standard Name, Statement.

    14. Alerts

      1. Type: Cross-Reference/ Related Records

      2. Available Reference: Regulatory Intelligence Items

      3. Display Control: Grid

      4. Record Lookup Configuration/Grid Display Properties Display Fields: Tracking ID, Title, Abstract

  2. In the Fields tab. Add the following fields:

  3. Navigate to Layout > Designer tab > Add New Layout Object

  4. Add Section named “LexisNexis Content” under “Authoritative Source” section.

  5. Place all the above created fields as shown in the screenshot below.

Graphical user interface, text, application Description automatically generated

  1. Click Apply.

Level: Topic

    1. Date Archived

      1. Type: Date

      2. Display Options: Date/Time

    2. Date Changed

      1. Type: Date

      2. Display Options: Date/Time

    3. Date Created

      1. Type: Date

      2. Display Options: Date/Time

    4. Create New / Rename existing Control Standards field to “Obligations”

      1. Type: Cross-Reference/Related Records

      2. Available Reference: Control Standards

      3. Display Control: Grid

      4. Record Lookup Configuration/Grid Display Properties Display Fields: Standard ID, Standard Name, Statement.

    5. Sub-Obligations

      1. Type: Cross-Reference/ Related Records

      2. Available Reference: Control Standards

      3. Display Control: Grid

      4. Record Lookup Configuration/Grid Display Properties Display Fields: Standard ID, Standard Name, Statement.

    6. Alerts

      1. Type: Cross-Reference/ Related Records

      2. Available Reference: Regulatory Intelligence Items

      3. Display Control: Grid

      4. Record Lookup Configuration/Grid Display Properties Display Fields: Tracking ID, Title, Abstract

  2. In the Fields tab. Add the following fields and click Apply:

    • Add Section named “LexisNexis Content” under “Topic” section.

    • Place all the above created fields as shown in the screenshot below

  3. In Level: Section, repeat step 9.

  4. In Level: Sub-Sectin, repeat step 9.

Task 2: Add DDEs to account for new layout changes

Rule 1: Hide LexisNexis content tabs

  1. Repeat below steps 2 to 6 at all levels (Source, Topic, Section and Sub Section) in Authoritative Sources application.

  2. Navigate to the Layout -> Rules tab for the following steps.

  3. Create New Rule from scratch:

    1. Name:  Content Source Does Not Contain LexisNexis

    2. Criteria:

      1. Content Source Does Not Contain LexisNexis

  4. Click Add New in the Linked Actions section.

  5. Select Apply Conditional Layout and click OK.

    1. Name:  Hide LexisNexis Content tabs.

    2. Hide all sections related to LexisNexis Content. Below is the list of sections:

      1. LexisNexis Content section: Do Not Display

      2. Alerts section: Do Not Display

      3. Control Mappings tab -> Obligations and Sub-Obligations sections: Do Not Display

    3. Set Qualified Users/Groups to Everyone.

    4. Save Action.

  6. Save rule.

Configure the data feed

Configure the JavaScript transporter settings

Note: The below steps can be skipped in SaaS instance as it will be completed by Archer SaaS Team. To proceed, navigate to Set up the Data Feeds section.

Before you upload a JavaScript file, you must configure JavaScript Transporter settings in the Archer Control Panel.

  1. On the General tab, go to the JavaScript Transporter section.

    1. Open the Archer Control Panel.

    2. Go to Instance Management and select All Instances.

    3. Select the instance you want to use.

    4. On the General tab, go to the JavaScript Transporter section.

  2. In the Max Memory Limit field, set the value to 2048 MB (2 GB).

  3. In the Script Timeout field, set the value to 120 minutes (2 hours).

  4. (Optional) If you want to allow only digitally signed JavaScript files in the data feed, enable Require Signature.

    1. In the JavaScript Transporter Settings section, select the checkbox Require Signature. A new empty cell appears in the Signing Certificate Thumbprints section

    2. In the Signing Certificate Thumbprints section, double-click an empty cell.

    3. Enter the digital thumbprint of the trusted certificate used to sign the JavaScript file.

      Note: For information on how to obtain digital thumbprints, see Obtaining Digital Thumbprints.

      Important: If you enable Require Signature and specify no thumbprints, no JavaScript files will be accepted by the system.

    4. (Optional) If you want to add additional thumbprint sources, repeat steps b-c for each thumbprint.

  5. On the toolbar, click Save.

Obtaining Digital Thumbprints

When running JavaScript data feeds, you can set the Archer instance to only allow digitally signed JavaScript files from trusted sources for security considerations.

For a certificate to be trusted, all the certificates in the chain, including the Root CA Certificate and Intermediate CA certificates, must be trusted on both the Web Server and Services Server machines.

Archer Technologies LLC cert in the Trusted Root CA Store

Archer Technologies LLC certificate is not present on every machine’s root by default.

  1. On the JavaScript file, right-click and select Properties.

    1. Click the Digital Signatures tab.

    2. From the Signature List window, select Archer Technologies LLC.

    3. Click the Details button.

    4. Click View Certificate.

    5. Click Install Certificate.

    6. Select Local Machine.

    7. Click Next.

    8. Select Place all certificates in the following store and click Browse.

      1. Select Trusted Root Certification Authorities and click OK.

      2. Click Next.

      3. Click Finish.

  2. Upon successful import, click OK.

Obtaining a Certificate Thumbprint

  1. In the Archer Control Panel environment, open the Manage Computer Certificates program.

    1. Click Start.

    2. Type:  certificate

    3. From the search results, click Manage Computer Certificates.

  2. Ensure that your trusted source certificates are in the Certificates sub-folder of the Trust Root Certification Authorities folder.

  3. In the Certificates sub-folder, double-click the Archer Technologies LLC that contains the thumbprint you want to obtain.

  4. Verify that the certificate is trusted.

    1. In the Certificate window, click the Certification Path tab.

    2. Ensure that the Certificate Status windows displays the following message:

      This certificate is OK

      Note: If the Certificate Status windows displays something different, follow the on-screen instructions.

  5. Obtain the trusted certificate thumbprint.

    1. In the Certificate window, click the Details tab.

    2. Select the Thumbprint field.

      The certificate's digital thumbprint appears in the window.

    3. Copy the thumbprint.

Set up the LexisNexis regulatory compliance data feeds

Important: Before you upload a JavaScript file, configure JavaScript Transporter settings in the Archer Control Panel. For more information, see Configure the JavaScript Transporter Settings.

The following data feeds are used as part of the LexisNexis Regulatory Compliance Integration process:

LexisNexis Regulatory Compliance data feeds are JavaScript transporter data feeds that retrieves data (Obligations, Sub-Obligations, Alerts and Tools related data) from the LexisNexis Regulatory Compliance API URL and creates and updates the records in the Archer Control Standard, Regulatory Intelligence Items and Tools application.

LexisNexis Regulatory Compliance Enhanced Content data feeds are JavaScript transporter data feeds that retrieves data (Mandates and Regulators related data) from the LexisNexis Regulatory Compliance Enhanced Content API URL and creates and updates the records in the Archer Authoritative Sources and Regulators application.

All data feeds must be configured. After setting up the data feeds, you can schedule them to run as needed per your organization’s requirements. Due to the nature of the LexisNexis API not supporting concurrent calls, it is recommended to run the data feeds in a convoy. For more information on Scheduling data feeds, see the Scheduling Data Feeds section.

There are nine data feeds created for this integration and needs to be run in the following order:

  • 01 LexisNexis - Obligations/Sub-Obligations

  • 02 LexisNexis – Alerts

  • 03 LexisNexis – Tools

  • 04 LexisNexis – Mandates (Full Load)

  • 05 LexisNexis - Mandates Sub Section Refresh (Differential)

  • 06 LexisNexis - Mandates Section Refresh (Differential)

  • 07 LexisNexis - Mandates Topic Refresh (Differential)

  • 08 LexisNexis - Mandates Source Refresh (Differential)

  • 09 LexisNexis – Regulators

Note: 04 LexisNexis – Mandates (Full Load) data feed only needs to be run once in the beginning and then deactivated. Due to the large volume of Mandates source content and the frequency of the data feed is scheduled to run Hourly. it is recommended to run the data feed during the weekend.

Below are the steps to set up the feeds:

LexisNexis - Obligations/Sub-Obligations

  1. Go to the Manage Data Feeds page.

    1. From the menu bar, click  .

    2. Under Integration, click Data Feeds.

  2. In the Manage Data Feeds section, click Import.

  3. Locate and select the: 01_LexisNexis_-_Obligations_Sub-Obligations.dfx5 file.

  4. Click Open.

  5. In the General Information tab.

    1. In the General Information section, in the Status field, select Active.

    2. In the Feed Information section, verify the Target is Control Standards application.

Note: Data Feed Locale value is set to English (Australia) in the Source Connection section. It is recommended not to change the value.

  1. Click the Source Connection tab.

  2. In the Transport Configuration section, do the following:

    1. Click Upload

    2. From the Upload JavaScript File dialog, click Add New.

    3. Locate and select the signed-LexisNexisAPI_v2.0.11 file.

    4. Click Open.

    5. From the Upload JavaScript File dialog, click OK.

  3. In the Custom Parameters section, enter key values. The following table describes the value for each key in Custom Parameters.

Key

Value

url

LexisNexis URL

(Required)

Ex: https://compliance.store.lexisnexis.com.au

Username

[Valid value]

Default = [empty]

(Required)

Password

[Valid value]

Default = [empty]

(Required)

Jurisdictions

[Valid value]

Default = [empty]

(Optional)

Ex: jurisdictions=NSW|VIC

where multiple jurisdictions are specified use “|” between each value

ignoreLastRunTime

[Valid value of true/false]

Default = true

(Optional)

Set the value to false if you wish to obtain the response from a specific date. The specific date being the LastRunTime of the data feed.

  1. The below additional parameter provides valid options for the Custom Parameters section for the current JavaScript file.

Key

Value

Proxy

[Valid value]

Default = [empty]

(Optional)

For each key type, determine whether you want it to be Protected or Plain Text. Selecting Protected encrypts the key value for the specified key in the log. In the Data Feed Setup window, verify that the key fields are present.

  1. Click Save.

  2. Click the Data Map tab.

  3. In the Field Map sub tab, configure all the source fields (new and modified) to the target Control Standards fields.

Source Field

Target Field

compliance_source

Compliance Source

consequence

Consequence

content_source

Content Source

description_directional

Description Directional

description_questional

Description Questional

historical_note

Historical Note

jurisdictions

Jurisdiction

date_changed

Last Content Update Date

module

Module

type

Obligation Type

practical_guidance

Practical Guidance

remedial_action

Remedial Action

sequence_id

Sequence

id

Standard ID

title

Standard Name

description_directional

Statement

topic

Topic

subObligations

Sub-Obligations (Self Cross reference to Control Standard Application. Need to map all the above field)

13. The field mapping settings should be as follows.

14. In the Key Field Definitions Sub tab, add the “Standard ID” as key field for Control Standards and Sub-Obligations.

LexisNexis - Alerts

  1. Go to the Manage Data Feeds page.

    1. From the menu bar, click  .

    2. Under Integration, click Data Feeds.

  2. In the Manage Data Feeds section, click Import.

  3. Locate and select the 02_LexisNexis_-_Alerts.dfx5 file.

  4. Click Open.

  5. In the General Information tab.

    1. In the General Information section, in the Status field, select Active.

    2. In the Feed Information section, verify the Target is Regulatory Intelligence Items application.

Note: Data Feed Locale value is set to English (Australia) in the Source Connection section. It is recommended not to change the value.

  1. Click the Source Connection tab.

  2. In the Transport Configuration section, do the following:

    1. Click Upload

    2. From the Upload JavaScript File dialog, click Add New.

    3. Locate and select the signed-LexisNexisAPI_v2.0.11 file.

    4. Click Open.

    5. From the Upload JavaScript File dialog, click OK.

  3. In the Custom Parameters section, enter key values.  The following table describes the value for each key in Custom Parameters.

Key

Value

url

LexisNexis URL

(Required)

Ex: https://compliance.store.lexisnexis.com.au

Username

[Valid value]

Default = [empty]

(Required)

Password

[Valid value]

Default = [empty]

(Required)

Jurisdictions

[Valid value]

Default = [empty]

(Optional)

Ex: jurisdictions=NSW|VIC

where multiple jurisdictions are specified use “|” between each value

ignoreLastRunTime

[Valid value of true/false]

Default = true

(Optional)

Set the value to false if you wish to obtain the response from a specific date. The specific date being the LastRunTime of the data feed.

  1. The below additional parameter provides valid options for the Custom Parameters section for the current JavaScript file.

Key

Value

Proxy

[Valid value]

Default = [empty]

(Optional)

For each key type, determine whether you want it to be Protected or Plain Text. Selecting Protected encrypts the key value for the specified key in the log. In the Data Feed Setup window, verify that the key fields are present.

  1. Click Save.

  2. Click the Data Map tab.

  3. In the Field Map sub tab, configure all the source fields (new and modified) to the target Regulatory Intelligence Items fields.

Source Field

Target Field

description

Abstract

archived

Archived

author

Author Name

compliance_source

Compliance Source

effectiveDate

Effective Date

impact_on_obligation

Impact

obligation_id

Standard ID (Under Impacted Obligations Cross Reference)

sub_obligation_id

Standard ID (Under Impacted Sub Obligation Cross Reference)

date_changed

LN Date Changed

date_created

LN Date Created

id

LN ID

content-source

Source

title

Title

topic

Topics

type

Type

The screen shows below provide examples of these field mappings.

  1. In the Key Field Definitions Sub tab, add the “LN ID” as key field for Regulatory Intelligence Items, “Standard ID” for Impacted Obligations and “Standard ID” for Impacted Sub Obligations.

  1. Schedule tab: This data feed is a Reference feed configured to run after 01 LexisNexis – Obligations/Sub-Obligations data feed.

LexisNexis - Tools

  1. Go to the Manage Data Feeds page.

    1. From the menu bar, click  .

    2. Under Integration, click Data Feeds.

  2. In the Manage Data Feeds section, click Import.

  3. Locate and select the 03_LexisNexis_-_Tools.dfx5 file.

  4. Click Open.

  5. In the General Information tab.

    1. In the General Information section, in the Status field, select Active.

    2. In the Feed Information section, verify the Target is Tools application.

Note: Data Feed Locale value is set to English (Australia) in the Source Connection section. It is recommended not to change the value.

  1. Click the Source Connection tab.

  2. In the Transport Configuration section, do the following:

    1. Click Upload

    2. From the Upload JavaScript File dialog, click Add New.

    3. Locate and select the signed-LexisNexisAPI_v2.0.11 file.

    4. Click Open.

    5. From the Upload JavaScript File dialog, click OK.

  3. In the Custom Parameters section, enter key values. The following table describes the value for each key in Custom Parameters.

Key

Value

url

LexisNexis URL

(Required)

Ex: https://compliance.store.lexisnexis.com.au

username

[Valid value]

Default = [empty]

(Required)

password

[Valid value]

Default = [empty]

(Required)

Jurisdictions

[Valid value]

Default = [empty]

(Optional)

Ex: jurisdictions=NSW|VIC

where multiple jurisdictions are specified use “|” between each value

ignoreLastRunTime

[Valid value of true/false]

Default = true

(Optional)

Set the value to false, if you wish to obtain the response from a specific date. The specific date being the LastRunTime of the data feed.

  1. The below additional parameter provides valid options for the Custom Parameters section for the current JavaScript file.

Key

Value

proxy

[Valid value]

Default = [empty]

(Optional)

For each key type, determine whether you want it to be Protected or Plain Text. Selecting Protected encrypts the key value for the specified key in the log. In the Data Feed Setup window, verify that the key fields are present.

  1. Click Save.

  2. Click the Data Map tab.

  3. In the Field Map sub tab, configure all the source fields (new and modified) to the target Tools fields.

Source Field

Target Field

category

Category

date_changed

Date Changed

date_created

Date Created

ext_link

External Reference Link

link

Lexis Nexis Link

obligation_id

Standard ID under Obligations cross reference

sub_obligation_id

Standard ID under Sub-Obligations cross reference

title

Title

tool_function

Tool Function

id

Tool ID

The screen shows below provide examples of these field mappings.

13. In the Key Field Definitions Sub tab, add the “Tool ID” as key field for Tools, “Standard ID” for Obligations and “Standard ID” for Sub Obligations

14. Schedule tab: This data feed is a Reference feed configured to run after 02 LexisNexis – Alerts data feed.

LexisNexis - Mandates (Full Load)

  1. Go to the Manage Data Feeds page.

    1. From the menu bar, click  .

    2. Under Integration, click Data Feeds.

  2. In the Manage Data Feeds section, click Import.

  3. Locate and select the: 04_LexisNexis _-_ Mandates (Full Load). dfx5 file.

  4. Click Open.

  5. In the General Information tab.

    1. In the General Information section, in the Status field, select Active.

    2. In the Feed Information section, verify the Target is Authoritative Sources > Source application.

  6. Click the Source Configuration tab.

  7. In the Transport Configuration section, do the following:

    1. Click Upload.

    2. From the Upload JavaScript File dialog, click Add New.

    3. Locate and select the signed-LexisNexisAPI_v2.0.11 file.

    4. Click Open.

    5. From the Upload JavaScript File dialog, click OK.

  8. In the Custom Parameters section, enter key values. The following table describes the value for each key in Custom Parameters.

Key

Value

url

LexisNexis URL

(Required)

Ex: https://compliance.store.lexisnexis.com.au

Username

[Valid value]

Default = [empty]

(Required)

Password

[Valid value]

Default = [empty]

(Required)

ignoreLastRunTime

[Valid value of true/false]

Default = true

(Required)

dataSource

[Valid value]

Default = mandates

(Required)

Note: Do not modify the value. It is being used in the script to identify the Enhanced content.

  1. The following additional parameter provides valid options for the Custom Parameters section for the current JavaScript file.

Key

Value

proxy

[Valid value]

Default = [empty]

(Optional)

pageSize

[Valid value]

Default = 1000

(Optional)

Description: Used to return the count of data from the API. Default value is 100. Maximum value is 2000.

country

[Valid value]

Default = [empty]

(Optional)

Description: mandate country of origin

Ex: Australia, International

level

[Valid value]

Default = [empty]

(Optional)

Ex: Federal, Local, State, Territory or Blank

Module

[Valid value]

Default = [empty]

(Optional)

For each key type, determine whether you want it to be Protected or Plain Text. Selecting Protected encrypts the key value for the specified key in the log. In the Data Feed Setup window, verify that the key fields are present.

  1. Click Save.

  2. Verify the settings on the Source Definition tab. This will be pre-configured to identify the necessary fields.

    Note: Repopulating the fields by clicking on “Load Fields” will lead to removal of some of the renamed source fields. Ex: The Source fields Level 1, Level 2, Level 3, and Level 4 Field on the Source Definition tab are renamed with Source, Topic, Section and Subsection

  3. Click the Data Map tab.

  4. In the Field Map sub tab, configure all the source fields (new and modified) to the target Authoritative Sources fields.

    Level 1: Source

Source Field (Level 1)

Target Field (Source)

content-source

Content Source

country

Country

dateArchived

Date Archived

dateChanged

DateChanged

dateCreated

LN Date Created

isArchived

Is Archived?

isGovernment

Is Government?

level

Level

id

Source ID

title

Source Name

state

State

url

URL

relationships->obligations->data->id

Obligations->Standard ID

relationships->subobligations->data->id

Sub-Obligations->Standard ID

relationships->alerts->data->id

Alerts->LN ID

The screen shows below provide examples of these field mappings.

Level 2: Topic

Source Field (Level 2)

Target Field (Topic References)

content-source

Content Source

dateArchived

Date Archived

dateChanged

DateChanged

dateCreated

LN Date Created

id

Topic ID

title

Topic Name

relationships->obligations->data->id

Obligations->Standard ID

relationships->subobligations->data->id

Sub-Obligations->Standard ID

relationships->alerts->data->id

Alerts->LN ID

The screen shows below provide examples of these field mappings.

Level 3: Section

Source Field (Level 3)

Target Field (Section References)

content-source

Content Source

dateArchived

Date Archived

dateChanged

DateChanged

dateCreated

LN Date Created

id

Section ID

title

Section Name

relationships->obligations->data->id

Obligations->Standard ID

relationships->subobligations->data->id

Sub-Obligations->Standard ID

relationships->alerts->data->id

Alerts->LN ID

The screen shows below provide examples of these field mappings.

Level 4: Sub Section

Source Field (Level 4)

Target Field (Sub Section References)

content-source

Content Source

dateArchived

Date Archived

dateChanged

DateChanged

dateCreated

LN Date Created

id

Sub Section ID

title

Sub Section Name

relationships->obligations->data->id

Obligations->Standard ID

relationships->subobligations->data->id

Sub-Obligations->Standard ID

relationships->alerts->data->id

Alerts->LN ID

The screen shows below provide examples of these field mappings.

  1. In the Key Field Definitions Sub tab, add the following as key field for Authoritative Sources application.

    1. Source: Source ID

    2. Topic References(s): Topic ID

    3. Section References(s): Section ID

    4. Sub Section References(s): Sub Section ID

      Reference Fields:

    5. Alerts: LN ID

    6. Obligations: Standard ID

    7. Sub-Obligations: Standard ID

LexisNexis - Mandates (Differential Load)

  1. Go to the Manage Data Feeds page.

    1. From the menu bar, click  .

    2. Under Integration, click Data Feeds.

  2. In the Manage Data Feeds section, click Import.

  3. Locate and select the: 04 LexisNexis - Mandates Sub Section Refresh (Differential). dfx5 file.

  4. Click Open.

  5. In the General Information tab.

    1. In the General Information section, in the Status field, select Active.

    2. In the Feed Information section, verify the Target is Authoritative Sources > Sub Section application.

  6. Click the Source Connection tab.

  7. In the Transport Configuration section, do the following:

    1. Click Upload.

    2. From the Upload JavaScript File dialog, click Add New.

    3. Locate and select the signed-LexisNexisAPI_v2.0.11 file.

    4. Click Open.

    5. From the Upload JavaScript File dialog, click OK.

  8. In the Custom Parameters section, enter key values. The following table describes the value for each key in Custom Parameters. Make sure to set the custom Parameter ignoreLastRunTime = false.

Key

Value

url

LexisNexis URL

(Required)

Ex: https://compliance.store.lexisnexis.com.au

Username

[Valid value]

Default = [empty]

(Required)

Password

[Valid value]

Default = [empty]

(Required)

ignoreLastRunTime

[Valid value of true/false]

Default = false

(Required)

Set the value to false if you wish to obtain the response from a specific date. The specific date being the LastRunTime of the data feed.

dataSource

[Valid value]

Default = mandates

(Required)

Note: Do not modify the value. It is being used in the script to identify the Enhanced content.

9. Repeat Steps 1 to 8. for 05 LexisNexis - Mandates Section Refresh (Differential), 06 LexisNexis - Mandates Topic Refresh (Differential) and 07 LexisNexis - Mandates Source Refresh (Differential) targeting their corresponding levels. These are all a convoy feed staring with 04 LexisNexis - Mandates Sub Section Refresh (Differential).

10. follow the mapping as shown in the table below:

Source Data (Level 4)

Target level (Sub Section)

content-source

Content Source

dateArchived

Date Archived

dateChanged

DateChanged

dateCreated

LN Date Created

id

Sub Section ID

title

Sub Section Name

relationships->obligations->data->id

Obligations->Standard ID

relationships->subobligations->data->id

Sub-Obligations->Standard ID

relationships->alerts->data->id

Alerts->LN ID
Relationships->parentMandate->data->id

Section Reference->Section Id

(Populate target fields with empty source field values =checked

Create new record with unknown source values = checked

Replace existing target field values = selected)

For Section and Topic follow the table above, only the parentMandate should be mapped to the upper level reference.

11. For Source level mapping follow the table below

Source Data(Level 1)

Target Level (Source)

content-source

Content Source

country

Country

dateArchived

Date Archived

dateChanged

DateChanged

dateCreated

LN Date Created

isArchived

Is Archived?

isGovernment

Is Government?

level

Level

id

Source ID

title

Source Name

state

State

url

URL

relationships->obligations->data->id

Obligations->Standard ID

relationships->subobligations->data->id

Sub-Obligations->Standard ID

relationships->alerts->data->id

Alerts->LN ID

12. In the Key Field Definitions Sub tab, add the following as key field for Authoritative Sources application.

  1. Source Level: Source ID

  2. Topic Level: Topic ID

  3. Section Level: Section ID

  4. Sub Section Level: Sub Section ID

  5. Alerts: LN ID

  6. Obligations: Standard ID

  7. Sub-Obligations: Standard ID

LexisNexis - Regulators

  1. Go to the Manage Data Feeds page.

    1. From the menu bar, click  .

    2. Under Integration, click Data Feeds.

  2. In the Manage Data Feeds section, click Import.

  3. Locate and select the 08_LexisNexis _-_Regulators.dfx5 file.

  4. Click Open.

  5. In the General Information tab.

    1. In the General Information section, in the Status field, select Active.

    2. In the Feed Information section, verify the Target is Regulators application.

  6. Click the Transport tab.

  7. In the Transport Configuration section, do the following:

    1. Click Upload

    2. From the Upload JavaScript File dialog, click Add New.

    3. Locate and select the signed-LexisNexisAPI_v2.0.11 file.

    4. Click Open.

    5. From the Upload JavaScript File dialog, click OK.

  8. In the Custom Parameters section, enter key values. The following table describes the value for each key in Custom Parameters.

Key

Value

url

LexisNexis URL

(Required)

Ex: https://compliance.store.lexisnexis.com.au

Username

[Valid value]

Default = [empty]

(Required)

Password

[Valid value]

Default = [empty]

(Required)

ignoreLastRunTime

[Valid value of true/false]

Default = true

(Optional)

Set the value to false if you wish to obtain the response from a specific date. The specific date being the LastRunTime of the data feed.

dataSource

[Valid value]

Default = regulators

(Required)

Note: Do not modify the value. It is being used in the script to identify the Enhanced content.

  1. The below additional parameter provides valid options for the Custom Parameters section for the current JavaScript file.

Key

Value

proxy

[Valid value]

Default = [empty]

(Optional)

verifyCerts

[Valid value of true/false]

Default = [empty]

(Optional)

country

[Valid value]

Default = [empty]

(Optional)

Description: mandate country of origin

Ex: Australia, International

level

[Valid value]

Default = [empty]

(Optional)

Ex: Federal, Local, State, Territory or Blank

pageSize

[Valid value]

Default = 2000

(Optional)

Description: Used to return the count of data from the API. Default value is 100. Maximum value is 2000.

For each key type, determine whether you want it to be Protected or Plain Text. Selecting Protected encrypts the key value for the specified key in the log. In the Data Feed Setup window, verify that the key fields are present.

  1. Click Save.

  2. Click the Data Map tab.

  3. In the Field Map sub tab, configure all the source fields (new and modified) to the target Tools fields.

Source Field (Level 1)

Target Field (Source)

acronym

Acronym

content-source

Content Source

country

Country

dateArchived

Date Archived

dateChanged

DateChanged

dateCreated

Date Created

isArchived

Is Archived?

isGovernment

Is Government?

level

Level

id

Regulator ID

name

Name

state

State

url

URL

relationships->mandates->ArcherRecord->id

Authoritative Sources->Source ID

The screen shows below provide examples of these field mappings.

  1. In the Key Field Definitions Sub tab, add the “Regulator ID” as key field for Regulators, “Source ID” for Authoritative Sources.

  2. Schedule tab: This data feed is a Reference feed configured to run after 01 LexisNexis – Mandates data feed.

Scheduling data feeds

When you schedule a data feed, the Data Feed Manager validates the information. If any information is invalid, an error message will display. You can save the data feed and correct the errors later, but that data feed is not processed until the errors are rectified.

Important: A data feed must be active and valid to successfully run.

  1. Go to the Schedule tab of the data feed that you want to modify.

    1. From the menu bar, click  .

    2. Under Integration, click Data Feeds.

    3. Select the data feed you want to modify.

    4. Click the Schedule tab.

  2. In the Recurrences section, enter the frequency, start and stop times, and time zone for the data feed.

  3. (Optional) In the Run Data Feed Now section, click Start to override the data feed schedule and run the data feed immediately. 

  4. Click Save.

               The following table describes the fields in the Recurrences section.

Field

Description

Frequency

Specifies the interval in which the data feed runs.

  • By minute: Runs the data feed by the minute interval set. For example, if you specify 45 in every list, the data feed executes every 45 minutes.

  • Hourly: Runs the data feed by the hourly interval set. For example, every hour (1), every other hour (2), and so forth.

  • Daily: Runs the data feed by the daily internal set. For example, every day (1), every other day (2), and so forth.

  • Weekly: Runs the data feed based on a specified day of the week. For example, every Monday of the first week (1), every other Monday (2), and so forth.

  • Monthly: Runs the data feed based on a specified week of the month. For example, 1st, 2nd, 3rd, 4th, or Last.

  • Reference: Runs a specified data feed as runs before the current one. This option indicates to the Data Feed Service that this data feed starts as soon as the referenced data feed completes successfully. From the Reference Feed list, select after which existing data feed the current data feed starts. A reference data feed will not run when immediately running a data feed. The Data Feed Now option only runs the current data feed.

Every

Specifies the interval of the frequency in which the data feed runs.

Start Time

Specifies the time the data feed begins running.

Start Date

Specifies the date on which the data feed schedule begins.

Time Zone

Specifies the time zone in of the server that runs the data feed.

  1. Test the data feed to ensure that all obligation, alerts, and tools details from LexisNexis were imported into the Control Standard, Regulatory Intelligence Items and tools application. If testing fails, try verifying the data feed and re-run. If you experience multiple failures, please contact your Partner.

Troubleshooting

Concurrent API Calls

The LexisNexis authentication API does not support concurrent calls. Please ensure when the data feed is configured and executing, no other instances (example: data feeds) is calling the LexisNexis API with the same credentials at the same time.

Lexis Nexis 404 API Response Code

It has been observed that (most often) during public holidays and weekends, Lexis Nexis does not update mandates. As a result, the API returns a 404 error response code. Due to this, the Archer data feeds fail as a 404 error response code indicates the requested resource is not found. The normal behavior for this case would be for the Lexis Nexis API to return a 200 error response code and the response data could be an empty JSON object/array. However, this specific Lexis Nexis system behavior executes out of the normal behavior pattern.

Please note that the data feed should execute successfully in the next scheduled run if the returned API response code is the 200-error response code.

Upgrade

JavaScript code has been updated to support process large volume of Mandates source content in the Integration. A new data feed is created only for the one-time full load of Mandates data.

If users are using existing LexisNexis Integration and wish to upgrade the Integration by utilizing the latest package, following steps is recommended:

  • Utilize the latest JS file included in the package for the data feeds.

  • Import the newly created Mandates (Full Load) data feed.

  • After completion of all the pages of the Mandates content. Inactivate the Data Feed.

    • Data Feed Tokens: PreviousRunContext token is used to identify the end of the content pages. After data feed completes, PreviousRunContext is set 0 indicates that there are no further content or pages to be import.

Key

Value

PreviousRunContext

[Valid value]

Default = [empty]

The value for the PreviousRunContext is set by the data feed.

Ex:

“” = Beginning of the page.

“1000” = Page index.

“0” = End of Page.

  • Activate and use the existing Mandates (Differential feeds) for daily updates.

Mandates level mapping

If users need more than 4 levels (Based on LexisNexis Content Subscription) mapping, then users need to reconfigure Authoritative Sources, following steps is for 7 level mapping:

  • Data Feed with 7 Levels mapping configuration.

  • Standard 4 Level mapping to Authoritative Sources (Source, Topic, Section, Sub-Section) app. Remaining 3 levels will be present in the Source definition tab. But it will not be mapped.

  • Users must level out Authoritative Sources till level 7. Map the remaining levels (5 to 7) in data feed and run it.

  • If in case users content subscription have more than 7 levels, they must level out authoritative sources app accordingly.

  • Users must reload the source fields in the Source definition tab of data feed to display the max number of levels from their subscription. (Requires source xml obtained from Transport Only method to load the fields).

  • Re-map the Source and the Target fields to run the data feed.

  • For Differential feeds Additional feeds needs to be created targeting each new level. The lowest level should be the first feed in the convoy of feeds.

  • To fetch data for each level the user needs to change the xslt for the new levels create and level number should be changed in line 33 and line 44. refer the image below (Requires source xml obtained from Transport Only method to load the fields).

Certification environment

Date Tested: January 2025

Product Name

Release Information

Operating System

Archer Suite

6.12

Virtual Appliance

LexisNexis

API v1.1, API v2.0

NA