Enhancement Release 12.11.0 -Pushing Package Revisions
Timeline
Pushing Package Revisions -Overview
The functionality to push package revisions to associated contracts has been enhanced with the following changes:
Enhanced design and layout
The UI will be updated with the following 3 tabs:
Eligible Contracts: List of contracts currently eligible for a package revision
Updated Contracts: List of contracts updated with the current package revision
Ineligible Contracts: List of contracts ineligible for a package revision
The contract lists will include the same information found in Contract search result
The UI has been improved with search and export functionality
Clients will have the ability to select which contracts they would like updated with the current revision
Clients will have the ability to auto-assign the updated contracts to the required party to fulfill the new requirements
Improved Layout
The column layout has been improved to standardization look and feel across the application.
The layout is same as the Contract>Search results and includes the following fields:
Application ID
Contract Language
Selling Code(s)
Advisor Name
Primary Party Name
Status
Current Party
Party Size
Last Modified Date
Health
Revision Version
Search & Export Functionality
Contracts can be searched based on the following criteria:
Application ID (partial search not available, client must enter the entire ID to find a match)
Selling Code (partial search)
Advisor Name (partial search)
Primary Party Name (partial search)
Revision version has been removed a search criteria as it was not compatible with the other searches. It will be addressed a future time through an isolated search or by allowing column sorting
Only one search criteria can be applied at a time (similar to search criteria in other areas of the application)
Contract lists can be exported into an excel file to be used a needed.
Note: All contracts visible on the screen will be exported, the export logic does not take into consideration whether a contract has been 'selected' or not
Note: If the user navigates away from the screen or to another tab, the selection criteria is not maintained
Eligible Contracts Tab
The Eligible Contracts tab has been created. It is populated with contracts which are:
Already associated to the package for which the new revision can be pushed
The client is assigned as the current party on the contract
The contract is in the same language as the package
Contracts in an active state (Active, Downgraded, Vested, Pending, isTerminating, isDowngrading)
Ability to Select Contracts
Clients have the option to select single, multiple or all eligible contracts ('select all') for which they would like to update with the new package revision.
This flexibility allows clients the option to select which contracts they would like to update and when, in order to provide great flexibility.
Note:
If a new search is completed the previous selection will be removed
If the user refreshes the page, or navigates to another tab, the selection will be removed
Update and Auto-Assignment
Functionality has been introduced to allow clients the option to automatically send the contract backwards to the party fulfilling the requirement(s)
This functionality is optional.
If 'Update Only' is selected, the contract will still be updated with the latest revision, but the client will remain as the Current Party on the contract
If 'Update and Send' is selected, the contract will be updated with the latest revision and assigned to the fulfilling party.
Error Handling
If for any reason a contract fails to be updated with a package revision or the contract fails to be auto-assigned (when selected) the system will make 3 attempts to update and if it unsuccessful, the change for that particular contract will be reverted.
The contract will remain in a 'selected state' in the Eligible tab. The remaining contracts which did not fail, will be updated as expected and moved to the Updated Contracts tab.
Note: if contracts are locked by another user, they will not successfully update.
Update Contracts Tab
Once a package revision has been pushed a contract, that contract will move from the Eligible to the Updated Contract list
Clients will be able to search and export record from this list
If the option to auto-assign the contract to the fulfilling party was selected, the Current Party will be updated to the fulfilling party in this tab
Ineligible Contracts Tab
Contracts in this tab include those:
Not currently assigned to the client
In a terminated state to which revisions cannot be pushed
In a different language than the package. This can occur due to Law 14 changes, when parties move to Quebec and the language on current and historical contracts are required to be changed to 'French'
Clients will be able to search and export records from this list and filter based on the ineligible reason
Maintenance Packages
Extension of the functionality to maintenance packages has been put on hold as the underlying logic for this package type is different and not compatible with the ability to push revisions without changing additional logic.
Go Live: February 26th, 2025
Ticket # | Summary | Description | Area of Impact |
|---|---|---|---|
SD-53955
| Pushing Revisions -Update & Auto-Assign Contracts | Developed the functionality to allow contracts to be auto-assigned to the fulfilling party based on client requirements. Clients have the option to either push revisions and auto-assign the contracts to the fulfilling part, or push the revisions, but keep the contract assignment as themselves in the event that there are additional changes they would like to make to other packages prior to sending the contract down. | Enhancement -Pushing Contract Revisions |
SD-65849 | Pushing Revisions -Error Handling | In the event that there of an error when sending a contract to a fulfilling party or pushing a revision, the affected contracts will be skipped to ensure that updates can be made to the other contracts. The affected contract will remain in the Eligible tab in a selected state and an error message will be displayed to inform the user. The successful contracts will be moved to the Updated tab. A retry mechanism has been introduced to automatically retry the affected contracts 3 times. | Enhancement -Pushing Contract Revisions |
SD-53206 | Pushing Revisions -Updated Tab | When a contract has been updated with the latest revision of a package it will be moved to the Updated Tab. If the user elected to assign the package to the fulfilling party when the revision was pushed, that will be reflected in the current party assignment on this tab. | Enhancement -Pushing Contract Revisions |
SD-54213 | Pushing Revisions -Updated Tab -Search | Contracts in the Updated Contracts Tab can be searched based on the following criteria:
Only one search criteria can be applied at a time (similar to search criteria in other areas of the application) It users navigate to another screen or tab, the search criteria will be removed and reset | Enhancement -Pushing Contract Revisions |
SD-54214 | Pushing Revisions -Updated Tab -Extract | Contracts displayed in the Updated Contracts tab can be exported at any time | Enhancement -Pushing Contract Revisions |
SD-53207 | Pushing Revisions -Ineligible Tab | Contracts which are ineligible for update will be listed in this tab. These include contracts which are:
| Enhancement -Pushing Contract Revisions |
SD-53956 | Pushing Revisions -Ineligible Tab -Search & Filter | Contracts in the Updated Contracts Tab can be searched based on the following criteria:
Only one search criteria can be applied at a time (similar to search criteria in other areas of the application) Contracts can also be filtered by ineligible reason
| Enhancement -Pushing Contract Revisions |
SD-54215 | Pushing Revisions -Ineligible Tab -Extract | Contracts displayed in the Ineligible Contracts tab can be exported at any time | Enhancement -Pushing Contract Revisions |
SD-65810 | Pushing Revisions -Search Logic | Search logic was improved to increase match rate for certain search criteria. This applies to all tabs (Eligible, Updated and Ineligible)
Revisions was taken out of the search logic and will be introduced at a later date with either an isolated search or through the use of column sorting | Enhancement -Pushing Contract Revisions |
SD-55474 | Pushing Revisions -Eligible Tab -Contracts Displayed | In certain scenarios some contracts were not displayed appropriately in the Eligible tab. This issue has been resolved. | Enhancement -Pushing Contract Revisions |
SD-66045 | Pushing Revisions -Eligible Tab -Error Message Displayed | An error message was being displayed when multiple versions of the same package was attached to the same contract. This applied to maintenance packages only. This issue has been resolved | Enhancement -Pushing Contract Revisions |
SD-65361 | CITS | Improvements were introduced to display document name in the response instead of just contract ID | CITS API |
SD-66095 | CITS | ProducerWithAppointment response was missing attachments for licence and E&O. This has been resolved | Technical -Internal |
SD-66327 | CITS | Create additional logging for CITS | Technical -Internal |
SD-65873 | Technical | Reduced Crawler logs (licence integration logs) to optimize the database | Technical -Internal |
SD-65875 | Technical | Purged Job Audit Log to optimize database | Technical -Internal |
SD-66261 | Technical | Purged PerformanceLog to optimize databae | Technical-Internal |