Related Topics
Every application you build in Process Director contains one or more Content List objects, also called Process Director objects, that define how the application will work. Each object performs a specific function in the application. A Form, for example, is the object that users access to enter information in electronic format, which the application will then process in some way. The Process Timeline models the process and defines the route the Form will take during each iteration of the application's life, from Form submission until the application has reached the end of the process. In general, a functional application needs at least one Form and one Process Timeline to perform a useful task. The Form stores the information needed by the application, and the Process Timeline routes the information to users who need to see and make decisions based on the information.
Most applications, of course, are more complex than this, and require other objects to function properly. An application may need to use a Business Value to extract information from an external data source, or a Business Rule to implement some specialized business logic. Applications that model business processes must often implement complex business logic or sophisticated information processing and evaluation. Thus, they may require many objects to function as desired. Each Process Director object encapsulates a specific function or feature, and enables you to create modular applications—often quite complex ones—without requiring you to write customized programming code. As an implementer, you add and configure the objects to your application to provide the desired features.
This section of the documentation lists, in alphabetical order, all of the Content List objects that are available to you. You can navigate to the documentation topic for each object using the Table of Contents displayed on the upper right section of this page, or by using one of the links below:
Business Rule: Enables you to incorporate business logic to return a true/false value, or other custom values, as the result of evaluating a condition.
Business Value: Enables you to use virtualized data anywhere in Process Director.
Case Definition: Enables you to implement Case Management applications.
Chart: Enables you to display infographics in your application.
Dashboard: Enables you to display Process Director objects in a unified screen, to organize what the end users see.
Datasource: Enables you to create connections to external databases, for extracting data, which is usually presented to end users via a Business Value.
Dropdown List Object: A list object that stores options to present in a Dropdown control on a Form. This object is re-usable and can be referenced by any Dropdown control on any form to provide the selectable options that will be visible to the end user.
Form: The primary data collection and storage object for an application.
Goal: An object that evaluates a condition, sets a system state, and optionally starts a specified process on a scheduled basis.
Knowledge View: The primary object for extracting and reporting on data in Process Director.
Machine Learning Object: A specialized data evaluation object for using complex statistical algorithms to evaluate large data sets and return a predictive result. Effective use of this object requires some academic grounding or experience in data science to use correctly.
Meta Data: A taxonomy system of categories and attributes that can be applied to most Process Director objects.
Process Timeline: The primary method of modeling the process an application will implement. The Process Timeline specifies the activities that will occur, their order, participants, and results.
Report: Using a sophisticated report creation component, this object enables you to create complex reports that can't be effectively presented through a Knowledge View.
Stream Action: This object can retrieve a dataset/recordset, and begin a process for each item/row of the recordset on a scheduled basis.
Workflow (Legacy): The original process model used by Process Director. This process model has been deprecated by the Process Timeline, and remains in the product solely for backwards compatibility. BP Logix recommends that you use the Process Timeline for all applications. The Workflow does not receive any functionality updates beyond necessary bug fixes, if any.
Documentation Feedback and Questions
If you notice some way that this document can be improved, we're happy to hear your suggestions. Similarly, if you can't find an answer you're looking for, ask it via feedback. Simply click on the button below to provide us with your feedback or ask a question. Please remember, though, that not every issue can be addressed through documentation. So, if you have a specific technical issue with Process Director, please open a support ticket.
