ServiceDesk

 View Only
  • 1.  Send Complete Workflow Message Component

    Posted Jan 03, 2011 02:25 PM

    We are trying to use this component to reassign in a custom Workflow, however we cant find any documentation on it.

    We are passing in data type of 'ToIncidentEscalateMessage" and have created a variable to pass in with the same data type. ( tho it could be hard coded in the component too, which we have tried )

    There are 4 required fields, Assignment type, Display name, Target ID and Target Name. So far no combination has done much for us, as the ticket is reassigned back to Support I each time. ( we get the reassign notice, so it at least gets into the message bus properly and tries.. )

    Anyone know of any documentation or pointers?



  • 2.  RE: Send Complete Workflow Message Component

    Posted Jan 03, 2011 03:54 PM

    This component basically puts a message on LBME.WorkflowResponseQueue.

    It uses Task ID as the message ID.

    The service ID attribute of the message can be specified by checking Specify Service ID on.

    The payload of the message is empty unless Empty Message is checked off.

    The Response Path Name of the message can be overridden by checking Dynamically Determine Path off.

    It uses lme://localhost/LBME.WorkflowResponseQueue unless Local Server is checked off. If off, it swaps "localhost" for the server you specify.



  • 3.  RE: Send Complete Workflow Message Component

    Posted Jan 07, 2011 10:54 AM

    Right, we have the basics down as you have above but we are stuck with populating the actual assignments.

    There are 4 fields involved:   Assignment Type, Display Name, Target ID, Target Name.

    "Assignment Type" is easy, and we assume that "Display Name" really is the display name of the person or group, but the others are are confused on and we apparently don't have them right as the update doesn't take place.

    This is the same component that is being used ( with the same data type of 'ToIncidentEscalateMessage ) in the MR2 escalation Workflow, so i know its the right way to do it. ( or at least one of the right ways :) )