TM Forum Community

Hi Mahendra,

Default behaviour with query string is ANDED

To retrieve trouble tickets where dateTime is greater than 2013-04-20 and less than 2017-04-20:

GET /api/troubleTicket?dateTime>2013-04-20&dateTime<2017-04-20

OR condition (ORING)

To retrieve trouble tickets where dateTime is less than 2013-04-20 OR less than 2017-04-20:

GET /api/troubleTicket?dateTime<2013-04-20;dateTime<2017-04-20

According to TMF guidelines, when customerId and siteName are provided together, the API must return results only if both attributes exactly match the provided values (AND + exact match). Partial/LIKE matching is not standard unless explicitly requested using regex operators as per above table.

Refer TMF630 for more details

Great summary by Subhanshu. To add a bit more context from an implementation and certification standpoint:

1. Certification: Stick to Exact Match by default. TMF Conformance Test Kits (CTK) expect strict matches; returning partial results when an exact string is provided may cause the API to fail compliance testing.

2. The 'AND' Logic: This is standard across all TMF entities. If you need an 'OR' condition (e.g., sites for Customer A OR Customer B), the standard syntax uses the semicolon: ?customerId=A;customerId=B.

3. Partial Matches: If your users need a 'LIKE' match, consider supporting the .regex or wildcard suffix as an extension, rather than making it the default behavior. This keeps the API 'Standard' but flexible."