Thanks again for your time this evening. I hope we gained a mutual understanding of our needs at OSPC. In case it wasn't clear, what I want is to be able to define the [value] for the arbitrary [key] in a URI string, to the conditions for any widget. Per our discussion, the slicer approach won't work because it results in overburdensome workloads, from both engineering and maintenance perspectives - we simply can't create a unique slicer for every possible field we might want to filter upon.

RFC 3986 explains the standard.

Taking the 3986 example as a framework, one of ours might be:

?key=132654989&key2=pc_maintenance.

So we want this functionality in the widget filter conditions:

But ideally we would prefer:

?invoiceID=132654989&service=pc_maintenance

RFC 3986 — Uniform Resource Identifier (URI): Generic Syntax

This is the core document that defines how URLs/URIs are structured, including query parameters.

What it covers (plain English):

URL structure

?key=value&key2=value2 format

Rules for arbitrary parameters

Official reference:

RFC 3986 (IETF)

Section 3.4 — Query

This section explicitly defines URL query parameters.