LexisNexis Regulatory Compliance

There is no Undo function for a package installation. Packaging is a powerful feature that can make significant changes to an instance. Back 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.

1. From the menu bar, click > Application Builder > 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.

Important: This step is required only if you are upgrading to a later version of Archer Documentation Request Tracking.

1. From the menu bar, click > Application Builder > Install Packages.

2. In the Available Packages section, locate the package you want to map.
3. In the Actions column, click for that package.

   The analyzer 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 instance 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).

   When the analyzer is complete, the Advanced Package Mapping page lists the objects in the package file and corresponding objects in the target instance.

4. On the Advanced Mapping page, click to open each category and review the icons next to each object to determine which objects you must map manually.

   The following table describes the icons.

   Icon	Name	Description
   	Awaiting Mapping Review	Indicates that the system could not automatically match the object or one of its children to a corresponding object in the target instance. Objects marked with this icon must be mapped manually. New objects should not be mapped. Select Do Not Map from the drop-down menu to clear this icon for an individual object, or click Do Not Map to clear the icon for all unmapped objects.
   	Mapping Completed	Indicates that the object and all children are mapped to objects in the target instance, or that they have been marked as Do Not Map. Nothing more needs to be done with these objects in Advanced Package Mapping.

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

5. For objects awaiting mapping review, do one of the following:
   • To map each object individually, use the drop-down menu in the Target column to select the object in the target instance to which you want to map the source object. To leave an object unmapped, select Do Not Map in the Target column.
   • To automatically map all objects in a category that have different system IDs but the same object name as an object in the target instance, click Auto Map. Select whether to ignore case and spaces when matching object names. Click OK.
   • To mark all unmapped objects as Do Not Map, click Do Not Map.

6. (Optional) Click to enable filter fields that you can use to find specific objects in each mapping category. To undo your mapping selections, click Undo, then select whether to undo all mappings in the category or only the mappings on a single page. If you choose to undo all mappings, you will be returned to the categories list.

7. (Optional) To save your mapping selections and return to the categories list without committing changes to the target instance, click .
8. After you review and map all objects, click Execute.
9. Select I understand the implications of performing this operation. Click OK.

   When the mapping is complete, the Import and Install Packages page displays.

   Important: Advanced Package Mapping modifies the system IDs in the target instance. You must update any Data Feeds and Web Service APIs that use these objects with the new system IDs.

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. From the menu bar, click > Application Builder > Install Packages.
2. In the Available Packages section, locate the package file that you want to install, and click the file name or at end of the row to open the Options menu.
   
3. In the Selected Components section, click the Lookup button to open the Package Selector window.
   • 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. Under the Translation Option drop-down menu, select an option for each selected component. To use the same Translation Option for all selected components, select a method from the top-level drop-down list.
   The Translation Option is enabled only when a language is selected.

   The following table describes the options.

   Option	Description
   Full Install	Installs the component and its translations from the selected languages.
   Translations Only	Only installs the translations from the selected languages.

5. Under the Install Method drop-down menu, select an option for each selected component. To use the same Install Method for all selected components, select a method from the top-level drop-down list.

   The following table describes the options.

   Option	Description
   Create New Only	Only creates new fields and other elements in the applications, questionnaires, workspaces, data feeds, and dashboards specified in the package file. This option does not modify any existing elements on your instance of Archer. This is useful when you want to add functionality to an existing application, questionnaire, workspace, dashboard, data feed, or access role, but you do not want to risk making any unwanted changes to the existing elements of workspaces, data feeds, or dashboards. iViews that are not currently on the dashboards that are selected for the package install are created. Note: The Create New Only option does not apply to access roles or languages.
   Create New and Update	Updates all elements in the applications, questionnaires, workspaces, data feeds, and dashboards as specified in the package file. This includes adding new elements and updating existing elements. Existing iViews on the dashboards that are selected for the package install are updated, and iViews that are not currently on the dashboards that are selected for the package install are created. Note: The Create New and Update option does not apply to access roles or languages.

6. Under the Install Option drop-down menu, select an option for each selected component. To use the same Install Option for all selected components, select an option from the top-level drop-down list.

   The following table describes the options.

   Option	Description
   Do not Override Layout	Installs the component, but does not change the existing layout. This is useful if you have a lot of custom fields and formatting in your layout that you do not want to risk losing. You may have to modify the layout after installing the package to use the changes made by the package. Note: The Do not Override Layout option does not apply to access roles or languages.
   Override Layout	Updates the layout as specified in the package file, overwriting the existing layout. Note: The Override Layout option does not apply to access roles or languages.

7. Click Continue to advance to the next object category in the Package Selector, and repeat steps 4 to 6. After reviewing all object categories, click OK.
8. 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 Apply a prefix to all deactivated objects, 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.
9. Click Install.
10. Click OK.

1. From the menu bar, click > Application Builder > Install Packages.

2. In the Package Installation Log section, click the package that you want to view.
3. In the Package Installation Log page, in the Object Details section, click View All Errors.
   

   Note: To view individual logs, in the Errors column of the log you want to view, click the Failures link or Warnings link. Clicking View All Errors, Failures, or Warnings opens the specific errors on a different page.

4. Click the Export icon to export the log file.
5. Click Close.

For a list of packaging installation log messages and remediation information for common messages, see Package Installation Log Messages.

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

Complete tasks 1 - 5 from Instal the Package to import and install the Archer LexisNexis Regulators 2024.11 Install Package.zip.

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.

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 “Lexis Nexis 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.

10. Click Apply.

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

    • Practical Guidance

    • Type: Text

    • Display Control: Text Area

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

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

14. Add above created field to “Practical Guidance” section.

15. Click Apply.

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

• Consequence

• Type: Text

• Display Control: Text Area

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

18. Add the above created field to “Consequence” section.

19. 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

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

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

22. Add the above created fields to “Remedial Action” section.

23. 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

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

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

26. Add the above created fields to “Content Source” section.

27. Click Apply.

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.

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 newly created fields to these sections.

   • General Information section

     • Tracking ID

     • Source

     • Title

     • Abstract

     • Link

     • Date published

     • Status

     • State

     • Topics

     • Compliance Source

   • LexisNexis Information

     • Impact

     • Impacted Obligation

     • Type

     • Effective Date

   • LexcisNexis Reference Information

     • LN ID

     • Archived

     • LN Date Created

     • LN Date Changed

7. Click Save.

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: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.

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.

3. 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

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

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

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

7. Place all the newly created fields as follows and click Apply.

• LexisNexis Content section

  • Level

  • Source ID

  • Country

  • State

  • LN Date Created

  • Date Changed

  • Regulators

  • Date Archived

  • Is Archived?

  • Is Government?

  • URL

• Alerts

  • Alerts

• Authoritative Source Source Level section

  • Control Mappings tab

    • Control Standards section

      • Obligations

      • Sub-Obligations

8. In the Fields tab, add the following fields and click Apply:

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

9. 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 follows.

  • LexisNexis Content

    • Date Created

    • Content Source

    • Date Changed

    • Date Archived

  • Authoritative Source Topic Level section, Control Mappings tab, Control Standards section

    • Obligations

    • Sub-Obligation

10. In Level: Section, repeat step 8.

11. In Level: Sub-Section, repeat step 8.

Rule 1: Hide LexisNexis content tabs

Repeat steps 1 - 5 at all levels (Source, Topic, Section and Sub Section) in Authoritative Sources application.

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 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.

5. Save rule.

Note: This task if for on-premises clients only.
For SaaS clients, this task is completed bythe 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.
   

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 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.
   

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.

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.

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_v3.1.0 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.

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

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.

10. Click Save.

11. Click the Data Map tab.

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

13. Review and update the field mapping settings on the Data Map tab.

14. In the Key Field Definitions Sub tab, add the “Standard ID” as key field for Control Standards and 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 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.

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_v3.1.0 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.

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

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.

10. Click Save.

11. Click the Data Map tab.

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

13. 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.

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

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.

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_v3.1.0 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.

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

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.

10. Click Save.

11. Click the Data Map tab.

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

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.

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_v3.1.0 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.

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

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.

10. Click Save.

11. 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

12. Click the Data Map tab.

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

    Level 1: Source

Level 2: Topic

Level 3: Section

Level 4: Sub Section

14. 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

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_v3.1.0 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.

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:

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

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

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_v3.1.0 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.

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

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.

10. Click Save.

11. Click the Data Map tab.

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

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

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

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).