CoreandServices.book - Ocean - Schlumberger

Custom Worksteps
You can assign the grid specified by the special “With 3D-Grid” command in the workflow
to the argument’s value by using the custom Ocean attribute
TakeValueOfWith3DGridAttribute.
Optional in Workflow
Normally, the Workflow editor requires that all arguments have a value assigned to them
before running the workflow. You can tell the Workflow editor that your argument is
optional.
When you use the OptionalInWorkflowAttribute, the Workflow editor will not
check if the argument has a value before running the workflow.
Ignore in Workflow
The final interoperability feature is to tell the Workflow editor to ignore your argument and
pass it through to your custom dialog UI.
The custom Ocean attribute IgnoreInWorkflowAttribute is useful if you have an
argument type that does not appear in a Petrel tree, like a drop down selection box
representing an enumeration or a verified date string. Using this attribute means you
typically create a custom dialog UI to assign a value to the argument. If you use the
default dialog UI, the ignored argument will always have its default value.
Here is an example of marking an argument to be ignored in the Workflow editor:
// argument to be ignored by Workflow editor
[IgnoreInWorkflow]
[Description(“Special type”, “custom enumerated well type”)]
public MyNamespace.MyWellType SpecialWellType
{
internal get { return swell;}
set { swell = value;}
}
...
Advanced - Argument Package Details
Creation of arguments using DescribedArgumentsByReflection is the preferred
and extremely convenient approach to creating argument packages, but it is not required.
So far, we have not looked at the convenience class in any detail; we will do that now to
provide a basis for discussion of the argument package alternatives. These details are an
advanced topic; a typical developer would just use the convenience class.
Schlumberger Private
Workflow 6-295