MSAMM
Back to course

Administering Cloud EPM: The Platform Beneath the Business Processes · Module 13 · Running the Environment

Feature updates and readiness

Lesson 151 of 201 · 10 min

A monthly patch. Applied to test environments early in the month, and to production later. Advance notification for minor updates is short; for major updates it is longer. What that gap is for. It is your test window, and it is not optional. AN ORGANIZATION THAT DISCOVERS A CHANGE IN PRODUCTION HAS WASTED THE MECHANISM. The readiness information, and where it lives: what is new, what has changed in behaviour, what is fixed. The routine to build. Read the readiness notes when they publish. Identify anything affecting your business processes or your automation. Test in the test environment, during the gap. Communicate anything users will notice. And note it in the operating log. THIS IS THE ROUTINE THAT SEPARATES A PLATFORM THAT SURPRISES PEOPLE FROM ONE THAT DOES NOT. IT TAKES AN HOUR A MONTH. One more thing: feature opt-ins. Some changes are optional, and some become mandatory later. Track

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.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 13 · Running the Environment

  1. 1The operating calendar
  2. 2Daily maintenance
  3. 3Feature updates and readiness
  4. 4Content update scheduling
  5. 5Configuring appearance
  6. 6Session timeout and environment description
  7. 7Email: sender, SPF, DKIM, DMARC
  8. 8Announcements
  9. 9What breaks
  10. 10Lab: build the calendar and set the rhythm