Creating a Screenflow

Presentations can be used directly from the process, but normally they are used by screenflows, which are a specialized kind of process for user interaction sequences. Screenflows are in turn called from the main process.

To create a screenflow:

  1. In the process design editor , right-click on the Create Expense Report activity, and click Main Task from the context menu. The Main Task dialog box appears.
  2. In the Implementation Type section, select Screenflow from the drop-down list.
  3. In the Related Screenflow section, click New. The New Screenflow wizard appears.
  4. In the Name field, enter Submit Report, and click Next. The Select Instance Variables page of the wizard appears.
  5. The reportArg variable should be set as follows:
    In Out
    No No

    All others should be set to No.

  6. Click Next. The Screenflow out - Process in Argument Mapping page appears.
  7. Verify that this page has no entries, and click Next. The wizard finishes, and you should see the "Screenflow created successfully" message.
  8. Click Finish. The wizard closes.
  9. Now specify the location of where the screenflow will be placed in the Project Navigator. Click OK to accept the default location shown, under Processes.
  10. Click OK in the Main Task dialog box. The dialog box closes and an editor opens with the Submit Report screenflow diagram. The Begin and End activities are automatically included, as when a new process is created.
  11. In Instance section of the Variables window, add an instance variable named reportSf, of type ExpenseReport.

    This instance variable will hold an ExpenseReport object during the life of the screenflow. We added the Sf suffix to make it easier to identify as a screenflow instance variable, as opposed to the process instance variable report.

    Note that this is not an ALBPM convention and is not required.

  12. Right-click on the reportSf instance variable and click Map as process incoming argument (Map as Incoming Argument icon 
				), and then right-click again and click Map as process outgoing argument (Map as Outgoing Argument icon 
				). The reportSf instance variable will receive the value of the incoming argument reportSfArg, while the outgoing argument reportSfArg will take the value of the reportSf instance variable. You can check this by right-clicking on the Begin or End activities and clicking on Argument Mapping.
  13. Save your changes.

You have now created the Submit Report screenflow, and set this screenflow as the main task of the Create Expense Report activity. You still need to design the screenflow, and will do this in the next task.