7.0.0-dev.91
Product Model - Updating stubPeriodType cardinality
Background
The cardinality of stubPeriodType inside CalculationPeriodDates is currently 0..1 which prevents specifying the stub type when a leg contains two stubs. The cardinality should be changed from 0..1 to 0..2. A cardinality of 2 enables the stub type to be specified for both the initial and final stubs simultaneously.
What is being released?
The cardinality of stubPeriodType inside CalculationPeriodDates has been updated from 0..1 to 0..2.
Review Directions
The changes can be reviewed in PR: #4444
Product Model - Updating Qualification Functions to Handle only exists Syntax
Background
In 7 dev, the only exists syntax does not apply to the choice Payout -> SettlementPayout, because there is always only one. Instead, only-element is used on the payout, which is incorrect, because if there is more than one payout then none will be set. The original intention was to allow for multiple of the same payout types.
What is being released?
Updating any previous instance of only-exist to use a function which checks whether only the payout in questions exists, allowing for multiple of the same payouts.
Review Directions
Changes can be reviewed in PR: #4430
Product & Event Model - Recall Provisions and Unscheduled Transfers
Background
There are several times during the lifecycle of a securities lending trade that cash and shares may need to be transferred between the lender and the borrower. Two of these scenarios - Returns and Recalls - happen on an ad-hoc basis, the timing of these transfers being decided by the lender or the borrower.
Returns happen during the term of a loan, or when the loan ends, as the borrower will need to return the securities to the lender, and the lender will need to return the collateral that they received against that loan to the borrower.
Recalls occur when an agent lender needs to recall the shares they have lent out on behalf of their clients, often required when the owner of the shares has sold them. To support these ad-hoc transfers the UnscheduledTransfer type is being introduced, as well as a new RecallProvision type where details of the recall criteria for a trade can be placed.
What is being released?
To support the entry of recall criteria the following enhancements have been made to the Product model:
- Addition of new
RecallProvisiontype, which includes attributes required to define a recall - Update to
TerminationProvisionto addRecallProvisionand update type conditions accordingly
To support the processing of transfers associated to returns or recalls the following enhancements have been made to the Event model:
- Addition of new
UnscheduledTransferEnumcontaining options for "Return" and "Recall" - Addition of new
UnscheduledTransfertype, which includestransferTypewhich uses the newUnscheduledTransferEnum - Update
TransferExpressionto now offerscheduledTransferand a newunscheduledTransferattributes - Move
priceTransferfromTransferExpressionto now be underUnscheduledTransfer - Update FpML ingestion mapping for
priceTransferto relocate tounscheduledTransfer -> priceTransfer
Review Directions
Changes can be reviewed in PR: #4397