Hello Friends,
Welcome to my blog series on the topic of “SuccessFactors Outbound Integrations using Intelligent Services Centre (ISC) & Integration Centre (IC)". In this post, I will delve into the details so we can understand different scenarios that can be addressed with the use of either Intelligent Service Centre (ISC) only or in combination with Integration Centre (IC).
Scenarios
1. SF Outbound Data Comparison i.e., ISC Vs IC
2. SF Outbound Filter Comparison i.e., ISC EC Business Rule Filter Vs IC Filter
3. SF Cross Portlet Update i.e., Integration Centre Vs Middleware System
Target Audience
This blog post is specifically designed for customers using SuccessFactors Intelligent Services Centre or Integration Centre (IC) for Outbound Integrations and it may help the following participants.
Architecture Diagram
This Architecture diagram is to highlight different systems and functionalities used by each of these systems.
Intelligent Services Centre (ISC): Monitors the business events and accordingly triggers actions configured/activated in this respective Service. ISC Performs XML data transfer to External Service Endpoints (like SAP Cloud Integration or Third-Party Application) or ISC can trigger Integration Centre Artefact for the given Entity Record based on the Event.
Integration Centre (IC): Performs XML, JSON, and CSV data transfer to respective External Service Endpoints (like SAP Cloud Integration or Third-Party Applications) or stores files onto SFTP Server.
SAP Cloud Integration: Performs data transformation and transfers it to Third Party or may also update data from Third Party into SuccessFactors via ODATA API.
Events: Events are basically system monitoring different actions performed by Admin, Employee, etc.
We will compare the outbound data generated by Intelligent Services Centre and Integration Centre.
We are using SAP CPI as External Service Endpoint.
We are using the Event “Change in Job Title” in Intelligent Services Centre to perform 2 Actions.
Scenario 1A: SF ISC -> SAP CPI
Scenario 1B: SF ISC -> SF IC -> SAP CPI
Configuration Steps
1. Goto Intelligent Services Centre and search for Event “Change in Job Title”.
2. Enter SAP CPI Inbound Service Endpoint and Credential details and Save Flow.
Scenario 1B: SF ISC to SF Integration Centre to SAP CPI
1. Click Integration to Add Integration via Integration Centre Artefact Creation.
2. Click Create New Integration
3. Insert 3 Sibling Elements each for UserId, StartDate, Event Reason resp.
4. Click on Field Mapping Icon on the top right and drag the field Start Date from Left Column (EmpJob) to the field StartDate in the central column. This is to map fields. Perform the same for a User ID to UserId and Event Reason to Event Reason resp.
5. Click next on Response Fields and Filter screens as we don’t need to configure anything here.
6. Enter CPI Service Endpoint and Credential details.
Now there are 2 configs done here and this is how it looks.
Scenario 1A: SF ISC to SAP CPI
Scenario 1B: SF ISC to SF IC to SAP CPI
Data Change Steps to Trigger Event
There are different ways to trigger Promotion but since we are testing, we will use a quick method.
1. Goto Employee Profile – Job Information – History – Click Insert
2. Enter the Effective date, Event, and new Position so Job Title is also changed which is good to trigger the Event we selected in ISC.
Data Comparison for Payloads Received in CPI
Intelligent Services Centre is calling Listener 5 Service and Integration Centre is calling Listener 4 Service. Both the flows are similar with Inbound Addresses being different.
Intelligent Services Centre Payload sent to CPI will be always in XML form and have only system default fields listed. We cannot add more fields to provide more data to an external system.
Integration Centre Payload sent to CPI is in JSON form as set in Integration Centre Artefact and has fields listed that were selected in IC Artefact. Hence, we can add more fields in Integration Centre to provide more data to an external system and in different formats like XML, JSON, and CSV based on Target System capability.
*************************
Hope you enjoyed it and these details help you understand the differences in data transferred by Intelligent Services Centre (ISC) and Integration Centre (IC).
You can check Part 2 of this blog series.
Your feedback and suggestions are welcome.
Stay Tuned for Part 3.
Thanks
Alim Momin
Welcome to my blog series on the topic of “SuccessFactors Outbound Integrations using Intelligent Services Centre (ISC) & Integration Centre (IC)". In this post, I will delve into the details so we can understand different scenarios that can be addressed with the use of either Intelligent Service Centre (ISC) only or in combination with Integration Centre (IC).
Scenarios
1. SF Outbound Data Comparison i.e., ISC Vs IC
2. SF Outbound Filter Comparison i.e., ISC EC Business Rule Filter Vs IC Filter
3. SF Cross Portlet Update i.e., Integration Centre Vs Middleware System
Target Audience
This blog post is specifically designed for customers using SuccessFactors Intelligent Services Centre or Integration Centre (IC) for Outbound Integrations and it may help the following participants.
- Admin
- Developers
- Consultants
Architecture Diagram
This Architecture diagram is to highlight different systems and functionalities used by each of these systems.
Intelligent Services Centre (ISC): Monitors the business events and accordingly triggers actions configured/activated in this respective Service. ISC Performs XML data transfer to External Service Endpoints (like SAP Cloud Integration or Third-Party Application) or ISC can trigger Integration Centre Artefact for the given Entity Record based on the Event.
Integration Centre (IC): Performs XML, JSON, and CSV data transfer to respective External Service Endpoints (like SAP Cloud Integration or Third-Party Applications) or stores files onto SFTP Server.
SAP Cloud Integration: Performs data transformation and transfers it to Third Party or may also update data from Third Party into SuccessFactors via ODATA API.
Events: Events are basically system monitoring different actions performed by Admin, Employee, etc.
Scenario 1: SF Outbound Data Comparison i.e., ISC Vs IC
We will compare the outbound data generated by Intelligent Services Centre and Integration Centre.
We are using SAP CPI as External Service Endpoint.
We are using the Event “Change in Job Title” in Intelligent Services Centre to perform 2 Actions.
Scenario 1A: SF ISC -> SAP CPI
Scenario 1B: SF ISC -> SF IC -> SAP CPI
Configuration Steps
1. Goto Intelligent Services Centre and search for Event “Change in Job Title”.
2. Enter SAP CPI Inbound Service Endpoint and Credential details and Save Flow.
Scenario 1B: SF ISC to SF Integration Centre to SAP CPI
1. Click Integration to Add Integration via Integration Centre Artefact Creation.
2. Click Create New Integration
3. Insert 3 Sibling Elements each for UserId, StartDate, Event Reason resp.
4. Click on Field Mapping Icon on the top right and drag the field Start Date from Left Column (EmpJob) to the field StartDate in the central column. This is to map fields. Perform the same for a User ID to UserId and Event Reason to Event Reason resp.
5. Click next on Response Fields and Filter screens as we don’t need to configure anything here.
6. Enter CPI Service Endpoint and Credential details.
Now there are 2 configs done here and this is how it looks.
Scenario 1A: SF ISC to SAP CPI
Scenario 1B: SF ISC to SF IC to SAP CPI
Data Change Steps to Trigger Event
There are different ways to trigger Promotion but since we are testing, we will use a quick method.
1. Goto Employee Profile – Job Information – History – Click Insert
2. Enter the Effective date, Event, and new Position so Job Title is also changed which is good to trigger the Event we selected in ISC.
Data Comparison for Payloads Received in CPI
Intelligent Services Centre is calling Listener 5 Service and Integration Centre is calling Listener 4 Service. Both the flows are similar with Inbound Addresses being different.
Intelligent Services Centre Payload sent to CPI will be always in XML form and have only system default fields listed. We cannot add more fields to provide more data to an external system.
Integration Centre Payload sent to CPI is in JSON form as set in Integration Centre Artefact and has fields listed that were selected in IC Artefact. Hence, we can add more fields in Integration Centre to provide more data to an external system and in different formats like XML, JSON, and CSV based on Target System capability.
*************************
Hope you enjoyed it and these details help you understand the differences in data transferred by Intelligent Services Centre (ISC) and Integration Centre (IC).
You can check Part 2 of this blog series.
Your feedback and suggestions are welcome.
Stay Tuned for Part 3.
Thanks
Alim Momin
- SAP Managed Tags:
