return : CommandResponse
| Property Name | Property Value | Property Description |
|---|---|---|
| Login | String | |
| Filters | {AiResponseRequiredWorkOrdersFilters object reference} | Field -> supported filter operator(s), in the MCP ConditionOperator vocabulary (Equal / Contains / In / GreaterThan / LessThan). This is what AiResponseRequiredWorkOrdersFilters is actually capable of today; it's the contract a caller (the MCP filter mapper) should map onto - not every operator listed here is necessarily wired up on the MCP side yet. provider_name : Contains - substring match, via ProviderName Equal / In - exact match by id, via ProviderNames -> ProviderIds customer_name : Contains - substring match, via CustomerName Equal / In - exact match by id, via CustomerNames -> CustomerIds work_zone_name : Contains - substring match, via WorkZoneName Equal / In - exact match by id, via WorkZoneNames -> WorkZoneIds wo_priority : Contains - substring match, via PriorityName Equal / In - exact match by id, via PriorityNames -> PriorityIds wo_number : Equal only - WoNumber goes through SqlUtl.EscapeForLike with no surrounding wildcards, i.e. an exact match despite the LIKE-shaped filter wo_status : Equal / In - exact match against one or more ids, via StatusIds wo_due_date : GreaterThan (DueDateAfter) / LessThan (DueDateBefore) - range, no Equal/In A single value for provider_name/customer_name/work_zone_name/wo_priority still resolves through the singular Name field (substring match); only 2+ values, or an explicit "in", should route through the Names/*Ids pair - see AiResponseRequiredWorkOrdersConfigurator.ApplyFilters for the exact branching. |
| SortBy | String | |
| SortDirection | String | |
| Take | Integer or NULL | |
| Skip | Integer or NULL |