scribe online 02 event based integration

CONFIDENTIAL | © 2015 Scribe Software Corporation. All rights reserved.

Event Based Integration

CONFIDENTIAL | © 2015 Scribe Software Corporation. All rights reserved. 4

Session Abstract

During this session we will discuss how the request/reply capability of Scribe Online works and some common use cases for it. After the session you will fully comprehend what situation it is appropriate to use this new feature and how to test and apply it to your integration.


Agenda

• Event Maps Overview

• Benefits of Event Based Maps

• Use Cases

• Design Techniques

Event Maps Overview


Scribe Online Event Maps

• Message Maps

◦ Only Supports Salesforce.com

◦ Utilizes Outbound messages and workflows

◦ Hits Scribe hosted REST endpoint

◦ SFDC Pushes XML out

◦ Scribe provides queueing mechanism



Scribe Online

Cloud Endpoint

OutboundMessage Acknowledgement

Scribe Online Agent

MessageRelayedto Agent

Target

Maps

Unique URLper map

Cloud Source



• Request/Reply

◦ REST Endpoint

◦ Accepts POST of JSON data

• Non-Hierarchical

◦ Issues JSON reply back to calling service

• Hierarchical


Scribe Online

Cloud Endpoint

Request withsource data

Response

Scribe Online Agent

Message Relayedto Agent

Target

Maps

Unique URLper map

Response fromTarget

Cloud Source


Benefits of Event Based Maps


Benefits of Event Based Maps

• Allows for real time integration

• Added control over Row counts

• Added control over API hits

• Data Presentation vs Integration

• Access to systems without a connector

Use Cases


Use Cases

• CRM Event driven integration

◦ OnLoad form events, button push to invoke web resources

◦ Useful for enrichment and cleanse


Use Cases


Use Cases

• SFDC Support Case

◦ Support reps log calls from Call Center

◦ When a Call is dropped, customer needs to be emailed follow up direction

◦ Must occur within 5 minutes


Use Cases


Use Cases

• SFDC Submission of data

◦ Sales Team works Sales Order

◦ Workflow fires based on specific fields having certain terms

◦ Creates Orders in ERP as well as Sales Order in SFDC


Use Cases


Use Cases

• WebHooks

◦ Gives marketing the control to sync data as a step in a workflow

◦ Allows for data to be fed from other systems to Scribe


Use Cases


Use Cases

• iFrames

◦ Display data fetched using Request and simply show it to a user when its required

◦ Limits rows and storage needs


Use Cases

Design Techniques


Design Techniques

• Message Maps

◦ No joins allows, must use Fetch or Lookup

◦ Only Transactional data, one row per message

◦ SFDC will not wait for reply from Integration, only that it was delivered successfully


Design Techniques

• Request/Reply

◦ Call via Custom Code

◦ Could be embedded inside Buttons, form loads, iFrames, etc

◦ Lead Enrichment common use case

◦ Used in Web Hooks from many SAAS offerings


Q+A


THANK YOU

scribe online 02 event based integration

Education