FESA3 Database Workflow - Issues to consider

The integration of the FESA3 database may affect the FESA development workflow known so far. If FESA software is supposed to be accessible via JAPC (Java applications) the FESA designs must be exported to the database. This may be achieved manually () or during the release of a class () or a depoy-unit (). The following issues should be considered when using the database:

• before a deploy-unit can be exported to the database the included class(es) must be exported first (/)
• before explicitly exporting an instance document the class and the deploy-unit must be in the database (/)
• the class / deploy-unit version must be increased for classes / deploy-units: when the design document has already been exported to the database
• if subsets are used only the generated subset designs must be exported to the database, not the original class design! () The subset designs are generated automatically by the FESA plug-in before the export to the database.

FESA Forum 16.01.2019: Release/Deployment of FESA Software and database considerations