META

Pipeline editor

The pipeline panel is accessible only to Administrator and Project administrator users. This is where the project pipeline can be created and edited.

More details about the pipeline.

Overview

The pipeline editor has three main areas: the toolbar on top contains a few useful menus and tools, the nodal view is where steps and pipes are connected, and the dock shows the editors (on the right side of the nocal view by default).

All docked panels can be undocked (as shown on the picture below) or docked on the other side of the nodal view, by dragging their title bar at the top of the panel.

Toolbar

On its left side, the toolbar displays a few menus.

On its right side, the toolbar has a few settings available.

Node view

In the node view, you can move around all the nodes (steps) by just clicking and dragging them. To select multiple nodes, just click on the background and drag the mouse to use a box selection.

You can select both nodes (steps) and connections (pipes); when a node or a pipe is selected, its corresponding editor is shown in the right dock area to let you edit its details.

To manipulate the view, use the following shortcuts:

When opening a project from the first time, the nodes may be stacked all together, and you’ll have to sort the spaghettis. To do this quickly, start by using the automatic layout! Select Layout ▸ Layout all steps or use the [Shift + L] shortcut.

Pipeline edition

To create and edit your pipeline, you just have to follow these simple steps:

Read the project step settings documentation for details about the settings in the step editor. You can also edit the applications (and their file types) assigned to the steps with the edit button.

In the pipe editor, you can check the steps from and to which the connections goes.

The Files list contains the file types this pipe can accept.

This list is what is passed to the Ramses Add-Ons when they’re exporting or importing items to and from the connected steps to let them know which kind of data and files they need to use.

More details about the pipeline.


  1. The data is not actually deleted from the server nor the local data, but just flagged as removed. A server administrator can still restore the data at any time, but there is no way (yet) to do that from the user interface of the application.