Symptom
In SAP C4C, visibility rules for Mashups are evaluated only once during the initial loading of the UI view (for example, when the Ticket TI view is opened).
These rules are not dynamically re-evaluated when field values or conditions change while the user is already inside the view.
Environment
SAP Cloud For Customer
Reproducing the Issue
-
Open the Overview view.
-
Verify that a visibility rule is configured to display the mashup only when a specific status value is met.
-
Open a record whose status does not meet the visibility condition.
-
Change the status so that it meets the visibility condition.
-
Observe that the mashup does not become visible immediately after the status change.
-
Refresh or reload the view, and confirm that the mashup is displayed.
Cause
When a visibility rule is created based on certain conditions (status, category, custom fields, etc.), the system:
- Evaluates the rule at view initialization
- Determines whether the mashup should be visible or hidden
- Renders the UI accordingly
During runtime, when the ticket data changes (for example, a status update or field modification inside the TI view), the UI framework does not trigger a re-render or re-evaluation of mashup visibility rules. This is because:
- Mashups are treated as static UI components once loaded
- Visibility rules are part of the view metadata, not event-driven logic
- The C4C UI client uses cached context data for performance reasons
Resolution
As a result, even though the underlying condition changes, the mashup’s visibility state remains the same until the view is reloaded.
In SAP C4C, mashup visibility rules are not dynamic at runtime, and there is no supported configuration, scripting, or SDK option to force a mashup to re-evaluate its visibility when field values change inside the same TI view.
Keywords
SAP C4C, mashup visibility, UI rules, ticket status, static UI components, visibility evaluation, refresh view, dynamic updates, cached context data, metadata rules. , KBA , AP-RC-UIF , C4C UI Framework , Problem
SAP Knowledge Base Article - Public