CoreandServices.book - Ocean - Schlumberger

Custom Processes
Now we need to rewrite our Apply button callback to check for the environment in which
we are running and handle the process environment. Use the context class type to
determine if you are a workstep wrapped in a process or not.
private void btnApply_Click(object sender, EventArgs e)
{
// update arg values from UI
this.args.Well = ...;
}
if (context is WorkstepProcessWrapper.Context)
{
workstep.InvokeSimple(args);
this.UpdateUI();
}
// notify the workflow that we have updated the arg package
context.OnArgumentPackageChanged(this, new
WorkflowContext.ArgumentPackageChangedEventArgs());
Since we are updating the UI ourselves after invoking the workstep, we need to add a
check to the argument package event handler.
void argPkgChanged(object s,
WorkflowContext.ArgumentPackageChangedEventArgs e)
{
// do nothing if sent myself; already handled update
if (sender == this)
return;
UpdateUI();
}
Step 3 - Implement Persistence
If you did not implement persistence on your workstep argument package, your process
arguments will not be saved. Each time the end user starts your process, the UI will have
the default values.
Not retaining the UI entries that the end user previously entered is contrary to the Petrel
conventions. You should implement persistence on your workstep argument package if
you have not already, using one of these two methods:
• Serialization
Schlumberger Private
Workflow 6-343