☁️
Flow IFS Cloud Development Guidelines
  • Flow IFS Cloud Development Guidelines
  • 👶Getting started
    • OData Basics
    • IFS Cloud
    • Terminology
    • Useful Applications
    • IFS documentation
      • IFS API Explorer
      • Entity details
    • Setting up the OData connector
      • Configure connection between Flow Server and IFS Cloud
      • Selecting which configurations are visible in Flow Server
  • 👩‍💻Flow Development with OData
    • Architecture
    • Flow development and distribution strategy
    • Implementation
      • Operations in OData machine steps
      • Missing operations
      • Translations
      • Iteration
      • Join data sets
      • Misc Tips and trix
      • Document / Media Library Management
      • Response status handling
        • Errors from IFS
      • Operation specific notes
        • Set input parameters using flow script
        • Update
        • 🛠️WIP - Create
        • Read
    • Configuration
      • Authentication models
        • Setup Client credential flow
        • 🛠️Setup Password credentials flow
        • 🛠️Setup Authorization code flow
        • 🛠️Setup OpenID flow
        • Obtaining Authentication related URLs from IFS Cloud
      • Projection administration
        • Administrating new projections
        • Administrating updated projections
      • Configuring projections in IFS
        • Custom Entities
        • Custom Projections
        • 🛠️WIP - Query Designer
        • Quick Reports
    • Trigger Flows from IFS Cloud
      • Trigger User Flows via External Navigation Links
      • Trigger Machine Flows via BPA using commands
      • 🛠️Trigger Flow via Event Action
    • Debugging and Testing
      • Aurena debugging
        • Inspect in web browser
        • IFS debug console
      • OData Connector Log
  • 🪄Advanced
    • Custom Request
    • C# usage in the OData connector
      • Different methods
      • Building request
      • 🛠️WIP - Code examples
Powered by GitBook
On this page
  • What?
  • How?
  • Inspecting result
  • Overview
  • Parameters
  • Request Body
  • Response
  • Request/Response Header

Was this helpful?

  1. Flow Development with OData
  2. Debugging and Testing

OData Connector Log

PreviousIFS debug consoleNextCustom Request

Last updated 2 years ago

Was this helpful?

What?

The OData connector will transform the machine step configuration into REST API call in OData connector. The OData connector will also transform the response from IFS for the Flow server.

Result of the transformation, data sent to IFS and response from IFS can be viewed/investigated in Communication Log.

Whenever Flow app receives "odd errors" it might be useful to see what call was sent to IFS and what was the actual response. In rare cases transformation of the response may not succeed even though IFS returns OK, but flow is returned with an error.

How?

Calls can be inspected in two ways:

  1. Inspect all calls to selected projection

  2. Show all calls to all projections.

Start by selecting connector configuration (= calls to which IFS Cloud configuration).

Then either select projection (=endpoint) to inspect all calls to selected projection or check "Show logs from all endpoints"

List contains information about operation (GET, POST, DELETE, PATCH), execution time and status code from IFS.

Rows can be further filtered based on Sent, User, Method, Status Code column values.

Inspecting result

When selecting a single call both the request to IFS and response from IFS can be inspected in different tabs.

Overview

Request: transformed REST call

Status Code: HTTP response code from IFS

Duration: execution time of the call

Parameters

This tab shows data sent to IFS as request parameters, applies to Read operation only.

Selected attributes and conditions defined in flow transformed to OData query syntax.

Request Body

This tab shows data sent to IFS in request body (=payload) in POST (Create, Action), PATCH (Update) or batch operations. This data is inserted viaInput tab in machine step in Flow.

When executing batch operations, for example adding two tasks to a Work Order with PrepareWorkOrderHandling/ActiveSeparate/WorkTaskeArray/Batch Add to WorkTaskeArray operation, request body contains all individual calls sent in one call to IFS and each call payload is presented as string within each call.

Response

In case operations return data (all CRUD operations), this can be inspected in Response tab. Returned values can be selected in Output or Select tabs in machine step in Flow.

Request/Response Header

"Request header"-tab contains OData connector generated REST call headers and "Response header"-tab contains the IFS response headers.

👩‍💻
Show log of selected projection
Show log of all calls
Read operation overview
Read parameters
Payload if Create operation
Individual call (green) and payload of each call (yellow)