The document below contains instructions for setting up Protheus Environments.
In environment management, a project is a work place that allows you to register changes to data dictionaries in a controlled way. A project can be developed separately from the production dictionary and other projects.
The project can later be used as a basis for updating approval or production environments or even be applied in other projects through the embedding option.
With the projects, the management of complex modifications becomes more productive and secure, where more than one team develops resources in parallel to be applied later together.
At the same time, the way of registering or editing the dictionaries in the configurator module is kept unchanged, minimizing training needs.
In the project, all actions (inclusion, edition, deletion) performed in a data dictionary (field, trigger, table, etc.) of an environment will be saved (Example: development) resulting in a Dictionary Differential file (sdf...), Help (hlp ...), Flavor (flv...), Flavor Help (hlpfv...).
These files can be added to a package for application in other environments (Examples: Homologation, Production).
It effectively creates a new project with an ID so your changes are made and saved while linked to the desired project through the ID.
A Project contains the following key information:
The change only applies to the registration data. Project content is maintained through the default routines of the configurator.
This option lets you copy the components of a project to another project.
Select a source and a target project.
Source project data that does not exist in the target project will be included. Data that from the source project that exists in the target project (with the same key) will be overridden.
The same key data will be displayed before completion. The user can check and choose not to embed the project.
The source project may or may not have its status changed to "embedded" at the end of the process. If the project is marked as "embedded", it can no longer be manipulated.
It displays, in addition to the registration data, the components (dictionaries) linked to the project.
The components will be grouped by dictionary type.
Example: tables dictionary, field dictionary.
It deletes both the project and the components (dictionaries) linked to it.
If the package was previously embedded, only the package data itself will be deleted.
Through this feature, the user can choose which Project to work on.
From this point on, any changes made to dictionaries in this section will be saved in the selected project.
A window containing the active projects for selection will be displayed.
The selected project will be kept until the user logs off the configurator module or logs into another project.
The maintenance of the data dictionaries of a project has not undergone modifications in relation to the normal process of the configurator. The difference is, after logging in the project, the changes begin to internally write the project code. You can separate the data between projects in the temporary area of the configurator.
For example, if you want to add a new custom table in the project, simply log in and perform normal configurator table registration procedures.
Through the "view" option of the project register, the user can check what is actually registered in the project.
A package is a set of items for updating an environment. The update may contain changes to dictionaries (and therefore table structure) and program patches.
The part related to the dictionary will be extracted from the data of a project previously registered and fed.
The package facilitates the distribution of dictionary updates, table structure and program patches between different environments.
SIGACFG, ATUSX and/or Patch files.
