The "Variables" view displays the value of any variable that is declared in the "Declarations" tab of the collaboration template definition. This includes the business objects that are automatically declared by Process Designer Express to be associated with each port that you create on the "Ports and Triggering Events" tab, as well as any variables you add to the "Declarations" tab yourself.
When you display an event as described in Displaying an event or manage a flow as described in Performing debugging operations, the "Variables" view updates the variable information it shows. You can expand any variables of BusObj type to view their attributes.
There is currently no way to display the triggeringBusObj variable. This is a system-declared variable that references the original flow that triggered execution of the collaboration object, and is typically very significant. If you want to maintain a record of the values of the triggeringBusObj variable, you can declare a new BusObj variable in the "Declarations" section of the collaboration template, then initialize it to the value of the triggeringBusObj variable in the first node of the scenario.
Furthermore, many delivered collaboration templates manipulate a variable named processingBusObj and leave the triggeringBusObj variable untouched. The processingBusObj variable is typically declared at the scenario level rather than the template level, though, so it is not displayed in the "Variables" view. To have the processingBusObj variable available in the "Variables" view, move the declaration for the variable from the scenario definition to the template definition.
You can filter the "Variables" view to only display variables of certain types. Do the following to filter the "Variables" view:
Collaboration Debugger displays the "Variables Filter" dialog, as shown in Figure 93: