Archer Discussion Forum

User: Discussion Owner

1. Go to the New Discussion.

   1. From the menu bar, click Discussion Forums

   2. Under Solutions, click Discussion Forums.

   3. Under Applications, click Discussions.

   4. Click New Record.

2. Enter the following in the General Information Section

   1. Discussion subject in [Subject].

   2. Description in [Body]

   3. Select any records related to the discussion in [Related Records]

   4. Select [Expiration Date]

   5. In [Expiration Plan], select Archive/Delete/None depending on what should happen to the discussion and its related responses on expiration.

   6. Select [Discussion Accessibility] as Public to make the record available to public. Default selection is Private.

3. Enter [Discussion Participants] and [Watchers] in the Discussion Stakeholders section

4. Click Save.

User: Discussion Owner/Discussion Participant

1. Open the discussion record. Click on Add New on the top right corner of the Reply section.

2. Enter the following in the General Information Section

   1. Reply subject in [Subject].

   2. Description in [Body]

   3. Select any records related to the reply in [Related Records]

   4. Select users in [Tag Users] to tag them for response.

3. Click Save.

User: Discussion Owner/Discussion Participant

1. Open the response record. Click on Add New on the top right corner of the Reply section.

2. Enter the following in the General Information Section

   1. Reply subject in [Subject].

   2. Description in [Body]

   3. Select any records related to the reply in [Related Records]

   4. Select users in [Tag Users] to tag them for response.

3. Click Save.

User: Discussion Owner

1. Open the discussion record.

2. In Discussion Owner Actions section, select Locked in [Discussion Status]

3. Provide [Discussion Conclusion], if any.

4. Click Save.

5. Overall Status for the discussion and related responses will change to Locked. Record and related responses become read-only to all users except Discussion Owner.

User: Discussion Owner

1. Open the discussion record.

2. In Discussion Owner Actions section, select Closed in [Discussion Status]

3. Provide [Discussion Conclusion], if any.

4. Click Save.

5. Overall Status for the discussion and related responses will change to Closed. Closed Date will be set to current day. Record and related responses become read-only to all users except  Discussion Owner.

User: Discussion Owner

1. Open the discussion record.

2. In Discussion Owner Actions section, select Archived in [Discussion Status]

3. Provide [Reason for Archive], if any.

4. Click Save.

5. Overall Status for the discussion and related responses will change to Archived. Archived Date will be set to current day. Record and related responses are only visible to the Discussion Owner.

User: Discussion Owner

1. Open a discussion record.

2. In Discussion Owner Actions section, select Open in [Discussion Status]

3. Provide [Reason for Reopening].

4. Change [Expiration Date], in General Information Section if required.

5. Click Save.

6. Overall Status for the discussion and related responses will change to Open. Reopened Date will be set to current day. Record and related responses become visible to all stakeholders.

User: Discussion Owner

1. Open a discussion record.

2. In the right corner of the record click on the share button and select Email.

3. Select the email template of your choice.

4. On Demand Email Dialog will popup. Provide the recipient mail address, modify subject and body, add attachments if any and click on send.

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 FAR Regulatory Correspondence is already present in your system, and you are installing this package.

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 Manage Data Feeds page.

   1. From the menu bar, click .

   2. Under Integration, click Data Feeds.

2. In the Manage Data Feeds section, locate and select the data feed.

3. From the General tab in the General Information section, in the Status field, select Active.

4. Click the Transport tab. Complete the fields in the Transport Configuration section as follows: In the URL field, type: YourServerName/VirtualDirectoryName/ws/search.asmx

5. In the User Name and Password fields, type the username and password of a Platform user that has API access and access to all of the records on the Platform instance (from which the data feed is coming).

6. In the Instance field, type the name of the Platform instance from which the data feed is coming (this is the instance name as you enter it on the Login window).

7. Verify that key field values are not missing from the data feed setup window.

8. Click Save.

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

As you schedule your data feed, the Data Feed Manager validates the information. If any information is invalid, an error message is displayed. You can save the data feed and correct the errors later; but the data feed does not process until you make corrections.

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.

   4. Click the Schedule tab.

2. Go to the Recurrences section and complete frequency, start and stop times, and time zone.

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

4. Click Save.

• Discussion Forum Community: Only community name is captured in the Discussion Category field in Discussions Application. This field is placed off-layout in package. Users can move this onto the layout if required.

• Discussion Forum Roles: Not Migrated.

  Note: Once the records are migrated from feature to applications, you must identify Discussion Owner, Participants and Watchers in the Discussions application. This is a one-time task.

• Forum: Data migration will be done for following components:

  1. Forum Name:

     1. Target Application – Discussions

     2. Target Field - Subject

  2. Description

     1. Target Application – Discussions

     2. Target Field - body

  3. Status (Locked/Archived)

     1. Target Application – Discussions

     2. Target Field – Discussion Status

  4. Forum Expiration Plan

     1. Target Application – Discussions

     2. Target Field – Discussion Expiration Plan

  5. Forum Expiration Date

     1. Target Application – Discussions

     2. Target Field – Discussion Expiration Date

  6. Created By

     1. Target Application – Discussions

     2. Target Field – Created By

  7. Created Date

     1. Target Application – Discussions

     2. Target Field – Created Date

• Message: Data migration will be done for following components:

  1. Subject:

     1. Target Application – Responses

     2. Target Field – Subject

  2. Body:

     1. Target Application – Responses

     2. Target Field – Body

  3. Created By

     1. Target Application – Responses

     2. Target Field – Created By

  4. Created Date

     1. Target Application – Responses

     2. Target Field – Created Date

1. Identify if there are any discussion fields in your applications.

2. Create cross-reference fields to those applications in the Discussions application. Name the fields with prefix “Related” for easy identification.

3. Add all the newly created cross-references to the Related Records, Multi Reference Display Control type, field.

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, locate and select the data feed.

3. From the General tab in the General Information section, in the Status field, select Active.

4. Click the Transport tab, provide connections to your archer instance database in Database configuration tab (Connection String, Username, Password).

5. If any new cross-references were created as mentioned in Task 1 above, then perform the following:

1. In Data Map > Field Map tab:

   1. Map discussions->discussion->dis_f_content id in source to Tracking ID of the all the newly created cross-reference fields under Parent Discussion.

   2. For Tracking ID field mapping of each cross-reference, make sure Empty Values is unchecked in the field population popup.

   3. At each newly mapped cross-reference field level, make sure Empty Values, Add Unknown are un-checked, and Field Population is set to Append data to list- based fields.

2. In Data Map > Key Field Definitions Tab, Add key field definitions for the newly created cross-references.

6. Check the key field definitions and field mappings once again. Click Save.

7. Go to the Schedule tab of the data feed, click Start to immediately run your data feed, in the Run Data Feed Now section. Click Save.

8. Inactivate the feed the datafeed is complete.

Note: Once the records are migrated from feature to applications, customers need to identify Discussion Owner, Participants and Watchers for the records in the Discussions application. This is a one-time task.

1. Go to Discussions default search results:

   1. From the menu bar, click Discussion Forums

   2. Under Solutions, click Discussion Forums.

   3. Under Applications, click Discussions.

2. Click on options dropdown to right corner of the search results header.

3. Select Enable Bulk Update button.

4. Select the records and bulk update discussion owner, discussion participants and watchers as required. Click Save Changes button on the right corner of the search results header.