Archer Australian Incident Management

User: General User

1. Create Incidents record.

   1. From the menu bar, click on the dropdown beside Incident Management Accelerator Workspace.

   2. Under Individual Incident Management > Incidents, click on New Record.

2. Fill in the following information in Event Information section:

   1. Enter Incident Name.

   2. Enter the Incident Description.

   3. Enter the details about How did the Incident Happen.

   4. Enter the details about Initial Actions Taken.

   5. Select Incident Cause by clicking   and making your selection.

   6. Select Interaction Point Affected by clicking   and making your selection.

   7. Select the Date Discovered, Date Occurred, and Date Reported by clicking the calendar icon next to the field

   8. Complete the remaining fields in the Event Information section.

3. (Optional) Add attachments/documentation to the record by clicking the | Add New | button in the Supporting Documentation field.

4. Once the record is complete, click Save in the Record Toolbar to save in record.

5. Click Submit Incident at the top left of the screen.

Users: Compliance Manager

1. Select the Incidents record you want to provide response by clicking the Incident Name under the Tasks section on your Task landing screen.

2. Click Edit in the top of the record.

3. Select user from the list in the Incident Owner field by clicking from the Incident Stakeholders section.

4. In the Intake Assessment section:

   1. Select Impact Assessment by clicking the down arrow next to the field and making your selection.

   2. Select Regulator by clicking and making your selection.

   3. If Impact Assessment is Critical OR Remediation Plan is Required for the Incident. Enter details in the Compliance Remediation Recommendations.

   4. Complete the remaining fields in the section.

5. In the Breach Assessment section:

   1. Select PotentialBreach? by clicking the down arrow next to the field and making your selection.

   2. If Potential Breach = Yes, select user from the list in the Applicable Legal Team field by clicking .

   3. If s912D Checklist Required? = Yes, complete the s912D Assessment section.

      1. If s912D Checklist Q5 = Yes, complete the Reportable Situation section.

      2. In the Reportable Situation section: if RG78 Checklist Q3 = Yes, then create Investigations by clicking the | Add New | button in the Investigations field. Refer below Tasks 3 and 4 for more details.

   4. If OAIC Assessment Required? = Yes, complete the OAIC Assessment section.

6. (Optional)Add Comments to the record by clicking the | Add New | button in the Comments section.

7. Click Save in the Record Toolbar.

8. Click Submit Assessment from the Actions dropdown at the top left of the screen.

User: Compliance Manager

1. Create Investigations record.

   1. From the menu bar, click on the dropdown beside Incident Management Accelerator Workspace.

   2. Under Individual Incident Management > Investigations, click on New Record.

2. Fill in the following information in General Information section:

   1. Enter Investigation Request Name.

   2. Select Related Incidents by clicking in the Target field.

3. In the Investigator Assignments section:

   1. Select user from the list in the Investigation Owner field by clicking .

   2. Select user from the list in the Investigation Manager field by clicking .

4. In the Investigation Request Information section:

   1. Select Request Type and Urgency by clicking the down arrow next to the field and making your selection.

   2. Select Investigation Location by clicking and making your selection.

   3. Enter Request Description.

5. Once the record is complete, click Save in the Record Toolbar to save in record.

Users: Compliance Manager

1. Select the Incidents record you want to provide response by clicking the Incident Name under the Tasks section on your Task landing screen.

2. Click Edit in the top of the record.

3. Navigate to Investigation Outcome section.

4. Not a Reportable Situation

   1. Select ‘Not a Reportable Situation’ value in the Reportable Situation Resolution field.

   2. Click on End Investigation – Not Reportable from the Actions dropdown at the top left of the screen.

5. Reportable Situation

   1. Select relevant value in the Reportable Situation Resolution field.

   2. Enter details in the Investigation Outcome field.

6. Click on End Investigation – Reportable from the Actions dropdown at the top left of the screen.

Users: Incident Owner

1. Select the Incidents record you want to provide response by clicking the Incident Name under the Tasks section on your Task landing screen.

2. Click Edit in the top of the record.

3. Navigate to the Resolution tab.

4. In the Financial Analysis section:

   1. Enter Financial Loss Amount, Recovered Amount and Amount Gained.

   2. Enter details in Cost Calculation field.

5. Create Remediation Plans by clicking the | Add New | button in the Remediation Plans section.

6. (Optional) Add Comments to the record by clicking the | Add New | button in the Comments section.

7. Click Save in the Record Toolbar.

8. Click Submit for Closure from the Actions dropdown at the top left of the screen.

Users: Compliance Manager

1. Select the Incidents record you want to provide response by clicking the Incident Name under the Tasks section on your Task landing screen.

2. Click Edit in the top of the record.

3. To Approve the incident closure

   1. Review the information in the Incidents Record.

   2. Enter comments in the Compliance Closure Comments field.

   3. Click on Approve Closure from the Actions dropdown at the top left of the screen.

4. To Reject the response:

   1. Click on Reject Closure from the Actions dropdown at the top left of the screen.

   2. Document the reason for rejecting the response in the Compliance Closure Rejection Comments field.

   3. Click on Submit from the Actions dropdown at the top left of the screen.

5. (Optional) Add Comments to the record by clicking the | Add New | button in the Comments section.

6. Click Save in the Record Toolbar.

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.

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. The Log Messages section provides a list of conditions that may cause objects not to be installed. The Package Installation Log section displays a log entry.

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

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

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.

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

6. Click Install.

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

   1. From the menu bar, click .

   2. Under Application Builder, click Applications.

2. In the Applications section, select the Incidents Application.

3. On the Advanced Workflow Tab, click ‘Activate’ in the top right corner of the page.

4. Then click ‘Save Workflow’ in the top left corner of the page.

5. Repeat Step 1 above. In the Applications section, select the Investigations Application.

6. On the Advanced Workflow Tab, click ‘Activate’ in the top right corner of the page.

7. Then click ‘Save Workflow’ in the top left corner of the page.

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 ‘Create Regulatory Correspondence from Investigations’ 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 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 the settings on the Source Definition tab. This will be pre-configured to identify the necessary fields.

   Note: The Type and Clear Notification Helper Field on the Source Definition tab will be automatically populated when you install the data feed. Repopulating the fields by clicking on “Load Fields” will lead to removal of these pre-populated fields from the list. Hence, follow the below steps to add the two fields in Source definition tab:

• Add a new field by clicking on “Add New” and rename as “Type” and select field type “Static Text” with appropriate value “Breach” in the Text editor.

• Add a new field by clicking on “Add New” and rename as “Clear Notification Helper” and select field type “Static Text” with appropriate value “Created” in the Text editor. Also, be sure that the data mappings are configured correctly after the load fields.

8. Verify that except for the Regulatory Correspondence, key field values are not missing from the data feed setup window.

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