constraint to " OTHERWISE" for a otherwise link in

[cetzhbo]

Hello Gurus,

I can set constraint to " OTHERWISE" for a otherwise link in transformer stage . what does that constraint mean?

thanks very much!

[chulett]

Catch all. It 'fires' only if none of the other triggers fire.

[cetzhbo]

thanks, but if I don't set this constraint for otherwise link, I think it also catch all the rows when there is not other constraint fired. is that right ? if that is it, why should we need use this setting?

[ArndW]

No, only rows that don't go down any other links will go down an "Otherwise".

[chulett]

Sorry, but for some silly reason I thought you meant an 'Otherwise' trigger in a Sequence job and were using the word 'constraint' in a more generic manner. Let's start over.

There is no such thing as an 'OTHERWISE' constraint. An empty constraint means the link is not constrained and accepts all rows - unless it is marked as a Reject link. A constraint expression allows records to pass down the link only when it evaluates to 'true'. Reject links are the only ones that behave in an 'otherwise' fashion and that based only on the links before it in the link order.

[chulett]

No, only rows that don't go down any other links will go down an "Otherwise".

Is this something new in 8.x or PX? An 'otherwise' constraint?

[cetzhbo]

Hi chulett,

that is true, please read following words from v8: ( this is definitly not "Otherwise/Log field" )

A constraint otherwise link can be defined by:

Set the constraint to OTHERWISE. This will be set whenever a row is rejected on a link because the row fails to match a constraint. OTHERWISE is cleared by any output link that accepts the row.

thanks very much!

[ArndW]

Nothing new, in server transform stages it was labelled "reject" link.

And it functions just as Craig and I have stated - if a row doesn't get output to any other link(s) then it goes to the otherwise link.

[chulett]

Great, thanks for the clarification. Does it still function as the Server 'reject' does where it is positional, meaning it fires if the links above it haven't? Or is it a true 'otherwise' constraint?

[ArndW]

I haven't checked at V8 or in PX. Could be a "gotcha"

[cetzhbo]

thanks friends,

but this otherwise link is not a reject link. and following is as abstract for v8 developer guide, hopeful you can make it clear:

A constraint otherwise link can be defined by: v Clicking on the Otherwise/Log field so a tick appears and leaving the Constraint fields blank. This will catch any rows that have failed to meet constraints on all the previous output links.

v Set the constraint to OTHERWISE. This will be set whenever a row is rejected on a link because the row fails to match a constraint. OTHERWISE is cleared by any output link that accepts the row.

v The otherwise link must occur after the output links in link order so it will catch rows that have failed to meet the constraints of all the output links. If it is not last rows may be sent down the otherwise link which satisfy a constraint on a later link and is sent down that link as well.

v Clicking on the Otherwise/Log field so a tick appears and defining a Constraint. This will result in the number of rows written

[cetzhbo]

thanks friends,

but this otherwise link is not a reject link. and following is as abstract for v8 developer guide, hopeful you can make it clear:

A constraint otherwise link can be defined by: v Clicking on the Otherwise/Log field so a tick appears and leaving the Constraint fields blank. This will catch any rows that have failed to meet constraints on all the previous output links.

v Set the constraint to OTHERWISE. This will be set whenever a row is rejected on a link because the row fails to match a constraint. OTHERWISE is cleared by any output link that accepts the row.

v The otherwise link must occur after the output links in link order so it will catch rows that have failed to meet the constraints of all the output links. If it is not last rows may be sent down the otherwise link which satisfy a constraint on a later link and is sent down that link as well.

v Clicking on the Otherwise/Log field so a tick appears and defining a Constraint. This will result in the number of rows written

[cetzhbo]

thanks friends,

but this otherwise link is not a reject link. and following is as abstract for v8 developer guide, hopeful you can make it clear:

A constraint otherwise link can be defined by: v Clicking on the Otherwise/Log field so a tick appears and leaving the Constraint fields blank. This will catch any rows that have failed to meet constraints on all the previous output links.

v Set the constraint to OTHERWISE. This will be set whenever a row is rejected on a link because the row fails to match a constraint. OTHERWISE is cleared by any output link that accepts the row.

v The otherwise link must occur after the output links in link order so it will catch rows that have failed to meet the constraints of all the output links. If it is not last rows may be sent down the otherwise link which satisfy a constraint on a later link and is sent down that link as well.

v Clicking on the Otherwise/Log field so a tick appears and defining a Constraint. This will result in the number of rows written

[ArndW]

If you don't believe the response you've gotten it only takes about 2 minutes to write a dummy job with a row generator, a transform stage and several peek stages. Please disprove what has been said so far about using the OTHERWISE functionality.

[chulett]

In other words, with the exception of (apparently) being able to type the word 'OTHERWISE' in the constraint, it works exactly the same as a Server reject link. Positional, logging, the whole nine yeards.