Navigation:  Configuration > General parameters >

SE Risk conversion

About the data conversion

This section will describe the main changes expected after the conversion process is completed. The SE Risk component went through several changes to SE Suite version 2.0. From a structural point of view of the system, two points stand out - the new relational tables used in version 2.0, which have the "RI” suffix instead of "HA” as in the old version, and the new ISOSYSTEM code of the component, which went from 163 to 215. Only the Object, Process and Project contexts of SE Suite 1.3 will be converted, that is, plans from other contexts will not be considered. The control plans of SE Suite 1.3 will not be converted either, since they were disabled in version 1.3.20. Below are the changes between the versions.

Tokens

There will no longer be customization of tokens per context as in 1.3. It is possible to customize a token in SE Suite 2.0 through the Administration Configuration Customize Token (AD031), which is valid for the entire system.

Plan revision

In SE Suite 2.0 the plan revision is generic, that is, the same revision method used for Scorecard, Process etc., and for a plan to go through revision, its type must be correctly configured.

By default, after data conversion, plan types will not be configured to have revision control. Therefore, the user has to do so by accessing the data type of the plan type and, in the Revision tab, select the option to control revision and fill in the fields.

All plans will be converted to "non-default”, that is, as if they were created from the Management Plan planning (RI301) menu. Therefore, they will not follow the revision of the associated object (e.g. Process, Project, Scorecard). 

The plans of SE Suite 1.3, that have one running revision and another under revision will be converted as follows:

▪The revision that was running will be closed (approved revision).

▪The revision under review will be converted to planning (revision in draft).

Security

The revision permission on the security of the SE Suite 1.3 plan type will no longer exist in SE Suite 2.0. Plan security in SE Suite 2.0 works like a hierarchy of screens, that is, in the "Plan security" tab of the screen of plan type, the permissions of all the plans recorded with this type are configured, and in the security tab of the plan data screen are configured the permissions of the structure of that plan.  The plan type also has the type security, where it is possible to configure the permissions for that type itself.

Executing the data converter

For the system to enable the conversion option, it is necessary to insert a record into the ADPARAMS table in the database. The SQL ANSI command for inserting the record into the database is:

After inserting the record into the database, the user must access the general parameters screen of the component through the Configuration General parameters (RI110) menu, according to the following image.

The conversion process of the data takes place in two steps, which must, necessarily, be executed in the following order:

1. Record: Converts all the records from the configuration and file menus of the system, that is, attributes, checklist, teams, identification masks, dynamic navigators, all the types (plan type, risk type, control type, etc.), and all the records (risk, control, treatment, etc.).

2. Plans: Converts all the records from the management and execution menus of the system, that is, risk plans, revisions, risk analyses and their evaluations, and control analyses and their evaluations.

When clicking on the 1. Record button, a new screen will be displayed. On that screen, the system will execute a conversion script that may take a few seconds to finish. The "Processing" message will be displayed while the screen remains open, and, at the end of the process, a message will be displayed according to the image below.

After executing the first conversion step (records), it is necessary to execute the last part of the conversion through the 2. Plans button. The process is identical to step 1 described before.

After executing the two steps, the user may check if there are differences between the data of the two versions of the system by clicking on the Conversion status button.

The conversion status will display a list of all the tables that were converted. A success icon will be displayed if all records of every table were converted. A failure icon will be displayed if at least one record was not converted or if the number of records is different.

It is important to point out that there may be a difference in the number of records converted from a table, caused by inconsistency of information from the SE Risk component. The image below shows the conversion status screen.

At last, the purpose of the Remove all records button is to delete all the data from the SE Risk component in SE Suite 2.0. It should only be used if a problem occurs in the conversion of the records. Records added in version 2.0 will also be deleted.

After the execution of the data converter

The risk analyses and control analyses were converted with the user being responsible for the SE Suite session at the time of conversion. To receive the analysis tasks, the responsible user must be changed.

SE Suite 1.3 Dashboards, now called Portals, have not been converted to SE Suite 2.0 because the widgets have changed. To use them, the users must add them manually in the Portals menu of the system.

As in SE Suite 2.0 a unification of the contexts of version 1.3 occurs, situations can occur where the ID # of the type record (plan type, risk type, control type, etc.) and other records (plan, risk, control, source of risk, etc.) are repeated. To overcome this situation, the converter adds a unique code at the end of the identifier of each record to differentiate them from one another.