You are here: Business Rules > Attached Rules > ReassignAllocations

ReassignAllocations

Description

The ReassignAllocations business rule is used to tell the system what funds to use in conjunction with Assignment. This can be used to apply all money into a defined fund. This is useful when the selection of allocation by the end user should be restricted. An allocation record is created when this rule is processed. The allocation record contains the fund the money is moving into. This business rule can also be used to pull all money from a specified fund into another fund.

Note:

This should be used in lieu of configuring any Allocation elements. Even if allocations tags are configured and selected in an activity, the attached ReassignAllocation business rules configuration takes precedence and applies money according to the business rule.
The Assignment Type when using ReassignAllocations should be a type that moves an entire amount of money, such as Apply or FullWithdrawal. An assignment type like ApplyByFund is expecting fund allocations (ie. ReassignAllocations business rule is for use with a generic Assignment Type such as Apply or FullWithdrawal, not for use with ApplyByFund).
ReassignAllocations writes to AsAllocation at the activity processing level. It will also overwrite the presence of the allocation element and any previous allocation records and writes the new records at the point the activity is saved.
Used with transactions like FullSurrender, AutoTransfer (where the money is moved from one fund to another), InitialPremium, etc.

ReassignAllocations Element/Attribute Table
Element/Tag	Definition	Attribute	Element/Attribute Value and Description
<ReassignAllocations>	The opening and closing tag for the business rule.
<From>	Optional element; - A SQL statement that locates the money that is to be moved from a fund is entered in the SQL<From> tag. Note: The amount passed in the <From> tag should be positive. It is converted to negative in the code. This tag is not always necessary as the money is not always moving from a fund. For example, in an Initial Premium transaction the premium amount is only moving to a fund. It was never established in a fund to be moved from, prior to the transaction.		Required element value; SQL Query to locate the fund where the money is taken from.
		PRORATA	Optional attribute; Yes/No Used to describe a proportionate allocation. A method of assigning an amount to a fraction, according to its share of the whole. Yes - the allocations after the ReassignAllocations is executed divides the percents according to the funds in the allocation list based upon their cash positions. Funds that are not in the allocation list should not be counted as part of the total value nor should they be inserted into the allocation list. No - Allocations will not be prorated.
<To>	Optional element;Used in transactions like FullSurrender, AutoTransfer and InitialPremium. Note: This element is used to indicate the fund where the money should be moved to.		Required element value; SQL Query to locate the fund where the money is moved to.
		PRORATA	Optional attribute; Yes/No Used to describe a proportionate allocation. A method of assigning an amount to a fraction, according to its share of the whole. Yes - the allocations after the ReassignAllocations is executed divides the percents according to the funds in the allocation list based upon their cash positions. Funds that are not in the allocation list should not be counted as part of the total value nor should they be inserted into the allocation list. No - Allocations will not be prorated.

XML Example

<ReassignAllocations>

<From>SELECT FundGUID, '01', -1 FROM AsFund WHERE FundGUID = '[DefaultAllocationFundGUID]'</From>

<To>SELECT FundGUID, '01', PercentInAllocation FROM AsAllocation WHERE TypeCode = '02' AND RelatedGUID = '[Policy:PolicyGUID]'</To>

</ReassignAllocations>

Schema Example

<ReassignAllocations>

<From PRORATA="[Yes/No]">[SQL]</From>

<To PRORATA="[Yes/No]">[SQL]</To>

</ReassignAllocations>