Workflow Soluiton

 View Only
  • 1.  Statically Assign Category

    Posted Jan 25, 2012 11:33 AM

    I am working on a long, complex workflow and I have everything working exaclty as I want it except I can't seem to figure out how to statically set an incident category (calssification). I know how to put the selector onto a form but this particular form will always have the same category (actually more than one depending on a specific selection on the form). Can anyone point me to the method for statically assigning a category? I assume I need to do some form of mapping on an incident data type but I can't seem to get the right combinations together to allow me to set the category correctly. Any information would be appreciated.

    I have posted this over in the SD forum as well but since it is a Workflow question I thought I would double-post.



  • 2.  RE: Statically Assign Category

    Posted Jan 25, 2012 12:11 PM

    If you're in a Single Value Mapping component, and you have the mapper up, look at the right side of the mapper at your "target" object. Right-click on the attribute you want to statically map to and select Create ConstantMappingAssignment. In this dialog you can set the value to whatever you wish and it will remain this way (well, it'll change if you write to it again further down the flow)

    Is this what you mean when you say "statically map"?



  • 3.  RE: Statically Assign Category

    Posted Jan 25, 2012 12:18 PM

    I can do that, I guess what I am looking for is more which target type the incident is that will allow me actually do the static mapping. I may not be making a lot of sense here.



  • 4.  RE: Statically Assign Category

    Posted Jan 25, 2012 12:27 PM

    In Service Desk, the incident "type" is ServiceDeskIncident, found in SD.Data... this is derived from BaseServiceDeskIncident in SD.DataTypesCore.



  • 5.  RE: Statically Assign Category

    Posted Jan 25, 2012 12:34 PM

    I thikn I've found it...Altiris.ServiceDesk.Data.ServiceDeskIncident. It shows me the correct mappings. So now I can statically map the categories and then merge that with the Actual Incident variable so that when I use the submit incident advanced component the category will be (should be set)!

     

    I will test it and see if that does what I want it to!

     



  • 6.  RE: Statically Assign Category

    Posted Jan 25, 2012 07:09 PM

    OK, still not getting it right. Let me try this again and give a thought.

    I am taking a bunch of different fields and combining them into the Incident Title, Description, Location, etc. I plan on using the Submit Incident Advanced component. I need to determine the actuall full category based on variables from the form so if "A = Fun" then the category needs to be Add-Install \ Software \ Office, if "A = Not Fun" then the category would be Delete-Remove \ Software \ Firefox.

    I can do the logic but I still can't seem to get the category tree populated. I don't kow if the issue is setting up the array and using that variable correctly or if there's something else going on. One thought I have is to the Submit Incident Advanced component and setting the ClassicClassificationCategory to a dynamic model and use the logic to set the category from there but again, I am not getting the array right somehow.



  • 7.  RE: Statically Assign Category

    Posted Jan 27, 2012 12:17 PM
      |   view attached

    I think I am understanding what you're saying. Sounds like you will need a decision table to route the "friendly" name to the actual category description. Once you import the Decision.dll then you should be able to find the component.

     

    Once imported and you get to the main section, you'll want to use a Matches rule across the X axis and a True/False rule across the Y axis. Attached is a screenshot. Hopefully this is what you're looking for.



  • 8.  RE: Statically Assign Category

    Posted Jan 27, 2012 01:41 PM

    Not quite but that will come in handy! 

    Here's what I have: 

    A form which takes some inputs to be submitted to the SubmitAdvancedIncident component. In that I am not asking for the category, I want to simply map the category inside of the workflow so that the category is set in the incident automatically (by me). I think I have something working in theory. I have a SingleValueMapping component with the target type of Altiris.ServiceDesk.Data.ServiceDeskIncident. Inside there I can set Classification_Category_01, Classification_Category_02, etc. which sould be mapping the category tree for the incident. I am assigning that to the Incident variable. Other items I set in this mapping such as IncidentType are being honored but the classification is not. I can submit the incident and the look at the ticket and everythign is populated correctly except for this category. I look in the database and those fields are not populated so I am not sure where the issue might be. It could be the component that isn't working right or it could be that I am doing something wrong somewhere else.

    I have verified that there is data inside that Incident data type for the classification further into the workflow just before the submission so I don't know where it might be going wrong.



  • 9.  RE: Statically Assign Category
    Best Answer

    Posted Jan 27, 2012 10:11 PM

    I have it working now. The SubmitIncidentAdvanced component uses the ClassicCategory field to run in the categories for an incident. I needed to extract the mappings that I had done from the Incident data type for Classification_Category_01, Classification_Category_02, etc. into a simple array and assign that array as the value of the ClassicCategory.

    Thanks for the help.