The automated assessment for KYC significance is done based on the KYCSignificantDecisionLogic rule that applies to the PegaFS-Data-PartypartyXref class and is requested while adding a related party. Based on the assessment, the bKYCSignificant property is either set to true or false.

While the preconfigured logic for assessing this flag typically covers most regular cases, there might be some situations where you may want to tune the automated assessment. To update the KYC significance logic, perform the following steps.

1. In the navigation pane of Dev Studio, click Records.
2. Expand the Decision category, and then click Decision Table.
3. In the Decision Table tab, search for and select the KYCSignificantDecisionLogic decision table.
4. In the Table tab, add new or update existing conditions return the true value based on your custom logic.
5. Click Save.

Parties are classified as deemed controlling based on the rule RelevantPartyDecision that applies to the PegaFS-Data-PartypartyXref class, which the system invokes while adding a related party. Based on the assessment, the IsDeemedControlling property is either set to true or false. The system persists the property in the pp_IsDeemedControlling column of the fsf_partypartyxref during the customer data synchronization.

While the preconfigured logic for assessing this flag typically covers most regular cases, there might be some situations where the Relationship Manager might need to override the automated assessment. To set the IsDeemedControlling to true or false, perform the following steps.

1. In the navigation pane of Dev Studio, click Records.
2. Expand the Decision category, and then click Decision Table.
3. In the Decision Table tab, search for and select the RelevantPartyDecision decision table.
4. In the Table tab, set the IsDeemedControlling property to false.
5. Click Save.