- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-22-2016 06:49 AM
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?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2016 08:47 AM
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2016 08:10 AM
No it shouldn't. SN had to have known people would change their SC_Task states, and why would activity.result show such flexibility for one activity type yet demand a validated list of strings for another. There's something I"m missing here...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2016 08:15 AM
I agree. I didn't think so either.....
'There's something I"m missing here...'
yeah! me too! It's like I am missing something rather obvious and I am not sure what it is.
Now did you have to go to the Create Task activity and add a condition default record in the related list of the create Task activity? I did not do that. I was only making my changes within the workflow catalog task activity I am processing. I don't think adding a default condition to the activity condition was required as I only want this condition during this workflow processing and not as a default any time a catalog task activity is defined for new workflow.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2016 08:22 AM
Here's what my condition looks like on the back end. I suppose its possible you could have checked any of those three boxes but I'm betting not.
And you're right about adding the conditions on the instance of the workflow activity, not the activity definition (that would be muchos muchos tres bad).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2016 08:29 AM
Thanks for the pic.
What field in your task is this value for? Is it for the state field? approval field? I'm assuming your values are against the state field also. Just trying to understand what is triggering the activity.result to be set so that the condition for activity.result can be evaluated by the activity definition.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2016 08:42 AM
Good question, and yes, its the state field. Task.state specifically.