Try OpenEdge Now
skip to main content
Application Developer's Guide
Using an LIST dataslot to invoke multiple subprocesses : Reviewing the publisher : Defining the main process worksteps
 

Defining the main process worksteps

As shown in the following figure, the Publisher application has three main worksteps:
*View publisher information — Displays the values of the first five dataslots (described in Table 8). For an illustration of how this workstep appears in Business Process Portal, see Figure 7.
*Invoke subprocesses — The subprocess performer, the @SubProcessNames LIST dataslot, creates three instances of the FictionAuthor application, and two instances of the NonFictionAuthor application. This LIST dataslot passes the values of AuthorIDs, AuthorNames, BookTitles, PublisherName, and publisheraddress dataslots by mapping them to dataslots in the subprocess instances. For example, the value in the AuthorIDs dataslot in the parent process is mapped to the AuthorID dataslot in the subprocess instances. If the dataslot name in the parent process is identical to the dataslot name in the subprocess, then no mapping is required. This workstep also stores the values returned from the subprocess instances, in the EstimatedDays and ExpectedRoyalty dataslots.
Note: The dataslots in each subprocess that receives data from the parent process must have the same name. In this case, for example, all subprocesses must contain dataslots named AuthorID, AuthorName and BookTitle.
*Get results — Displays the value of the EstimatedDays and EstimatedRoyalty LIST dataslots, returned by each of the subprocess instances.
Figure 7. Publisher application worksteps