|
<< Click to Display Table of Contents >> Navigation: Best Practice Flows > Workflows |
A workflow in g-Space is a named sequence of jobs — procedures and database operations — that run together as a single chain. Workflows are stored inside the project so they are available to every user with access to the project and can be re-executed without re-entering parameters.
•Create — add a new workflow with a user-supplied name.
•Rename — change the name of an existing workflow.
•Remove — delete a workflow from the project.
•Set current — choose which workflow is edited and executed next.
Each workflow is composed of jobs. A job wraps one g-Space procedure plus its saved parameters, or a database operation. Jobs can be added, renamed and removed inside the active workflow. Execution runs the jobs sequentially, feeding the output of one into the next when their data types line up.
Progress is reported in the Output View while the workflow runs. If any job fails, execution stops and the workflow can be resumed after the error is corrected.
1.Select the workflow to execute in the workflows wizard.
2.Confirm the parameters of every job — click a job to inspect or override its saved parameters.
3.Press Execute. The full chain runs as a single service task, with progress reported in the Output View.
•Repeatable workflows used across many wells or survey lines (for example standard petrophysical stacks).
•Team-wide protocols where the same sequence of procedures must be applied to every project.
•Pipelines chaining import, processing and export operations without intermediate user input.