Top
Top
LibraryEASYProcess Reference ManualInstallationDatabase

Database

For each application made by EASYProcess, a Base Application is also needed. See below the Base and EASYCommerce Applications that exist for a single instance of EASYProcess. When opening EEM, the environment will be shown. In this example, the environment is PD2. Below this are the two applications that create this environment: EASYCommerce and Base. Once EASYProcess is open for the PD2 environment, the user has an option to open either of these applications. When viewing the databases for the PD2 environment, one will exist for both applications.

Applications for an EASYProcess environment in EEM

Applications in EASYProcess

Databases in SQL Management Studio

Database Naming Convention

Naming the databases should always follow the naming convention for EASYProcess databases:

EP_[ProjectName]_[Environment]_[ApplicationName]

EP_[ProjectName]_[Environment]_Base


Base Database
Application Database

Base Database

Each EASYProcess environment requires a database connection to the base database. The base database contains data that is essential to core EASYProcess functionality. Connection to this database is required in order for EASYProcess to function correctly. Developers should never have to access the base database or make changes to it over the course of development. The base database is only ever affected when EASYProcess is upgraded or there is some change being made to EASYProcess itself. Changing records in the base database affect how EASYProcess works and should only be done when intentional through an EASYProcess upgrade using EEM to automatically make the proper changes.

Examples of Base Database Tables:

  • Service Tables - Every service that can be used in a process canvas is defined in a table in the base database. When EASYProces is upgraded, if a new service is added or an old service is deprecated, the records related to those services are edited/added in the base database by EEM which performs the upgrade.
  • Entity Tables - EASYProcess has copies of database table definitions which are called entities. It does this so it can quickly do the equivalent of table joins and even store more information related to each record than it has defined in the table (such as the next number which EASYProcess generates and will insert into the table’s primary key column). In the Base Database, entities are used for Workflows, Processes, and WebParts. The information for a single WebPart is stored across many tables (related to fields, sections, etc). EASYProcess uses entities to quickly grab associated data related to the desired WebPart and display it when EASYProcess is used to view the WebPart.
  • System Level Configuration Variables Tables - Configuration Variables that are considered necessary for EASYProcess to create any Application will be part of the System category (instead of the Application category). These will be defined in the Base Database.

Application Database

The application database contains all of the data that defines what the application is and what it does. Any component designed and developed in EASYProcess for an application is stored here. This is the database that the developer will be accessing and using to create the application.

Examples of Application Database Tables:

  • Custom Tables - When new features are added to the application, if a database table is desired, it will be added to the Application Database.
  • SCM Tables - All SCM tables are directly related to the application and are defined in the application. These tables store info like what sources are currently checked out, what project they belong to, what developer is working on it, etc.
  • WebPart, Process, Workflow, and WebPage Tables - Every aspect of the application exists as a record in a table in the application database. These tables store the XML which define the WebPart, Process, etc.
  • Entity Tables - EASYProcess has copies of database table definitions which are called entities. It does this so it can quickly do the equivalent of table joins and even store more information related to each record than it has defined in the table (such as the next number which EASYProcess generates and will insert into the table’s primary key column). In the Application Database, entities are used for commonly used tables such as the shopping cart or order tables.
  • Application Level Configuration Variables Tables - Configuration Variables created for the specific application will be part of the Application category (instead of the System category). These will be defined in the Application Database.

Custom Table Naming Convention

When creating custom tables, it is important to Follow standard naming conventions. Depending on the purpose of the table, a different template should be used.

Type of Custom Table

Naming Convention

Comments

Client Specific Table

[ClientAbbreviation]_[TableName]

This ensures that all custom tables made for a feature are located by each other in the alphabetized table list. This also makes custom tables easy to identify for other developers.

EASYProcess System Table

EP_[TableName]

This is the existing naming convention for EASYProcess system tables used by the Application.

Application Table

[ApplicationAbbreviation]_[TableName]

“EC_[TableName]” is the existing naming convention for EASYCommerce tables.


Powered by EASYProcess (© 2019 K-Rise Systems, Inc).