About Business Process Services
ENOVIA Business Process Services provides the configurable user interface and
schema and features used throughout ENOVIA products, such as Collections,
Discussions, document management, and company profiles.ENOVIA Business Process Services also allows internal and external (such as suppliers) users
to collaborate while maintaining access controls to data and provides
metrics reporting capability to assess performance based on product data.
ENOVIA Business Process Services combines these formerly separate applications:
- Application Exchange Framework
- Common Components
- Team Central
- ENOVIA Business Metrics Module
About Common Components
Common Components includes tools that are common to many ENOVIA products.
Common Components include:
- Routes and tasks and route templates
- Common profile management
- Common document management
- Subscriptions
- Discussions
- Workflows
- Issue Management
- Member Lists
- Common file search
- Parts and Part Families
- Engineering Changes
- Image Management
- Quick File Access
An application can use the common components to implement a feature or
use its own programs. Most common components are configurable so each
application can tailor it as needed. For example, the checkin pages can
be configured to show specific fields and attributes. If an application
has requirements that are not included in the common component, it uses
its own programs.
Before Reading This Guide
You should be familiar with how the ENOVIA Live Collaboration user interface
works. See the Application Exchange Framework User's Guide.
Getting the Most Out of This Guide
This guide contains sections that describe how to use each of the Common Components. You can access the help by clicking on a dialog box or page. Use the Sitemap and Index to locate the needed information.
Published examples in this document, including but not limited
to scripts, programs, and related items, are intended to provide some
assistance to customers by example. They are for demonstration purposes
only. It does not imply an obligation for ENOVIA to provide examples
for every published platform, or for every potential permutation of platforms/products/versions/etc.
|