evaluateTermConditions
- Description
- This transaction evaluates whether a party is eligible for a product or product bundle, and enables you to determine the impact of potential changes on a given account. The criteria that are evaluated by this transaction are based on product terms and conditions, as well as additional information such as person details and contract details.
- Web Services
- Operation name: evaluateTermConditions
- Example
- John Smith wishes to close his Regular Checking account without actually closing his value package agreement. Use this transaction to determine the effect that this account closure will have on his Super Business banking product bundle.
- Usage information
- This transaction uses either the TermConditionId or the combination
of EntityName, InstancePk, and UsageType to retrieve the associated
term conditions. Optionally, this transaction can use party and contract
information, either stored within InfoSphere® MDM or otherwise, to determine eligibility.
This transaction works with the Term Condition Rules Framework. For more information about implementing and configuring the rules used within this framework, refer to the developer documentation about managing product terms and conditions.
- Preconditions
- The product term conditions must be defined within InfoSphere MDM.
The business rule must be associated with the term condition usage type, the term condition, or both.
- Mandatory input
- Either of the following:
- TermConditionId
or
- A combination of EntityName, InstancePK, and UsageType
- TermConditionId
- Inquiry levels
- Not applicable
- Filter values
- Not applicable
- Transaction behavior
- The transaction response includes a collection of evaluation outcomes for each term condition that was evaluated. The response states either 'Eligible' or 'Not Eligible', and also returns the term conditions, and any additional party or contract details, that the transaction used to complete its evaluation.
- Request message
- <TCRMTxType> evaluateTermConditions
<TCRMTxObject> TermConditionEvaluationInputBObj
<TCRMObject> TermConditionEvaluationInputBObj
with optional business objects (including multiples of each as required): - Response objects
- TermConditionEvaluationResultBObj with child business objects:
And optional business objects (including multiples of each as required):
- Special note
- Out of the box, this transaction supports TCRMPersonBObj and TCRMContractBObj. However, provisions have been made to enable this transaction to be extended to support any other business object using the built-in InfoSphere MDM extension framework.