Server-side integration enhancements for Microsoft Outlook

With our February 2018 release, we are excited to bring several new capabilities to our server-side integration for Microsoft Outlook.

Outlook for mobile add-in support

We have listened to your feedback – the server-side add-in now works in the Outlook mobile app (on iOS and Android).

The add-in is available in the email read window with the same look and feel as on the desktop. We are working with Microsoft to bring the latest and greatest on mobile front in this space!
Here is how this looks on the Outlook app on the iPad.

 

Add-in pinning

The server-side add-in can now be pinned in Outlook for Windows. You asked for this and we now have enabled this feature for both the email read and compose mode. So as a user, you can keep the add-in pinned and go through different emails without having to reload the add-in each time to get contextual information from SAP.
For exact requirements on which versions of Outlook for Windows support this, please refer to the thread here.

Auto-sharing of emails

E-mails can now be automatically shared with SAP Hybris Cloud for Customer letting you do spend more time doing what you do best – sell more! This powerful feature even links the e-mails to the right account so that all your conversations are automatically linked and available.

A key-user can turn this feature on under E-Mail Integration > Groupware Settings > Profile as follows:

Certain domains or email addresses can also be excluded in the configurations – emails to/from such addresses will not be automatically shared with SAP.

Apart from the above, there are several smaller enhancements made to the solution for both end-users and key-users – for example, profile changes made by a key-user can now be forced (updated) to all end users in a particular organization from the E-mail Integration > Groupware Settings > Organization tab.

Stay tuned for more exciting features coming in our upcoming releases! http://bit.ly/2BAGZ1G #SAP #SAPCloud #AI

Asynchronous Retries With AWS SQS

ICYDK: While designing our integration points against the remote APIs, we also need to consider error scenarios. Two types of errors/failures can occur during API communication: functional and non-functional. Most non-functional errors, (like temporary network outages, infrastructure problems, slow resources) are retriable.

We can implement two kinds of retry-mechanisms against these failures: synchronous and asynchronous. https://goo.gl/UaZJxs #DataIntegration #ML

The Growing Importance of GitHub Topics for Your API SEO

When you are operating an API, you are always looking for new ways to be discovered. I study this aspect of operating APIs from the flip-side–how do I find new APIs, and stay in tune with what APIs are to? Historically we find APIs using ProgrammableWeb, Google, and Twitter, but increasingly GitHub is where I find the newest, coolest APIs. I do a lot of searching via GitHub for API related topics, but increasingly GitHub topics themselves are becoming more valuable within search engine indexes, making them an easy way to uncover interesting APIs.

I was profiling the market data API by Alpha Vantage today, and one of the things I always do when I am profiling an API is to conduct a Google and then, secondarily, a GitHub search for the API’s name. Interestingly, I found a list of GitHub Topics while Googling for Alpha Vantage API, uncovering some interesting SDKs, CLIs, and other open source solutions that have been built on top of the financial data API. Showing the importance of operating your API on GitHub, but also working to define a set of standard GitHub Topic tags across all your projects, and helping encourage your API community to use the same set of tags, so that their projects will surface as well. https://goo.gl/hzXcKS #DataIntegration #ML