Workflow Soluiton

 View Only
  • 1.  Workflow not creating a ticket log in winuser console

    Posted Feb 23, 2009 04:31 AM
    Hi,

    We have the winuser console for the end-users to submit tickets but when I use the webforms that I created to submit the ticket, the ticket log is not seen in the winuser console. The ticket log for other normal submissions is seen (I mean ticket submissions using normal winuser console)

    Q1> How do I make sure that user is able to see this log in the winuser console after they submit the ticket using the webform deployed as a service catalog task?

    Now that I have been able to set the values for most of the fields in the Ticket; I still cannot fill the values for contacts and assets

    Q2> How do automatically fill the contact and asset values when the form is submitted?

    Any help is appreciated. Thank You.

    -- Mel

    Attachment(s)



  • 2.  RE: Workflow not creating a ticket log in winuser console

    Posted Feb 23, 2009 08:02 AM
    Once the 'Contact' part of Q2 is solved, the issue of Q1 will be solved.

    To get the 'Contact' to automatically assign to the ticket being created through Workflow, I use two components at the beginning of my Workflow or WebForm projects that are directly down-stream of the "Create Notification Server Credentials" component that authenticates into the Helpdesk NS server. The two components are the "GetCurrentUser" and "FindServiceDeskContact" components. Please see the attached doc that will explain how to set up these components in a Web Form project and allow the components to automatically set the Contact on a ticket. Note, the attached doc is with the assumption that the user filling out the webform is authenticated into a windows domain and the user is not selecting from a list of contacts on the form.

    You can do a similar method for the asset using either the "GetAssetsForUserComponent" or "GetAssetsForUserByIdComponent". You'd want to have one of these components downstream of the "GetCurrentUser" and "FindServiceDeskContact" components or as part of a dynamic model in a WebForm (for the user to select from a list of their assets for example). I haven't personally used the asset side in any of my projects yet but you're basically going to use one of these components to get the desired asset information into a variable for the asset and then in the "CreateTicketComponent" or "EditTicketComponent" you go to the 'Associations' tab and for the "Managed Object ID" you use a variable and map it to the ID from your asset variable.

    Someone that has already used Assets in their projects already could probably give you a better answer on that but I believe that's all there is to it. There are also some Active Directory components that a company called Incendio" has put out on the Juice for download you could use so you could pull data not from the Helpdesk server's Contact database but directly from AD. I haven't fully used those yet in my projects though.


  • 3.  RE: Workflow not creating a ticket log in winuser console

    Posted Feb 23, 2009 08:06 AM
    By the way, the attached procedure won't work when debugging. For debugging, I usually just manually set the "Contact ID" on the 'Associations' tab of the "CreateTicketComponent" to my actual Contact ID and then change it to the variable when I publish the project.


  • 4.  RE: Workflow not creating a ticket log in winuser console

    Posted Feb 23, 2009 08:12 AM
    Hey thanks 'matzebru' for the quick response again. I will try this out and let you know if it worked out. Thanks again.

    -- Mel


  • 5.  RE: Workflow not creating a ticket log in winuser console

    Posted Feb 24, 2009 02:54 AM
    Hi,

    For some reason, the solution that you suggested did not work for me. I am sure I did the exact procedure as mentioned in your document which is an excellent compilation. What do you think I am missing? I have attached the workflow screenshot beloew which is very simple workflow. Do you think I need to add any more components to actually make this thing work?

    Thanks again for your help.

    -- Mel