Bypassing notification activity in a sequencer

[splayer]

I would like to bypass notification activity in a sequencer based on certain condition. For other conditions, I would like to execute the Notification Activity. What would be the best way to go about it?

[narasimha]

Use a Nested Condition in your Job sequence.
Based on your condition, pass the output links to a Notification Activity or somethiing else

[splayer]

I would like to develop a custom or build stage to do this. Would it be a good idea? Which one would be better?

[thebird]

Why not just put the condition in the Trigger and link it appropriately to Notification Activity and the other DS activity that need to be triggered?

Again it would depend on the condition that you would want to specify - what theoptimal solution is. What is the condition that you need to trigger these based on?

[chulett]

You don't need a custom stage, or a Nested Condition typically. As noted, you should be able to do this via Triggers the vast majority of the time. Send the results off to Notification that you want and the rest simply bypass it.

If that's unclear, why not provide some specific examples so we can understand your issue?

[splayer]

I have a WaitForFile activity stage. If the file does not appear by a certain time (let's say noon), I have to notify by email using the Notification activity.

[narasimha]

Craig, always has a better method

Have two O/P links from the Wait_For_File_Activity
One to the Notification Activity, the Expression can be like -

Code: Select all

Wait_For_File_Activity_0.$ReturnValue = 0

Another having expression

Code: Select all

Wait_For_File_Activity_0.$ReturnValue = 1

Check the Return Values before implementing it.

[I_Server_Whale]

How about this?

Code: Select all

Wait_For_File   -------------------------------> Notification_Activity
       |
       |
       |
       |
       |
       |
       V
Terminal_Activity

You should probably be using 'ReturnValue' triggers.

Whale.

[chulett]

You don't need to check anything specific for this. Two simple triggers - OK (Conditional) and Otherwise will do it for you. OK will fire when the file is found and the Otherwise trigger will catch anything else, including when it doesn't show up.

[narasimha]

You don't need to check anything specific for this. Two simple triggers - OK (Conditional) and Otherwise will do it for you. OK will fire when the file is found and the Otherwise trigger will catch anything else, including when it doesn't show up.

Now its bestest!

[splayer]

Craig, where can I find the values of WaitForFileActivity? That is, under what conditions would it be Ok? Is that when the file is present?

As far as my problem, it is little bit more complicated than that. At 12 noon, I need to check whether the file is there or not using WaitForFileActivity which is looping and checking every minute. If it is not there then I send the notification email using NotificationActivity stage and then continue with the loop.

Anyway, I did another sequence job where I do an ExecCommand to check for the file's existence and then do the notification. I plan to schedule this at noon.

Anyway, a better solution from anyone would be appreciated.

[I_Server_Whale]

Exactly what I suspected !

You do not want to wait for a certain period of time to find whether the file has appeared or not.

But instead you want to check its existence exactly at 12 noon.

Am I right?

Whale.

[narasimha]

Craig, where can I find the values of WaitForFileActivity? That is, under what conditions would it be Ok? Is that when the file is present?

It can be Ok based on the condition selected by you is met i.e
"Wait for file to appear" or "Wait for file to disappear" , otherwise it is not OK
In other words
If you get a return value from Wait_For_File_Activity_0.$ReturnValue as 0 then it is OK

[chulett]

I've never seen it officially documented anywhere, this is just from my experience using it. And Narisimha is correct in that whatever your condition is you select - for a file to appear or disappear - when the condition is met you get an OK status from the stage. When the timeout limit is reached, you get a 'not OK' status.

And I wouldn't use the $ReturnValue even though it may very well work. That's just me being anal, but technically you would only get a 'Return Value' from a Routine Activity or Execute Command stage. Otherwise, it's a status that can be checked with 'normal' triggers.

[DSguru2B]

That's just me being anal, ...

O c'mon Craig. Your just being technically correct