Stream Actions Object

Users of Process Director v5.26 and higher have access to the Stream Actions object. This object will read a recordset stream from a Datasource, and enable you to submit a form instance for each record in the stream. Stream Actions can be scheduled and run on a recurring basis to import data on any desired schedule.

While Process Director enables Knowledge Views to run a new process instance for each row in the Knowledge View's results, this feature has a limitation. It can only be implemented when the data is reportable by a Knowledge View. Data from outside of Process Director cannot be returned via a Knowledge View, which limits the data that can be accessed and used to prompt a process instance.

The Stream Action, on the other hand, can access any data from any accessible Datasource and return that data as a recordset stream. Data from each record in the stream can be extracted, placed into a new form instance, and automatically submitted. In general, the Stream Action is used to process external data, while the Knowledge View is used to access internal Process Director data.

The Knowledge View begins a Timeline instance for each record. The Process Timeline may or may not have a Form associated with it and may or may not use any of the Knowledge View's data. Conversely, the Stream Action directly maps the data from each record to a new form instance, which is then automatically submitted. If you want a process to run, you must specify the process in the Form definition's Automatically start this process after Form is submitted property. The Stream Action is specifically designed to transfer data from a recordset into a series of Form instances by mapping data from the stream into Form fields.

A common use case for the Stream Actions Object would be to import data from an Excel spreadsheet, external data source, or Business Value, then create a new form instance for each row in the recordset, fill out fields on the form instance, then submit it to begin a process for each record.

The Stream Action requires a Form to operate, along with a Datasource object that enables you to retrieve the data you want. Without a Datasource object, you won't be able to access your data. Without a Form, you won't be able to map your data to any Form fields. Additionally, while a Stream Action can use a manually written SQL statement to retrieve the data from a data source, a Business Value is commonly used to return the data. These objects must all exist before you can configure the Stream Action, so it's best to create them prior to creating the Stream Action.

Properties Tab #

The Properties tab provides the basic object configuration settings.

The following Properties are configurable.

Below the Stream action is currently... property you'll see a message that says: "The Stream Action has never been run." This message will display until the Stream Action has run, after which it will be replaced with the date and time of the Stream Action's last iteration.

Data Set Tab #

The Data Set tab enables you to configure the data source you wish to use for this Stream Actions object. The configuration properties available on this tab will depend on the Data Set Type you select to use. You can select either a Business Value as a data source, which is the most common user case, but you can also configure a SQL data source directly as well.

Start Process Tab #

The Start Process tab enables you to specify the form to use to import the data and start a process when the form is submitted by the Stream Actions Object. When the object runs, it will import the data, create a new form for each row of data in the dataset, then immediately submit the form you specify here. If the Form Definition is configured to start a process when a new form instance is submitted, the process will begin immediately, with the data you've imported via the Stream Actions object.

The following properties are configurable.

Schedule Tab #

The Schedule table enables you to create the schedule you'd like to use to import the Stream data on a periodic basis.

The following properties are configurable.