Workflow and ServiceDesk Community

 View Only

  • 1.  Field mapping issue on field Workflow 7.1 SP1

    Posted Nov 09, 2011 12:19 PM

    Dear All,

    Now that I have published my Workflow, it is misbehaving in different ways to in Debug! That is called testing, I suppose.

    I am getting this error:

    Application Name : PasswordResetting
    Process ID : 7732
    Date :09/11/2011 15:02:58
    Log Level :Error
    Log Category :LogicBase.ExecutionEngine
    Machine Name : ALTIRIS01
    Message :
    resulting exception from execution
    System.Exception: exception component created:  ---> LogicBase.Framework.BusinessRuleException: The critical error failed execution on component Set up the Password Reset Log : Field mapping issue on field DueDate1stLevel : at LogicBase.Core.SingleMappingDefinition.DoMappingInternal(IData startData, Object targetObject) at LogicBase.Core.SingleMappingDefinition.DoMapping(IData startData) at LogicBase.Components.Default.Mapping.SingleValueMappingComponent.Run(IData data) in c:\build\projects\WF71MR2\components\LogicBase.Components.Default\Mapping\MappingComponents.cs:line 165 at LogicBase.Core.ExecutionEngine.SinglePathProcessComponentExecutionDelegate.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)

    It is pointing to a "Set up the Password Reset record" component. It is configured like this:

    The complex variable that is on the left is the record and the variable being mapped to is the one on the right as well. All I am wanting to do is to persist the values in the record by mapping the values in the current variable to the ones that I want to keep and map in new values into the Status and End fields.

    Why is it complaining when I am trying to map the first field in the complex data type? Am I doing wrong here? What is the correct way to do this?

    Kindest regards,

    QuietLeni



  • 2.  RE: Field mapping issue on field Workflow 7.1 SP1

    Posted Nov 10, 2011 03:26 AM

    Check if you have logging level switched to Debug because on this level much more information should be logged during mappings processing. Try to analyse lines in log just between exception has been thrown.

    In case the source object was null should be logged: "mapping fieled is null".

    In case the target object was null should be logged: "target not found".



  • 3.  RE: Field mapping issue on field Workflow 7.1 SP1

    Posted Nov 10, 2011 04:52 AM

    All I got was this:

     

    Application Name : PasswordResetting
    Process ID : 5540
    Date :10/11/2011 09:50:28
    Log Level :Error
    Log Category :LogicBase.Core.Models.Workflow.WorkflowServices
    Machine Name : ALTIRIS01
    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 Set up the Password Reset Log : Field mapping issue on field DueDate1stLevel : at LogicBase.Core.SingleMappingDefinition.DoMappingInternal(IData startData, Object targetObject) at LogicBase.Core.SingleMappingDefinition.DoMapping(IData startData) at LogicBase.Components.Default.Mapping.SingleValueMappingComponent.Run(IData data) in c:\build\projects\WF71MR2\components\LogicBase.Components.Default\Mapping\MappingComponents.cs:line 165 at LogicBase.Core.ExecutionEngine.SinglePathProcessComponentExecutionDelegate.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.Models.EmbeddedDecisionModel.EmbeddedDecisionModelExecutionEngine.Run(IData data)
       at LogicBase.Core.Models.EmbeddedDecisionModel.EmbeddedDecisionModelDataType.Run(IData data)
       at LogicBase.Core.AbstractConfigurableWorkflowComponent.HandleTimeout(String taskID, String workflowID, IData data)
       at LogicBase.Core.AbstractEnsembleWorkflowComponent.HandleTimeout(String taskID, String workflowID, IData data)
       at LogicBase.Core.Models.Workflow.WorkflowServices.ProcessTimeout(String serviceId, WorkQueueItem item)
       at LogicBase.Core.Models.Workflow.WorkflowServices.ProcessTriggers(String serviceId, String[] ids)



  • 4.  RE: Field mapping issue on field Workflow 7.1 SP1
    Best Answer

    Posted Nov 14, 2011 07:08 AM

    Dear All,

    I ws doing a silly and unnecessary thing. I was taking what was already in the AddedPasswordReset and mapping it over to itself, but placing more data into the record.

    When I took the unnecessary mappings out (i.e. the ones going from itself to itself) the error went away and it worked.

    Just thought that you might like to know.

    Regards,

     

    QuietLeni