Reference · built on requestConnectorERP & finance

IFS Cloud

Business entities from IFS Cloud projections, read and written over OData REST with IAM client tokens.

Request accessPricing ↗

About

IFS Cloud is IFS's suite for ERP, enterprise asset management, and field service. Its API surface is the projection: a self-contained web API for one business function, exposed by the IFS OData Provider as an OData service. Each projection publishes an OpenAPI document at /int/ifsapplications/projection/v1/<name>.svc/$openapi, and the built-in API Explorer lists them. Permission sets grant a projection at one of four access levels: None, Read Only, Custom, or Full.

An operator on Fibric reads entity sets with OData query options, watches records through Custom Defined Events, and proposes creates, updates, or bound actions for your approval. Every proposal carries its own receipt with the change, the reason, and the way back.

This is a reference listing. It documents what Fibric would read from IFS Cloud and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Integration projections, listed from AllProjections.svc/Projections with $filter=Categories eq 'Integration'
  • Entity sets of any granted projection, read with $filter, $top, $skip, and the extended $apply for aggregation
  • The OpenAPI specification of each projection at <name>.svc/$openapi, in OAS 2.0 or 3.0
  • Custom Defined Events that fire when entities are created, updated, or removed, with conditions evaluated before actions run
  • @odata.etag on each record, required as If-Match when calling a bound action

Proposed actions

  • Target capability: propose creating a record with POST to an entity set, such as BusinessLeads in the BusinessLeadHandling projection
  • Target capability: propose a bound action on one record, such as SetInProgress on a lead, sent with its If-Match etag
  • Target capability: propose an Event Action of type REST Call so IFS Cloud posts to an external endpoint when an event fires

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Turn a failing asset into a work request

    Read equipment and maintenance history from the granted projections, correlate with sensor data, and propose a maintenance work order for the planner to approve.

    With Predictive Maintenance, Service Interval

  • Assign a field job with the parts on the van

    Read open work orders and part availability, propose a technician and start time, and post the assignment after the dispatcher accepts it.

    With Field Dispatch, Parts Readiness

  • Reorder spares before the next service interval

    Compare spare part stock against upcoming service intervals and propose a purchase requisition line for approval.

    With Parts Reorder, Spares Reorder

Requirements

  • An IFS Cloud environment and an IAM client that is confidential, allows direct access grants, and has service accounts enabled
  • A permission set granting each projection the operator reads or writes, at Read Only or Full access level
  • The system URL and namespace for the token endpoint, and the projection names from API Explorer
Authentication
An IAM client in IFS Cloud using the OAuth 2.0 client credentials flow against /auth/realms/<NAMESPACE>/protocol/openid-connect/token, with scope openid microprofile-jwt.

Limits

  • Access tokens are short-lived (expires_in 180 seconds in the documented response); the client must refresh continuously
  • Each token refresh returns a new refresh token; the old one must be discarded
  • Read Only projections reject entity actions and projection actions; some projections are Read Only by design
  • Outbound events are Event Actions configured in Solution Manager; each action must be enabled before its event fires

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request IFS Cloud ↗

Questions and answers

How does an integration authenticate without a user?
With the client credentials flow. The application posts grant_type=client_credentials, scope openid microprofile-jwt, and its IAM client ID and secret to the token endpoint. The access token belongs to a service user tied to the client, not to a person.
Where do I find the API for a business object?
In Solution Manager, open Integration, then API Explorer. Filter by API name to find the projection, open its API Documentation, and copy the request URL. The same specification is available as JSON from the projection's $openapi endpoint.
Does IFS Cloud push changes to external systems?
Through Events. A Custom Defined Event fires when an entity is created, updated, or removed. An enabled Event Action then runs; action types include E-Mail, Application Message, Task, Workflow, Streams Message, and REST Call, which sends the request to the endpoint you configure.
Ask about IFS Cloud

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with IFS Cloud through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy