Definition
An interface to retrieve the authorization token of SAP Intelligent Robotic Process Automation (SAP iRPA) Service Credentials.
Business Context and Use
SAP Business ByDesign (SAP ByD) would like to support its customers to trigger SAP Intelligent Robotic Process Automation (SAP iRPA) bot via APIs. This webservice will provide an interface to retrieve authorization token of SAP Intelligent Robotic Process Automation Service Credentials.
Prerequisites
Technical Prerequisites:
This web service must be activated within a communication arrangement. Customer can create new Communication Scenarios under work center view Application and User Management - Communication Scenarios by clicking button "New", then add operation "iRPAServiceInboundSI" and later on create new communication arrangement under work center view Application and User Management - Communication Arrangements using Communication Scenarios.
Customer can download the XML message from work center view Application and User Management - Service Explorer with filter "All Synchronous Inbound Operation" with name "iRPAServiceInboundSI" -> Click on Download WSDL
Business Prerequisites:
You must scope Integration with SAP Intelligent Robotic Process Automation in Business configuration under Question tab-> Communication and Information Exchange->Integration with External Applications and Solutions->Integration Scenarios for Cloud Solutions from SAP
Option: Do you want to enable integration with SAP Intelligent Robotic Process Automation? Should be Reviewed
Constraints and Integrity Conditions
General Rules for Using This Web Service
<MessageHeaderiRPA>
<CreationDateTime>2006-03-28T12:00:00.1234567Z</CreationDateTime>
</MessageHeaderiRPA>
Note: Default date is coming as 2006-03-28T12:00:00.1234567Z, however there is no relevance of this date to generate authorization token
More Information
Request Payload
<n0:IRPAServiceCredentialMessageRequestType>
<MessageHeaderiRPA>
<CreationDateTime>2006-03-28T12:00:00.1234567Z</CreationDateTime>
</MessageHeaderiRPA>
</n0:IRPAServiceCredentialMessageRequestType>
Response Payload
<?xml version="1.0"?>
-<n0:IRPAServiceCredentialsMessageResponseType>
<AuthorizationToken>XXX</AuthorizationToken>
<TokenType>YYY</TokenType>
<ExpiryTimeIn>ZZZ</ExpiryTimeIn>
</n0:IRPAServiceCredentialsMessageResponseType>
Here in response payload, XXX is authorization token, YYY is Authorization Type and ZZZ is Token Expiry Time
Definition
An interface to retrieve the authorization token of SAP Intelligent Robotic Process Automation (SAP iRPA) Service Credentials.
Business Context and Use
SAP Business ByDesign (SAP ByD) would like to support its customers to trigger SAP Intelligent Robotic Process Automation (SAP iRPA) bot via APIs. This webservice will provide an interface to retrieve authorization token of SAP Intelligent Robotic Process Automation Service Credentials.
Prerequisites
Technical Prerequisites:
This web service must be activated within a communication arrangement. Customer can create new Communication Scenarios under work center view Application and User Management - Communication Scenarios by clicking button "New", then add operation "iRPAServiceInboundSI" and later on create new communication arrangement under work center view Application and User Management - Communication Arrangements using Communication Scenarios.
Customer can download the XML message from work center view Application and User Management - Service Explorer with filter "All Synchronous Inbound Operation" with name "iRPAServiceInboundSI" -> Click on Download WSDL
Business Prerequisites:
You must scope Integration with SAP Intelligent Robotic Process Automation in Business configuration under Question tab-> Communication and Information Exchange->Integration with External Applications and Solutions->Integration Scenarios for Cloud Solutions from SAP
Option: Do you want to enable integration with SAP Intelligent Robotic Process Automation? Should be Reviewed
Constraints and Integrity Conditions
General Rules for Using This Web Service
<MessageHeaderiRPA>
<CreationDateTime>2006-03-28T12:00:00.1234567Z</CreationDateTime>
</MessageHeaderiRPA>
Note: Default date is coming as 2006-03-28T12:00:00.1234567Z, however there is no relevance of this date to generate authorization token
Example
Request Payload
<n0:IRPAServiceCredentialMessageRequestType>
<MessageHeaderiRPA>
<CreationDateTime>2006-03-28T12:00:00.1234567Z</CreationDateTime>
</MessageHeaderiRPA>
</n0:IRPAServiceCredentialMessageRequestType>
Response Payload
<?xml version="1.0"?>
-<n0:IRPAServiceCredentialsMessageResponseType>
<AuthorizationToken>XXX</AuthorizationToken>
<TokenType>YYY</TokenType>
<ExpiryTimeIn>ZZZ</ExpiryTimeIn>
</n0:IRPAServiceCredentialsMessageResponseType>
Here in response payload, XXX is authorization token, YYY is Authorization Type and ZZZ is Token Expiry Time