Workflow and ServiceDesk Community

Hello everyone, has anyone run across and repaired something like this?  I'm trying to add a Run Ruleset component to the SD.IncidentManagementSimple.Classification project, so that when the evaluations determine that the owner has been changed and saved, the corresponding ruleset runs.

What seems like a fine idea is quickly quashed with this error message:

Any ideas on this one?

Thanks!!

Check the ServiceID of the project I'm sure it already has Servicesdesk or IncidentManagement Does the run ruleset have the option to choose which ruleset and the list match what you have in SD Process Automation? Compare the libraries that you have in this with SD.IncidentManagementSimple There's a couple of Automation Libraries that you may need to add

Yeah, Service ID defaults as SERVICEDESK-CLASSIFICATION or some such, i tried changing it to several things, including INCIDENT-MGMT and INCIDENT-MGMT(randomstuff).  Checked the library, it's referencing the shared bin, so in theory it should be using the same .dll that the sd.incidentmanagementsimple is using.  The component doesn't even show the field for rule selection so long as it's busted like that.

To add a ruleset component to a project requires that the project ServiceID exactly matches the ServiceID coded for the ruleset. Thus the predefined rulesets for Incident Management will only work with the IncidentManagementSimple project. 

Please be very VERY careful with changing Service IDs in ways that result in duplicates. Message queues are based on Service IDs and having duplicate Service IDs is a sure way into a very serious mess.

You might get away with it with Webforms or Decisions to some degree but this is definitely not advised and the moment you have two or more Workflow projects or Web Applications running with the same Service ID that mess will not be easily fixable. At least not without losing existing open processes or starting with a new database :)

Is there a legitimate manner by which I could capture an ownership change on "edit incident" and actually run the "ownership changed" ruleset then?  From the sound of it, there isn't a supported way to do so.

I would agree that you should be very careful duplicating the Service ID. However... I do have a decision only project running with the INCIDENT-MGMT ID to do ownership and queue changes that does kick off that ruleset. It's been working fine for me for over a year. Obviously don't test that in production if you go that route and note that just because it works for me, there is no guarantee it'll work for you.

I was going to test that today - creating a web service caller to send over path and ticket info to a custom-made decision project with the incident-mgmt service id.  from what i've heard and read (thanks to liaison Alex Hedley for much information), the service id issues lie within task calls and tables.  well, if there are no tasks involved (decision only, simple ruleset calls and exit), then i don't see where a collision could occur.

warnings and cautions and risks of implosion and catastrophe duly noted, of course.

although if anything goes wrong, i'm going to tell everyone that michael george told me it was 100% safe and that his seal of guarantee is on the solution.

That's obviously not what I said. What I said was it works great for me, so if it doesn't work for you, you must have implemented it wrong. I do agree, though; the issue will be with tasks, so no tasks should equal success.

I think the issue is that Tasks already created from IM Simple will look for a project with ServiceID of "INC-MG" and if your new project does then it might invoke that instead of IM and therefore stop that task from working.