Administering Cloud EPM: The Platform Beneath the Business Processes · Module 13 · Running the Environment
Lab: build the calendar and set the rhythm
Lesson 158 of 201 · 2 min
An hour, and the first deliverable is the artifact the module is named for. Eight of them. A complete operating calendar for Northwind: daily, monthly, quarterly, annual — with the close-week overlay and AN OWNER PER ACTIVITY. Maintenance windows set per environment, justified against user working hours in both countries AND against the Module 11 automation schedule. A patch-handling routine: who reads readiness notes, when, what gets tested, who communicates. Appearance configured to make test and production unmistakable, with evidence. Idle session timeout set with a documented rationale and a named security decision-maker. Email sender, SPF and DKIM configured or fully specified, with a delivery test plan to a REAL user mailbox. An announcement drafted for an upcoming maintenance window, written for finance users. And a written note on the two-country working-hours conflict for the maintenance window, and how you resolved it. The acceptance criteria. THE CALENDAR HAS AN OWNER…
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.