CloudWorks–This is how we use it - Part 5: Model-to-model
If you need a reminder on CloudWorks; go here.
Why we are excited
With the new CloudWorks release comes a long-awaited feature: “model-to-model" (or M2M) actions.
Until now, you had 2 options to automate Anaplan-to-Anaplan flows:
- Implement a third-party tool such as Anaplan Connect (requiring a server that can run Java)
- Use an ETL (involving an additional maintenance), and up until recently, CloudWorks supported Anaplan Actions involving file upload only
The new CloudWorks enhancement brings exciting changes:
- Trigger M2M actions directly from an Anaplan screen. Using Anaplan Connect or complex IT integrations are not mandatory.
- Schedule M2M actions for timely integration needs
This article gives an example on how to setup M2M in CloudWorks and achieve an even closer vision of Connected Planning.
NB: The following will not be applicable for models subject to ALM that are not in the same workspace than their DEV model.
This is currently under investigation.
Illustrating the use case: Data Hub to spoke model
Setting the stage
For this illustration, we will use the well-known models from the Level 2 certifications. In the training, you were asked to create two models, "Level 2 Supply Chain" and "Level 2 Data Hub."
In one of the processes, called "1. Build Geography Hierarchies," the goal is to generate the Geography hierarchies:
All the imports within this process are model-to-model actions (from the hub to the Supply Chain model).
Note: As best practices, we recommend to use saved views as source for your M2M models. It gives you more control on the data you share and can be easily amended (see Planual Rule 5.04-09).
For instance, the import 1.1 Build Region is based on the view called "Build Region" in the "SYS05 Region Details" module.
Setup M2M in CloudWorks
We will now leverage those actions and set up an integration with CloudWorks.
- Open CloudWorks via the Hamburger button (ensure you are an integration admin first)
- Go directly to “Integrations & Processes” (no need to create a connection)
- Select Process as the type of object to create
- Fill the drop-down button with the necessary information regarding the process to execute and click Create
- You now have a M2M process registered, and you can execute it by clicking on Run.
An ephemeral popup will appear on the right side of the page, stating “Started Integration.”
The blue icon means the task is queued and will be executed soon.
Once the integration is done, you will get the final status of the task.
What about scheduling?
As mentioned earlier, a great CloudWorks feature is its scheduler.
To generate one, simply go the tab called “Schedule” and click on “Create schedule.”
Enter the settings.
After clicking on “Save,” you created a Process with an “Active” scheduler mentioned in the “Status” column.
It means that from that moment, the task will be executed daily at 3 pm Paris time.
To deactivate that task, make sure you select “Deactivate” after clicking on the 3-dot button, as shown above.
With that example, we've shown how easy it is to manage data flow between Data Hubs and Spoke Models, or M2M flows.
Please take advantage of that new feature, and happy Connected Planning!
Got feedback on this content? Let us know in the comments below.
Contributing authors: Pavan Marpaka, Anna Miller, and Christophe Keomanivong.
@annejulie Thanks for the great article. Just wondering whether we can setup an email notification for email ids other than the creator of the integration in cloudworks.4
Thank you for your suggestion; It's on our roadmap!1
For now, one can create "rules" in one's email client to forward emails automatically.1
@annejulie also what about setting trigger frequency in minutes, we currently see hourly, daily, weekly and monthly available.
Another query regarding notification mechanism availability, in case of failed process ability to notify creator or group DL for their required intervention ?1
I see nebisht's comment about trigger frequency....she says she sees hourly but the most frequent that I see is daily. Why is this?0
@nebisht and @jakesachs
You can set up daily schedule at a specific time (hh:mm) - see the screenshot above for example.
If you want to trigger multiple integrations within the day, we recommend that you create multiple schedules.
Daily at 9:00, 9:30, 10:00, etc.
@nebisht please submit your suggestion on notification on the Idea Exchange1
Is there any documentation around user permissions and the service account set to run the actions? From what I see on Anapedia, it appears that the scheduled action runs under the account of the Tenant Administrator that created the schedule? Is that correct? So, that user would need to be a workspace admin and full permissions to all selective access, etc., like with AnaplanConnect? If I was looking for details in the model history, would I look for the changes showing under the Tenant Admin's email address?
Thanks in advance!
To setup and run integrations in CloudWorks, user needs to have the role of Integration Admin (does not need to be Workspace Admin). Integrations in CloudWorks are run (manually and scheduled) as a service. The runs appear in model history against a dummy user called "Internal (Full Access)" that represents the service.1