Try OpenEdge Now
skip to main content
Developing BPM Applications with Developer Studio
Using dataslots : Creating user-defined dataslots : Setting the dataslot access
 

Setting the dataslot access

You can use the Access section in the Dataslots tab to define access properties of the dataslot.
Note: The Access section is not available for dataslots in Web applications.
From the Access section, you can select (or clear) any of the following access modifier checkboxes:
*Public: By default, all dataslots are public and this checkbox is selected. Public dataslots have persistent dataslot values even after the process instance is completed. If the Public checkbox is not selected, the dataslot is private and its value cannot be accessed from other Business Process Server components such as the Management module in Business Process Portal and BPM Events.
*Management Access: This checkbox is disabled for List, Map, Business Objects, and Object dataslot types. It allows you to make viewable or hide dataslots from view in the Application Status Viewer in the Management module in Business Process Portal. By default, the Management Access checkbox is selected and dataslots are visible in the Management module. With both Public and Management Access selected, editing dataslots in the Management module is allowed
*Global: Select this checkbox to change the dataslot from a process instance-level dataslot to an application-level dataslot. When you create a Global dataslot, its value is shared for all process instances in an application. If you modify a Global dataslot value in one process instance, that dataslot value in all instances of the application has to be changed. Global dataslots enable business applications to keep statistics of all instances of an application and provide accessibility to a workflow, which is important if workflow decisions are based on those statistics.
*Tasks Column: This checkbox is disabled for List, Map, Business Objects and Object dataslot types. Select this checkbox to add the dataslot as a column for the application in Business Process Portal. In the Business Process Portal, the Home module’s Task List page displays the dataslot label (or dataslot name if no label is assigned) as the column heading for the selected application.
Note: You must select the specific application in which the Tasks Column option was set . If the Application and Version drop-down list in Business Process Portal is set to All, the Tasks Column settings will not be displayed.
Data for the dataslot, however, is displayed in the column only if the dataslot is specified as input or output to that workstep.