There are 3 common scenarios for Sharing a Style Guide. Which of the below is not part of th scenario.

The scenario described in option B is architecturally incorrect for achieving a common, shared login flow. For components like a menu or login flow to be common and easily updatable across multiple applications, they must be defined in a shared, referenced module, such as a Custom Theme. A Custom Template is only used to create a new application; any subsequent changes to the template are not propagated to the applications already created from it. Therefore, placing a common login flow in a template would prevent centralized updates and break the "common" requirement. The other options describe valid, standard OutSystems architectural patterns for sharing UI components.

A. This is a valid scenario for an Intranet where a common authentication (SSO) is required, but each application has its own distinct navigation menu.

C. This correctly describes a pattern for fully independent applications. A custom template provides a consistent starting point, but each application then manages its own UI components without sharing.

D. This is the standard and most common pattern for a portal or a suite of enterprise applications, ensuring a fully consistent user experience by sharing both menu and login via a central theme.

1. OutSystems Official Documentation

"Share a Style Guide Across Apps": This document explicitly outlines the three common scenarios for sharing UI.

Scenario: Portal - Common Menu and Login: "To have a common menu and login for all your apps

define the Menu and Login blocks in the Theme of your Style Guide." This directly supports option D as a valid pattern and contradicts the implementation in option B.

Scenario: Intranet - Common Login

but own Menu: "To have a common login

but an app-specific menu

define the Login block in the Theme of your Style Guide. The Menu block should be defined in the app itself." This validates option A.

Scenario: Independent Apps - Own Menu and Login: "If you want to have a set of apps that are completely independent

with their own menu and login

you can create a custom app template." This validates option C.

2. OutSystems Official Documentation

"Create and use a custom screen template": This document clarifies the purpose of templates. It states

"A Screen Template is a starter for creating new Screens... When you use a template to create a new Screen

OutSystems copies the template's content..." This highlights that templates are for one-time creation

not for ongoing

shared dependencies

which is why option B is an incorrect pattern for a common login.