Ocean* Application Development Framework - Ocean - Schlumberger

Custom Worksteps
You can use this class directly and create one instance for each of your arguments.
class Args : IDescribedArgumentsSource
{
MyArgClass o;
...
public DescribedArgument[] DescribedArguments
{
{
DescribedArgument arg1 =
new DescribedArgument(
o.first.Name, o.first.Description, ArgumentRole.In);
..
}
}
}
...
// allocate an array and load the objects
// return the array
You can also create a custom derived type and override the protected properties if
you cannot easily create the object via the constructors.
class MyDescribedArgs : DescribedArgument
{
...
}
Advanced - Writing
Your Own Argument
Package
The only reason to describe your argument package to the system is so Ocean can
use your argument package for the convenience functionality. If you do not want to
use any of the Ocean conveniences, then you are free to write your own argument
package.
Without any Ocean clients of your argument package, the only clients will be your
own code: your workstep algorithm and your custom UI. Your argument package
will transfer data back and forth between your UI and your workstep.
You can design your argument package with whatever interfaces and interactions
you feel are needed to communicate with your other classes. Once the conveniences
are not being used, Ocean places no restrictions on your argument package design.
To recap, this technique means that:
• Your line UI will be a placeholder.
• You must provide a custom dialog UI for the user to set inputs to your workstep.
• You cannot use the workflow editor interoperability features (AssignToGlobal,
With3DGrid, IgnoreInWorkflow) or the value $variables.
6-250 Ocean Application Development Framework 2009.1