CoreandServices.book - Ocean - Schlumberger

Custom Worksteps
Your workstep is not the only client of the argument package, Ocean uses it to construct
the line UI and default dialog UI.
Fig. 6-27 Line UI for Workstep Example
Fig. 6-28 Default Dialog UI for Workstep Example
Notice that all four arguments are shown as inputs; that is not correct, the workstep has
two inputs and two outputs. Also, notice that the argument names are exactly the
property names from our argument package class.
We can give more information to Ocean to help it build a better UI for us. For each
argument we can give its:
• Role (input and/or output)
• Initial value
• Description
Argument Roles
We need to tell the system what roles our arguments have: whether they are input
arguments, output arguments, or both. This is accomplished via the accessibility of the
property get and set.
For an input argument, the system will need to give us the argument value from the UI.
The set is public to allow the system to load the argument value from the UI into our
argument package. The get for an input argument does not need to be public because
the system does not need to use it, so we make it internal by convention.
Schlumberger Private
Workflow 6-287