02.05.2014 Views

CoreandServices.book - Ocean - Schlumberger

CoreandServices.book - Ocean - Schlumberger

CoreandServices.book - Ocean - Schlumberger

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Overview<br />

The Processes button in the Workflow editor shows all worksteps. Native Petrel worksteps<br />

are organized in categorized folders and all custom worksteps are in the <strong>Ocean</strong> Plugins<br />

folder.<br />

Processes<br />

button for<br />

worksteps<br />

native<br />

Petrel<br />

worksteps<br />

custom<br />

worksteps<br />

{<br />

Fig. 6-9 Native Petrel and Custom Worksteps<br />

A workflow usually contains many different types of steps; it is not limited to the data<br />

processing worksteps. Other steps in a workflow may handle execution control,<br />

messaging, and native Petrel data operations. These features and more are available from<br />

the Utility and Operations buttons. See the Petrel documentation for details.<br />

Workflow Inputs<br />

Workflows are executed in a batch mode; that is, the workflow and its steps have no<br />

interactive user input while it is being run. All inputs must be set by the user prior to<br />

running the workflow.<br />

A workflow may have many inputs since it can contain multiple worksteps. Each workstep<br />

may need multiple pieces of input data.<br />

A workstep has two user interfaces where the end user can specify the input data:<br />

• A line UI within the Workflow editor<br />

• A dialog UI in a new window outside Workflow editor.<br />

6-270 <strong>Ocean</strong> Application Development Framework 2008.1<br />

<strong>Schlumberger</strong> Private

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!