- 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-22-2016 06:53 AM
try with quotes
activity.result='15'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-22-2016 06:57 AM
Tried that already... The workflow has not moved. It is still stuck on the catalog task even though my status value in my catalog task record has changed to 'Failed' (15).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-22-2016 07:00 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2016 06:44 AM
So lets get the more obvious stuff out of the way first. Sorry if this remedial:
1) "15" actually exists as a state on your Catalog Task table, right?
2) State of 15 will cause the Catalog Task to become active=false, right?
2 is just as critical as 1. Activity.result is what happens "at the end", but the only way sc_task knows its ended is by switching to active=false.