EDCI

1. Ensure that your Archer system meets the following requirements:

   • Archer 2024.06 and later

2. Download the installation package from the Archer Community.

   • Archer 2024.09 EDCI Integration Install Package.zip.

   Note: The data feeds are included in the package file. The signed JavaScript file is a separate file.

3. Read and understand "Packaging Data" in the Archer Platform Help.

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

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. From the menu, click > Integration > Data Feeds.

2. If you did not install the data feeds through the package, import the file.

   1. On the data feed listing page, click .
   2. Locate and select the .dfx5 file for the data feed.
3. Select the data feed you want to configure.

4. On the General tab, in the General Information section, select Active.

5. On the Source Connection tab, follow the set of steps below based on the transport type.

Note: Before you upload a JavaScript file, you must configure the JavaScript Transporter settings in the Archer Control Panel. For more information, see "JavaScript Transporter Settings" in the Archer Control Panel Help.

1. In the Transport Configuration section, select the JavaScript file you want to upload.

   Archer provides a JavaScript sample in the Transport Configuration section, describing each part of the script, and how to configure each part for your environment.

   1. From the Transport Configuration section, click

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

   3. Navigate to and select the applicable JavaScript file below and click Open.

      • EDCI_Ingress_1.0.0.js

   4. In the Upload JavaScript File dialog, and click OK.

2. Important: If the JavaScript Transporter has been set up in the Archer Control Panel to only allow digitally signed JavaScript files from trusted sources, you can only select digitally signed JavaScript files from trusted sources. For more details, see "Configuring JavaScript Transporter Settings" in the Archer Control Panel Help.

3. In the Custom Parameters section, enter the following custom parameters you want to reference within the selected JavaScript file.

   The following table lists the data feed custom parameters for the feed.

   Key	Value
   baseUrl	[Insert the base URL of your Archer instance]
   archerUser	[Insert user account name that has read access to all EDCI Annual Report records]
   archerPass	[Insert password for the archerUser account name]
   archerInstance	[Insert the name of your Archer instance]
   edciUrl	[Insert the EDCI API URL]
   ousername	[Insert the OAuth username that you received from ECDI]
   opassword	[Insert the OAuth password that you received from ECDI]
   gpname	[Insert the GP name value that you received from ECDI]
   gpkey	[Insert the GP key value that you received from ECDI]
   ingressEndpoint	This value comes prepopulated in the feed.

4. The following table lists additional valid custom parameters.

   Key	Type	Value
   verifyCerts	N/A	[true] or [false] By default, this value is set to true. If you have configured Archer to use HTTPS, and the SSL certificate is self-signed or is another form of non-perfected SSL certificate from a top tier Certificate Authority, you must set this value to false.

5. Click the Data Map tab, then click the Field Map and Key Field Definitions tabs.

6. The data feed might map to objects and key fields in applications that you do not have licensed. Clicking on the Field Map and Key Field Definitions tabs allows the system to resolve these mappings.

A data feed must be active and valid to successfully run. A successful data feed run processes all input data, completes all expected record updates, and does not report any failures in the Run Details Report.

Validating a data feed

The Data Feed Manager validates the information when a data feed is scheduled. If any information is invalid, the data feed displays an error message. You can save the data feed and correct the errors later, but the data feed does not process until you make corrections.

Running a data feed

You can set up data feeds to run automatically at regular intervals. This reduces the time and effort required to import data from an external file.

You can initiate data feeds at various times and configure them to run in regular increments for an indefinite period of time.

You can run the data feed immediately.

To prevent excess server load, schedule data feeds on a staggered basis. Archer recommends scheduling a maximum of 10 data feeds to run at a time.

Setting up a reference data feed

A reference feed allows you to specify another feed. This indicates to the Data Feed Service that this feed will start running as soon as the referenced feed completes successfully.

1. Go to the Run Configuration tab > Schedule section.

2. Do one of the following to schedule your data feed.

   • Run on Schedule. You can configure your data feed to run on a defined schedule.

   • Run After. The Data Feed Services starts the current data feed after the referenced data feed completes successfully.

   • Run Now.

3. Save the feed.

The data in an EDCI Annual Report record is calculated based on underlying metric results that match both the portfolio company and the fiscal year.

1. In the Portfolio Company application, verify that you have completed records for each portfolio company for which you want to create an EDCI Annual Report record.
2. In any Portfolio Company record, click Initiate EDCI Functionality.
3. From the Actions menu, select Create EDCI Annual Reports.

4. The "Portfolio Management - EDCI Publish DF1 - Create EDCI Annual Report" data feed runs and creates EDCI Annual Reports records for each active portfolio company as follows:

   • If a new portfolio company has an Initial Investment Year set, the feed will create reports for each year from the initial investment year through the current fiscal year.

   • If a new portfolio company does not have an Initial Investment Year set, the feel will create a report only for the current fiscal year.

   • For existing portfolio companies, the feed will create reports for the current fiscal year.

   Note: The fiscal year is calculated based on the Fiscal Year Starting Month field, which can either be set in the Data Gathering Program record (where it is called Program Fiscal Year Starting Month) or in individual Portfolio Company records.

Each EDCI Annual Report record has a "Stage for Publish" field which defaults to "No".

When you're ready to send annual reports to the EDCI portal, set this field to "Yes" and the report will be processed by the "Portfolio Management - EDCI Publish DF2 - Bulk Publish EDCI Annual Report" data feed.

Note: You can inline edit this field or update it in bulk from the Search Results page.

When the feed runs, it automatically includes any other EDCI Annual Reports for the same fiscal year to ensure that all data for a given year is submitted.