SubjectID definition and behaviour

General
, ,
1

Hi Team,

I wanted to clarify my understanding of SubjectID and SubjectType.

My understanding was that the the SubjectType reflected the ContextName of the interaction and the SubjectID would be the unique identifier of the Context.

for example if an inbound container request had a ContextName = Customer and a CustomerID as the SubjectID then the container response would return the same CustomerID as the SubjectID and the SubjectType would be the customer class.

Conversly if an inbound container request had a ContextName = Account and an AccountID as the SubjectID then the container response would return be the same AccountID as the SubjectID and the SubjectType would be the Account class.

However my tests don’t seem to show this. No matter the request payload the SubjectID returned is always a CustomerID and the SubjectType is always the Customer class.

Is this expected behaviour?

Regards,

Andrew

2

@AndrewW40 this is the expected behavior. The pySubjectID and pySubjectType will always reflect the Primary context class, which in your case is the Customer. Even if the ContextName is Account and the AccountID is provided, the SubjectID returned will be the CustomerID, and the SubjectType will be the Customer class.

:warning: This is a GenAI-powered tool. All generated answers require validation against the provided references.

MultiLevel Decisioning - Outbound Schedule