The Unvired Mobile Platform offers a rich set of REST APIs to build custom integrations easily. The REST APIs are broadly classified into APIs that deal with:
- Sessions – Handles persistent login sessions
- Users – Work with Unvired users (Create, Update, List, Lock etc)
- Groups – Work with groups of users (Create, Update, List etc)
- Applications and Libraries – Work with Unvired applications and libraries (Execute functions, Deploy, Undeploy, Configure Properties and Settings etc)
- Messages and Attachments – Queue messages, attachments, retrieve them etc.
Other APIs include:
- Companies – Work with Unvired Companies (Departments) (Create, Update, Activate plans, List etc)
- Status – Get technical status information on the platform for monitoring etc.
Some use cases can be to create a user in the UMP when a user is provisioned in MS Active Directory, or write command line tools that create users/groups based on other Identity Management systems like ADS, LDAP etc, deploy (make available) applications to users belonging to specified ADS groups etc. The APIs can also be used to for e.g. execute functionality in an enterprise system like a ticketing system from a web site wherein the user can request support.
The APIs are documented in detail and the documentation is made available as Swagger definitions for import into API testing tools, code generation etc. Additionally if you are a Postman fan (http://getpostman.com) you can directly import the UMP Postman collection to work with the APIs and test/develop.
The detailed documentation can be accessed at the Unvired Developer Portal (http://developer.unvired.com)
Enjoy developing smart integrations. Let us know what you build here and receive a memento from Unvired 🙂
Chatbots are the rage, but we are in the early days. We are still not sure about how best to design for bots. Yes, while conversational interfaces have promise to redefine the User Experience, the challenge facing us is to identify the right Use Cases, and the appropriate design. After reviewing the nascent literature on this, talking to customer end users, and based on our own experience of building chatbots for enterprise systems, here are 3 ideas for Designing for Chatbots:
- Minimize Input: The user experience should be the priority. Expecting users to enter free text has the potential for failure. Instead, it may be best to have users give structured input. For example, our developers at Unvired have designed a Command Infrastructure that eliminates lengthy free text input. For example, Users can select Approve or Reject a Purchase Order in SAP or View Sales order from Oracle EBS with a Get Order Details simple chat command.
- Hybrid Approach: In some cases, the user may want to talk to a human at some point in the conversation with the bot. Good design should enable a human to jump in at any time. Say, for example, you are ordering flowers on Facebook Messenger using a chatbot, but are frustrated because you cannot find what you are looking for. There should be a way out to reach out to a human.
- Simple: The design for chatbots should be simple. One of the advantages of bots is that the need for say, a 3 screen application is eliminated. There is no GUI. Bots interactions should be kept simple and short—the user should give minimal input, and receive the output.
Let me know if you have other ideas for designing for bots. These are early days, and we can all learn from each other.
This blog was first posted on LinkedIn.
Lately, there has been a lot of buzz around bots. Bots are the lightweight programs that will make our work easier, and help us escape the multitude of apps that users have to navigate. Bots have a simple text interface that eliminates the need for a Graphical User Interface (GUI). Bots talk to systems, applications, and things- hence the term chatbots. Much has already been written about bots, machine learning, AI, Natural Language Processing, and so this blog discusses a very specific sub-topic: Chatbots for SAP.
Interfaces with SAP come in many forms—the SAP GUI, Personas, and SAP Fiori among others. That is till now-enter the conversational interface. At Unvired, we have developed chatbots for SAP to enable various Use Cases:
1.SAP ERP-Workflow: How about SAP messaging you an alert that a Purchase Order needs to be approved? You look at the details, and approve. Your text “Approve” gets the PO approved in SAP.
2.SAP ERP-Sales: The Sales leader needs to report to the CEO the latest sales figures. A quick text to SAP, and the answer comes right back. How about looking at a sales chart—that can be viewed too.
There are so many chatbots for SAP that would be a must have—for SAP ERP, S/4 HANA, SAP CRM, Cloud for Customer (C4C), SuccessFactors, and others. Customers in industries including Manufacturing, Chemicals, Financial Services, and Real Estate have indicated interest in exploring Use Cases for chatbots.
Chatbots for SAP enable receiving alerts from SAP, taking actions/decisions on those alerts, and searching/querying all with the intent to streamline workflow, and make work easier.
If you are an SAP customer or SAP partner, and want to collaborate with Unvired to build chatbots for SAP, please send me an Inmail or email me or comment on this post. We would love to jointly define some Use Cases for chatbots. These are exciting times indeed. As always, looking forward to others sharing their experience with and thoughts on bots.
Earlier this week, I attended the Best Practices for Chemicals (SAP) Conference hosted by The Eventful Group in Houston. It was a great conference attended by several CIOs including from Huntsman, Nova Chemicals, PLZ Aeroscience, and Americas Styrenics among others. There were many great presentations. Here are the top themes:
1.Digital: Chemical companies are embracing digital. Mobile applications, Internet of Things (IoT), Predictive Analytics, and the Cloud is being adopted by this industry. Agricultural chemical companies are combining sensor data, soil data and weather information to increase crop yield. HANA is beginning to be adopted as a database and SAP S/4 HANA is also making headway as the digital core. Customers, Suppliers, Employees, and Assets are the four pillars of Digitization.
2.Outcome based: Chemical companies are also innovating and defining new business models. For example, instead of selling compressors, they are selling “Compressed Air” as a service. It is all about Outcome based models.
3.Cyber-security: Chemical companies are very concerned about being hacked. Given the nature of the products they make, a cyber attack can be very dangerous. There are regular meetings held where Chemical companies discuss how best to implement cyber security.
4.Global Compliance: Chemical companies have to ensure that their products comply with various regulations. Also, they have to register each product in the country where they plan to sell. Regulations change frequently, and it is critical to stay on top.
This blog first appeared on LinkedIn