Document Properties
Kbid25S917
Last Modified04-Feb-2020
Added to KB18-Aug-2014
Public AccessEveryone
StatusOnline
Doc TypeGuidelines, Concepts & Cookbooks
Product
  • ICM 7.6
  • ICM 7.7
  • ICM 7.8
  • ICM 7.9
  • ICM 7.10

Guide - Pipeline Layout

Table of Contents

Product Version

6.0

Product To Version

 

Status

final

Introduction

This document describes conventions for the layout of pipelines for applications based on Intershop 7.

Guidelines

  • The pipeline execution should flow downwards. This means that transitions in general should not go up (loops are an exception).

  • Prefer straight transitions and right angled transitions to diagonal ones.

  • An exception can be made if a call node has more than one exit. One transition will go straight down and the others will start diagonally (down and right) and then go down.

  • The transition that follows the normal execution exit of a pipeline node (pipelet next, decision node “yes”) should go straight down and the ones that follow the error exit should go to the right (or diagonally down and right in case of a call node).

  • The directions of the normal and error exit transitions can be reversed if it would produce a cleaner pipeline (for example if when using the previous rules some transitions intersect)

  • Do not overlap transitions

  • For loop nodes the last transition of the loop goes left and up.

  • If a branched pipeline is combined again, the transition can go left.

  • A transition may also go left if two different branches have to be merged. Merging different branches should be avoided.
  • Create additional join nodes when required by the above rules.

These rules should not be broken, unless it will improve the clarity and readability of the pipeline.

Disclaimer

The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.

Customer Support
Knowledge Base
Product Resources
Support Tickets