One selection condition of a ClaimGenerationSetup, expressed as field path, operation and value with a sequence number. RulePredicate compiles the rows into a single dynamic-LINQ predicate that runs in SQL, combined either by the parent's RuleSuccessCriteria (AND/OR) or by its RuleSuccessCustomLogic formula over the sequence numbers; when the parent also sets FilterExpression, the two are ANDed together. Field names may walk navigations, so conditions like Scheme.IsClaimable or Invoice.Status are valid.
Fields
| Field | Label | Type | Required | What it does |
|---|
ClaimGenerationSetupId | Claim Generation Setup | Lookup → ClaimGenerationSetup | Yes | |
CreatedById | Created By | Lookup → UserAccount | Yes | |
CreatedDateTime | Created Date | DateAndTime | Yes | |
FieldName | Field Name | Text | Yes | The field on the setup's source entity this condition tests; navigation paths are allowed, which is how claimability is usually expressed as a condition on the related scheme rather than on the ledger row itself. The path is compiled into SQL, so it must resolve against the model, not just against the loaded object. |
FieldValue | Field Value | Text | | The comparison value, typed by inference rather than declaration — the literal 'null' (any casing) becomes a null comparison, 'true'/'false' become booleans, numeric and GUID-shaped strings are used unquoted, and everything else is treated as text. For the in and not-in operations this is a comma-separated list. |
ModifiedById | Modified By | Lookup → UserAccount | Yes | |
Name | Document Number | Text | Yes | |
Operation | Operation | PickList | Yes | The comparison used. Equals, not-equal, greater-than and less-than compare literally with type inference (true/false, numbers and GUIDs are recognised, everything else is quoted as a string); contains does a substring match forced to string; in and not-in expand a comma-separated value list into an OR chain. Values: Equals, Not Equal, Greater Than, Less Than, Contains, In, Not In. |
OwnerId | Owner | Lookup → UserAccount | Yes | |
SequenceNumber | Sequence | Number | Yes | Orders the rules and, more importantly, is the identifier the parent's custom-logic formula refers to. Two rules sharing a number make the formula ambiguous, and a number the formula references but that has no rule row makes the run fail. |
UpdatedDateTime | Modified Date | DateAndTime | Yes | |
Actions
| Action | Label | Type | What it does |
|---|
BulkDelete | Delete | Delete | Delete the selected records. |
Delete | Delete | Delete | Delete |
DeleteInList | Delete | Delete | Delete the record. |
Edit | Edit | Edit | Edit the ClaimGenerationSetupRule. |
EditInLine | Edit | EditInline | Edit inline. |
EditInList | Edit | EditInline | Edit inline in the list. |
New | New | New | Create a new ClaimGenerationSetupRule. |
NewInLine | Quick Add | NewInline | NewInLine |
