Overview

This section aims to provide an overview of how the objects deployed by iDynamics Incident Management are structured, in order to make their customization easier.

Modifications to Standard Tables

The tables belonging to headers and lines of each of the Business Central documents from which incidents can be created, include a field indicating the number of incidents in which the document/line is involved. This is a field calculated from the incident line table, based on the type and document no. fields, as well as the line no. (and sub-line) within the document.

The Activities Cue table includes a calculated field indicating the number of open incidents. It is the one used on the Business Central home page as a new stack in the Activities section.

The marketing tables To-do and Interaction Log Entry, include the fields Incident No. and Incident Line No. in order to relate these marketing tasks and interactions to the incidents.

In all instances, the fields added by the application are easily located by the prefix IDPIMG.

New Tables

The various tables that the product adds to Business Central are described below in alphabetical order.

• IDPIMG Inc. Source Doc. and IDPIMG Inc. Source Doc. Line. Temporal tables used in the incident report from source documents. The 2nd one is used in the selection of the source document lines to be included in the incident. They are only used by application, they do not store data.
• IDPIMG Incident Category. Categories of incidents.
• IDPIMG Incident Close Reason. Reasons for closing incidents.
• IDPIMG Incident Comment Line. Comments on incidents. Both for the header and lines (if the Incident Line No. is specified).
• IDPIMG Incident Entry. Incident entries. They are generated automatically when closing or reopening incidents.
• IDPIMG Incident Header. Incident header. Information of the incident is stored: No., Description, Date/Time, Details, Category, Type, Priority, Status (Open/Closed), Originated By, Reported By, Assigned User.
• IDPIMG Incident Line. Incident line. Each line of the incident corresponds to a line of the document from which the incident originated. There can be several lines, if several documents and/or lines are involved.
• IDPIMG Incident Notifier. Incident notifies (e.g., Customer, Warehouse Manager, Shipping Agent, etc.).
• IDPIMG Incident Reopen Reason. Reasons for reopening incidents.
• IDPIMG Incident Source. Incident sources (e.g., Sales Dept., Warehouse Dept., Purchasing Dept., Shipping Agent, etc.).
• IDPIMG Incident Type Activity. Table to configure the marketing activities to be carried out for the resolution of incidents of this type, in case you want to use marketing tasks to manage the incidents, which is optional.
• IDPIMG Incident Type. Types of incidents. They depend on the categories.
• IDPIMG Incidents Setup. General configuration of the application. The only parameter available at the moment is the No. Series to be used to number the incidents.

Customization Events

The application publishes several events aimed at providing customization of the application. They are explained in detail in each of the points of this Developers section.

If you need any additional event, or have questions about how to approach any customization, please do not hesitate to contact us through our support portal.