Select your user interface: Web Shell Smart Client

Business Process Instance Status Page

To start a business process (BP), you select a parameter set and use one of the following options:

• Manually from the business process parameter set page

• Job schedule

• Queue

• Windows script file

• Infinity task (Manually)

A business process instance status page or also known as the "status page" is primarily used to view the recent and historical statuses for a business process and its associated parameter set. After a business process is started manually, the task or action typically redirecta the user to the status page. Users typically navigate to the status page from the parameter set page or from other pages or tasks, if needed.

How you design your status page is up to you.  Keep in mind that a typical business process instance status page should provide the ability to:

1. View business process instance parameter set information via a custom View Data Form

2. View the recent status of the business process instance by leveraging an out-of-the-box View Data Form

3. Start the most recent business process instance using the parameter set provided for the instance by a Start process action button

4. Edit the parameter set for the business process with an action that calls upon an Edit Data Form

5. Generate a Windows Script File that launches the business process with the current parameter set. The script generation is kicked off by an action that calls on out-of-the-box CLR code.

6. Create a job schedule to launch the business process with the current parameter set by leveraging an out-of-the-box Add Data For

7. Create an Infinity task that launches the business process with the current parameter set via an action that calls upon an out-of-the-box Add Data Form

8. Delete the current parameter set for the business process

   

   

   Figure: Status page, recent status tab, and actions

9. View historical business process instances in a custom data list . See below.

10. Delete status history and any related output tables, if they exist, by leveraging an out-of-the-box record operation.

    

    

    Figure: Status history requires a custom data list and an action to call a record operation that deletes the selected history

11. View and manage job schedules by leveraging an out-of-the-box data list , Add Data Form, Edit Data Form, and Delete Record Operation

    

    

    Figure: Job Schedules tab

Below is a UML Use Case diagram that represents a typical business process instance status page. Each oval represent a Use Case. A Use Case is a UML modeling element that describes how a user of the proposed system interacts with the system to perform a discrete unit of work. It describes and signifies a single interaction over time that has meaning for the end user (person, machine or other system). In this case, the end user (actor) would typically be a system administrator (not shown) or other role that has permission to the feature or ability to perform an action on the page. The use case ovals represent a feature or action that references a feature. Green use case ovals depict custom features while blue use case ovals depict existing features created by Blackbaud.

Figure: UML Use Case diagram that depicts the status page