Integrate and Connect

Introduction

• Some common interfaces, and the information shared between these interfaces and the Fluent Platform
• GraphQL, and understand its benefits over REST APIs.
• Events API, Inventory Batches, Webhooks, and Connectors
• Some recommended practices around the use of these methods.

GraphQL

• Introduction to GraphQL
• Differences to REST
• Benefits of using GraphQL
• Basic structure of a query
• A GraphQL mutation
• Types of common integrations that use GraphQL

• GraphQL is an open-source data query and manipulation language for APIs, and a runtime for fulfilling queries with existing data. It was developed by Facebook and released to the public in 2015.
• The objective of GraphQL is to reduce the amount of data that's going over the wire and for the calls that are made, to be as-specific-as possible. 

• GraphQL is always a POST HTTP Method.
• GraphQL returns 200 OK HTTP Status, even if errors occur. Errors will be in the Response body.
• GraphQL queries that do not find any result, respond as 200 OK, and a data object with null or empty entity field.
• GraphQL schema provides strongly typed validation and includes documentation.
• GraphQL allows querying multiple entities in a single HTTP request.

• Get: To retrieve an entity with a unique identifier and display results
• Search: To search and display a list of results, while applying some filters

• Input types for Create mutations have mandatory parameters that are used to define the entity to be created uniquely.
• All entities of orchestrate-able types fire orchestration events on creation. This can be used to trigger workflows.
• Every create mutation creates the entity in the “CREATED” status. This enables the clients to trigger orchestrations for that entity, if the client wishes to change the status of that entity after creation.

• Input types for update mutations have mandatory parameters that are used to identify the object to be updated uniquely.

1mutation {
2 createOrder(input:{
3     ref:"HD_2341"
4     type:"HD"
5     retailer:{id:1}
6     customer:{id:34}
7     items:{
8         ref:"VPRD_13"
9         productRef:"VPRD_13"
10         quantity:2
11     }
12 }){
13     id
14     createdOn
15 }
16}

1mutation {
2 updateOrder(input:{
3     id:5432
4     status:"BOOKED"
5 }){
6     id
7     createdOn
8 }
9}

• Order Create:
  Order creation from the Sales Channels
• Product Availability:
  Extracting Virtual Positions to be used for PLP pages or Search results
• Reporting:
  Extracting orders / fulfillments for reporting purpose
• Light Webhooks:
  In order to achieve light weight webhooks, the Webhook should only contain the entityID, but then the system to be integrated will need to extract the entity details using a GraphQL query

Events API

• Intro / Recap on what Event is
• Events API
• Event Structure
• Event Contracts & relationship to Workflow
• Types of common integrations that use Events
• Events best practices

• name: This is the name of the event which matches with the ruleset in the respective workflow.
• retailerId: This is the Fluent OMS's retailer ID.
• entityType: The entity against which the event is triggered. Example: FULFILMENT, LOCATION, INVENTORY_POSITION, etc. 
• entityId: The ID of the entity against which the event is triggered. Example: fulfilmentId, locationId, etc.
• entityRef: The ref of the entity against which the event is triggered. Example: inventoryPositionRef, etc. 
• rootEntityType: The root entity against which the event is triggered. Example: ORDER, INVENTORY_CATALOGUE, etc.
• rootEntityId: The ID of the root entity against which the event is triggered. Example: orderId, etc.
• rootEntityRef:The ref of the root entity against which the event is triggered. Example: orderRef, inventoryCatalogueRef, etc.
• attributes: The event attributes passed to the ruleset handling the event, these attributes are used by the rules of the ruleset. 

Webhooks

• Introduction/Recap on what Webhooks are
• Webhook Structure
• Webhook Features
• Types of integrations for Webhooks
• Webhook best practices

• Order status updates hook
• Email/SMS provider hook
• Carrier aggregator hook

1{
2"id": "b34281d0-ada4-11e9-a1a7-5da7a83b9sd97cd" ,
3"name": "OrderStatusChange"
4"accountId": "ACME",
5"retailerId": "1",
6"rootEntityId": "123",
7"rootEntityRef": "0_123",
8"rootEntityType" : "ORDER",
9"entityId": "123"
10"entityRef": "0_123",
11"entityType": "ORDER",
12"entityStatus": "SHIPPED",
13"type": "NORMAL"
14"attributes": {
15"ShippingPartner": "Awesome Shipping Co."
16"TrackingNumber": "TRACKING123" ,
17"TrackingURL": "http://awesomeshippingco.test/track/q=TRACKING123"
18 }
19}

1"rules" : [
2    {
3"name": "FLUENTRETAIL. base .SendWebhook",
4"props": { "url": "https://testwebhook.fluentretail.com/clicksend" }
5}
6]

• flex.signature
• fluent-signature 

Inventory Batches

• Intro/Recap on what Batches are
• Loading Inventory data via Batch

• Create a Batch: Create a Batch in the Fluent Order Management
• View a Batch: Retrieve details of the Batch

Connectors

• Intro to Connectors
• Out-of-the-box connectors 
  • Salesforce Service Cloud 
  • Salesforce Commerce Cloud 
  • Adobe Commerce Cloud

• Salesforce Commerce Cloud (SFCC)
• Salesforce Service Cloud (SFSC)

• Real-time order synchronization between order data passed from the storefront to Fluent Order Management
• Order History views with real-time updates from Fluent Order Management.
• Fluent Store Locator Widget integrated as part of the checkout process for pickup of in-store orders.
• Store data pulled from Fluent Order Management to the Storefront through the scheduled job.
• Product and Categories passed to Fluent Order Management through a scheduled job.
• Live inventory check on PDP via Fluent APIs, including click and collect store inventory.
• Features that are toggled and configurable via the Business Manager Site Preferences.

• Compatibility with GraphQL and Global Inventory(GI). For more information about GI, see Global Inventory Overview.
• The Fluent Store Locator Widget (FSLC) integrated as part of checkout for pickup in-store orders is now replaced with the native functionality provided by the SFCC platform.
• The reference Fluent rules to demonstrate the Product Availability (PA) inventory check on Product Details Page (PDP) and checkout via Fluent Fulfilment Options APIs are provided in the SDK.

• Reduce call time - Customer service staff can manage orders from just one application, so they can resolve calls faster.
• Enhance customer experience - Shorter call times means happier customers.
• Reduce training time - Using the familiar Salesforce UI to manage orders requires less training. This makes it easier to ramp up staff for peak season.
• Access powerful business logic - Order updates are processed by the powerful business rules stored in Fluent Order Management.

•  Master data synchronisation
•  Inventory synchronisation
•  Customer order synchronisation & orchestration
•  Order and fulfilment status synchronisation, shipment & invoice creation