In OutSystems 11 a dependency is considered weak only when the consumer doesn’t compile any executable code that must call the producer at runtime. Elements that are used solely for design-time metadata (e.g., Static Entities, Structures, Screens used only as type definitions) can therefore become weak dependencies. Referencing any executable Action, however, forces Service Studio to generate a direct runtime call, which always creates a strong dependency. Server Actions are executable code units that run on the server; consequently they can never be tagged as weak dependencies. Hence option C (Server Actions) is the only element in the list that is not eligible to become a weak dependency in OS11.

A. Screens – If no Navigate-To or entry reference exists, the dependency is only design-time and becomes weak.

B. Static Entities – Used merely as literal values, they compile into constants and the reference is weak.

D. Database Entities – When used only for type definition (e.g., StructureFromEntity), dependency is weak.

E. Service Actions – Behave like Server Actions but may be referenced only for default output structure, allowing weak dependency when not invoked.

F. Local Storage Entities – Similar to database entities; type-only usage leads to weak dependency.

G. Structures – Purely design-time type information; if no records are instantiated, dependency is weak.

1. OutSystems Documentation v11

“Dependencies: Weak vs. Strong Dependencies”

paras 3-4 (docs.outsystems.com/11).

2. OutSystems 11 Service Studio

Help > Manage Dependencies Window

table “Elements that always create strong dependencies”

note on Actions (build version 11.14).

3. OutSystems Training – Development Fundamentals

Module “Decoupling Architecture”

slide 12 “Actions always create strong dependencies” (Training portal course ID DF-110).

4. OutSystems Architecture Guideline eBook v11

section 4.2 “Weak References”

pg 27-28 (OutSystems Engineers

2019).