One condition of a partner resource's automatic-assignment setup. When a Lead, Opportunity or Appointment is created, the partner resources whose partner account (and optional branch) fit the record are tried in ascending Assignment Sequence Number order, with empty numbers first. Each candidate's Rule Success Criteria (exact text: All Rules Are Met or empty, Any Rule Is Met, Always (No Criteria)) combines its rules, and the first matching candidate's resource replaces the record's Executive. It never runs on edit, and it is skipped for a field that an active Process Studio assignment writes on create. Partner resource From and To dates, resource status and branch authorization are not checked. The entity is in no app: open it from the App Launcher. The shipped Partner Resource forms show neither the sequence number nor the success criteria, and they do not list these rules.
Fields
| Field | Label | Type | Required | What it does |
|---|
AssignmentType | Assignment Type | PickList | | A classification of the rule. Assignment never reads it, so it has no effect on which executive is picked. Values: Appointment. |
CreatedById | Created By | Lookup → UserAccount | Yes | |
CreatedDateTime | Created Date | DateAndTime | Yes | |
FieldName | Field Name | Text | | The internal name of the field on the record being created that the rule tests, for example Industry or NumberOfEmployees. Capitals do not matter. It is not the on-screen label. A name that is not a standard field of that record, including any custom field, makes the rule fail. |
FieldValue | Field Value | Text | | The value the record's field is compared with, written as text. Whole-number and date fields convert it, and the rule fails if it does not convert. Every other field, including amounts, picklists, yes/no (True or False) and lookups (the record ID), is compared as exact, case-sensitive text. |
Id | Id | Guid | Yes | |
ModifiedById | Modified By | Lookup → UserAccount | Yes | |
Name | Name | Text | Yes | A label for the rule, typed by hand. It is required and no number series fills it. |
Operation | Operation | PickList | | How the field and the value are compared. Assignment recognises only the stored values equals, notEqual, lessThan, greaterThan, lessOrEqual and greaterOrEqual. Greater and less work only on whole-number and date fields. The shipped option Equal stores the value Equal, which is none of these, so a rule saved with it always fails until an administrator adds options with the correct stored values. Values: Equal. |
OwnerId | Owner | Lookup → UserAccount | Yes | |
PartnerResourceId | Partner Resource | Lookup → PartnerResource | Yes | The partner resource (candidate) this rule belongs to. Its success criteria decides how this rule combines with the candidate's other rules. |
RecordTypeId | Record Type | Guid, hidden | | |
SequenceNumber | Sequence Number | Number | | A number for your own ordering of rules. Assignment does not read it: rules are combined by the partner resource's success criteria, not in sequence. |
UIProps | UI Props | Text | | |
UpdatedDateTime | Modified Date | DateAndTime | Yes | |
Actions
| Action | Label | Type | What it does |
|---|
Clone | Clone | ServerAction (Clone) | Create a copy of this record |
DeleteEntity | Delete | Delete | DeleteEntity |
DeleteHeader | Delete | Delete | DeleteHeader |
DeleteRow | Delete | Delete | DeleteRow |
EditEntity | Edit | Edit | Edit |
EditInLine | Edit | EditInline | EditInLine |
EditRow | Edit | Edit | EditRow |
New | New | New | New |
