Hi Shivam,
That is an excellent observation!
The reason it works automatically for Caller and Assignment Group in your scenario is likely because of Data Faceting (filtering based on results), not explicit cascading configuration.
Here is the technical difference:
1. Why it works for you (Facet/Data Source Filtering): If both of your filters are connected to the same Data Source (e.g., the Incident List), they act like Facets.
How it works: When you select a Caller, the Data Source updates and returns only the records for that user (let's say 5 incidents).
The Assignment Group filter then looks at those 5 remaining records and updates itself to show only the groups present in those specific records.
Conclusion: It "cascades" because the data result set got smaller, so the available options were reduced automatically.
2. When you need the "Manual State" method: The method I described in my previous reply is required when you want "Input-Based Cascading" without fetching data first, or for unrelated fields.
Example: Selecting a Country and then seeing a list of Cities.
Since "Country" and "City" are just lookup values (not incident records), picking a Country won't filter a list of Incidents instantly. You need the State Parameter to tell the City filter: "Hey, the user picked USA, please only load US Cities from the reference table."
Summary:
Automatic: Works if filters share the same Data Source and are filtering an existing list of records (Facet behavior).
Manual (State): Required for Reference Inputs, standalone dropdowns, or when filtering queries before the data is loaded.
If this clarifies the "How-To" for Workspace, please mark it as Accepted Solution.
Best regards,
Brandão.
