Thanks Travis. So the workaround for now would be to replace these SM Get Relationship activities with PowerShell activities when developing Runbooks? Or is there another way to access the "Affects Configuration Item" relationship on an Incident in a runbook?
From: [email protected] [mailto:[email protected]] On Behalf Of Travis Wright Sent: Thursday, May 9, 2013 3:55 PM To: [email protected] Subject: [servman] RE: Getting the Affected CI from an Incident in Orchestrator This is a known issue in the Orchestrator integration pack for Service Manager. When browsing classes it doesn't allow you to choose "abstract" classes like Work Item or Config Item. You have to choose a non-abstract class like Windows Computer. We are working on fixing this, but it is what it is for now. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Brandon Ryan Sent: Thursday, May 9, 2013 1:16 PM To: [email protected]<mailto:[email protected]> Subject: [servman] Getting the Affected CI from an Incident in Orchestrator Does anyone know of a blog post or documentation that shows how to get the Affected CI from an Incident in Orchestrator? I get the incident fine, but then can't find what settings to put in the "Get Relationship" activity to get the CI information. I know how to get the relationship using PowerShell, but the class types that show up in Orchestrator don't include WorkItem or ConfigItem so I don't think I am finding the right relationship. Thanks! Brandon Ryan Software Engineer | [email protected]<mailto:[email protected]> ClearPointe(r) | 7 Office Park Dr., Suite 200 | Little Rock, AR | www.clearpointe.com<http://www.clearpointe.com/> MANAGED IT SERVICES: Your IT. Our People. 24/7. Guaranteed.
