LEARN. PRACTICE. GROW.Concept and mechanism
Scope identifies the application and bounds access to artifacts and resources. It is more than a code folder: a cross-application call may depend on table access, Script Include availability, and cross-scope authorization. In the application record, Runtime Access Tracking in Enforcing mode records requests and requires authorization before permitting them. Tracking and Enforcing should not be confused. Restricting the tables displayed during design also does not replace runtime control. Define small contracts for external consumers, specifying operations, data, and errors. Dependencies should include components actually used, including references made through scripts, to avoid an application that works only because development already has everything installed.
Guided application
A module is a navigation entry. Select the link type according to the task: opening a filtered list differs from opening a new record. Confirm table, view, filter, Active state, and roles. Override application menu roles permits an exception to the menu role while retaining the module’s own requirements. Use relative links for internal destinations; an absolute development URL can travel with the application into production and send operators to the wrong environment. During a Lisbon–Paris handover, check the link using an operator’s identity and an unauthorized user. Navigation should make work easier; data protection needs its own rules and separate evidence.
A promoted module opens development: inspect its absolute destination before changing permissions.
Common pitfalls
Scope treated as universal authorization; filter treated as ACL; assumed dependencies.
Related topics: Needs, data, and design · Forms and client/server logic · Security and access contracts
Portable links and explicit contracts reduce promotion failures.
Reference: Application Navigator category: module configuration · CAD blueprint January 2026