This means you don’t have to duplicate rules for each possible role an ontology might take up. You can simply combine all possible roles for the ontology into one declaration.
This makes it easier to configure conditions.
A bank is onboarding a trust, which involves many different people with different roles and responsibilities.
Let’s focus on two of the people who will be involved in this case: one is a settlor of the trust, the other a beneficiary of the trust.
The bank’s regulations require that the onboarding process for trusts always includes an assessment of the risk profile of both settlors and beneficiaries. For that purpose, the document ‘Client Risk Calculation (trusts)’, has been added to the bank’s atfinity system.
Without Role Choices, the bank would have to create one document ‘Client Risk Calculation (trusts)’ for the settlor in the case, with the condition
p is Person, Settlor
attached to it, and a duplicate for the beneficiary, with the condition
p is Person, BeneficiaryOfTrust
Using Role Choices, the need for duplicates like this has vanished. Instead, the bank's atfinity configurer can write a single rule for the document, which covers both trust settlors and beneficiaries.
That rule is:
p is Person, Settlor or BeneficiaryOfTrust
The document will show up for either of these roles.