Administering Cloud EPM: The Platform Beneath the Business Processes · Module 5 · Business Processes and Migration
What breaks
Lesson 60 of 201 · 2 min
Sequence first. "The migration did not work." Check in this order. One. Is the snapshot version compatible with the target environment? Two. Is the target the right business process type? Three. Did the import report warnings you skipped past? Four. Are the users provisioned in the target's identity domain? Five. Are role assignments in place in the target? Six. Are integrations pointing at the old environment? Then eight cases. One. "Snapshot will not import — version." Compatibility rules. Check before planning, not during cutover. Two. "Application migrated, nobody can log in." THIS IS NOT A FAILURE. IT IS THE EXPECTED STATE. Users are identity-domain-scoped and roles are separate. Plan the step — and tell the project manager it is a step, before somebody reports a successful migration as broken. Three. "We switched the business process and lost the application." No external backup. Lesson 4, ignored. Four. "EDM stopped accepting records…
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