Integration As A Service (IaaS)

Overview

Integration As A Service (IaaS) is a PlatformManager capability that provides a framework for automated file-based integrations. IaaS enables administrators and data managers to configure recurring data uploads and data downloads. The feature supports common scenarios where external systems exchange structured files with Pricefx.

IaaS uses an event-driven execution model. Jobs run only when data is available or when a schedule triggers them, reducing the infrastructure footprint and improving operational efficiency. The approach is designed to replace selected IntegrationManager use cases, particularly for simple file-based integrations.

IaaS provides a no-code configuration, automated data uploads and downloads and integrated monitoring and error handling.

Use Cases

Recurring uploads of data files (e.g., product, customer, transactions).
Recurring exports of partition data to external systems.
One‑time or event-driven transfers from SFTP locations.
Incremental exports and validation‑controlled uploads.
Monitoring and notifications for success/failure states.

IaaS is optimized for recurring uploads/downloads of reasonably sized files. Very high‑frequency streams of small files are not recommended.

IaaS Features

Automated Data Upload

Defines how inbound files are collected, validated, and loaded into a partition. Typical inputs: CSV/XLSX (optionally zipped) delivered to SFTP or uploaded by external processes.

For details, see How to Create Automated Data Upload.

Automated Data Download

Defines how partition data is extracted, optionally filtered and mapped to an output layout, and then written to files that are delivered to a destination (commonly SFTP).

For details, see How to Create Automated Data Download.

Connections

Centralizes access to Pricefx partitions and external endpoints (i.e., SFTP). This enables secure reuse of credentials and consistent routing of files without hardcoding connection details.

Mappings

Specify input/output field structures for uploads and downloads. Mappings define column names, data types, and optional conversions, ensuring the target entity receives well-structured data.

Scheduling

Controls when uploads or downloads run. You can use time-based schedules or file-arrival triggers. For coordinated flows, schedules can trigger workflows or downstream steps through Event Orchestration.

For details on scheduling automated uploads, see How to Create Automated Data Upload | Upload Schedule.

Monitoring and History

Provides a consolidated view of all executed jobs with timestamps, status, and diagnostics. Use History of Runs to investigate errors of automated jobs.

For details, see History of Runs.

Archiving and Backups

IaaS can archive processed files and supports mechanisms for solution backups.

Prerequisites

Feature flag use-iaas enabled for the account.
Partition, SFTP, and credential management must be configured.
Appropriate PlatformManager permissions (partition data management, integrations, and access to Event Orchestration if using schedules/notifications).

When to Use IaaS vs. IntegrationManager

Use IaaS when:

The integration is file-based and requires minimal transformation.
You need fast setup through configuration rather than coding.
Runs should be on demand, event-driven, or on simple schedules.
You aim to minimize infrastructure cost and operational overhead.

Use IntegrationManager when:

Complex transformation logic, enrichment, or multi-stage processing is needed.
You require near real-time integrations or API orchestration.
Long-running, highly customized workflows or broad protocol support are required.

Limitations

No complex transformations: advanced joins, aggregations, or business rules should be handled upstream or in IntegrationManager.
IaaS does not perform complex cleansing or data preparation operations.
Real-time API-driven patterns are out of scope: use Event Orchestration or IntegrationManager for near real-time/API orchestration.

Typical End-to-End Patterns

Inbound file > Validate > Load to entity > Archive file. Triggered by file arrival on SFTP.
Scheduled export > Map fields > Deliver to SFTP. Uses filters to limit scope.