Spring 2023 Release Notes
1. Preface
This is a living document, and its contents may be updated often. Any changes to the contents of this document are listed in the Change Record section. Make sure that you have the latest version for use.
The contents of this document are applicable to all the customers who have installed the latest version of Q2 OriginationSpring'23 release for the first time or have upgraded from an earlier version. You can access the release notes of the previous releases from the Q2 Customer Portalor Q2 Lending Help Center.
1.1 Purpose of this Document
This document provides information on the following for the Spring'23 release:
1.2 Intended Audience
The audience of this document includes business users, implementers, and system administrators.
1.3 Prerequisites for Use
This document assumes a basic knowledge of the product concepts, the product release, and the Salesforce platform.
2. Introduction
These release notes may be updated after the first release. Any changes to the contents of these release notes are listed in the Change Record section.
3. Installation Information
Contact your Q2 Professional Services team or the Customer Success team for information on the package dependency and installation order of the packages required to install and set up the latest version of Q2 Origination.
4. Technical Assistance
For all customers and partners of Q2 Software, Inc., our technical support team provides technical assistance. Q2 Software, Inc. customers are served via a dedicated support desk. Contracted customers are provided a sign-on to communicate with Q2 Software, Inc. technical support staff.
5. Upgrade Considerations
For information on the upgrade steps, see release-related steps in the Q2 Product Upgrade Guide.
6. System Performance
To view the SOD batch jobs performance statistics for Q2 Origination without customizations under test conditions, see the Q2 Performance Benchmarking Guide.
7. New Features and Enhancements
This section briefly describes the new features and enhancements added in the Spring'23 release of Q2 Origination.
For a detailed description of the new features and enhancements, see the following guides published over the Q2 Customer Portal:
- Q2 Origination User Guide
- Q2 Origination Administration Guide
7.1 The maximum character length for certain fields has been reduced to 32768 (Jira ID: PDRFF-1634/GD-7231)
Feature Description
If the maximum character length of certain custom fields such as Large Text Area or the Rich Text Area that you may have added in an org exceeds the allowed limit, then the upgrade or installation fails with the following error:
"Error: <(objectname.fieldname)> Custom long text area field limit exceeded.
Details: Either you or your organization has exceeded the maximum number of custom long text area fields allowed in the system. Please contact your administrator for more information."
To mitigate this issue, the maximum character length for the following fields has been reduced to 32768:
genesis_Borrowing_Entity_Summary_c
genesis_Financial_Information_c
genesis_Loan_Review_Summary_c
genesis_Risk_Assessment_c
7.2 Configuration to store execution criteria results (Jira ID: GD-7380)
Feature Description
With this release, there is a configuration provided for each FI to decide if the execution criteria results need to be logged.
This will give FIs the necessary flexibility to decide not to store the results and reduce Salesforce storage.
7.3 Enhanced Send Email functionality on the Documents page (Jira ID: GD-7295)
Feature Description
With this release, when users click on "Send Email" on the Documents page, the emails will be sent to the respective parties associated with the documents.
7.4 Configuration to set Policy Condition status for rejected documents (Jira ID: GD-7269)
Feature Description
A configuration has been introduced to determine the status of the policy condition when the associated documents are rejected. FIs will have the option to decide if the policy condition should have the status as Exception or Rejected.
7.5 Bulk Asset Upload for Lease applications (Jira ID: GD-7176)
Feature Description
In Lease applications, users will now be able to upload a CSV file to create Asset records on an application in bulk.
When the CSV file is uploaded, users will have the option to map the fields from the CSV file to Q2 Originate fields.
7.6 Clone application (Jira ID: GD-7230, GD-7232)
Feature Description
FIs need to support the cloning of applications for multiple use cases. Some of the use cases are:
Reduce data entry in a business Loan/Lease application, where repeat business is involved.
Create drawdown/takedown applications multiple times with exact same details.
Create a clone application to initiate contract creation for a subset of assets underwritten at a deal level.
With this release, users can now clone Loan/Lease Applications.
There will be a configuration provided to decide the following:
Statuses in which the Clone Application transaction should be allowed.
Set of objects and fields that must be cloned as part of the clone transaction.
7.7 Drawdown Condition on package/deal applications (Jira ID: GD-7138)
Feature Description
Prior to this release, there were five pre-defined drawdown conditions that were associated with the package applications.
Not all of these drawdown conditions were applicable to all package/deal applications. With this release, users can now select and add conditions manually.
7.8 Support for Balloon Payment calculation (Jira ID: GD-6331)
Feature Description
Prior to this release, Balloon payment calculation assumed that the final payment on a loan is equal to the balloon payment.
With this release, there are two options provided to the user for Balloon Payment:
Balloon Amount Including Principal and Interest
Balloon Amount Including Only Principal
Based on the selection, the payment schedule and balloon payment amount are calculated.
7.9 Rule Framework Enhancements (Jira ID: PD-1303)
Feature Description
This enhancement adds the ability to configure rules that can compare two fields within an object.
7.10 Task Management Enhancements (Jira ID: PD-1369, PD-1362, PD-1363, PD 1364)
Feature Description
The following Task Management enhancements have been made:
Claiming of multiple queue-configured tasks in one go.
Releasing queue configured task back to queue after a user has claimed the task.
Timestamps of claiming/releasing queue configured tasks to be stored, with support for creating reports.
Support for Queue admin.
Provide an entry point for queue-configured tasks in any application.
Filter the tasks based on applied filter criteria.
Ability to configure SLAs for Tasks.
Ability to generate notifications for Task SLAs.
7.11 Application Snapshot Export to PDF (Jira ID: PD-1392)
Feature Description
Adds the ability to export an Application Snapshot as a PDF.
8. Fixed Issues
For the details on the issues fixed in this release, see the Post Spring'23 Release section.
9. Known Issues
This section briefly describes the known issues in the Spring'23 release of Q2 Origination.
| Issue ID | Description | Workaround |
|---|---|---|
|
GD-7448 |
Exception task does not gray out when other users try to login. |
Not Applicable |
|
GD-7445 |
Skuid error -when click on the edit button in the party page. |
Not Applicable |
|
GD-7444 |
Multi picklist values are not visible - Questionnaire. |
Not Applicable |
| GD-7442 | 'Payment Schedule' should not be present for LOC application under Pricing Tab. |
Steps:
|
| GD-7437 | Display issues when open Task page and try to complete the tasks. | Not Applicable |
| GD-7431 | Cross Browser testing - Safari Issues (Monterey 15.6 )-Spring2023. | Not Applicable |
| GD-7427 | CLONE - System should not display selected product on change product option list. | Not Applicable |
| GD-7425 | Appraisal Bid is getting approved even when no bid amount is given. | Not Applicable |
| GD-7424 | Override on Vendor Points not working. | Not Applicable |
| GD-7408 | Score card issues. | Not Applicable |
| GD-7389 | Issues in Clone Application : Document, Policy Exception. | Not Applicable |
| GD-7379 | Error Message: 'Model 'Task' has unsaved changes. To update this model's data, you must first save or cancel the changes.' on opening Required Actions Page. | Not Applicable |
| GD-7245 | Legal Entity Type defaultly displaying when new contact is selected. | Not Applicable |
| GD-7205 | Line items are getting overlapped in PDF when common sizing toggle button is ON. | Not Applicable |
10. New Objects
The following table describes the objects added in the Spring'23 release of Q2 Origination:
For more details on the new objects, see Q2 Origination Data Dictionary Guide.
| Object Name | Field Name | Description |
|---|---|---|
| Application Clone Configuration | genesis__Application_Clone_Configuration__c | This is used to copy the component of current application to a new application as per defined configuration and the "Where Clause" is used as part of the query to fetch data. |
| Equipment Upload Template | genesis__Equipment_Upload_Template__c | This holds the header columns for bulk upload of file with sequence number. |
| Task History | clcommon__Task_History__c | This stores information about the task's history. |
| Task Junction | clcommon__Task_Junction__c | This is the junction between the Task object and its related child objects. |
| Queue Admin | clcommon__Queue_Admin__c | This stores the information of the queue admin. |
| Snapshot Progress Tracker | genesis__Snapshot_Progress_Tracker__c | This tracks the progress and status of the chained queueable jobs which run serially to export the snapshot to a PDF. |
11. Modified Objects
The following table describes the objects modified in the Spring'23 release of Q2 Origination:
For more details on the modified objects, see Q2 Origination Data Dictionary Guide.
| Object Name | Field Name | Description |
|---|---|---|
| Application (genesis__Applications__c) | Cloning Application Id (genesis__Cloning_Application_ID__c) |
This newly added field is a lookup field used to identify if the application is a cloned application or not. It also stores the cloning application ID or the ID of the application that is to be cloned. |
| Application (genesis__Applications__c) | Balloon Payment Type |
This newly added field is a picklist field used to describe the method to calculate balloon payments schedule. |
| Org Parameters (genesis__Org_Parameters__c) | Status to Enable Clone Application (genesis__Status_to_Enable_Clone_Application__c) | This newly added field is a text area field that provides status to enable clone application option. |
| Org Parameters (genesis__Org_Parameters__c) | Policy Condition Status for Documents |
This newly added field is a text field that provides Policy Condition Status for Rejected documents. If it is null, then by default we will use 'Rejected'. |
| Org Parameters (genesis__Org_Parameters__c) | Do not Store Execution Criteria Result (genesis__Do_not_Store_Execution_Criteria_Result__c) |
This newly added field is a checkbox field used to disable storage of records in the Execution Criteria Result object. |
| Lending Calculator (genesis__Lending_Calculator__c) | Balloon Payment Type (genesis__Balloon_Payment_Type__c) |
This newly added field is a text field used to describe the method to calculate balloon payments schedule. |
| Activity | clcommon__Task_Junction__c | This newly added field is a reference to the Task Junction object. |
12. New APIs
There are no new APIs added in the Spring'23 release of Q2 Origination.
For more details on the added or modified APIs, see Q2 Origination REST APIs Guide.
13. Modified APIs
There are no APIs modified in the Spring'23 release of Q2 Origination.
14. New Global Methods
The following table describes the global methods added in the Spring'23 release of Q2 Origination:
For more details on the added global methods, see Q2 Origination Global Methods Guide.
| Class Name | Global Method Name | Description |
|---|---|---|
| SkuidCloneApplication V1 |
cloneApplication |
This newly added method creates a new application that is a clone of the application that is passed in the method parameter. |
| PolicyCondition DefinitionsAPI Class |
savePolicyCondition |
This newly added method creates or updates Policy Condition definition for an application with the execution criteria. |
| PolicyCondition DefinitionsAPI Class |
savePolicyException |
This newly added method saves policy exception and evaluates the policy condition. |
| LoanDashBoard Class | claimQueue ConfiguredTasks |
This method is used for claiming one or more queue-configured tasks by that queue user. |
| LoanDashBoard Class | releaseTasksBack ToQueue |
This method is used for releasing one or more claimed queue-configured tasks back into the queue. |
| LoanDashBoard Class | getDueDateCurrent DateDiff |
This method calculates the difference between the current and task activity dates and returns the map serialized as a string of task ID to days difference. |
14.1 Modified Global Methods
There are no global methods modified in the Spring'23 release of Q2 Origination.
For more details on the modified global methods, see Q2 Origination Global Methods Guide.
15. Post Spring'23 Release
Follow this section for the details on the issues fixed in the patches on the Spring'23 release.
15.1 Issue fixed in the August 30, 2024 patch
15.1.1 An error is displayed on Collateral Analysis page (Jira ID: PDRFF-3324/GD-9056)
Fixed Version
CL Originate Skuid Extension Spring'23 (4.2008.23)
Issue Description
The Collateral Analysis page is not loading and the following error is displayed:
Apex heap size too large: 8996841 Resolution
This issue can be fixed by unpacking the CollateralAnalysis_Q2Originate page from Q2 Originate package.
15.2 Issue fixed in the December 29, 2023 patch
15.2.1 Some objects are not getting cloned while cloning an application (Jira ID: GD-8045)
Fixed Version
Q2 Origination: Spring'23 (4.2008.22)
Issue Description
To make a copy of an existing application, when a user clicks Clone Application, the information for the following objects are not getting copied to the new application:
Collateral
Questionnaire
Team Members
Drawdown Terms
Covenants
Resolution
This issue is fixed now as all the information is getting copied when cloning an application.
15.3 Issues fixed in the December 1, 2023 patch
15.3.1 Owner name of cloned applications is not getting updated correctly (Jira ID: PDRFF-2634/ GD-7979)
Fixed Version
Q2 Origination: Spring'23 (4.2008.21)
Issue Description
While cloning applications, the owner's name is getting updated with the original application's owner's name instead of the user's name who is cloning the application.
Resolution
This issue is fixed now as the user who is cloning the application becomes the owner of the cloned application.
15.4 Issues fixed in the October 31, 2023, patch
15.4.1 An error is displayed while saving a newly created rule (Jira ID: PDRFF-2520/GD-7929)
Fixed Version
This issue has been fixed in the following versions:
CL Common: Spring'23 (4.2004.19)
Issue Description
While saving a newly created rule with multiple rule conditions, the following error is displayed:
Maximum view state size limit (170KB) exceeded. Actual view state size for this page was 222.063KB
Resolution
This issue is fixed and no error is displayed while saving a newly created rule.
15.5 Issues fixed in the October 16, 2023, patch
15.5.1 An error is displayed on the Dynamic Queries page( Jira ID: PD-1558/PDRFF-2475)
Fixed Version
This issue has been fixed in the following versions:
CL Common: Spring'23 (4.2004.18)
Issue Description
When the Dynamic Queries page is opened, the following error is displayed
Maximum view state size limit (170KB) exceeded. Actual view state size for this page was 222.063KB
Resolution
This issue is fixed as no error is displayed on the Dynamic Queries page.
15.6 Enhancements made in the September 20, 2023, patches
15.6.1 Improved performance with FinCalc 4.0 (Jira ID: GD-7305)
Enhancement Versions
This enhancement is available in the following versions:
Q2 Origination Spring'23 (4.2008.17)
CL Common (4.2004.17)
CL Originate Skuid Extension Spring'23 (4.2008.17)
Enhancement Description
The Financial Calculator (FinCalc) has been improved and updated to a newer version, FinCalc 4.0, to achieve better performance by employing a new method that calculates the scheduled payment amounts more quickly. To further achieve better results, the scheduled payment amounts are rounded up after they have been calculated.
You can begin to utilize this new and enhanced version from the Spring'23 patch release. To begin utilizing FinCalc 4.0, you can specify this new version in the Financial Calculator Version field of the Org Parameters.
The system, however, continues to use the earlier version of FinCalc (even if you have selected the new version) only in scenarios where an application includes a Repayment Plan that has at least one Payment Type as Principal Only provided in any order with the Repayment Procedure selected as EMI or Flexible, as well as an application that has the Accrual Through Date type of accrual and an application that has a Flat interest type.
For more details on FinCalc 4.0, see the documentation: Financial Calculator Version 4.0 - FinCalc 4.0
15.7 Issues fixed in the August 14, 2023, patches
15.7.1 Document categories are not getting deleted correctly (Jira ID: GD-7726)
Fixed Version
This issue has been fixed in the following versions:
Q2 Origination: Spring'23 (4.2008.17)
CL Originate Skuid Extension: Spring'23 (4.2008.17)
Issue Description
When the document category criteria is not getting satisfied for one child document category for a parent document category having two or more child document categories, the document category is getting deleted along with Parent Document Category, resulting in delinking of the other document categories and parent document category field gets updated as null
Example to understand this issue
Let us configure the document definition by performing the following steps:
Create a document definition with the Document Definition Name as Identity Documents and keep the Document Type field empty.
-
Create two document definition with the following details:
First document definition:
Document Definition Name: Identity Documents Child1
Document Type: Identity Documents
Criteria Details: Requested Loan Amount > $8000.
Second document definition:
Document Definition Name: Identity Documents Child2
Document Type: Identity Documents
Criteria Details: Requested Loan Amount > $10,000.
Note:Marking the Document Type field as Identity Documents, creates a parent-child relationship between the created document categories.
In this scenario:
Parent Document Category is Identity Documents.
Child document categories are Identity Documents Child1 and Identity Documents Child2.
-
Create an application (ABC) with Requested Loan Amount as $12,000.
As per the above defined criteria details, this application satisfies both the document categories.
-
Verify the created document definitions in the DOCUMENTS tab or Developer Console.
It must display the following created document categories:
Identity Documents
Identity Documents Child1
Identity Documents Child2
The Parent Category Name field must display as Identity Documents for the Identity Documents Child1 and Identity Documents Child2 document categories.
-
Now, update the application (ABC) with Requested Loan Amount as $9,000.
Note:Whenever there is any change in the application, all the rules associated with the application are rerun in the system.
As per the above defined criteria, this application satisfies the document category Identity Documents Child1 and fails for Identity Documents Child2.
Observed behavior
When the Identity Documents Child2 document category does not satisfy the defined criteria, it gets deleted along with Identity Records (Parent Document Category).
Due to deletion of Identity Records (Parent Document Category), the document category Identity Documents Child1 is also getting delinked.
Expected behavior
When the Identity Documents Child2 document category does not satisfy the defined criteria, it must get deleted.
Resolution
This issue is fixed as the document categories are getting deleted correctly.
Existing document categories that have a parent document category of null are not updated with the parent document ID. To update them with the parent document ID, you must re-generate the document categories.
New records created after this fix will not face any issues.
15.7.2 The Document Viewer pop-up is getting displayed at the bottom of the document screen(Jira ID: PDRFF-2303/GD-7732)
Fixed Version
This issue has been fixed in the following versions:
Q2 Origination: Spring'23 (4.2008.17)
CL Originate Skuid Extension: Spring'23 (4.2008.17)
Issue Description
While clicking on any attached document in the Document tab, the Document Viewer pop-up window is getting displayed at the bottom of the document screen instead of top of the screen.
Resolution
This issue is fixed as the Document Viewer pop-up is getting displayed at the top of the Documents screen.
15.8 Issues fixed in the July 31, 2023 patches
15.8.1 When an application is submitted to the next stage, the Stage field is not getting updated on the Application dashboard (Jira ID: PDRFF-2195/GD-7659)
Fixed Version
This issue has been fixed in the following versions:
Q2 Origination: Spring'23 (4.2008.15)
CL Originate Skuid Extension: Spring'23 (4.2008.15)
Issue Description
After completing a task for an application, when the application moves to the next stage by clicking the Move to Next Stage button, the Stage field is not getting updated.
Observed behavior
When a task is moved to the next stage after its completion, the Stage field is not getting updated on the Application dashboard.
Expected behavior
When the tasks are completed and an application is moved to next stage, the Stage field must get updated on the Application dashboard.
Resolution
This issue is fixed as the Stage field is getting updated correctly when the tasks are completed and the application is moved to the next stage.
15.8.2 Sub document category status is getting cloned from the parent document category status (Jira ID: PDRFF-2235/GD-7656 /GD-7673)
Fixed Version
This issue has been fixed in the following versions:
Q2 Origination: Spring'23 (4.2008.15)
CL Originate Skuid Extension: Spring'23 (4.2008.15)
Issue Description
While adding an additional document category manually from the Documents tab, the default status of the sub document category is getting cloned from the parent document category.
Resolution
This issue is fixed, understand it better with the following example:
When the parent document category status is updated to "Submitted" and a new sub document category is added manually to it then the status of the sub document category is now displayed as "Open" and not as "Submitted".
15.8.3 Policy Condition Exception is not getting generated for the Party object (Jira ID: PDRFF-2107/GD-7697)
Fixed Version
This issue has been fixed in the following versions:
Q2 Origination: Spring'23 (4.2008.15)
CL Originate Skuid Extension: Spring'23 (4.2008.15)
Issue Description
After configuring the policy conditions, the exceptions are not getting generated even when the policy condition criteria are satisfied.
Example:
Configure two policy conditions for a party and name them as P1 and P2.
-
Add the party (Dravid) for which policy conditions are configured, to an application that satisfies P1 policy condition but not P2.
Now, ensure the added party (Dravid) satisfies the P2 policy condition criteria also.
Observed behavior
For a few parties even when the policy condition criteria are satisfied, the policy exception is not getting generated.
Expected behavior
When the policy condition criteria are satisfied for any party, the policy exception must be generated.
Resolution
This issue is fixed as the policy exceptions are getting generated for the party object.
15.8.4 Previously generated tasks are getting displayed when the filter conditions are removed (Jira ID: GD-7437)
Fixed Version
This issue has been fixed in the following versions:
Q2 Origination: Spring'23 (4.2008.15)
CL Originate Skuid Extension: Spring'23 (4.2008.15)
Issue Description
If the filter conditions on the Tasks tab are removed, the previously generated tasks are also getting displayed on the Tasks tab.
Resolution
The issue is fixed as the previously generated tasks are not getting displayed on the Tasks tab.
15.9 Issues fixed in the June 30 patches
15.9.1 An error is displayed on the Required Action page (Jira ID: PDRFF-2032, GD-7379)
Fixed Version
This issue has been fixed in the following versions:
Q2 Origination: Spring'23 (4.2008.12)
CL Originate Skuid Extension: Spring'23 (4.2008.12)
CL Common: Spring'23 (4.2004.3)
Issue Description
After accepting any application and clicking the Required Action button, the following error is displayed:
There were 1 problems with this Skuid Page. Click to display...
Resolution
This issue is fixed by unpacking the "RequiredActions_Q2Originate" page in the "OriginatePages" pack of the Originate module.
To unpack the RequiredActions_Q2Originate page, unpack the OriginatePages pack.
15.10 Issues fixed in the June 1 patches
15.10.1 Financial Statement Calculation issue (Jira ID: GD-7396)
Fixed Version
This issue has been fixed in the following versions:
Q2 Origination: Spring'23 (4.2008.9)
CL Originate Skuid Extension: Spring'23 (4.2008.9)
CL Common: Spring'23 (4.2004.2)
Issue Description
While using the following product API in the Person Account to calculate the Statement Details Sum, the balance is not getting calculated:
genesis.FinancialStatementActions.saveStatementDetailsAndCalculateBalance();
Resolution
This issue is fixed and the now the balance is getting calculated using the above mentioned product API.
15.10.2 Exception Tasks remain enabled even after completion (Jira ID: GD-7448)
Fixed Version
This issue has been fixed in the following versions:
Q2 Origination: Spring'23 (4.2008.9)
CL Originate Skuid Extension: Spring'23 (4.2008.9)
CL Common: Spring'23 (4.2004.2)
Issue Description
Observed behavior: After marking an exception task as completed, the corresponding checkbox remains enabled for the other user who logs in.
Expected behavior: Once an exception task is marked as completed, the corresponding checkbox must be disabled for the other user who logs in.
Example to Understand the Issue
Let us perform the following steps to understand this issue:
Create an application as an admin user.
Navigate to Required Actions.
Create an Exception Task and mark it as Completed.
Now, assign it to other user.
-
Log in as the other user and open the same application.
The checkbox is still enabled. It must be disabled for the other users if the admin user has marked the Exception Task as Completed.
Resolution
This issue is fixed and the checkbox is grayed out for the other user when the exception task is marked as completed.
15.10.3 Skuid is throwing an error when any party details are edited (Jira ID: GD-7489)
Fixed Version
This issue has been fixed in the following versions:
Q2 Origination: Spring'23 (4.2008.9)
CL Originate Skuid Extension: Spring'23 (4.2008.9)
CL Common: Spring'23 (4.2004.2)
Issue Description
While trying to edit any party details on the party page by clicking the Edit button, the following Skuid error is displayed "There were 1 problems with this skuid page. Click to display..".
Resolution
This issue is fixed as no error is displayed while editing the party details.
15.11 Issues fixed in the May 23 patches
15.11.1 The system is providing an option to select the already selected product when trying to change the product to another one where Asset Class remains the same (Jira ID: GD-7427)
Fixed Version
This issue has been fixed in the following versions:
Q2 Origination: Spring'23 (4.2008.6)
CL Originate Skuid Extension: Spring'23 (4.2008.6)
Issue Description
When trying to change the selected product for an application, where the Asset Class is the same for the earlier Product selected and the new Product to be selected, in the list of Products to change to, the system is also displaying the one that’s already selected. The system must not display the already selected product on the Change Product option list.
For example, let us perform the following steps:
-
Create a Lease application with the following values:
Asset Class: Commercial Secured
Product: Equipment
-
Now click MORE > Change Product.
Note:The Asset Class for the changed product remains the same, which is Commercial Secured.
Check the list of available products to change to.
Expected behavior: After clicking MORE > Change Product, the list must not contain the already selected Product, which is Equipment. The list must display all the other available products to change to. For example, the available list of products to change to can display the following:
Lease Fee Definition
Uber
Actual behavior seen: After clicking Change Product, the list also contains the selected product. For example, the available list of products to change to displays the following:
Equipment
Lease Fee Definition
Uber
Resolution
This issue is fixed and the available list of products that you can change to is no more displaying the existing already selected Product for the same Asset Class configured.
15.11.2 Multiple choice options are not visible in the Questionnaire section (Jira ID: GD-7444)
Fixed Version
This issue has been fixed in the following versions:
Q2 Origination: Spring'23 (4.2008.6)
CL Originate Skuid Extension: Spring'23 (4.2008.6)
Issue Description
When trying to select the value from the multiple choice options question in the Questionnaire section, the page is not displaying all the options as there is no scroll bar to scroll down to see more options.
For example, let us perform the following steps:
Create an Application.
Navigate to the Questionnaire section and select the Questionnaire Name.
Now try to select multiple options from the list of options.
Expected behavior: A complete list of options must be visible.
Actual behavior seen: A complete list of options is not visible as there is no scroll bar to scroll down to see more options.
Resolution
This issue is fixed and now there is a scroll bar to scroll down to see a complete list of options to select from when viewing or filling a Questionnaire.
15.11.3 Payment Schedule is seen for an LOC application in the Pricing tab (Jira ID: GD-7442)
Fixed Version
This issue has been fixed in the following versions:
Q2 Origination: Spring'23 (4.2008.6)
CL Originate Skuid Extension: Spring'23 (4.2008.6)
Issue Description
In the Pricing tab of an LOC application, the system is displaying a Payment Schedule, which is an incorrect behavior. An LOC application must not display a Payment Schedule in the Pricing tab.
For example, let us perform the following steps:
Create an LOC application.
Click PRICING.
Expected behavior: Only Fees and Interest must be visible, not Payment Schedule.
Actual behavior: Payment Schedule is also visible in addition to Fees and Interest.
Resolution
This issue is fixed and now the Payment Schedule is not visible in the PRICING tab of an LOC application.
15.11.4 Incorrect UI seen when using the application on an iPad (Jira ID: GD-7169)
Fixed Version
This issue has been fixed in the following versions:
Q2 Origination: Spring'23 (4.2008.6)
CL Originate Skuid Extension: Spring'23 (4.2008.6)
Issue Description
While using an iPad, following issues are seen:
Notes and Messages section is seen incorrectly placed in between the Collateral details instead of being on the right hand side panel.
Financial spread table header is not completely visible.
Resolution
The preceding UI issues seen while using an iPad are now fixed.
15.11.5 Overriding Points or Points Amount on Vendor Points is not working as expected (Jira ID: GD-7424)
Fixed Version
This issue has been fixed in the following versions:
Q2 Origination: Spring'23 (4.2008.6)
CL Originate Skuid Extension: Spring'23 (4.2008.6)
Issue Description
When trying to override Points (Override) field with a different value, it does not update the Points Amount (Override) field accordingly and when trying to override Points Amount (Override) with a different value, it does not update the Points (Override) field accordingly.
For example, let us perform the following steps:
Create a Lease application.
Add Equipment to the application.
Go to MORE > Lease Pricing.
Click Pricing.
Click Calculate Points on application.
Override the Points (Override) and verify if Points Amount (Override) displays the correct value, or override the Points Amount (Override) and verify if Points (Override) displays the correct value.
Expected behavior: On overriding the Points (Override), the Points Amount (Override) must display the correct value and on overriding the Points Amount (Override), the Points (Override) must display the correct value.
Resolution
This issue is fixed.
15.11.6 Incorrect Appraisal Bid is getting accepted (Jira ID: GD-7425)
Fixed Version
This issue has been fixed in the following versions:
Q2 Origination: Spring'23 (4.2008.6)
CL Originate Skuid Extension: Spring'23 (4.2008.6)
Issue Description
When varied Bid Amounts are provided for different bids and Auto Select Bid is selected in Actions, an incorrect appraisal bid is getting accepted which is not the highest. The expectation is that the highest bid must get accepted automatically when Auto Select Bid is selected in Actions.
For example, let us perform the following steps:
As a prerequisite to the following steps, set up the Appraisal Management.
Create an application.
Add a Collateral and in the Appraisal Management section, enter the required details, and click Send Request.
Go to App Launcher > Launchpad > Appraisal Administration section.
If there are two Appraisal bids, then provide a Bid Amount of $10,000 for the second one and a Bid Amount of $5,000 for the first one.
In Actions, click Save and then click Auto Select Bid.
Expected behavior: The Status of the second Appraisal Bid of $10,000 must be Accepted and the Status of the first one of $5,000 must be Rejected as the second bid is higher than the first one.
Actual behavior seen: The Status of the first Appraisal Bid of $5,000 is getting Accepted and the second Appraisal Bid is getting Rejected.
Resolution
This issue is fixed and the Status of the bids are now getting updated correctly.
16. Change Record
| S. No | Change Date | Description of Change |
|---|---|---|
| 1 | April 28, 2023 |
Published the release notes for the Spring'23 General Availability release (4.2008). |
| 2 | May 23, 2023 | Added section 15.11 |
| 3 | June 1, 2023 | Added section 15.10 |
| 4 | June 30, 2023 | Added section 15.9 |
| 5 | July 31, 2023 | Added section 15.8 |
| 6 | August 14, 2023 | Added section 15.7 |
| 7 | September 20, 2023 | Added section 15.6 |
| 8 | October 16, 2023 | Added section 15.5 |
| 9 | October 31, 2023 | Added section 15.4 |
| 10 | December 1, 2023 | Added section 15.3 |
| 11 | December 29, 2023 | Added section 15.2 |
| 12 | August 30, 2024 | Added section 15.1 |