I did the integration on version 8.1 using the plugin (for outgoing) and API (incoming) as LJ outlined in his email. So far, no issues.
Setting up the plugin and API takes a couple of hours and the Slack integration should be another hour (customizing the Support Group form and adding a couple filters on HPD:Help Desk/ WOI:Work Order etc..). Thanks, Mahesh On Fri, May 12, 2017 at 8:00 AM, LJ LongWing <[email protected]> wrote: > ** > Ok, being you are on 8.1, you don't have access to Remedy through Restful > services OOTB...so, for the ability for Slack to publish to Remedy, I > recommend this application > > https://communities.bmc.com/docs/DOC-29073 > > Then, regardless of what version of Remedy you are running, there is no > OOTB way to CONSUME restful services in Remedy, thus my plugin > > http://remedylegacy.com/tools/restful-api-plugin/ > > The first tool is stood up in a Tomcat server and is used to access Remedy > through Restful to both pull and push data from/to Remedy. The second is > an ARDBC plugin that allows you to access restful services through > workflow, pushing/pulling information from/to the remote service. > > Between these two, you should be able to configure both services to be > able to read/write information creating a fully functional integration. > > The first tool is provided free of charge by a German company, the plugin > is provided by me....I'll do my best to support you with any issues you > encounter, but I don't anticipate any issues :) > > On Fri, May 12, 2017 at 5:13 AM, Arner, Todd <[email protected]> wrote: > >> ** >> >> Hi LJ, >> >> We are looking to have Remedy initiate the push to Slack when an >> assignment is made to a specific team and ultimately to allow Slack to send >> info back to Remedy such as assignee and work info. From Mahesh’s post it >> sounds like Rest is supported. Can you point me in the direction where I >> can find more info on your RESTful plug-in. >> >> >> >> Thanks, >> >> Todd >> >> >> >> *From:* Action Request System discussion list(ARSList) [mailto: >> [email protected]] *On Behalf Of *LJ LongWing >> *Sent:* Thursday, May 11, 2017 10:15 AM >> *To:* [email protected] >> *Subject:* Re: BMC Remedy and Slack Integration >> >> >> >> ** >> >> When you say 'send send information to Slack', do you mean you want >> Remedy to initiate the call to slack and push the information, or are you >> (as I suspect) talking about Slack being able to pull information from >> Remedy, and Slack's ability to push information INTO Remedy..... >> >> >> >> What sort of integration technologies does slack support...if you tell me >> Rest is one of them, then I think you are in luck :) >> >> >> >> On Thu, May 11, 2017 at 8:57 AM, Arner, Todd <[email protected]> wrote: >> >> ** >> >> Hi LJ, >> >> Thanks for the response. Slack is a team messaging tool. What we want >> to do is both send incident information to Slack and then have slack be >> able to send information back to Remedy. Do that help? I also should >> mention we are currently running version 8.1 of Remedy. >> >> >> >> Thanks, >> >> Todd >> >> >> >> *From:* Action Request System discussion list(ARSList) [mailto: >> [email protected]] *On Behalf Of *LJ LongWing >> *Sent:* Thursday, May 11, 2017 9:45 AM >> *To:* [email protected] >> *Subject:* Re: BMC Remedy and Slack Integration >> >> >> >> ** >> >> Todd, >> >> For those of us (myself included) that don't know what Slack is, or what >> it does......what sort of integration are you looking for? Are you looking >> for slack to be able to pull information out of Remedy, or push information >> into it? Are you looking for Remedy to be able to push/pull information >> from Slack? >> >> >> >> I can think of several different technologies and tools that will work to >> do both....some through REST, some through SOAP, others through custom Java >> capabilities....but I would need more information from you regarding WHAT >> you would want the integration to accomplish... >> >> >> ------------------------------ >> >> The information contained in this communication may be confidential, is >> intended only for the use of the recipient(s) named above, and may be >> protected under state or federal law. If the reader of this message is not >> the intended recipient, you are hereby notified that any dissemination, >> distribution, or copying of this communication, or any of its contents, is >> strictly prohibited. If you have received this communication in error, >> please forward the communication to [email protected] immediately and >> destroy or delete the original message and any copy of it from your >> computer system. If you have any questions concerning this message, please >> contact the sender. >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> >> >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
