BluInsights offers a Transformation Center feature which will help you get through the transformation process of the inputs provided by a Codebase Project.
Creating a new Transformation Center project is accessible through the “New” button. A few elements are asked to complete the creation : a name, a customer, a description, and a referenced Codebase Project.
For a Codebase project to be acceptable as a referenced one, it has to follow this rule:
A Codebase Project is considered a valid reference for a Transformation Center if it contains at least one file considered as eligible for transformation.
A file is considered eligible for transformation if it has a valid legacy type supported by Velocity (see Legacy Types section).
Once the creation process is done, you will be redirected to the main Transformation Center dashboard, similar to the Codebase dashboard.
The supported legacy types are the following, followed by their related managed extensions :
- BMS : .bms, .map;
- BTG : .btg;
- CL : .cl, .clle, .clp;
- COB : .cbl, .cblle, .cblmf, .cob, .sco, extensions containing clb;
- CSD : .csd;
- DBD : .dbd;
- DDL : .ddl;
- DSPF : .dspf;
- JCL : .jcl;
- JF : .jf;
- LF : .lf;
- LISTCAT : .listcat;
- MFS : .fmt, .mfs;
- PF : .pf;
- PL1 : .pl1, .pli;
- PROC : .prc, .proc;
- PRTF : .ppf, .prt, .prtf;
- PSB : .psb;
- RPG : .rpg, .rpgle, .sqlrpgle;
- SQL : .sql, .sqlc;
Build your team
The Transformation project relies on some information from the Codebase project. For security reasons, only members of the reference Codebase project with the Assets permission can be invited.
Members of the Transformation project have the same permissions as in Codebase. For example, if the user does not have the right to see Management in Codebase Project, the columns related to Management (workpackages, status, labels) would not be displayed in the Inputs > Files module.