Problem
The person relationship on workflow card activity records is always returned as {}. The actor's identity is only available by parsing their name out of the comment string — and only for some activity types (e.g. reassignment events contain no name at all).
Expected Behaviour
Populate the person relationship on WorkflowCardActivity records with the actor's Person ID, consistent with how person relationships are handled elsewhere in the People API.
Why It Matters
Building accountability reports and reassignment audit trails currently requires fragile string-parsing of comment text instead of clean structured data. Actor attribution completely disappears for certain action types (e.g. reassignment).
Current Workaround
Regex-parse the comment string for names where available. Fails silently for reassignment events and other actor-less comment types.
Problem
The
personrelationship on workflow card activity records is always returned as{}. The actor's identity is only available by parsing their name out of thecommentstring — and only for some activity types (e.g. reassignment events contain no name at all).Expected Behaviour
Populate the
personrelationship onWorkflowCardActivityrecords with the actor's Person ID, consistent with how person relationships are handled elsewhere in the People API.Why It Matters
Building accountability reports and reassignment audit trails currently requires fragile string-parsing of comment text instead of clean structured data. Actor attribution completely disappears for certain action types (e.g. reassignment).
Current Workaround
Regex-parse the comment string for names where available. Fails silently for reassignment events and other actor-less comment types.