pub struct DynamicGroupProcessHandleMembership {
pub comment: Value,
pub group_member_fields: Option<BTreeMap<String, Value>>,
pub group_member_status: Value,
pub group_type_role_id: Value,
pub member_end_date: Value,
pub member_start_date: Value,
pub extra: Map<String, Value>,
}Expand description
Leaving out a value or setting it to null is handled identically: When creating a membership the default value is used, when updating a membership the value is left unchanged. Target groupMemberStatus none requests deletion of an existing membership. For queryResultOnly, use an actual membership state to create a membership.
Fields§
§comment: ValueOmit or use null for context-dependent fallback (default on creation, unchanged on update). {unchanged: true} preserves a value; {default: true} requests the process default. Use a scalar or {value: …} for an explicit value. An empty object passes request schema validation but fails when the rules execute. Explicit null cannot reliably clear every membership field in the current processor.
group_member_fields: Option<BTreeMap<String, Value>>Membership-field values keyed by numeric field ID or reference name. The request schema only accepts lowercase letters, digits and hyphens as keys; field existence and value semantics are resolved during refresh.
group_member_status: ValueAllowed values: active, none, requested, to_delete, waiting.
group_type_role_id: ValueGroup-type role ID, or a value-control object. It must be valid for this group when executed; the request schema does not resolve it.
member_end_date: ValueOmit or use null for context-dependent fallback (default on creation, unchanged on update). {unchanged: true} preserves a value; {default: true} requests the process default. Use a scalar or {value: …} for an explicit value. An empty object passes request schema validation but fails when the rules execute. Explicit null cannot reliably clear every membership field in the current processor.
member_start_date: ValueOmit or use null for context-dependent fallback (default on creation, unchanged on update). {unchanged: true} preserves a value; {default: true} requests the process default. Use a scalar or {value: …} for an explicit value. An empty object passes request schema validation but fails when the rules execute. Explicit null cannot reliably clear every membership field in the current processor.
extra: Map<String, Value>Fields not described by the spec, e.g. instance-specific DB fields.