Working with variables for content objects
About this task
To access the properties of a case solution, in the Business Automation Studio, open the case solution in the designer. In the library for the opened case solution, under Data, you can see a list of all the data types that have been defined in Case Builder and brought in to the designer. The Content Object section of the list includes all the business objects, case types, and activities. The Property section of the list includes all the case properties that have been "mirrored" in the designer.
To understand how the content objects for case types, activities, and business objects can be used in the designer, say you want to leverage some of the exposed content objects in a process that implements a case type activity. By default, processes created in Case Builder include a reference to the corresponding content objects. In the Variables view of the process, under Content Objects, you can see the content objects that you can work with. In the Definition view, the user task for the process is implemented as a client-side human service, which models the user interface (UI) for the specified case activity implementation.
If you are creating a new client-side human service for one of the following entities in a process that implements a case activity, the New Client-Side Human Service wizard enables you to select content objects as well as variables to use as inputs or outputs for the new client-side human service:
- User task
- Details UI
- Launch UI
In the Variables view of the client-side human service, all the content object variables are passed by reference between the process implementing the case type activity and the service and they are listed as input variables. You can select the properties of each content object to specify which case data to expose to the client at run time, as described in the procedure below.
Note that you can also use views to represent the different case properties. When you create a client-side human service for your case solution UI, you can use the views that have the case properties.
Procedure
For security or privacy purposes, to reduce the exposure of customer data at run time, for example, you might want to filter out some of the case properties that you don't want to expose to the client through the UI. To specify which case properties to pass to the client-side human service and expose at run time: