Create a subscription

Combination of TargetId + Entity + Op must be unique.

Filter operators:

Operators applied to field values Supported field types: string, bool, int, float

Syntax: "field-name": { "operator": "field-value" }

$EQ    => equal
$NE    => not equal
$GT    => greater than
$GE    => greater than or equal
$LT    => lower than
$LE    => lower than or equal
$IN    => in (list of values)
$NIN   => not in (list of values)
$LIKE  => like (with % as the only possible wildcard)
$NLIKE => not like (with % as the only possible wildcard)

Operators applied to field names

Syntax: "operator": "field-name"

$EXISTS  => field exists in either Original or New data sections
$NEXISTS => field does not exist in both Original and New data sections

Note about User Defined Fields (UDFs):

In the Maximizer CRM, UDFs can be referred to by using three different notations:

Udf/$TYPEID(xx) => xx represents an unique integer identifier of the Udf field
Udf/$NAME(nn)   => nn represents the name of the Udf field
Udf/$TAG(tt)    => tt represents the tag of the Udf field (for internal use only)

As for events, the UDFs are always generated with the default Udf/$TYPEID notation.

This means we cannot use the other notations to create filters for events containing UDFs, as they won't be represented that way in the event and there will be no match.

If you want to create a filter for a UDF, you must use the Udf/$TYPEID notation. To find out the actual TypeId for the UDF you want to filter, you can use Octopus API to read the object definition using the Metadata/Schema search. Please refer to the Developer Portal for more details on how to use the Octopus API for this purpose.