The following definitions apply to topics covered in this guide.
activity | A unit of work performed by a single process flow user. |
---|---|
activity name | The label given to an activity in a process flow. |
actor | The role or user that performs the work associated with a given activity in a process flow. |
Administration | The management and configuration activities that are performed by the EPX administrator |
alias rule | A specific actor is assigned to a role type and receives all work items related to that role. |
All split | A point in a process flow where a single thread of control splits into two or more parallel paths. Work item versions are always sent to all destinations of the split. |
And join | A point in a process flow where two or more parallel executing activities converge into a single common thread of control and are synchronized |
API | Application Programming Interface |
automatic activity | A representation of the action that a BIC performs in a process flow |
BIC | Business Integration Component. An independent program used to integrate data, files, and messages from external file systems and third- party applications, and to automate activities in a process. |
content pane | A term used to specify the work area in a window such as the large area on the right hand side of the Design Console, TaskManager, and Report Tool. |
Draftbox | The box containing a list of work items that have been created, but not yet introduced into a process flow. |
DSN | Delivery Service Notification |
EJB | Enterprise JavaBeans |
EPX | EnterWorks Process Exchange. An object-oriented, Java-based automation tool that extends process flow technology to business processes task |
enroute work item | A work item that has been introduced into a process flow but has not yet reached its final destination activity in the process flow. |
form element | A tag name within a form tag on an HTML page, which appears as an option in a work item viewer. |
HTML field | An input field defined in an HTML form. |
HTML work item | A work item that is viewed using an HTML form IIOP Internet Inter-ORB Protocol. |
Inbox | A list of pending work items assigned to a user Java An object-oriented, cross-platform programming language developed by Sun Microsystems specifically for use on the Internet. |
JavaHelp | A full-featured, platform-independent, extensible help system for incorporating Help into applets, components, applications, operating systems, and devices. Allows EPX users to view the product documentation. |
JDBC | Java Database Connectivity |
JDK | Java Development Kit |
join | An activity in a process flow where two or more parallel activities converge into a single common thread of control. |
JVM | Java Virtual Machine. The program responsible for processing Java applications. |
LDAP server | A directory server supporting Lightweight Directory Access Protocol. Often used on the Internet or within intranets to store user details such as e-mail addresses, phone numbers, and address information. LDAP is based on the X.500 directory standard. |
manual activity | A representation of the action that a user performs in a process flow. |
Migration Tool | An application used to migrate information from one EPX server to another. |
navigation pane | The area or window that allows users to select or move through various elements of the Design Console, TaskManager, and Report Tool. |
object types | Classifications of the EPX-specific data stored in the EPX database, such as process flows and their components |
ODBC | Open Database Connectivity |
One split | A point within a process flow where a single thread of control splits into two or more parallel activities. Only one activity receives a work item. |
Or join | A point within a process flow where two or more alternative activities’ branches re-converge to a single common activity as the next step within the process flow. As no parallel activity execution has occurred at the join point, no synchronization is required. This type of join requires that each work item be released back into the process flow when completed. |
override viewer | The viewer configured to display a work item’s contents at a specific activity. |
pool rule | Multiple actors are assigned to a single activity, allowing all actors in a group (pool) to view any work items that are sent to the activity |
process flow | The flow of information and control in a business process |
process flow canvas | The area where a process flow is graphically defined |
process flow template | A process flow or subflow layout that can be used as a basis for creating new process flow or subflow processes |
RDBMS | Relational database management system |
Report Tool | A Web-based application used to obtain reports on the status of business processes implemented within EPX |
role | Represents a function in a process flow that can be assumed by one or more users. Typical roles might be “supervisor” or “administrator”. |
routing slip | When a split occurs in a process flow, a routing slip appears in TaskManager where a user specifies which activity (One split) or activities (Some split) to send the work item to |
RMI | Remote method invocation |
schedule rule | A specific actor works all activities assigned to a specific role during a specified period of time |
send | A request to send a work item to the next destination in the process flow |
sender | The user or BIC that requests a work item to be sent |
Sent | The list of work item versions that have been acted on by a particular user or role. |
servlet | A small, pluggable Java extension to a server that enhances the server’s functionality. Servlets are used in EPX to provide dynamic content for TaskManager and to provide access to Report Tool. |
Some split | A point within a process flow where a single thread of control splits into two or more parallel activities. One or more destinations can receive a work item. |
split | A point within a process flow where a single thread of control splits into two or more parallel activities. Depending on the type of split, work items are sent to one, some, or all destination activities. |
SQL | Structured Query Language |
SSL | Secure Sockets Layer |
starting point | An activity within a process flow in which work items can be introduced |
TaskManager | A Web-based application that allows process flow users to access the work items they are assigned to. |
transition | The path between two activities in a process flow with an origin at the source activity and a termination at the destination activity. |
transition arrow | A graphical representation of a transition in a process flow between two activities. It consists of a line with an arrow pointing to the destination activity. |
URL | Uniform Resource Locator, used by Web browsers |
user | Actor that performs the work represented by a manual activity instance. |
viewer | That portion of TaskManager that uses an HTML file to display work items in a particular format |
viewer association | A work item viewer can be associated with a given work item type. This association indicates which HTML forms can be used to view a work item of a given type. |
viewer URL | A Uniform Resource Locator to an HTML file. In EPX, it must be specified relative to the server URL. |
work item | An electronic document or other form of data passed in a process flow. |
work item content | An instance of the data that represents a work item at a given activity in a process flow. Also called work item version. |
work item name | A label assigned to a work item. |
work item type | An abstract category used to classify work items, denoted by a name, such as Time Sheet. |
work item viewer | An HTML file displayed by TaskManager that represents a view of the data contained in a work item version. |
XML | Extensible Markup Language. Allows you to define your own set of tags to define data, thereby defining the logical structure of the data. |
XSL | Extensible Style Language. Used for formatting XML documents. |