Business Objects

This section defines the business objects installed by BPS.

Business Object Description

Company Name Company object

This is a placeholder for your company. You should replace "Company Name" with the name of your company. For more details about setting up your company, see Setting Up Vaults, Companies, and Users.

eService Generator

See eService Object Generator below.

eService Object Generator

This type of object and the eService Generator are responsible for automatically naming objects. The only autonamer objects installed with Business Process Services are the ones for common objects (such as Publish Subscribe and Event objects). The autonamer objects for objects specific to an application are installed with the application.

eService Trigger Program Parameters

There are several business objects of this type that run trigger programs to:


  • populate the Originator attribute whenever any type is created or revised
  • perform actions when a task is completed (populate the completion date, notify route owners when the last task is completed)
  • performs actions when a route is started (create a task for route members with order numbers of 1 and notify them)

These objects are stored in the eService Administration vault. For information about triggers, see Triggers.

Sample data

If sample data was installed along with ENOVIA Business Process Services, then ENOVIA Business Process Services includes many test persons. There are three test persons to represent each role. Each person is added as an person administrative object and as a business object of the type Person. The sample Person business objects are all in the Active state. Each person is assigned to the role indicated in the person's name. The naming convention for the persons is "Test ROLE_NAME", "Test1 ROLE_NAME", and "Test2 ROLE_NAME". For example, the test persons added for the Product Manager role are named Test ProductManager, Test1 ProductManager, and Test2 ProductManager. All sample business objects are stored in the eService Sample vault.

Test Everything Person object

This person corresponds to the person administrative object Test Everything. This person is assigned to all roles and should be used for testing. The business object is connected to Company Name with the Employee and Company Representative relationships. This person is stored in the eService Production vault.