How is the activity conditions value set for catalog task activities?

sherard · ‎01-22-2016

Need assistance with workflow activity catalog tasks. I need the workflow activity catalog task to accept additional conditions. I can add new conditions to the activity, but it is not accepting it and the catalog task activity just sits there. Am I missing something?

So I have a new state value of 'Failed' with db value as 15 as part of my Catalog Task status field. I created a condition in my workflow catalog task activity to look at activity.result == 15. So, when I run my workflow, update the created catalog task state value to 'Failed' (15), I would expect the catalog task activity to accept the new condition. am i doing this wrong?

Uncle Rob · ‎01-25-2016

Something about this bugs me. If you set the condition so that the state value is 4 and it works, that means there's a business rule that's touching hte parent workflow again.

Here's something to try. Build a temporary business rule on sc_task table. Copy the contents of "SNC - Run parent workflows" business rule. Make your conditions current.active.changesTo(false). That rule will essentially tell the parent workflow to check if it needs to proceed when you set an SC_Task to inactive.

Also... that got me thinking. This is a Catalog Task activity right? And that new state is a state on the Catalog Task table?

View solution in original post

sherard · ‎01-25-2016

I thought the trigger of setting the activity.result was that the task record had to be 'inactive'. That is why I used the close_states attribute on the sc_task to allow my state value of 15 to also make my task record inactive along with the OOB (close states). But it seems like it is more than that that assumes the workflow activity is 'complete' to set the activity.result. This is my main question for this entire thread.

If I can figure out what triggers the setting of activity.result or the completion of the workflow activity, then I think I will be able to get this working.

Right now, from what I can tell, and this is all OOB stuff, is that the catalog task workflow activity seems to only 'complete' or move on or set the activity.result value only when the states of 3,4,7 are used. and I am not sure how/where to change that or add to that short list.

Uncle Rob · ‎01-25-2016

Right... 3,4,7 are the states used by the "SNC - Run parent workflows" rule. However on my use case the tables in the workflow are custom, and don't match the "3/4/7" patter in the task business rule... but the workflows run anyway with those activities.

May save yourself some time with a phone call to SN Support.

Uncle Rob · ‎01-25-2016

Something about this bugs me. If you set the condition so that the state value is 4 and it works, that means there's a business rule that's touching hte parent workflow again.

Here's something to try. Build a temporary business rule on sc_task table. Copy the contents of "SNC - Run parent workflows" business rule. Make your conditions current.active.changesTo(false). That rule will essentially tell the parent workflow to check if it needs to proceed when you set an SC_Task to inactive.

Also... that got me thinking. This is a Catalog Task activity right? And that new state is a state on the Catalog Task table?

sherard · ‎01-25-2016

I think you are on to something. That business rule "SNC - Run parent workflows" seems to be what is making this process the way it is.

I created a new business rule for sc_task and defined the rule as you stated. And it works as it recognizes to process the workflow for any inactive and sets the activity.results to my state value.

I think that was the culprit and now I understand what the heck is going on!

Thanks so much for your assistance. I should be able to get it from here. I'll mark this as answered.

Uncle Rob · ‎01-25-2016

Glad I was able to help. What bugs the bejeepers out of me is that this works fine on my custom task types without the use of the SNC Run Parent Workflow rule