Workflow Soluiton

I am having an issue with my decision table that I can't seem to get past.

I have verified the matchesrule's a few times now, and created a breakpoint to make sure the variables I am matching against are getting data.  It just doesn't want to match.

What values aren't matching, the Windows version names?  What does the Matches Rule configuration look like?

Both of them hang and time out, then the workflow errors.

Here is one of them:

What do the logs say when the workflow errors?

...\Symantec\Workflow\Tools\Symantec.Explorer.exe - Log Viewer

Application Name : AIRv4
Process ID : 3588
Date :12/18/2014 12:19:10 PM
Log Level :Error
Log Category :LogicBase.Core.Models.Workflow.WorkflowServices
Machine Name : TXUSPIPLT868
Message : 
System.Exception: Execution Engine Exception  ---> System.Exception: Execution Exception ---> System.Exception: exception component created:  ---> LogicBase.Framework.BusinessRuleException: The critical error failed execution on component Decision Table : Object reference not set to an instance of an object. :    at LogicBase.Components.DecisionTableComponent.Run(IData data)
   at LogicBase.Core.ExecutionEngine.MultiPathProcessComponentExecutionDelegate.Execute(IData data, IOrchestrationComponent comp, String& outputPath, IExecutionEngine engine, TLExecutionContext context)
   at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunComponent(TLExecutionContext context, IData data, IOrchestrationComponent comp)
   --- End of inner exception stack trace ---
   at LogicBase.Core.ExecutionEngine.ExceptionComponentDelegate.Execute(IData data, IOrchestrationComponent comp, String& outputPath, IExecutionEngine engine, TLExecutionContext context)
   --- End of inner exception stack trace ---
   at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunEngine(List`1 executionQueue)
   --- End of inner exception stack trace ---
   at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunEngine(List`1 executionQueue)
   at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.ExecuteComponent(IData data, IOrchestrationComponent component)
   at LogicBase.Core.ExecutionEngine.ExecutionEngineExtensions.FollowLinks(IExecutionEngine engine, TLExecutionContext context, IData data, IOrchestrationComponent component, IComponentLink[] links)
   at LogicBase.Core.Models.Workflow.WorkflowServices.ReturnFromWorkflow(Object oparms)

You may want to set a breakpoint on that decision table in the debugger and make sure that the "OSChosen" variable exists at runtime.  Send me a PM if you want to have a quick webex look at it and get it knocked out.

There seems to be a bug with that component in my version of Workflow - 7.5.3001.64.  I'll attempt to confirm.

Great, good to know I was setting it up correctly.

Hey Africo, is there a ticket number that I can follow up on or have my rep possibly escalate?

There isn't a ticket; I sent a note through Connect to one of the Symantec guys who works with workflow.

hi jwurm - a bug ticket has been submitted internally (Symc team).  i'll keep you apprised of any new info as it is made available to me.

This issue has been fixed and is available from Symantec Technical Support. You will need to request the latest WF rollup build. 

For those customers running Workflow builds 7.5.6+ the latest build is 7.5.6183.15. For customers running version 7.5.3+ you will want build 7.5.3001.74.

Thanks for your help with this TGiles!