The sample project is comprised of several Process Director objects.
Business rules define some aspect of a business process and control its operation. Business Rules provide a convenient and useful way to encapsulate complicated or frequently used decisions and make them available for use by any process or eForm.
Business rules generally evaluate a condition or set of conditions, and then return a value based on the results of the evaluation. A condition refers to an existing state of some data or activity. For instance, in the BP Logix Getting Started Sample Project, there is a Business Rule called Is Finance Approval Needed? The condition this rule evaluates is whether the total amount contained in the ExpensesTotal field of the Travel Expense Request eForm is greater than $1,000. Based on this evaluation, the rule returns a "Yes" or "No" answer. If the answer is "Yes", the Process Timeline will send the request to the Finance department to approve the amount. This example demonstrates a simple use of a Business Rule that the Process Timeline uses to determine the path a process must take.
Other, more complicated, business rules might evaluate a number of conditions and return a number of different values. For example, let's say that you have a sales representative assigned to a particular state, or number of states. The business rule may evaluate a field that contains the state in which a customer lives and
return the name of the appropriate sales representative to a Process Timeline. The Process Timeline can then assign an action to the appropriate sales representative. In this example, the Business Rule evaluates a set of fifty-one different conditions (if we include the District of Columbia). Based on the result of that evaluation, the Business Rule will return the name of the sales representative for the customer's home state.
eForms are electronic forms that serve as the container for the data that is used in your workflow. EForms can enable users to input information, present information collected from other sources, control what users participate in the workflow, and much more. Each eForm consists of a number of Process Director controls.
A control is a user interface object, like a button or text box, that enables you to interact with an eForm. Controls are central to the operation of the eForm, because controls enable users to enter or edit information. Many controls, such as text input fields or checkboxes, may already be familiar to you.
You will use Microsoft Word to design eForm templates. Most of the activity of designing an eForm consists of placing Process Director controls on a Word page. Process Director will convert your templates into an appropriate format for viewing in a web browser, while retaining your design and formatting conventions.
When you place a control on an eForm page, Process Director also creates a data field that is bound to that control. Process Director uses this data field to store the value that users enter into the control when they submit the eForm. As an example, there may be a textbox control named FirstName in an eForm. When you enter a name into the control and submit the eForm, it is saved to the FirstName field in Process Director.
Because the form control and the form field are so tightly bound, we will use the terms ‘form control’ and ‘form field’ interchangeably.
There are also other controls, like the Section control, that determine how information is grouped or displayed by serving as a container for other controls. An eForm is essentially a container for controls, and the section control is, in turn, a container for other controls.
The Process Timeline is an exclusive feature of Process Director that adds the element of time to business process management. Instead of modeling a business process with a traditional flowchart, the Process Timeline is structured much like a Gantt chart, enabling you to include start and stop times, due dates, dependencies, and other time-based elements to your business process models. As a result, the Process Timeline enables you to easily identify the critical paths in each business process that you model.
Knowledge Views are the primary method used to retrieve information from Process Director. Knowledge views enable the user to find running processes, historical data, eForm instances, or many other types of data, and display information about them in a tabular format. The data produced by the Knowledge View can also be exported to files or other database systems.