Implementing Cloud Financials: From Empty Pod to Go-Live · Module 1 · The Financials Landscape
Navigating the application
Lesson 7 of 153 · 11 min
The home page and its parts: the navigator, the springboard, the global header. Then work areas — and the concept behind them, which is that they are organised by task rather than by module. That is why looking for a screen by the name of the module it belongs to often fails. Infolets are the tiles on a work area. You can add, remove and personalise them, and you generally should: the default set is rarely the right one for the job you actually do. Then personalisation that pays for itself — favourites, recent items, the watchlist — and where notifications and approvals surface. Search by task name rather than memorising navigation paths. Paths move between releases; task names are far stabler. A course that teaches you a click path teaches you something with an expiry date on it. Bookmark the Setup and Maintenance area before you leave this lesson.…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Implementing Cloud Financials: From Empty Pod to Go-Live, with a certificate on completion and a fourteen-day refund window.
In this module: Module 1 · The Financials Landscape
- 1The application family
- 2The data flow mapFree preview
- 3Navigating the application
- 4The Setup and Maintenance area
- 5Rapid vs. full implementation
- 6Working with a system integratorFree preview
- 7Lab: navigate the setup area
