-
Notifications
You must be signed in to change notification settings - Fork 97
Georgina Tarres CDM Event Model - Termination for Schedules #4123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Georgina Tarres CDM Event Model - Termination for Schedules #4123
Conversation
CDM Event Model - Termination for SchedulesBackground When a termination applies to a quantity schedule, all the dated values from the effective period onwards should be set to zero. What is being released? The The period from which the change should take effect is determined using the Mappings The mapping from the FpML termination effective date has been added to the function Review Directions Changes can be reviewed in PR: #4123 Note This comment was generated via Rosetta. |
✅ Deploy Preview for finos-cdm ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
This PR replaces PR #4001 (mappings added and conflicts solved). |
|
@CDM-ReleaseManagement-OT the code was updated to the last version, but the build appears to be still failing. Could you please assist us in resolving this? Thanks in advance, |
|
Superseded by #4144 |
rosetta-source/src/main/rosetta/product-common-settlement-func.rosetta
Outdated
Show resolved
Hide resolved
|
What is being released? Minor style improvements. Note This comment was generated via Rosetta. |
Event Model - Termination for SchedulesBackground Previously, when a termination applied to a quantity schedule, the model did not correctly update all dated values following the termination’s effective period. As a result, quantities after the termination date could still retain non-zero values. To address this, the logic has been improved so that any dated values from the effective period onward are correctly set to zero when a termination occurs. What is being released? The The period from which the change should take effect is determined using the Mappings The mapping from the FpML termination effective date has been added to the function Review Directions Changes can be reviewed in PR: #4123 |
|
What is being released? fixed bug for multiple quantities. Note This comment was generated via Rosetta. |
No description provided.