New York, NY 10036
The OneCloud Platform
OneCloud ensures that cloud and on-premise applications operate together. The platform's native connectivity to many of the most widely used enterprise performance management (EPM), business intelligence (BI), and resource management systems allows seamless connections between systems. OneCloud eliminates the challenges of integrating a hybrid mix of technologies that co-exist on premise and in the cloud. Key features of the OneCloud architecture include:
Self-service ability to control, view and run automated processes via web, mobile interfaces and messaging platforms (Slack).
CloudRunners and GroundRunners that natively integrate cloud and on-premise applications.
| OneCloud Anaplan BizApp
The OneCloud Anaplan BizApp provides Anaplan administrators and users the ability to automate complex workflows and integrations with Anaplan across a hybrid mix of on-premise relational technologies and cloud applications including Tableau, Salesforce, Workday, NetSuite and Google Drive. Additionally, the OneCloud Anaplan BizApp allows users to run Anaplan Actions and Processes as part of a workflow. In turn, this enables application owners to greatly enhance their ability to share and streamline data and tasks between Anaplan Models and other applications in a controllable, auditable, and scalable environment.
Later in this white paper, we will explore three possible use cases of the OneCloud Anaplan BizApp:
Automate the load of data to Anaplan from source systems.
Leverage Anaplan as a data source to automate data loads to a target system.
Pre-process data using OneCloud operations to facilitate the load of data into Anaplan.
But first lets provide a bit more background on the OneCloud platform.
(VP Financial Planning, Seagate)
Connect & Automate
"The OneCloud platform enabled our corporate planning team to be self-sufficient from day 1 to connect and automate our cloud and on-prem apps…the easiest go-live we’ve ever experienced."
OneCloud Anaplan BizApp
OneCloud is an integration and automation platform designed to boost end-user productivity and reduce the burden on IT.
OneCloud enables centralized orchestration to connect and automate on-premise and cloud technologies, resulting in seamless end-to-end processes. With its intuitive, code-free interface, and ability to integrate into messaging platforms, OneCloud creates a landscape that puts powerful automations into the hands of non-technical and technical users alike.
The focus of this whitepaper is to highlight specific OneCloud functionality that supports Anaplan. The intended audience are users and administrators of Anaplan.
To learn more about the OneCloud platform or other application specific support, please visit: www.onecloud.io
OneCloud allows non-technical users to easily connect & automate their applications.
OneCloud Chains are created by simply adding automation commands and setting parameter values.
In the example to the left, OneCloud directly loads data from Salesforce to Anaplan, executes an Anaplan process, and loads process log files to Google Drive based on conditional branching.
Step 2 - Add Commands to the Chain
The first command group loads data directly from Salesforce to a data template file in Anaplan and subsequently runs an Anaplan process to import the data.
Commands are the building blocks of OneCloud automation workflows (chains). A command is a single task that is pre-configured to perform an operation on a system. When building a command, the user links it with a connection in order to choose where the command is executed.
A linear sequence of commands that represents an automation workflow. Chains can be scheduled, run manually, or even triggered externally via the OneCloud API. Each chain allows a user to build commands based on conditional logic. Commands can also be grouped within a chain, and execute either serially or in parallel.
A connection consists of a resource (i.e. a server) that is pre-configured to run a certain type of command and the credentials associated with connection to a particular application (i.e. login information for a SaaS platform). Connections can be configured to use either a Linux or Windows environment. Commands are aware of which connections they need to run (for example, a command that can run only in a Windows environment), and cannot be created until an appropriate connection is configured.
Environments are used to manage the life-cycle of your chains. Chains can be moved between environments, and variables can be set per environment. The most common example is using a development environment to test your chain, and when you are happy with the results, you can promote the chain into a production environment.
Resources are files that are managed within the OneCloud platform. They be can attached to commands as inputs, and even support variable replacement for extensibility and re-usability throughout a user's workflows.
Runners are the agents that carry out commands and send the results to OneCloud. CloudRunners are managed by OneCloud, whereas GroundRunners operate within a user's the corporate firewall. Users control where commands are run by linking each connection to a particular runner.
In the context of OneCloud, variables are inputs that can be changed. Variables defined on a workspace can be used across chains that belong to that workspace, and variables defined in a chain can be used locally by the chain's commands. In addition, commands can use a variety of system-level (for example, current time) and metadata variables (chain name, environment, etc).
Outputs are artifacts from previous Commands and can have the following types: Strings, Integers, Lists, Dates, JSON, Maps, File. They will appear as variables in subsequent commands in a chain.
A grouping of related workflows that encapsulates multiple environments. In addition, workspaces can store variables that can be used within chains and commands. Lastly, connections are stored at the workspace level.
OneCloud Anaplan BizApp - Case Studies
Case Study I: Automating the Load of Source Data
Step 1 - Create a OneCloud Chain
Creating a OneCloud chain is the first step to setting up an automation workflow. Once the chain is setup, you can add commands, schedules, variables and triggers.
Loading data into Anaplan from source systems is critical for your connected planning journey. OneCloud provides the ability to automate this process on an hourly, nightly, weekly, or ad-hoc basis to ensure that your data is always where you want it when you want it. Automating these data loads is easy with OneCloud's out-of-the-box connectivity to source data systems including Salesforce, NetSuite, Tableau, Workday, relational and text files.
The following example explores how to sync data sourced from Salesforce into Anaplan. Additionally, you'll see OneCloud's conditional branching logic based on the output of the data load to send an email on error and load the process log files to Google Drive on warning.
Case Study I: Automating the Load of Source Data (cont'd)
Step 3 - Run the OneCloud Chain
Each Command in the Chain will execute creating an end-to-end OneCloud process.
When a Command executes, an end-user can view the live output of the running command with relevant and actionable insight such as the live completion status, the number of records or any warning and error conditions.
Branching Logic - On Warning
Alternatively, if any of the commands in the first group produce a warning log, the chain will follow the warning branch.
The first command in this group will upload any log files produced from the RUN ANAPLAN PROCESS command and upload to a folder in Google Drive.
The second command will send an email notification based on set properties To, From, Subject and Message.
Branching Logic - On Error
If any of the commands in the first group fail or produce an error log, the chain will run the command SEND ERROR EMAIL. This command is configured by setting properties such as To, From, Subject, Message, and attachments (such as the process log file).
Group 1 (cont'd)
The first command (pictured left) will load Account data from Salesforce directly into an Anaplan server file (template file) based on a simple SOQL query and defined Anaplan Workspace and Model parameters.
Similar to the first command, the second command in this group will load Opportunity data from Salesforce directly into an Anaplan server file based on a SOQL query and defined Anaplan Workspace and Model parameters.
The third command will run an Anaplan process that first creates and/or updates list values using the uploaded server files and then subsequently uses the same source server files to import into relevant modules.
Case Study I: Automating the Load of Source Data (cont'd)
Step 3 - Add Commands to the Chain
The first command will run the Anaplan export action that writes to a Server File in Anaplan.
The second command will then download the Anaplan Server File.
The last command will then extract the Anaplan metadata. The reason for this is so we can use the metadata to dynamically create the target relational database.
The second group of commands will interact with the target Oracle relational database. The first command will create the target table using a SQL statement dynamically generated based on the format of the Anaplan export action (an output from the prior command)
The last command will then insert into the Oracle table choosing the Anaplan download file as the data source, the chain variable as the target table, and the Relational Columns from the command Get Export Metadata as the target fields.
Case Study III: Add Row ID's to source data
The final command will use the Anaplan connection to upload the output of ADD ROW NUMBERS to an Anaplan server file.
Step 1 - Create a OneCloud Chain
Create a chain, RowIDs for Anaplan, that will hold three commands to complete the workflow.
Step 2 - Add Commands to the Chain
This command selects data from an Oracle database using a simple SQL statement.
Add Row Numbers
Add the second command by selecting Lightweight ETL > Transform > Add row numbers. Note that the input file will be the output from the previous command, RUN QUERY.
Step 1 - Create Anaplan Export Action
In order to push data from Anaplan to Oracle relational, first setup an Export Action within Anaplan to extract the desired data in tabular format.
Step 2 - Create a OneCloud Chain
Create a OneCloud chain and assign variables that will be used throughout the commands of the chain. The first variable will hold the name of the Anaplan export action. The second variable will hold the name of the target relational table.
Case Study II: Anaplan as a Data Source
Anaplan is an enriched source of data that is beneficial when used, and often required, to augment target systems. OneCloud streamlines this process by automating workflows that extract List or Module data from Anaplan and then push it to on-premise technologies or other cloud applications.
The following example leverages Anaplan as a data source and then automates the data load to an Oracle relational database.
When loading data to an Anaplan List and Module from the same source file it's imperative that the file contains a unique identifier. If the source data does not include a Unique ID, a popular mechanism is to just concatenate key columns in that file. But what if that concatenation goes over the 60 character limit or simply does not create a unique ID? With OneCloud's transformation functionality, you can simplify this process by adding a Row ID. OneCloud can also perform other transformations for tabular data including row and column filtering, find and replace, joining columns, splitting columns, inserting columns, and mapping headers.
The chain below highlights how you can dynamically add Row IDs to any data source to pre-process the data before loading into Anaplan.
Technical data subject to modification and delivery subject to availability. Any liability that the data and illustrations are complete, actual or correct is excluded. Designations may be trademarks and/or copyrights of the respective company, the use of which by third parties for their own purposes may infringe the rights of such owner.
List Export Actions
List Import Actions
Publish Date: 07.31.2018
Rev no: 01
The OneCloud Anaplan BizApp has three different Connection types and the following commands are available to connect and automate Anaplan with other applications supported by OneCloud. Each command has different parameter inputs and outputs that are relevant to the operation being performed. Please see http://docs.onecloud.io/ for more information.
All rights reserved, including intellectual property rights. Changes to technical data reserved. Delivery subject to availability. Any liability that the data and illustrations are complete, actual or correct is excluded. Designations may be trademarks and/or copyrights of the respective company, the use of which by third parties for their own purposes may infringe on the rights of such owner. For further information see http://www.onecloud.io
©2018 OneCloud, Inc
Get Export Metadata
Relational Upload (deprecated)
Salesforce Upload (deprecated)
Run Export Action
Run Import Action
More on the OneCloud Anaplan BizApp