Navigation:  Additional procedures > Post-installation activities >

SE Risk conversion

About the data conversion

This section will describe the main changes expected once the conversion process is finished. The SE Risk component went through several changes to SE Suite version 2.0. From the structural point of view of the system, we can highlight the new relational tables used in version 2.0, that have the "RI” suffix, instead of "HA” in the old version, and the new ISOSYSTEM code of the component, which changed from 163 to 215. Only the Object, Process and Project contexts of the SE Suite 1.3 will be converted, that is, the plans that are from other contexts will not be considered. The control plans from SE Suite 1.3 will not be converted either since they have been disabled from version 1.3 on. See below the changes between the versions.

Tokens

There will no longer be token customization by context, as in version 1.3. It is possible to customize a term in SE Suite 2.0 through the Administration Configuration Customize Token (AD031) menu, 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 is used for a Scorecard, Process, etc., and, for a plan to go through revision, its type must be properly configured.

By default, after data conversion, plan types will not be configured to have a revision control. Therefore, the user will have to do it by accessing the plan type data screen and, in the Revision tab, check the option to control the revision as well as to fill in the fields.

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

The SE Suite 1.3 plans that have a revision in execution, and another one in the analysis will be converted as follows:

▪The revision that was in execution will be finished (released revision).

▪The revision that was under analysis will be converted to planning (revision in the draft step).

Security

The revision permission in the plan type security of SE Suite 1.3 will no longer exist in SE Suite 2.0. The plan security in SE Suite 2.0 works as a hierarchy of screens, that is, in the "plan security" tab, on the plan type screen, the user configures the permissions of all the plans created in that type and, in the security tab, on the plan data screen, the user configures the structure permissions of that plan. The plan type also has the type security, where the permissions of that type are configured.

Executing the data converter

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

After entering the record in the database, the user must access the General parameters screen of the component through the "Configuration General parameters (RI110)" menu, as in the image below.

The data conversion process is performed in two steps, which must, necessarily, be executed in the following order:

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

2. Plans: Converts all records that understand the management and execution menus of the system, that is, risk plans, revisions, risk analysis and their evaluations, and control analysis 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, which may take a few seconds to finish. The "Processing" message will be displayed while the screen remains open and, when the process finishes, a message will be displayed according to the image below.

After executing the first conversion step (records), the user must go to the last part of the conversion through the 2. Plans button. The process is similar to what was described in step 1.

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

The conversion status will show a list with all the tables that were converted. A success icon will be displayed if all records of each 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 some differences between the number of converted records of a table, caused by inconsistency in the information coming from the SE Risk component. The image below shows the conversion status screen.

Finally, the purpose of the Remove all records button is to erase all data from the SE Risks component of Suite 2.0 and should only be triggered if there is a problem in the conversion of the records. Records added from version 2.0 will also be deleted.

After the execution of the data converter

The risk and control analyses were converted with the user being logged in SE Suite session during the conversion. To receive the analysis tasks, the users must edit the responsible user.

The Dashboards of Suite 1.3, now called Portals, were not converted to SE Suite 2.1 because the widgets have changed. To use them, the users must create them manually through the system Portals menu.

Since in SE Suite 2.0 there is a unification of the contexts of version 1.3, there may be situations in which the ID # of type records (plan type, risk type, control type, etc.) and of other records (plan, risk, control, risk source, etc.) are repeated. To overcome this situation, the converter adds a unique code at the end of each record ID # to differentiate them.