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 Origination 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 Portal or Q2 Lending Help Center.
This document provides information on the following for the release:
The audience of this document includes business users, implementers, and system administrators.
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.
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.
For information on the upgrade steps, see release-related steps in the Q2 Product Upgrade Guide.
This section briefly describes the new features and enhancements added in this release.
Note
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
Rate Card configuration enhancements (Jira ID: GD-7107)
Feature Description
As part of enhancing the Rate Card configuration, we have made the following changes in the configuration:
-
Rules based rate cards have been introduced to ease the configuration and maintenance of the rate cards.
-
The Rate Card details page is updated to differentiate between the Product Type (Loan or LoC) and Pricing details.
-
The Term and Frequency fields are moved to the Pricing Details section from the Criteria section that allows the users to add multiple rules to rate card and set various Term and Frequency combinations.
If the criteria are met, the system generates corresponding pricing offers.
-
For each rate card, users can now set three distinct pricing details for Loan or LoC product type and one for Lease product.
-
Provided the flexibility to define any criteria based on the Application object.
Feature Description
As part of enhancing the Credit Memo configuration, a new View Relationship button is added. This button allows the users to view both the Party Relationship Graph and the Party Ownership details directly in the Relationship Summary section of the Credit Memo page. This enhancement aims to provide the party relationship and ownership information during the final review and signing off the loan application.
Documents tab enhancement (Jira ID: GD-7817)
Feature Description
As part of enhancing the Documents tab, we have made the following changes in the current release:
-
Introduced the following three new filters to quickly identify the documents as the Documents tab contains multiple documents related to loan origination and covenant compliance.
-
Document Category: The values in this filter are sourced from the Document Definitions.
-
Status: The values in this filter represent the present state of the document.
-
Applicable Period: The values in this filter are sourced from the Covenants tab if the document is part of covenant compliance. If it’s not part of covenant compliance, the value is set as NA by default.
-
-
Updated a default sorting mechanism. Now, all account-related documents are displayed at the top of the page, followed by all the documents collected for covenant compliance.
Process Builders and Workflows migration to Flows (Jira ID: GD-7815)
Feature Description
As part of enhancing the Process Builders and Workflows, we have migrated the following pre-existing packaged Process Builders and Workflows to flows:
-
Approve Credit
-
Decline Credit
-
Create Application Snapshot
-
Generate Scorecard & Pricing
-
Generate Trid Disclosure
-
Pull Credit
-
Unlock Application (manually created)
-
Update Application Status
Starting from this release, the users have an option to utilize the flows. However, the existing Packaged Process Builders and Workflows remain available for use.
SKUID Upgrade to Edinburgh Update 2 (16.2.6) (Jira ID: GD-7849)
Feature Description
We have upgraded the Skuid version to Edinburgh Update 2 (v16.2.6) and it is available for customers who would like to upgrade.
The following section briefly describes the issues fixed in this release.
|
Jira ID |
Description |
|---|---|
|
Exception Tasks remain enabled even after completion. |
|
|
An error is displayed when the Edit button is clicked on the party page |
|
|
Multi-picklist values are not visible in the Questionnaire |
|
|
Payment Schedule is seen for an LOC application in the Pricing tab. |
|
|
Previously generated tasks are getting displayed when the filter conditions are removed. |
|
|
The system provides an option to select the already selected product when trying to change the product to another one where the Asset Class remains the same. |
|
|
Incorrect Appraisal Bid is getting accepted. |
|
|
Overriding Points or Points Amount on Vendor Points is not working as expected. |
|
|
Issues in Scorecard. |
|
|
Policy exceptions are not getting generated in the clone application. |
|
|
An error is displayed on the Required Action page. |
|
|
Legal Entity Type displays as default when a new contact is selected. |
This section briefly describes the objects added in this release.
Note
For a complete list of the Q2 Origination objects, see the Q2 Origination Data Dictionary.
There are no new objects added in this release.
This section briefly describes the objects modified in this release.
Note
For a complete list of the Q2 Origination objects, see the Q2 Origination Data Dictionary.
This object stores the result of the evaluation of each scorecard criterion for an application. So if ten criteria are executed for an application, then ten Application Scorecard Results are created in the system.
The following table describes the field that is added to this object. This field is optional:
|
Field API Name |
Description |
Field Type |
|---|---|---|
|
Related_To__c |
This field indicates the entity name with which the Application Scorecard Result is associated. It can store the Application or Party name depending on Scorecard's parent object type. |
Formula |
This object stores the documents that need to be/are collected for an Application and/or Account, Collateral record in the system. Let's say for processing a loan application, the lender needs to collect identity documents like driver's license of the borrower. Then the driver's license for Mr X who is taking a loan would be one document category in the system and driver's license for Mr Y would be another document category in the system. Each document category is associated to a document definition in the system.
The following table describes the field that is added to this object. This field is optional:
|
Field API Name |
Description |
Field Type |
|---|---|---|
|
Related_To__c |
This field indicates the entity name with which the Document Category is associated. It can store the Application, Party, or Collateral name depending on the Document Category parent object type. |
Formula |
This object stores the details of the financial spread details configuration.
The following table describes the field that are added to this object. These fields are optional:
|
Field API Name |
Description |
Field Type |
|---|---|---|
|
genesis__Tab_Label__c |
This field represents the name of the tabs available on the Financial Spread page. |
Text |
|
genesis__Tab_Order__c |
This field indicates the order of the tabs available on the Financial Spread page. |
Number |
This object stores the custom setting defined at the org/user/profile level, which is used to drive the behavior of features that impact the organization level.
The following table describes the field that is added to this object. This field is optional:
|
Field API Name |
Description |
Field Type |
|---|---|---|
|
genesis__Enable_Rule_Base_Rate_Cards__c |
If this field is selected, indicates the generation of the new rule based rate card. |
Checkbox |
This object stores the policy condition definition.
The following table describes the field that is added to this object. This field is optional:
|
Field API Name |
Description |
Field Type |
|---|---|---|
|
genesis__Enable_Rule_Base_Rate_Cards__c |
This field indicates the exception type to which policy exception is associated. |
Formula |
This object stores the details for each rate card option. It has details like, for a given maximum-minimum loan amount, term, interest rate, payment frequency, credit rating, and so on that determine the availability of this option for any application.
The following table describes the field that are added to this object. These fields are optional:
|
Field API Name |
Description |
Field Type |
|---|---|---|
|
genesis__Pricing_Generation_ Rule__c |
This field represents the relationship of the rule associated with this Rate Card. |
Reference |
|
genesis__Pricing_Factors__c |
This field represents the JSON of all the permutations of Term & Frequency related to the Rate Card. |
Text |
This object serves the purpose of defining the template for the rate cards so that the various attributes of the rate cards can be stored. Each rate card has a list of rate card setup details entailing the data for various combinations of amounts, rates, terms, filtering conditions, and so on.
The following table describes the field that is added to this object. This field is optional:
|
Field API Name |
Description |
Field Type |
|---|---|---|
|
genesis__Rule_Based_Rate_Card__c |
This field, if selected, indicates the header of the rule based rate cards. |
Checkbox |
There are no REST APIs added in this release.
Note
For a complete list of the Q2 Origination REST APIs, see Q2 Origination REST APIs Guide.
There are no REST APIs modified in this release.
Note
For a complete list of the Q2 Origination REST APIs, see Q2 Origination REST APIs Guide.
There are no global methods added in this release.
Note
For a complete list of the Q2 Origination global methods, see Q2 Origination Global Methods Guide.
There are no global methods modified in this release.
Note
For a complete list of the Q2 Origination global methods, see Q2 Origination Global Methods Guide.
Follow this section for the details on the issues fixed in the patches on the release of the following packages:
-
Q2 Origination
-
CL Originate Skuid Extension
-
CL Common
Configuration for Formula based Payment Amount Calculation for Pricing Generation (Jira ID: GD-8975)
This enhancement has been made in the following versions:
-
Q2 Origination: December 2023 (4.4001.45)
-
CL Common: December 2023 (4.4000.21)
Till now, a batch job is used to generate amortization schedules for each pricing option and assign payment amounts to them. This functionality is now enhanced to enable the calculation of the payment amounts using a formula therefore giving users the flexibility to calculate the payment amount with the click of a button and so speeding up the pricing generation process.
Enable the new functionality
Enable the new functionality by performing the following Steps:
Prerequisite
Make sure that the org does not have any namespace associated with it.
Steps
-
Log in to your Salesforce account.
-
Go to Setup.
-
In the Quick Find box, search for Custom Settings and select it.
-
Select Org Parameters with the namespace prefix (genesis) and select Edit.
-
Add a new custom field of type Checkbox, and provide the following details:
-
Field Label: Generate Payment Amount With Pricing
-
Field Name: Generate_Payment_Amount_With_Pricing
-
Default Value: True
-
-
Select Save > Manage.
-
Select Edit, and then select the Generate Pricing with Payment Amount checkbox.
-
Select Save.
The pricing options are generated based on the default value of Days Convention, which is 30/360. Perform the following steps to set a new default value in your org:
-
Log in to your Salesforce account.
-
Go to Setup > Object Manager.
-
In the Quick Find box of the Object Manager, search for Applications and select it.
-
Go to Fields & Relationships, and select Days Convention.
-
Scroll down to the Values section and edit the value you wish to set as default for your org.
-
Select the Default checkbox.
-
Select Save.
Note
If the pricing option is generated using the Rate Card setup, you can define the Days_Convention__c value, which, once selected, will automatically update the corresponding Days Convention field in the associated application. This centralized setup lets you control the Days Convention directly from the Rate Card, ensuring consistent calculations.
An error is displayed while associating an attachment to a document category (Jira ID: PDRFF-3447/ GD-9199)
Fixed Version
This issue has been fixed in the following version:
-
CL Common: December 2023 (4.4000.21)
Issue Description
The users are unable to sync the documents with applications that are attached to an account. This behavior is observed for the documents with names having more than 80 characters.
Resolution
This issue is fixed now as the documents having names with more than 80 characters can be synced with the applications. As the file name still accepts only 80 characters, including the file extension, the file name gets truncated to display just 80 characters in the Skuid UI. To view the complete file name, click on the file and open it, and the complete name of the file is displayed.
Calculated Values for Financial Statements are appearing as rounded off (Jira ID: PDRFF-3363/GD-9144)
Fixed Version
This issue has been fixed in the following versions:
-
Q2 Origination: December 2023 (4.4001.39)
Issue Description
The calculated values for the Financial Statements are being rounded off upon refreshing the page, despite the decimal places being set to two in the Financial Spread configuration. However, the decimal values are correctly displayed at the object level (Statement Details).
Resolution
This issue is fixed now as the decimal values are not getting rounded off.
An error is displayed while generating pricing (Jira ID: PDRFF-3338/GD-9104)
Fixed Version
This issue has been fixed in the following versions:
-
Q2 Origination: December 2023 (4.4001.39)
Issue Description
If the rate card has large number of additional determining factors configured, and the Generate Pricing button is selected, then following error is displayed:
Resolution
This issue is fixed now as the pricing is getting generated successfully.
Unable to view the Documents & Disclosure tab (Jira ID: PDRFF-3280/ INTCL-2389)
Fixed Version
This issue has been fixed in the following versions:
-
Q2 Origination: December 2023 (4.4001.35)
-
CL Originate Skuid Extension: December 2023 (4.4001.35)
Issue Description
Users were unable to view the Documents & Disclosure tab due to incorrect object details configured in the Skuid page model.
Resolution
This issue is fixed now by updating the object details. The Documents & Disclosures tab is now visible to users if the integration configuration is present.
Unable to select the Object Type while adding rules (Jira ID: PDRFF-3040, GD-8612)
Fixed Version
This issue has been fixed in the following versions:
-
Q2 Origination: December 2023 (4.4001.23)
-
CL Originate Skuid Extension: December 2023 (4.4001.23)
Issue Description
When a user tries to select the Application and Application Collateral Object Type while defining rules in the Policy Condition Definition Detail by selecting the Add Rule button, the Object Type does not display any detail.
Resolution
This issue is fixed now, and the users are able to select the Object Type for the Application and Application Collateral objects.
Unable to access existing quick quote records (Jira ID: PDRFF-2946, GD-8376)
Fixed Version
This issue has been fixed in the following versions:
-
Q2 Origination: December 2023 (4.4001.23)
-
CL Originate Skuid Extension: December 2023 (4.4001.23)
Issue Description
After upgrading from Q2 Origination version 3.6004.6 to 4.4001.7, due to an issue in the NewModel model in the QuickQuoteDetail Skuid page, the existing quick quote records are not accessible and the following error is displayed:
Error Message
An unexpected error has occurred. Your solution provider has been notified. (skuid)
Resolution
This issue is fixed now, and the users are able to access the quick quote records.
To resolve this issue, use the latest Skuid page.
Note
If you are unable to use latest Skuid page due to customizations, then ensure that NewModel model in the QuickQuoteDetail Skuid page is removed.
Creation of Document Categories (Jira ID: GD-8636)
Fixed Version
This enhancement has been made in the following versions:
-
Q2 Origination: December 2023 (4.4001.23)
-
CL Originate Skuid Extension: December 2023 (4.4001.23)
Feature Description
In the past, the document categories were getting created only when a new account was added, but with this release, the categories are also created when the account is updated for a Party with Reusable Document Definitions. When the account record is updated, an account level document category gets created if the account has a legal entity type assigned to it.
Users are not receiving email notifications (Jira ID: PDRFF-2959, GD-8398)
Fixed Version
This issue has been fixed in the following version:
-
Q2 Origination: December 2023 (4.4001.19)
Issue Description
When a user tags another user in the Team Communications, the tagged user is not receiving an email notification despite the post being successfully added.
Resolution
This issue is fixed now, and the tagged users are receiving the notification emails.
An error is displayed while uploading a file (Jira ID: PDRFF-2799, GD-8252)
Fixed Version
This issue has been fixed in the following version:
-
CL Common: December 2023 (4.4000.10)
Issue Description
While uploading a file to a document category containing over 200 files, the following error is displayed:
Error message
Aggregate query has too many rows for direct assignment, use FOR loop.
Resolution
This issue is fixed now, and files are now uploading successfully .
Fixed Version
This issue has been fixed in the following version:
-
CL Common: December 2023 (4.4000.10)
Issue Description
While saving a Step-up schedule and generating a schedule in the Payment Schedule section, the following error is displayed:
Error message
List index out of bound; 12
Resolution
This issue is fixed now as the Step-up schedule is getting saved and schedules are generating correctly upon clicking Generate Schedule.
Some fields are not getting copied in the cloned application (Jira ID: PDRFF-2570, GD-8246)
Fixed Version
This issue has been fixed in the following versions:
-
Q2 Origination: December 2023 (4.4001.15)
-
CL Originate Skuid Extension: December 2023 (4.4001.17)
Issue Description
To make a copy of an existing application, when a user clicks Clone Application, the values of the Custom Fields of the Party object are not getting copied to the cloned application.
Resolution
This issue is fixed now as the values of the Custom Fields of the Party object are copied to the cloned application.
Capability to reorder the Financial Statement Tabs (Jira ID: PDRFF-2552, GD-8324)
Fixed Version
This enhancement has been made in the following versions:
-
Q2 Origination: December 2023 (4.4001.15)
-
CL Originate Skuid Extension: December 2023 (4.4001.17)
Feature Description
Now, the administrator has the capability to rearrange the tabs within the Financial Statements according to their requirements.
Prerequisities
The Tab Order and Tab Label fields must be added to the Page layout of the Financial Spread Details Configuration.
To add these fields, follow these steps:
-
Go to Setup > Object Manager > Financial Spread Details Configuration > Page Layouts.
-
Select Financial Spread Details Configuration Layout.
-
Drag the Tab Order and Tab Label fields from the Fields section and drop them under the Information section.
-
Select Save.
Steps
To define the configuration, follow these steps:
-
Log in to the Salesforce account and go to Origination Configuration.
-
Select Financial Spread Configuration under the Financial Spreading Setup section , and then select Initial Configuration.
-
Go to the Related tab.
In the Related tab, all the financial spread configuration details are listed.
-
To modify the configuration details, expand the dropdown menu of the financial spread configuration that you want to modify and select Edit.
-
Change the values for the Tab Order and Tab Label fields as needed.
Refer to the following table as an example on how the configurations can be modified:
Statement Type
Tab Order
Tab Label
Balancesheet
1
Balance Sheet
Income
2
Income
Cashflow
3
Cashflow
Ratio
4
Ratio
UCACashflow
5
UCACashflow
GlobalCashflow
6
GlobalCashflow
Note
-
If you are making changes in the Tab Order and Tab Label configuration, ensure to rearrange all the available tabs. For example, if you want to move Cashflow to second position, ensure that all the six tabs are arranged from one to six positions, as moving only one tab may leave any tabs with the same order. If you do not rearrange all the available tabs, the system may not work properly.
-
When you use the Tab Order configuration, the system displays the tab which is marked as 1 as the default tab. You can change the tab order to set it to 1 for the required default tab.
-
Added Application Number (APP-XXXXXXXXX) in the Email Templates (Jira ID: PDRFF-2689, GD-8337)
Fixed Version
This enhancement has been made in the following versions:
-
Q2 Origination: December 2023 (4.4001.15)
-
CL Originate Skuid Extension: December 2023 (4.4001.17)
Feature Description
The following email templates of the team communications are enhanced to include the application number:
-
Send Message to Backoffice User: This email template is enhanced to include the application number in the subject line for back office users
-
Send Message to Portal User: This email template is enhanced to include application number in the email body for portal users.
Salesforce Spring'24 release is impacting Skuid users (Jira ID: PDRFF-2810, GD-8239)
Fixed Version
This issue has been fixed in the following versions:
-
CL Common: December 2023 (4.4000)
-
Q2 Origination: December 2023 (4.4001.7)
-
Skuid: Edinburgh (16.4.3)
-
CL Originate Skuid Extension: December 2023 (4.4001.8)
Issue Description
In the Salesforce Spring'24 release, a crucial security update pertaining to Visualforce JavaScript remoting is implemented. This change has the potential to impact the following Skuid users:
-
Who are using any version of Skuid Edinburgh (16.x.x) prior to 16.4.3 version.
-
Who have integrated Skuid pages within Visualforce pages.
For reference, see https://community.skuid.com/t/issue-with-spring-24-affecting-skuid-users/13676
Note
Users with versions of Skuid older than Edinburgh (16.x.x) will not be impacted. Salesforce is enforcing these versions of the Salesforce API that Skuid changed to the initial Edinburgh release. If you are on any version of Skuid older than Edinburgh, you should not be affected.
What's New?
Salesforce will force the enablement of JsonAccess annotation validation within Visualforce JavaScript remoting. This update was made available in Winter'23 and will be enforced in Spring'24.
The Visualforce Remoting API uses JavaScript to call methods in Apex controllers from Visualforce pages, and this update is increasing security across packaging namespaces. Skuid pages are in the Skuid namespace, and Visualforce pages are in the org namespace, resulting in an error that might trigger a message similar to the following:
Error Message
Cannot create property 'totalsuccess' on string 'The concrete implementation 'skuid.Utils.SkuidResult' in namespace 'skuid' has a JsonAccess annotation serializable attribute defined that prevents serialization. The Apex object cannot be serialized.
Resolution
This issue can be fixed by upgrading to fixed versions mentioned above and ensuring that you are using Skuid 16.4.3 version.
|
S.No |
Change Date |
Description of Change |
|---|---|---|
|
1. |
December 22, 2023 |
Published the release notes for the General Availability release (4.4001). |
|
2. |
February 06, 2024 |
Added section 1.14.9 |
|
3. |
February 29, 2024 |
Added section 1.14.8 |
|
4. |
March 15, 2024 |
Added section 1.14.7 |
|
5. |
March 28, 2024 |
Added section 1.14.6 |
|
6. |
April 17, 2024 |
Added section 1.14.5 |
|
7. |
July 31, 2024 |
Added section 1.14.4 |
|
8. |
August 30, 2024 |
Added section 1.14.3 |
|
9. |
September 24, 2024 |
Added section 1.14.2 |
|
10. |
November 5, 2024 |
Added section 1.14.1 |