Best practices in organization of integration projects

This document describes some best practices for organizing and configuring projects in order to facilitate their maintenance and evolution.

Organization

Projects must be organized according to the functional areas of the product. This form of organization ensures that, regardless of the complexity of the project, it is possible to perform evolution / maintenance on a module without causing impact on the others.

Therefore, we recommend that:

1 - The name of the projects is composed of up to three items, following this format [ProducerName].[Module].Extensibility.

2 - Classes that implement extensibility are organized into folders by functional area (Sales, Purchases, etc.).

3 - Classes that implement interface events are composed of the functional area name followed by the 'Editor' suffix.

4 - Classes that implement API events are composed of the name of the functional area followed by the 'Service' suffix.

References

To avoid problems between ERP versions, references to PRIMAVERA assemblies must be respected:

1 - The value of the 'Copy Local' property must be False.

2 - The value of the 'Specific Version' property must be False.