Skip to main content


Workday Adaptive Planning Knowledge Center

Integration Workflow

The Integration framework acts as a secure bridge for importing data and metadata from different data sources into Adaptive Planning. Data sources can include spreadsheets, databases, and cloud-based or on-premises systems. You can filter, clean, map, and merge the information coming from these sources to eliminate potential import errors. You can also schedule tasks and operations so that data automatically imports at specific times. 

The architecture for the Adaptive Planning Integration framework uses this flow:

Adaptive Insights Applications Adaptive Planning and Consolidation, or Dashboards take the loaded data or metadata to update the model, accounts, sheets, transactions, or charts.
Adaptive Insights Integration Management


Loaders map the data or metadata from the source system to the corresponding destination in Adaptive Planning, and load it.

The staging area for data preparation of extracts from source systems. Manual or scheduled tasks to format and filter the data from the staging area to hand it off to Loaders.

Data Sources and Adapters that extract data from source systems.


Sources include Adaptive Planning, Workday, NetSuite, Salesforce, SAGE Intacct, MSDGP, and other cloud systems.

 On-premise Agents load data directly from Oracle or other on-site systems.

 Spreadsheets load directly from uploaded .XLSX files.

Business Users of Integration: Developers, Implementers, and Analysts

This architecture supports the workflows of three types of business users, with work shifting from one to the next in this order:

  1. Developers (only required for CCDS)
  2. Implementers
  3. Analysts

Each group gets a role with permissions in Adaptive Planning. Each role contributes to the overall Integration workflow. Most business users are Implementers and Analysts. Implementers configure data sources so that Analysts can run tasks.  If a Custom Could Data Source (CCDS) is required to pull data from a web-accessible system, a Developer user begins the workflow by writing JavaScript to import data. The workflow then shifts to an Implementer, and finally an Analyst.

Developer Workflow

Integration Developer Role Permissions

The Developer user is only needed when a Custom Cloud Data Source (CCDS) is required to import data from a web-accessible system. Developers receive the role of Integration Developer, and must be experienced javaScript programmers to make use of the APIs that pull data into Adaptive Planning.

  1. Define parameters
  2. Create scripts and test them
  3. Release the CCDS to a data designer 

View the full CCDS workflow.

Implementer Workflow

Data Designer Role Permissions

The Implementer, with the Integration role of Data Designer, creates the data sources that Analysts use to run their tasks. Implementers select data from columns in tables, filter it, preview it, merge it with other data, and prepare it so that analysts can then run tasks on it. Implementers can also grant permissions to users or groups to execute tasks. This lets implementers restrict lower-level data entry staff to executing specific tasks without letting them access anything else.

If a CCDS is required, the Data Designer relies on the Integration Developer to first write and test JavaScript.

  1. Define data sources, including their transforms and mappings
  2. Create loaders
  3. Create tasks

Analyst Workflow

Integration Operator Role Permissions

Analyst users (often FP&A staff), with the role of Integration Operator, run manual or scheduled tasks to get data into Adaptive Planning. Analyst users can only see and execute tasks based on the launch permissions an Implementer user grants them.

  1. Run manual or scheduled tasks
  2. Manage notifications
  3. View the results in Adaptive Planning
  • Was this article helpful?