Alpha Filter Type Options are disabled

[Adithya]

While attempting to change the filter type in the filter options, it is disabled, and I cannot modify it. By default, it is set to “range,” which does not meet my requirements. I need a “select” option so users can choose a specific case type.

[Eldho]

@Irfan_Ali @vaibhav @Paul_Thomas please help

[doomedCode]

Hi @Adithya,
Let us understand the how the filter type is determined first, followed by explanation for your concerns.

How Filter Type Is Determined

Binding Types Overview

There are three binding contexts in which mapping properties appear. Each context defines a set of properties and their data types, from which we infer the appropriate Filter Type.

CO (Case Object) Binding

• Definition: Models created and maintained by users in the Workflow Studio’s Model editor.
• Structure Source: Dropdown options come directly from the properties defined in this model.
• Type Info: Every property in the model has an explicit data type (string, number, boolean, date).
• Filter Derivation: We map each data type to one (or in some cases two) predefined Filter Types (see Section 1.2).

Case Instance Binding

• Definition: A fixed, system-provided model representing the data structure of a case.
• Structure Source: The platform’s internal schema; not editable by users.
• Type Info: Predefined and read-only.
• Filter Derivation: Same mapping rules apply, but types come from the system model.

Task Instance Binding

• Definition: A fixed, system-provided model representing an individual task within a case.
• Structure Source: The platform’s internal task schema; read-only.
• Type Info: Predefined in the system.
• Filter Derivation: Identical mapping rules, based on the system task schema.

---

Mapping Property Types → Filter Types

Each mapping property is assigned one of these predefined Filter Types, based on its data type:

Property Type	Filter Type(s)	Behavior & Purpose	Common Examples
number	Range	Specify a minimum and/or maximum. Ideal for continuous or discrete numeric data.	Premium amount, Age, CID, Task ID
string	Search / Multi-select	- Search: Type-ahead lookup against free-text fields. - Multi-select: Choose from a known set.	Username (Search), Status (Multi-select)
boolean	Boolean	Multi-select to choose from True and False.	Active flag, Completed status
date	Date Range	Start and end dates for filtering within a timeline.	Created date, Birth date

Note: Properties of type array or object are not supported for filtering.

---

Your Reported Concerns

Filter Type for cid

1. Binding Context:
   • Comes from the Case Instance model (system-defined).
2. Property Definition:
   • In the Case Instance schema, the cid field is defined as a number.
3. Filter Result:
   • Because it’s numeric, the UI uses a Range filter for cid.
4. Implication:
   • Users can enter lower and upper bounds to locate cases by their numeric cid.

Utility of the caseType Filter

1. Data Relationship:
   • Each Alpha Project is associated with exactly one case type.
   • Therefore, all tasks, cases, and signals in the Case Manager UI share the same caseType for a given project.
2. Filter Redundancy:
   • Since the project context implicitly fixes caseType, offering it as a filter adds no value.

---

Let me know if you’d like further clarification or additional examples on any of these points.

[Adithya]

So to meet my current requirement I need to change it to CO in short .

In my CO there is cid as well

So technically i should be able to filter out and make it work right

But

It is not working is there anything more that i need to add or implement to make it work

[Eldho]

@Irfan_Ali @vaibhav @gaurav.pandey please help