Service-Flow User Interface Guide

This is a guide for using Service-Flow User Interface (UI). 

Service-Flow UI is a tool where integrations can be monitored, debugged and modified. Some features are yet to be editable from the UI. Meanwhile you can contact experience@service-flow.com for changes or additional questions.

Service-Flow UI consist of the following sections

  1. Message View
    • Easy to understand feed to the messages relayed within an integration
  2. Statistics (TBA)
    • A dashboard to integration related metrics, i.e. message counts, error counts and message pass through times.
  3. Endpoints
    • In this section, all the endpoints and their definitions are defined.
  4. Routing Rules
    • In this section, all rules that fulfil the integration logic between different endpoints are defined. 

See sub-pages for details.

Concepts & Glossary


TermExplanation
Inbound messageMessage that initiates the workflow in Service-Flow. In most process integrations, the message is sent from the source system to Service-Flow's receiver interfaces (PUSH). If the endpoint is using polling mechanism for inbound, the message is then queried form the source systems API (PULL).
Outbound messageMessage that is sent out to the target system by Service-Flow.
EndpointA system that is integrated via Service-Flow (i.e. a ServiceNow system or vendor's ESB). In most cases the endpoint includes both inbound and outbound traffic.
Entity typeType of an entity used while communicating with the endpoint (i.e. incident, incident_task, request or server)

Routing rule

A set of mappings that defines how inbound message is transformed into outbound message

Message type

Message types are used to define different schemas for different messages. This typically reflects to a certain need from an endpoint interface (i.e. Submit, Update or Resolve). This is optional and typically used with SOAP integrations.

ConversationAn object that contains information about a ticket lifecycle.
Conversation attributeAn attribute that can be stored into Conversation object when applying a Routing Rule. This value can be then later used as a condition and/or a target attribute value within the messaging in the same Conversation.
Virtual attributeAn attribute that can be used as a helper while executing a Routing Rule. Typical use case is to parse a part of the inbound attribute value and then use the parsed value in a Table Mapping.