Administering Cloud EPM: The Platform Beneath the Business Processes · Module 5 · Business Processes and Migration
Switching business processes
Lesson 54 of 201 · 11 min
When you would do this — repurposing an environment, correcting a mistake, a change in plan. Then the pre-switch checklist: backup taken and externally stored, users notified, integrations disconnected. Perform the switch, show the resulting empty environment, and recreate a business process in it. THIS REMOVES WHAT IS THERE. Said plainly and more than once. Back up externally first. The most common LEGITIMATE reason is a training or development environment being repurposed. The most common illegitimate one is somebody creating the wrong thing in a hurry. Confirm the environment from its URL before acting. Module 4's habit, again.
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Administering Cloud EPM: The Platform Beneath the Business Processes, with a certificate on completion and a fourteen-day refund window.
In this module: Module 5 · Business Processes and Migration
- 1One environment, one business process
- 2Creating from the Standard landing page
- 3Creating from the Enterprise landing page
- 4Switching business processes
- 5Migration: the concepts
- 6Migration paths by business process
- 7Performing a migration
- 8Transitioning the data management business process to standalone
- 9Essbase in Cloud EPM
- 10What breaks
- 11Lab: create, migrate, and write the plan