Adopting a cloud-first IT strategy brings a host of benefits – like lower costs and stronger infrastructure – to name a few.
Portals and APIs are two technologies driving cloud automation.
In this webinar, we’ll explore how and why they should be your next go-to solutions – with demos so you can see for yourself.
Here’s more of what we’ll cover:
• SaaS vs. on-prem solutions: the differences in deployment, scalability, security management, support, and beyond
• Eliminating manual data management and gaining better data quality through more efficient system integration, with APIs for SAP data and process automation
• Automating processes requiring complex SAP data interactions with other third-party systems, like Salesforce
• How our Automate Evolve portals help you automate processes beyond SAP to streamline master data creation and provide customized experiences for your customers – all with no code required
2. Benefits of adopting a cloud-first
IT strategy
• Optimizing IT infrastructure
• Lowering electricity expenses
• Reduced staffing
• Lower, more predictable capital costs
• Improved reliability without the need for redundancy
• Reduced carbon footprint
2
3. How does this compare to our current
offering?
Customer Managed Hosted
Deployment options
On premise, AWS, or
Azure
AWS
Hosting & managed service agreement Not applicable Included
Development & Production environments Customer Included
Infrastructure support Customer IT/DevOps Included
OS & database support Customer IT/DevOps Included
Application support Precisely Included
Managed services Not applicable Included
Pricing & terms Not applicable Included
Evolve/SM Upgrades Customer or Partner Included
Control over all infrastructure aspects Customer Included
Quickly scale to meet new demands Not applicable Included
SSO configuration
Professional Services or
Partner
Included
Security management Customer Included
4. Precisely Evolve SaaS offering
Trusted end-to-end support for your automation platform
DEPLOYMENT SERVICES
ONGOING MANAGED SERVICES
SLA of 99.9% uptime
Infrastructure provisioning
Demonstrations before
upgrade availability
Environment testing
Infrastructure planning
and recommendations
Response and resolution—
infrastructure and cloud
Intrusion protection
with 24/7 monitoring
Emails before
upgrade availability
Software installation
Proactive
vulnerability mgt.
OS and
database patching
Upgrades scheduled
SSO configuration
Daily database backups
24/7 environment monitoring
and support
Evolve/Studio Manager
upgrades included
Management of compute,
network, and storage
Environment sizing
Development & Production
Proactive monitoring
for uptime, capacity
and performance
Application
patch deployment
5. 5
Operational/
environment
support hours
24/7
Application
Support hours
24/5
PRIORITY ESTIMATED RESPONSE TIME
4 – LOW
Information or enhancements requests
24 hours or next business day
3 – MEDIUM
Problem where acceptable workaround
is available
8 hours or next business day
2 – HIGH
System is operational, but functionality
is seriously affected
4 hours
1 – CRITICAL
System is down
1 hour
Support case response time SLA
Precisely support coverage
8. 8
Automate
Evolve
Portals
Secure internet access
for your SAP data
• Create custom portals for
customer, vendor, partner and
employee self-service data
management
• Streamline master data
processes
• Simplified portal development
experience
• Internal portals for Winshuttle
form users
9. 9
Widget-based
design
experience
Simple to create and
deploy
• No-code portal development
• Visual designer
• Drag and drop simplicity
• Connect to workflows
• Enable customized user
experiences
• Collect supporting files
10. Adding
external
portals
Custom web portals
for external (and
internal)
stakeholders
EXAMPLE USE CASES:
• External vendor or customer
portals for managing SAP data
• Internal portals with custom landing
pages
10
SAP ERP
WFM
Deployed
Portal
Portal users
Hosted on
Azure
Automate
Evolve
Private Cloud
or On-Premise
11. Evolve Portals capabilities &
features
11
User Self-service Chat Users manage SAP data
User dashboards Launch workflows Multilingual UI
12. Evolve Portals
Example use cases
Vendors/suppliers
1. Onboarding
2. Change requests
3. Profile management
4. Cost price updates
5. Etc.
Presentation name
12
Customer
1. Onboarding
2. Change requests
3. Profile management
4. Etc.
Distribution/partners/m&a
1. Onboarding
2. Joint Product Launch
3. Wholesale alliance
4. Cost price updates
5. Etc.
13. Evolve Portals Example
Vendor onboarding
13
1. Employee creates a request to onboard
a vendor
2. Vendor receives an email with link to
sign up for the portal and register
3. Vendor registers on the portal, sets
password and logs in to provide
requested information on the form
4. The request and associated information
is sent to the internal employee to
approve the vendor
5. If all details are correct, vendor is
approved and created in SAP
NOTE: At every step of the process, Vendor can be
notified about the process details via an email notification.
SAP ERP
WFM
Vendor
Portal
Portal users
Hosted
Process and Data
management
Automate Evolve
Private Cloud
or On-Premise
1
4 5
2
3
14. 14
APIs
Connected SAP data
management and process
automation
• RESTful API’s for automating
end-to-end processes
• Efficiently integrate systems to
processes and eliminate
manual data management
• Connect multiple systems and
cloud services with SAP
• Streamlined master data
processes
15. Set of RESTful APIs for
SAP data & process
automation
SAP Data API
REST API that enables direct
integration with SAP for scenarios that
don’t require data enrichment. Applies
to Studio Manager and Evolve. Easy
Inbox upgrade.
Presentation name
15
Digital Access API
REST based API that enables external
software to kick start or update an
Evolve workflow for users to
contribute data before it is ultimately
posted to SAP.
3rd-party API
support
Connecting to other REST APIs that
enables an Evolve process to connect
to different system of records to read
or update data.
16. Presentation name
Simplifying SAP data integration
Adding value in the automation eco-system
16
SAP Data API
RESTful API that enables direct
integration with SAP for
scenarios that don’t require
data enrichment. Applies to
Studio Manager and Evolve.
Easy inbox upgrade
SAP ERP
WFM
API Call
RPA Bots
Partners
Third-party applications
Governance and
server scheduling
SAP Data API
17. Presentation name
Evolve only APIs
Triggering Evolve processes
17
Evolve Digital Access
API
RESTful API that enables external process
to kick start or update an Evolve
workflow for users to contribute data
before it is ultimately posted to SAP. SAP ERP
WFM
Proces
s Data
Process and Data
management
Automate
Evolve
18. Presentation name
Enabling larger end-to-end processes
Digital Access API
18
Example use cases
• Creation of customer data
across CRM and SAP
• Creation of product data across
PLM and SAP
SAP ERP
WFM
Proces
s Data
Data collection
for SAP
Automate
Evolve
19. Presentation name
Evolve only APIs
Interacting with other systems of record
19
Evolve 3rd-party API
support
Connecting to other RESTful APIs that enables an
Evolve process to connect to different cloud
system of records to read or update data.
Includes ODATA support.
SAP ERP
WFM
Data
Process and Data
management
Automate
Evolve
20. Presentation name
Connecting to more systems of record
Use Evolve to manage end-to-end processes
20
Example use cases
• Collecting data from multiple systems
• Multi-system data governance
• Multi-system master data governance
• Complex process automation
SAP ERP
WFM
Data
Process and Data
management
Automate
Evolve
21. Presentation name
Connecting to more systems of record
Third-party RESTful API support
21
SAP ERP
WFM
EnterWorks
Automate Evolve
Generic Protocols
SOAP SQL ODBC
OLEDB ODATA REST
22. Let’s continue the
conversation…
Contact us
Set up a 30-minute
personalized demo
+1-877-700-0970
“Get in touch” on
www.precisely.com
www.precisely.com
Demos
White Papers
Case Studies
Note to sales:
Automate Evolve is built with a modern, intuitive user interface to speed up solution development.
Note to sales:
On this slide we want to highlight that we have a number of design features that enable people without SAP programming skills to quickly build solutions.
Why Portals?
A common request we have received from customers is to extend vendor/customer onboarding scenarios to stakeholders outside the organization. With Evolve Portals, you can build your own supplier self-service and customer self-service portals.
And you will also be able to use this for internal portals, to build specific landing pages for specific groups of users.
This extends Evolve use cases and opens up new opportunities for you to deliver more and better service for your customers and suppliers. External Portal deployment is available as an add-on to Evolve 20.2 and later. Talk to your sales rep about pricing for external portals based on your needs.
You can also develop and deploy portals for internal audiences at no cost.
In our conversations with Gartner, it’s been evident that this is an area that is still largely unsolved for a lot of customers. Companies are left trying piece together their own solutions. With Evolve Portals we are providing the fastest path to a custom portal.
Note to sales:
Our ability of offer a choice of front ends is another key differentiator against both BPA vendors and SAP MDG.
Here are some of the use cases that we planning to address with the initial release of Evolve Portals.
Onboarding, change requests, data updates and more can be accomplished through the portals.
Let’s walk through an example use case of how Evolve Portals would work.
We consider this an example of “Permission-driven” portal access, meaning that an internal employee will trigger portal registration/on-boarding process for the vendor who is going to be accessing the vendor portal.
Employee creates a request to onboard a vendor
Vendor receives an email with link to a sign up for the portal and register
Vendor registers on the portal, sets password and logs in to the portal
A task is assigned to the Vendor to provide other requested information on the form.
Request is sent to the internal employee to approve the vendor
If all details are correct, vendor is approved and created in SAP
At every step of the process, Vendor can be notified about the process details via an email notification.
To recap, the solution developer uses the Evolve Portal Builder to create this portal, and it is very easy for the solution developer to create and customize such a portal with the widgets you want.
With the 20.2 release of Winshuttle Evolve, the platform now includes a set of RESTful APIs that enable Evolve to manage and automate broader, end-to-end processes by connecting multiple systems and cloud services with SAP.
These API's help solution developers efficiently integrate systems to and processes to eliminate manual data management that often leads to poor data quality and ungoverned process tracking.
For teams creating seamless, end-to-end solutions, Evolve automates business processes that require complex SAP data interactions with other, third-party systems like Salesforce, or that use the ODATA protocol. Traditionally, processes like these required inflexible, custom solutions that do not easily adjust to dynamic business environments. Evolve gives you the agility and flexibility you need to compete and thrive in today's business landscape.
With Evolve 20.2 we are including access to three RESTful API’s that will further enhance your digital transformation and automation efforts. They are:
SAP Data API: REST API that enables direct integration with SAP for scenarios that don’t require data enrichment. It acts as the last-mile into SAP for other applications and combines eliminates the need for RPA bots to screen-scrape the UI to deliver faster, more stable process automation.
Evolve Digital Access API: This RESTful API allows you to seamlessly launch Evolve workflow processes for either human-assisted workflows or completely automated sequences with your SAP ERP system.
Evolve 3rd-party API support: This RESTful API enables Evolve solution developers to easily integrate with other systems of record that have RESTful APIs, such as Salesforce or SAP’s ODATA service. You can query data from these third-party systems into your process or send
This combination of API’s available with Evolve 20.2 delivers a significant benefit to SAP teams looking to be part of larger, more complex digital transformation and automation efforts.
SAP Data API
RESTful API that enables direct integration with SAP for scenarios that don’t require data enrichment. It acts as the last-mile into SAP for other applications and combines eliminates the need for RPA bots to screen-scrape the UI to deliver faster, more stable process automation.
The SAP Data API enables direct and differentiated integration, via the Winshuttle Function Module, with SAP ERP systems for loading data into SAP and has scalable runtime performance.
It is an add-on to Studio Manager and Evolve and activated by a license key.
Easy inbox upgrade
This API is commonly applied to these types of direct SAP integration
RPA Bots
Partners software integration like Abbyy
Or third party applications that need to get data easily in and out of your SAP ERP system with enormous flexibility offered by the ease of leveraging studio scripts..
The Digital Access API allows you to seamlessly launch Evolve workflow processes for either human-assisted workflows or completely automated sequences with your SAP ERP system. For human-assisted workflows, you use a web form leveraging all of the functionality in Evolve.
This slide shows how other system of records use the Digital Access API to start or update an Evolve workflow (so both Process and Data are involved in this workflow interaction).
Similarly, the workflow may connect with these systems to store or retrieve information as part of the workflow execution.
The Digital Access API is an asynchronous API that scales in terms of the amount of data managed and the frequency of process triggering. Doing this enables an external application to kick start or update an Evolve workflow before its data is ultimately posted to SAP. Using this API, you can also get and act on user assignments allowing you to show Evolve tasks on a UI other than Evolve.
This RESTful API enables Evolve solution developers to easily integrate with other systems of record that have RESTful APIs, such as Salesforce or SAP’s ODATA service. You can query data from these third-party systems into your process or send data from your process to third-party systems depending on your use case.
It can also be used in conjunction with the Digital Access API to manage and govern data using Evolve through complex process workflows to support broader digital transformation initiatives.
This slide shows how these other system of records may start or update an Evolve workflow (so both Process and Data are involved in this workflow interaction).
Similarly, the workflow may connect with these systems to store or retrieve information as part of the workflow execution.
In fact, we’re increasingly encountering more and more non-SAP systems in our use cases. Even though SAP is still the dominant system of record, there is often a need to also connect to several other systems for complete automation of a use case.
We have a deeply integrated experience when it comes to SAP and we also support a number of generic protocols for connecting to other systems and data sources.
click
Evolve can now support EnterWorks natively as a data source. In addition to that, we will continue to expand the generic protocols we support for connecting to other systems. More specifically, we’re adding support for REST and ODATA APIs which are typically the APIs you’ll find in a lot of cloud-based third-party applications.
click
This will be how Evolve solutions will connect to other SAP products that support ODATA. Depending on the specific third-party system, there may be additional future work required around authentication methods, but we have connectors for S/4HANA as well as Salesforce and we support a variety of authentication methods for connecting with third party systems coming out with this release.
Next slide
None/Anonymous: No authentication.
Basic Authentication : Required User name and password when accessing APIs
Http Headers : Where system key or secret or license key etc are required to send in Request HTTP headers.
SAP Hana Basic: Required User name and password when accessing SAP Hana APIs
Questions?
Can you also do Vendor and Customer masters too?
I’m on S4 Hana will this work with my system?
I have custom fields in my material master, does this work for those?
We often have fields that the business is missing can you make them require even if SAP doesn’t require them?
We would love to speak to you in more detail about your product data processes and how we can help you make an impact to your business , so please feel free to reach out to us.