Remedy 8.1 and MAPI support
Good morning, We're looking to upgrade out version of Microsoft Office internally, as well as Exchange, and there is being a lot of pressure to get our Remedy server upgraded from using Outlook 2007 for MAPI inbound email. I've tried looking all over BMC's site, their compatibility matrix doesn't list any email clients that it would be compatible with, the release notes reference MAPI but not what version of Outlook is supported, and even a Google search hasn't returned anything useful as far as I can see. Does anyone know where BMC documents what versions of Outlook are compatible with ARS 8.1? Also, this is something I should probably ask for the 9.0 beta program but will they ever find a better way to do inbound email than putting Outlook on my application server? Our Exchange system seems to go down all the time in such a way that Remedy can't reconnect easily (one of the drivers for wanting to upgrade) so I'd like to look at other options. We use SMTP for outgoing email and I can't recall the last time it had a problem. Thanks, Shawn Pierson Remedy Developer | Energy Transfer Private and confidential as detailed here: http://www.energytransfer.com/mail_disclaimer.aspx . If you cannot access the link, please e-mail sender. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Remedy 8.1 and MAPI support
Shawn, I know this does not answer your question but you should also find out what version of Exchange you are using. We are using Exchange 2013 and something to keep in mind is there is a newer MAPI protocol and a legacy protocol and the 2013 version of Exchange only supports the new version while the Remedy MAPI protocol uses the old version. This led us to setting up our own hMail server on our Mid Tier and having our Exchange people forward mail over to it and then connecting via POP to pull in mail. Levi Lippincott / Remedy Administrator +1 402 561 7014 office +1 402 321 5421 mobile levi.lippinc...@interpublic.commailto:levi.lippinc...@interpublic.com Interpublic Group 6825 Pine Street, Omaha, NE 68106 Talent is a Gift; But Character is a Choice. -Matt Grotewold- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W Sent: Monday, February 02, 2015 9:17 AM To: arslist@ARSLIST.ORG Subject: Re: Remedy 8.1 and MAPI support ** You could use the standards of POP3 or IMAP for inbound email This is one of the advantages I have being on Linux.. MAPI is a MS Windows only protocol so I don't have to deal with it. Fred From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Pierson, Shawn Sent: Monday, February 02, 2015 9:10 AM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Remedy 8.1 and MAPI support ** Good morning, We're looking to upgrade out version of Microsoft Office internally, as well as Exchange, and there is being a lot of pressure to get our Remedy server upgraded from using Outlook 2007 for MAPI inbound email. I've tried looking all over BMC's site, their compatibility matrix doesn't list any email clients that it would be compatible with, the release notes reference MAPI but not what version of Outlook is supported, and even a Google search hasn't returned anything useful as far as I can see. Does anyone know where BMC documents what versions of Outlook are compatible with ARS 8.1? Also, this is something I should probably ask for the 9.0 beta program but will they ever find a better way to do inbound email than putting Outlook on my application server? Our Exchange system seems to go down all the time in such a way that Remedy can't reconnect easily (one of the drivers for wanting to upgrade) so I'd like to look at other options. We use SMTP for outgoing email and I can't recall the last time it had a problem. Thanks, Shawn Pierson Remedy Developer | Energy Transfer _ARSlist: Where the Answers Are and have been for 20 years_ This message contains information which may be confidential and privileged. Unless you are the intended recipient (or authorized to receive this message for the intended recipient), you may not use, copy, disseminate or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail, and delete the message. Thank you very much. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Remedy 8.1 and MAPI support
You could use the standards of POP3 or IMAP for inbound email This is one of the advantages I have being on Linux.. MAPI is a MS Windows only protocol so I don't have to deal with it. Fred From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Pierson, Shawn Sent: Monday, February 02, 2015 9:10 AM To: arslist@ARSLIST.ORG Subject: Remedy 8.1 and MAPI support ** Good morning, We're looking to upgrade out version of Microsoft Office internally, as well as Exchange, and there is being a lot of pressure to get our Remedy server upgraded from using Outlook 2007 for MAPI inbound email. I've tried looking all over BMC's site, their compatibility matrix doesn't list any email clients that it would be compatible with, the release notes reference MAPI but not what version of Outlook is supported, and even a Google search hasn't returned anything useful as far as I can see. Does anyone know where BMC documents what versions of Outlook are compatible with ARS 8.1? Also, this is something I should probably ask for the 9.0 beta program but will they ever find a better way to do inbound email than putting Outlook on my application server? Our Exchange system seems to go down all the time in such a way that Remedy can't reconnect easily (one of the drivers for wanting to upgrade) so I'd like to look at other options. We use SMTP for outgoing email and I can't recall the last time it had a problem. Thanks, Shawn Pierson Remedy Developer | Energy Transfer ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Remedy 8.1 and MAPI support
You and Frederick bring up a good point, and actually I've been investigating and we're now allowed to use POP and IMAP against our mail server where in the past it was forbidden so I have some new things to try out in development. Thanks, Shawn Pierson Remedy Developer | Energy Transfer From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Lippincott, Levi (OMA-GIS) Sent: Monday, February 02, 2015 9:27 AM To: arslist@ARSLIST.ORG Subject: Re: Remedy 8.1 and MAPI support ** Shawn, I know this does not answer your question but you should also find out what version of Exchange you are using. We are using Exchange 2013 and something to keep in mind is there is a newer MAPI protocol and a legacy protocol and the 2013 version of Exchange only supports the new version while the Remedy MAPI protocol uses the old version. This led us to setting up our own hMail server on our Mid Tier and having our Exchange people forward mail over to it and then connecting via POP to pull in mail. Levi Lippincott / Remedy Administrator +1 402 561 7014 office +1 402 321 5421 mobile levi.lippinc...@interpublic.commailto:levi.lippinc...@interpublic.com Interpublic Group 6825 Pine Street, Omaha, NE 68106 Talent is a Gift; But Character is a Choice. -Matt Grotewold- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W Sent: Monday, February 02, 2015 9:17 AM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Re: Remedy 8.1 and MAPI support ** You could use the standards of POP3 or IMAP for inbound email This is one of the advantages I have being on Linux.. MAPI is a MS Windows only protocol so I don't have to deal with it. Fred From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Pierson, Shawn Sent: Monday, February 02, 2015 9:10 AM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Remedy 8.1 and MAPI support ** Good morning, We're looking to upgrade out version of Microsoft Office internally, as well as Exchange, and there is being a lot of pressure to get our Remedy server upgraded from using Outlook 2007 for MAPI inbound email. I've tried looking all over BMC's site, their compatibility matrix doesn't list any email clients that it would be compatible with, the release notes reference MAPI but not what version of Outlook is supported, and even a Google search hasn't returned anything useful as far as I can see. Does anyone know where BMC documents what versions of Outlook are compatible with ARS 8.1? Also, this is something I should probably ask for the 9.0 beta program but will they ever find a better way to do inbound email than putting Outlook on my application server? Our Exchange system seems to go down all the time in such a way that Remedy can't reconnect easily (one of the drivers for wanting to upgrade) so I'd like to look at other options. We use SMTP for outgoing email and I can't recall the last time it had a problem. Thanks, Shawn Pierson Remedy Developer | Energy Transfer _ARSlist: Where the Answers Are and have been for 20 years_ This message contains information which may be confidential and privileged. Unless you are the intended recipient (or authorized to receive this message for the intended recipient), you may not use, copy, disseminate or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail, and delete the message. Thank you very much. _ARSlist: Where the Answers Are and have been for 20 years_ Private and confidential as detailed here: http://www.energytransfer.com/mail_disclaimer.aspx . If you cannot access the link, please e-mail sender. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Engage 2015 Call for Papers
Is there a solution for printing from the web client yet? That might be a good topic to bring up especially for those of us who are trying to justify getting away from the User Tool. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of David Charters Sent: Friday, January 30, 2015 9:30 PM To: arslist@ARSLIST.ORG Subject: Re: Engage 2015 Call for Papers ** I think making it configurable to fit the clients module is best. I just might have my team code this and release a beta on it. Would you guys be interested in testing it? Sent from Samsung tablet. Original message From: Grassi, Christopher cgra...@columnit.commailto:cgra...@columnit.com Date: 01/30/2015 17:23 (GMT-05:00) To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Re: Engage 2015 Call for Papers ** +1 to Jon Chris Grassi +44 750658 3977 Sent from my iPhone On 30 Jan 2015, at 02:14, John Sundberg john.sundb...@kineticdata.commailto:john.sundb...@kineticdata.com wrote: ** How about building a Kanban for managing (your) tickets in a state. You could make it very generic… Config: What table. What query. What field is state. What field(s) represent the description. -John On Thu, Jan 29, 2015 at 3:17 PM, LJ LongWing lj.longw...@gmail.commailto:lj.longw...@gmail.com wrote: ** heheheheh, I'm not re-creating the user tool folks.:) On Thu, Jan 29, 2015 at 1:48 PM, Andrew Hicox and...@hicox.commailto:and...@hicox.com wrote: ** An aruser client ... that works as an app on iOS and Android :-) Actually, it'd be kinda crazy if bmc wasn't working on something like that already (I hope) On Jan 29, 2015 2:41 PM, Sanford, Claire claire.sanf...@memorialhermann.orgmailto:claire.sanf...@memorialhermann.org wrote: ** LJ – Make us a new user tool!! hiding Claire From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing Sent: Thursday, January 29, 2015 2:18 PM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Engage 2015 Call for Papers ** Hello ARSList, I have a question for you. Some of you know me personally, others just through the list. My passions lie in the extending of Remedy through API programmingI'm looking for a topic for this years Engage and I wanted to take some suggestions from users to see what topics I might be able to develop and present. The call for papers just came out today https://communities.bmc.com/community/engage/blog/2015/01/29/bmc-engage-2015--call-for-papers-window-now-open and I would like to submit a topic this year that is other than my own designthoughts? _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_ -- John Sundberg Kinetic Data, Inc. Your business. Your process. 651-556-0930 I john.sundb...@kineticdata.commailto:john.sundb...@kineticdata.com www.kineticdata.comhttp://www.kineticdata.com/ I community.kineticdata.comhttp://community.kineticdata.com/ [http://keg.kineticdata.com/images/KEG15_EmailFooter.png]http://keg.kineticdata.com_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
Re: Remedy 8.1 and MAPI support
We were in the same boat. We had been using Outlook 2007 to use MAPI on our 8.1 servers. When it came time to build a new 8.1 server I was determined to break the Outlook chains. POP and IMAP are also not allowed in our environment. Just like Levi we setup an hMail server for our incoming email and it has been working great! The Email Engine has been more reliable since moving away from using Outlook. Jason On Mon, Feb 2, 2015 at 7:48 AM, Pierson, Shawn shawn.pier...@energytransfer.com wrote: ** You and Frederick bring up a good point, and actually I’ve been investigating and we’re now allowed to use POP and IMAP against our mail server where in the past it was forbidden so I have some new things to try out in development. Thanks, *Shawn Pierson * Remedy Developer | Energy Transfer *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Lippincott, Levi (OMA-GIS) *Sent:* Monday, February 02, 2015 9:27 AM *To:* arslist@ARSLIST.ORG *Subject:* Re: Remedy 8.1 and MAPI support ** Shawn, I know this does not answer your question but you should also find out what version of Exchange you are using. We are using Exchange 2013 and something to keep in mind is there is a newer MAPI protocol and a legacy protocol and the 2013 version of Exchange only supports the new version while the Remedy MAPI protocol uses the old version. This led us to setting up our own hMail server on our Mid Tier and having our Exchange people forward mail over to it and then connecting via POP to pull in mail. *Levi Lippincott / *Remedy Administrator +1 402 561 7014 office +1 402 321 5421 mobile levi.lippinc...@interpublic.com *Interpublic Group* 6825 Pine Street, Omaha, NE 68106 *Talent is a Gift; But Character is a Choice. -Matt Grotewold-* *From:* Action Request System discussion list(ARSList) [ mailto:arslist@ARSLIST.ORG arslist@ARSLIST.ORG] *On Behalf Of *Grooms, Frederick W *Sent:* Monday, February 02, 2015 9:17 AM *To:* arslist@ARSLIST.ORG *Subject:* Re: Remedy 8.1 and MAPI support ** You could use the standards of POP3 or IMAP for inbound email This is one of the advantages I have being on Linux.. MAPI is a MS Windows only protocol so I don’t have to deal with it. Fred *From:* Action Request System discussion list(ARSList) [ mailto:arslist@ARSLIST.ORG arslist@ARSLIST.ORG] *On Behalf Of *Pierson, Shawn *Sent:* Monday, February 02, 2015 9:10 AM *To:* arslist@ARSLIST.ORG *Subject:* Remedy 8.1 and MAPI support ** Good morning, We’re looking to upgrade out version of Microsoft Office internally, as well as Exchange, and there is being a lot of pressure to get our Remedy server upgraded from using Outlook 2007 for MAPI inbound email. I’ve tried looking all over BMC’s site, their compatibility matrix doesn’t list any email clients that it would be compatible with, the release notes reference MAPI but not what version of Outlook is supported, and even a Google search hasn’t returned anything useful as far as I can see. Does anyone know where BMC documents what versions of Outlook are compatible with ARS 8.1? Also, this is something I should probably ask for the 9.0 beta program but will they ever find a better way to do inbound email than putting Outlook on my application server? Our Exchange system seems to go down all the time in such a way that Remedy can’t reconnect easily (one of the drivers for wanting to upgrade) so I’d like to look at other options. We use SMTP for outgoing email and I can’t recall the last time it had a problem. Thanks, *Shawn Pierson * Remedy Developer | Energy Transfer _ARSlist: Where the Answers Are and have been for 20 years_ This message contains information which may be confidential and privileged. Unless you are the intended recipient (or authorized to receive this message for the intended recipient), you may not use, copy, disseminate or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail, and delete the message. Thank you very much. _ARSlist: Where the Answers Are and have been for 20 years_ Private and confidential as detailed here http://www.energytransfer.com/mail_disclaimer.aspx. If you cannot access hyperlink, please e-mail sender. _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
Re: Remedy 8.1 and MAPI support
I’ve been testing IMAP since around the time of my first email and it’s working great. I even uninstalled Outlook completely from my server to make sure I’m not accidentally referencing it somehow. It took me all of five seconds to configure IMAP and disable the MAPI mailbox, and I’m looking forward to the next Exchange patch and reboot schedule to see if that helps with some issues we’ve had. I hope to see two benefits from going to IMAP: 1) No Outlook, with its dozens of patches to make it work within my company’s environment and no worry about upgrades. 2) Improved connectivity, since I shouldn’t have the email engine disconnect and be unable to reconnect to Exchange without restarting the process. Thanks, Shawn Pierson Remedy Developer | Energy Transfer From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Jason Miller Sent: Monday, February 02, 2015 1:10 PM To: arslist@ARSLIST.ORG Subject: Re: Remedy 8.1 and MAPI support ** We were in the same boat. We had been using Outlook 2007 to use MAPI on our 8.1 servers. When it came time to build a new 8.1 server I was determined to break the Outlook chains. POP and IMAP are also not allowed in our environment. Just like Levi we setup an hMail server for our incoming email and it has been working great! The Email Engine has been more reliable since moving away from using Outlook. Jason On Mon, Feb 2, 2015 at 7:48 AM, Pierson, Shawn shawn.pier...@energytransfer.commailto:shawn.pier...@energytransfer.com wrote: ** You and Frederick bring up a good point, and actually I’ve been investigating and we’re now allowed to use POP and IMAP against our mail server where in the past it was forbidden so I have some new things to try out in development. Thanks, Shawn Pierson Remedy Developer | Energy Transfer From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Lippincott, Levi (OMA-GIS) Sent: Monday, February 02, 2015 9:27 AM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Re: Remedy 8.1 and MAPI support ** Shawn, I know this does not answer your question but you should also find out what version of Exchange you are using. We are using Exchange 2013 and something to keep in mind is there is a newer MAPI protocol and a legacy protocol and the 2013 version of Exchange only supports the new version while the Remedy MAPI protocol uses the old version. This led us to setting up our own hMail server on our Mid Tier and having our Exchange people forward mail over to it and then connecting via POP to pull in mail. Levi Lippincott / Remedy Administrator +1 402 561 7014tel:%2B1%20402%20561%207014 office +1 402 321 5421tel:%2B1%20402%20321%205421 mobile levi.lippinc...@interpublic.commailto:levi.lippinc...@interpublic.com Interpublic Group 6825 Pine Street, Omaha, NE 68106 Talent is a Gift; But Character is a Choice. -Matt Grotewold- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W Sent: Monday, February 02, 2015 9:17 AM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Re: Remedy 8.1 and MAPI support ** You could use the standards of POP3 or IMAP for inbound email This is one of the advantages I have being on Linux.. MAPI is a MS Windows only protocol so I don’t have to deal with it. Fred From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Pierson, Shawn Sent: Monday, February 02, 2015 9:10 AM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Remedy 8.1 and MAPI support ** Good morning, We’re looking to upgrade out version of Microsoft Office internally, as well as Exchange, and there is being a lot of pressure to get our Remedy server upgraded from using Outlook 2007 for MAPI inbound email. I’ve tried looking all over BMC’s site, their compatibility matrix doesn’t list any email clients that it would be compatible with, the release notes reference MAPI but not what version of Outlook is supported, and even a Google search hasn’t returned anything useful as far as I can see. Does anyone know where BMC documents what versions of Outlook are compatible with ARS 8.1? Also, this is something I should probably ask for the 9.0 beta program but will they ever find a better way to do inbound email than putting Outlook on my application server? Our Exchange system seems to go down all the time in such a way that Remedy can’t reconnect easily (one of the drivers for wanting to upgrade) so I’d like to look at other options. We use SMTP for outgoing email and I can’t recall the last time it had a problem. Thanks, Shawn Pierson Remedy Developer | Energy Transfer _ARSlist: Where the Answers Are and have been for 20 years_ This message contains information which may be confidential and privileged. Unless you are the intended recipient (or authorized to
Filter spliting into separate workflows
Hi All, We have a requirement for A form when ever this form is submitted then we need to push the data to Form B in this requirement we have written on Submit and modify mode on form A to create a new record in form B given a filter execution order is 1000 currently it is working fine in this filter we have mapped around 178 fields to push the data to form B . Few cases the field values are pushing to previous values(Updating ) on form B . Currently we are thinking creating a new request with the all mandatory fields for form B fields separating the workflows with the execution order 1000,non mandatory fields which are left from 178 fields planning to create new workflows for each field so around 155 workflows need to create and these workflow if no request match take no action if any request match modify first match request with the execution orders will be the same 1000. If I Implement like this way is there any performance issues will occurred? Do you have any solution kindly let me know . Thanks Sagar ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
