Naming convention for links in Sequencer

laiko · Post by **laiko** » Wed Apr 22, 2009 10:57 am

Anyone knows any naming convention for links inside Sequencers??

ray.wurlod · Post by **ray.wurlod** » Wed Apr 22, 2009 2:20 pm

You can't have a link inside a Sequencer, you can only have links attached to a Sequencer. I think the word you wanted was "Sequence".

You have to invent your own naming conventions; no-one will impose any.

laiko · Post by **laiko** » Thu Apr 23, 2009 12:59 am

Thanks, Ray. Just wondering if anybody knows a good way to name them or has done so - I can't think of anything better than something like: lnk_To_<Job_name/ChildSequence name>

ray.wurlod · Post by **ray.wurlod** » Thu Apr 23, 2009 1:28 am

upstream_activity_Done (unconditional)
upstream_activity_OK
upstream_activity_Error
upstream_activity_NonFail (custom: OK or warn)
etc.

(I don't mean literal activity names, more the task that it performs.)
Outputs from a Nested Condition activity should reflect the condition.

PhilHibbs · Post by **PhilHibbs** » Wed May 13, 2009 8:49 am

laiko wrote:Anyone knows any naming convention for links inside Sequencers??

On our project I rigorously insist and enforce that all links inside Job Sequences be named in the convention DSLinknn where nn is an arbitrary number of any length.

DSXchange

Naming convention for links in Sequencer

Naming convention for links in Sequencer

Re: Naming convention for links in Sequencer