Oxygen Release Notes

1.   Preface

This is a living document, and its contents may be updated often. Make sure that you have the latest version for use.

This document provides information about the new and enhanced functionality in Q2 Origination, Oxygen General Availability (GA) release. You can access the release notes of the previous releases from the Q2 Customer Portal.

The contents of this document are applicable to all the customers who have installed the Q2 OriginationOxygen version (3.5004.60) for the first time or have upgraded from an earlier version.

1.1 Purpose of this Document

This document provides information on the following for the Oxygen release:

• Installation Information

• Upgrade Considerations

• System Performance

• Preface

• Fixed Issues

• Known Issues

• New and Modified Objects

• New and Modified APIs

• Global Methods

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 Preface 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.   Upgrade Considerations

For information on the upgrade steps, see release-related steps in the Q2 Product Upgrade Guide.

5.   System Performance

To view the batch jobs performance statistics for Q2 Origination without customizations under test conditions, see the Q2 Performance Benchmarking Guide.

6.   New Features and Enhancements

This section briefly describes the new features and enhancements added in the Oxygen release of Q2 Origination.

6.1 Enhanced User Experience (JIRA ID: GD-3071)

Feature Description

CL Originate has been enhanced with a new interface that makes it easy for users to access statements, view comparative data, align values according to general practice, and interact with the spreads more effectively.

Specific enhancements have been in the following areas:

• Trend Analysis – Prior to this release, trend analysis was a separate report. With this release, users will now be able to trend each statement/schedule by turning a button on/off.

• Update Multiple Statement Periods Simultaneously – Prior to this release, users were updating a single statement period at a time. With this release, users will now be able to enter data across multiple periods simultaneously (like a user enters data in a spreadsheet).

• Instant Calculation – Prior to this release, users had to perform a Save action to run various calculations associated with the spread configuration. With this release, users can expect these calculations to be updated in real-time as data is entered into CL Originate.

• Prior to this release, every line item in the financial spreads had to have a unique name. With this release, same names can be applied to multiple line items.

• The ability to configure certain financial template line items for computation only and not display these items on the financial spreads themselves.

6.2 Clone Financial Statement Templates (JIRA ID: GD-3142)

Feature Description

There are scenarios where the FIs will need to modify the template after a financial statement template has been configured and statements have been captured for borrowers. To enable such modifications with ease, CL Originate has been enhanced to clone the financial statement templates and create newer versions of the template to capture the new financial statements of borrowers.

6.3 Spread Multiple Financial Statements for a Business Entity (JIRA ID: GD-2467)

Feature Description

CL Originate has been enhanced to enable credit analysts to capture financials for a single borrower on multiple templates. For example, an underwriter may want to capture only key financial statement values for a small ticket loan.

6.4 Annualize Interim Income Statements (JIRA ID: GD-2468 )

Feature Description

CL Originate has been enhanced to calculate the annualized values for interim income statements. Any ratio and cashflow calculations will consider the annualized values.

6.5 Configuration: Removed Dependency on Chart of Accounts (JIRA ID: GD-3213)

Feature Description

With this release, users/system administrators will not have to associate any chart of account while configuring financial statement template. The hierarchy between a “rollup” and corresponding “input” has been achieved with a new configuration of a “parent template detail.

6.6 Add Parties with Multiple Roles (Jira ID: GD-3276)

Feature Description

In a business/commercial loan application, an individual may be associated with multiple roles. For example, an owner of a business needs to be associated with roles like Beneficial Owner, Signer, Guarantor and Beneficial Owner Manager in a loan application transaction.

Prior to this release, the user would have to add the same individual(account) as a party for every single role. This would mean that the user would have to perform the add party action four times in the above example. With this release, users will now be able to associate multiple roles and additionally establish a relationship between the business entity and the individual as part of a single party addition.

6.7 Upload and Manage Documents at a Relationship Level (JIRA ID: GD-3347)

Feature Description

CL Originate has enhanced the Account Relationship Dashboard to enable FIs to upload and manage all relationship documents in one place.

With this release, it supports the following scenarios:

Scenario 1: Create Account > Upload Documents > Create Application

In this scenario, the end user will be able to view, upload and manage documents as a part of the Account relationship management documents prior to any application creation. The documents uploaded on Account must be visible on Application.

Scenario 2: Create Account > Create Application > Upload Documents on Application > View and Manage Documents on Account

In this scenario, there are no documents uploaded on the Account, however the documents relevant to the Account are uploaded on the Application. The user will be able to view and manage the uploaded documents (relevant to the account) on the Account as well.

Scenario 3: Upload Documents on an Existing Account > Create New Application for the Existing Account > View Account Documents on Application

In this scenario, documents are uploaded on an existing account, and if an application is created on that existing account, the user will be able to view and manage the Account documents on the Application.

6.8 Give Multiple Users Access to View and Decision Appraisals (JIRA ID: GD-2750)

Feature Description

Prior to this release, the association of an appraisal administrator role was to a single user per collateral category. With this release, an appraisal administrator can be associated with a Salesforce queue, enabling association of the role to multiple users. Additionally, there are enhancements made to perform effective collateral analysis by calculating and displaying the advance value, superior liens, and available value on the collateral.

6.9 Application Snapshot (JIRA ID: GD-3531)

Feature Description

Application snapshot is a snapshot of the data of the application and its related records at different points in time of the origination workflow. Prior to this release, users were able to view the different snapshots and compare the snapshot from one version to another side by side. However, this view did not honor the Salesforce field permissions and field encryptions and posed an operational risk.

With this release, CL Originate has been enhanced to honor both the Salesforce field permissions and field encryptions in the Application Snapshot UI.

6.10 Loan Fee Enhancements (JIRA ID: GD-3306)

Feature Description

CL Originate has been enhanced to support the configuration and the application of fees to a loan application with ease. The following enhancements have been made:

• Auto apply the fees based on the product selected.

• Calculate fees that are a percentage of loan amount.

• Have a configuration for 'minimum fee' and the loan officer cannot negotiate below this configured minimum.

• Validate the Min/Max fee amounts for percentage-based fees.

• Fees flagged as "Include for APR" are considered for APR calculation.

• Fees flagged as "Add to amount financed" is added to the Loan Amount.

7.   Fixed Issues

8.   Known Issues

There are no known issues known in the Oxygen release of Q2 Origination.

9.   New and Modified Objects

This section briefly describes the new and modified objects in the Oxygen release of Q2 Origination.

9.1 New Objects

The following table describes the objects added in the Oxygen release of Q2 Origination.

9.2 Modified Objects

The following table describes the objects modified in the Oxygen release of Q2 Origination.

10.   New and Modified APIs

This section briefly describes the new and modified APIs in the Oxygen release of Q2 Origination.

10.1 New APIs

There are no new APIs added in the Oxygen release of Q2 Origination.

10.2 Modified APIs

There are no APIs modified in the Oxygen release of Q2 Origination.

11.   Global Methods

This section briefly describes the global methods that are added or modified in the Oxygen release of Q2 Origination.

11.1 New Global Methods

The following table describes the global methods added in the Oxygen release of Q2 Origination.

11.2 Modified Global Methods

There are no new Global Methods modified in the Oxygen release of Q2 Origination

12.   Post GA Release

Follow this section for the details on the issues fixed in the patches on the Oxygen release.

12.1 Issue fixed in July 31,2024 patch

12.1.1 An error is displayed while associating an attachment to a document category (Jira ID: PDRFF-3285/ GD-8989)

Fixed Version

This issue has been fixed in the following version:

• CL Common: Oxygen (3.5008.47)

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.

12.2 Issues fixed in the December 1, 2023 patch

12.2.1 Unable to sync the documents (Jira ID: PDRFF-2635/ GD-7980)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Oxygen (3.5004.66)

• CL Common: Oxygen (3.5008.46)

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.

12.3 Issues fixed in the June 30 patches

12.3.1 Unable to attach a file to a document folder if the file name exceeds 80 characters (Jira ID: PDRFF-1962, GD-1047, GD-7611)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Oxygen (3.5004.65)

• CL Originate Skuid Extension: Oxygen (3.5004.56)

• CL Common: Oxygen (3.5008.46)

Issue Description

Unable to attach a file to the document folder if the file name contains more than 80 characters.

The file name can only be 80 characters long including the file extension.

Resolution

This issue is fixed and so now the file name with more than 80 characters can be attached to a document folder. 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.

12.3.2 An error is displayed on the ApplicationDrawdownTerms page while adding the Collateral Types (Jira ID: PDRFF-1983, GD-7534, GD-7616)

Issue Description

While adding the Collateral Types under the Drawdown Terms for the Deal or Package application if the names of the Collateral Types field exceed 255 characters in length, an error is displayed.

Resolution

This issue is fixed as the Drawdown Terms are getting updated.

12.3.3 Tax Deferral Payment Period is not getting calculated correctly in the Payment Schedule table (Jira ID: PDRFF-2158, GD-7614)

Issue Description

After creating an application, when the Tax Deferral Payment Period field has some value and proceeds for Calculate Pricing. The tax amount splits into half and added to the next two payment schedules in the 3.5004.61 version.

Example to Understand the Issue

1. Create an application with a Tax Deferral Payment Period as 2.

2. Click Calculate Pricing and check the Payment Schedule.

Expected behavior: The Payment Amount + Tax Amount is getting calculated correctly for the 2nd month in the Payment Schedule table.

Observed behavior: The Payment Amount + Tax Amount is not getting calculated correctly for the 2nd month in the Payment Schedule table.

Resolution

The issue is fixed as the Payment Amount + Tax Amount is getting calculated correctly.

12.4 Issues fixed in December 30, 2022

12.4.1 Common Oxygen – Error while adding Rule Criteria to the Task Setup Page of Origination Configuration (Jira ID: PD-1289)

Issue Description

While adding the Rule Criteria from the Task Setup Page, if more than five criteria is added to the Rule, the following error message is getting displayed:

“Maximum view state size limit (170KB) exceeded”.

Resolution

This issue is fixed.

12.4.2 Error while adding a broker to an existing Relationship (Jira ID: GD-7122)

Issue Description

When a single account is added as party to multiple applications, for example parties with party type dealer, broker and that Account/Contact record is subsequently updated, it gives the following error

“System.LimitException: Apex CPU time limit exceeded”.

Resolution

This issue is fixed.

In the Custom Setting> Org Parameters>Manage(genesis)>Closed Status> (Specify the party type. For example: Dealer, Broker.)

12.4.3 Error while inserting fees: “UNABLE_TO_LOCK_ROW” (Jira ID: GD-7038)

Issue Description

The following error message is getting displayed while inserting multiple fee records:

“UNABLE_TO_LOCK_ROW”.

Resolution

This issue is fixed.

The field preference has been changed.

12.5 Issues fixed in September 14, 2022 patches

12.5.1 Skuid Oxygen – Some alignment issue on the Collateral page (Jira ID: GD-6951)

Issue Description

With the new Skuid version 15.0.12, there are a few misalignments of the UI elements on the Collateral page.

Resolution

This issue is fixed.

12.5.2 Skuid Oxygen – Document preview and download options are not working (Jira ID: GD-6949)

Issue Description

With the new Skuid version 15.0.12, on the Documents page, the Preview and the Download options are not working for the created financial statements.

Resolution

This issue is fixed.

12.5.3 Skuid Oxygen – Unable to add party to the application (Add Party frame is not loading) (Jira ID: GD-(Jira ID: NBP-6948)

Issue Description

With the new Skuid version 15.0.12, on the Parties page, on clicking the Add Party option, the Add Party window is not loading.

Resolution

This issue was occurring because the CLSBase package was not unpacked and a few pages were duplicated. After deleting the duplicate pages, the issue is fixed.

12.5.4 Skuid Oxygen – Unable to upload document on the Documents page of the application dashboard (Document upload frame is not loading) (Jira ID: GD-6947)

Issue Description

With the new Skuid version 15.0.12, on the Documents page, on uploading a file to a document category, the Upload File window is not loading.

Resolution

This issue was occurring because a few pages were duplicated. After deleting the duplicate

12.6 Issues fixed in June 17, 2022 patches

12.6.1 Oxygen – Change version of apex.js and connection.js to latest Salesforce versions (at least 50+) (Jira ID: GD-6447)

Issue Description

Salesforce is retiring API version up to 20 by March 2022 and 21-30 by March 2023.

Resolution

Hence, all the js files that use Ajax toolkit (apex.js and connection.js) should start using the latest versions. The application needs to be upgraded to use the latest API version that is 54.0.

12.7 Issues fixed in April 30, 2022 patches

12.7.1 Unable to edit fee amount for ONE-TIME frequency (Jira ID: GD-6447)

Issue Description

For an application, user cannot edit the amount of One-Time Fees. Also, for the Periodic Fees with the Frequency set to Monthly, after editing the fee amount using the Create Using Fee Definition feature, when a user is clicking on Save, the system is not saving the new calculated values.

Resolution

This issue is fixed.

12.7.2 Team Communication - Not searching across last name and only first five results are displayed (Jira ID: GD-6472)

Issue Description

In Teams Communication, user is unable to search and tag persons using their last name. Also, if user search persons using their first name and there are more than five results, the system is showing only top-five results.

For example, if a user wants to search for a person with the name as “FSR 2116” and the user searches using the last name as “2116”, no results are displayed. If user search using the first name as “FSR” and there are more than five results, the system will show only the top-five results, and this may not have the searched person.

Resolution

This issue is fixed.

12.7.3 Team Communication in CL Originate is picking up different application messages (Jira ID: GD-6391)

Issue Description

In Teams Communication, whenever we initiate a message, the record is saved in clcommon_Message_c with a 16-character Target ID (same as the Application ID). If the Application ID for two or more applications is similar and if it's case insensitive and we can see message from the different applications in Team communication.

For example, the Target IDs can be a6o5Y000000tRMo and a6o5Y000000tRmo.

Resolution

This issue is fixed.

12.7.4 Deletion of uploaded document/file from dashboard failing (Jira ID: GD-6363)

Issue Description

In the Documents section on the Loan Dashboard, after we select a file to delete from the documents folder, the Delete icon is disabled and a user is unable to delete an uploaded file.

Resolution

This issue is fixed.

12.8 Issues fixed in February 1, 2022, patches

12.8.1 The Lease application is including the VAT Tax Amount in the Total Fee Amount by default to compute the yield (Jira ID: GD-6072)

Issue Description

While computing the yield, the Lease application is considering the Fee that is including the Tax Amount (VAT) too in the Total Fee Amount.

For example, if the VAT is 10% and the Original Amount of the fee is $2,000, then the Total Fee Amount is considering the VAT too. So, the Total Fee Amount = $2,000 + (10% of $2,000) = $2,000 + $200 = $2,200.00.

However, there are scenarios where the system may need to consider the Total Fee Amount including the VAT amount for few fee definitions and excluding the VAT amount for others, and the system was unable to meet such a requirement. For example, while computing the yield in the Lease application, the system was, by default, considering the field, VAT amount added on Fee, while deriving the cash flow and the associated yield and APR. This was not correct as the VAT must be included in the computation only based on the nature of the fee.

Resolution

With the Oxygen patch (3.5004.44) release, this issue has been fixed, and the Lease application has now been enhanced to provide you with an ability to select between a computation that includes the VAT and another that does not.

This has been achieved by making use of a flag named Waived. This flag is used to indicate whether the tax amount (VAT) for the fee is required to be added to the calculations of the yield amount or not.

Thus, the system calculates the yield on the basis of the value of the Waived flag as explained in the following table:

12.9 Issues fixed in December 24, 2021 patches

12.9.1 Account Document Dashboard Related VF Page to be Enabled in Lightning (Jira ID: GD-5948/PDRFF-650)

Issue Description

Earlier, the Account Document Dashboard-related VF page (genesisExtn_AccountRelationDashboard) was displayed in the Account Page Layout.

Resolution

As a fix, we need to directly add that VF page to the Lightning page. And for that, it is required to make this page lightning enabled.

12.10 Issues fixed in November 30, 2021 patches

12.10.1 Oxygen Patch – The Annualize Values Check Box is Missing in the Income Tab – Financial Statements (Jira ID: GD-5764)

Issue Description

The Annualize Values check box is not present in the Financial Spreads > Income Tab.

Resolution

This issue is fixed.

12.10.2 CLONE – System is Not Considering Floor Value to Calculate Amort Value if Interest Rate is Lesser than Floor (Jira ID: GD-5765)

Issue Description

While calculating the Total Due Amount from both the Pricing page and the Payment Schedule > Rate Schedule page, system is considering the Interest Rate and not the Rate Floor even if the Interest Rate < the Rate Floor.

Whereas the condition is to consider the Rate Floor value to generate the Amortization schedule when the Interest Rate < the Rate Floor.

Resolution

This issue is fixed.

12.10.3 Problem with Solving for Payments When Yield is 0 (Jira ID: GD-5733)

Issue Description

While calculating payment amount for a finance lease/operating lease with a configured additional yield, the following errors are being displayed:

1. ERROR: Problem with calculating payment amount – Yield cannot be negative for finance lease

2. Calculated standard yield should be greater than zero.

Resolution

This issue is fixed.

12.11 Issues fixed in October 15, 2021 patches

12.11.1 Financial Spreads Improvement (Jira ID: GD-5137)

Issue Description

The following enhancements are made in this patch release:

• Whitespace on the Financial Spread UI is reduced.

• Row height is reduced to show more rows on a page.

• Width of first column is increased.

• The fields to be showed in the statement header can be customized. The implementation team can hide the fields that a customer does not want to show in the statement header.

  This increases space to show more rows on a page.

• A button is provided to open the below highlighted area in a different tab.

  This increases space to show more rows on a page.

  

Resolution

This issue is fixed.

12.11.2 CLONE - Subfolders Are Not Getting Created for Parties (Guarantor, Co-Borrower) in Both QA & UAT (Jira ID: GD-5409)

Issue Description

On adding parties to a loan application, Document subfolders are not getting created for those parties.

When the first Guarantor party is added, subfolders are created for the party. Subsequently, when more parties (Guarantor/Co-Borrower) are added, the subfolders are not created for them.

Resolution

This issue is fixed

12.12 Issues fixed in August 31, 2021 patches

12.12.1 Scroll Bar is Not Working on Clicking Move to Previous Department in the Task List (Jira ID: GD-4798)

Issue Description

When the Move to Previous Department option is clicked, the Department List table is not scrollable, and all the departments are not displayed.

Resolution

This issue is fixed.

12.12.2 Financial Statement is Displaying the Name Field Not the Label Field (Jira ID: GD-4775)

Issue Description

When a financial statement is printed, the line items are displaying the Name field value rather than displaying the Label field value. Hence, the line item’s name is different in UI and PDF.

Resolution

This issue is fixed. If the label field value is present, the line items will display the label else the name will be displayed in the PDF.

12.13 Issues fixed in July 30, 2021 patches

12.13.1 In Questionnaire Window, Cursor Disappears, Making Difficulty in Typing in the Text Boxes (Jira ID: GD-3548)

Issue Description

In the Questionnaire window, while keying in the details, the cursor disappears intermittently, making it difficult for the user to input the details.

Resolution

This issue is fixed. The cursor stays on the text fields and only goes away, or the data is saved when the user clicks outside the text fields.

12.13.2 Added Periodic Fees are Not Being Reflected in the 1) Amortization Schedule 2) CS Loan Documents (Jira ID: GD-4759)

Issue Description

The fee schedule is not working as expected. Irrespective of whether the Include In EMI check box is selected or not, the fee amount is added to the payment and is reflected on the Payment Schedule page.

On changing the payment Frequency of Fee, the outstanding principal balance is also getting changed.

When a periodic fee is added, verbiage needs to be added in the business loan agreement (BLA) that outlines the type of fee, the amount of the fee, and the fee’s due date.

Resolution

This issue is fixed.

If Include In EMI is true, the fee amount is added to the payment schedule. To include all the associated fees in the payment schedule when the Include In EMI flag is true, frequency, and start date must be the same for all the fees, and the Fee Calculation Method to be Fixed.

12.13.3 Inconsistency in Amortization Schedule on Adding Bank Hours/Holiday (Jira ID: GD-4497)

Issue Description

When bank hours/holidays are added to the amortization schedule, there is an issue in generating the amortization schedule. The amortization schedule is not considering the bank hours/holiday. Random/inconsistent due dates are being displayed in the amortization schedule.

For example, if Friday is set as a holiday, the dates falling on Friday should not be displayed as the due date in the amortization schedule.

Resolution

This issue is fixed. The time zone of the user and the bank hour should be the same.

12.13.4 Tagging of Users in Team Communication (Jira ID: GD-4752)

Issue Description

A user working on the application should be able to tag any Salesforce user to Team Communication without adding them as team members.

Resolution

This issue is fixed. Any Salesforce user can be tagged in Team Communication except the AutomatedProcess UserType.

12.14 Issues fixed in July 15, 2021 patches

12.14.1 Policy Condition Trigger Giving Exception (Jira ID: GD-4698)

Issue Description

While selecting the Do you want to override the status of this policy condition? check box, the policy condition trigger is throwing an exception.

Resolution

This issue is fixed.

12.14.2 Applicant Documents are Not Getting Generated if We are Inserting an Internal Party for a Bank User (Jira ID: GD-4676)

Issue Description

The API for document category creation is throwing an exception and the applicant related documents are not getting generated.

Resolution

This issue is fixed. As per the requirement, the document category creation is not required when the Internal User flag is enabled. The document category is created for those parties for whom the Internal User flag is disabled.

12.14.3 UAT – Spreading – Financial Statement Print Outs Should be in Portrait Layout with each Statements (BS, IS, Ratio, etc) Limited to a Single Page (Jira ID: GD-4675)

Issue Description

The pdf for financial statements (Balance Sheet, Income Statement, Ratio, etc.) is spreading across multiple pages whereas each statement type should fit in single page with portrait layout. (except for extremely large financial)

The rows with zero across all periods should not be printed in the pdf for balance sheet and income statement.

Resolution

This issue is fixed. Rows having zero or null values will not be printed in the pdf.

12.15 Issues fixed in May 17, 2021 patches

12.15.1 Financial Spread – Comma (,) for Digit in Global Cashflow is Getting Replaced with Decimal on Clicking Twice on Values and Value gets Changed to Lower Digit (Jira ID: GD-4392)

Issue Description

In the Global Cashflow statement, if a number is having comma (,) in it, then when the user is double clicking on the number, the comma is replaced with a full stop (.) and the number is becoming a decimal number by rounding to the lower digit. For example, 1,008.00 is changing to 1.00.

Resolution

This issue is fixed.

12.15.2 Financial Spread – In Edit Statement Details Pop Up, the First Value in Drop Down is Coming Back as Blank for “” Statement Year (Jira ID: GD-4393)

Issue Description

While editing a financial statement (Balance Sheet, Income), in the Edit Statement Details window, for the Statement Year and the Previous Statement drop downs, the first value is displayed as blank.

Resolution

This issue is fixed.

12.15.3 Financial Spread – On Editing Income Statement Details from Annual to Interim, the Month Covered is not Updating on Clicking Save Button (Jira ID: GD-4391)

Issue Description

For Income statement, on changing the Statement Type from Annual to Interim, the selected Months Covered is not getting saved and is defaulting to 12.

Resolution

This issue is fixed.

12.15.4 New Policy Condition Page Introducing CSS Overriding Issue on Lookup Type Field (Jira ID: GD-4402)

Issue Description

In the Create Policy Condition window, for the Policy Condition Definition field, the search icon is not aligned correctly, and the asterisk icon is coming below the lookup field.

Resolution

This issue is fixed.

12.15.5 Financial Spread – Save PDF as Content Document (Jira ID: GD-4428)

Issue Description

To use the financial statement with Conga, it needs to be saved as content document in place of attachments.

Resolution

This issue is fixed.

12.15.6 System is Requiring that the Amortization Term be Greater than the Loan term (Jira ID: GD-4426)

Issue Description

For Consumer Unsecured Loan, when both Amortization Term and Term are of same value, system is throwing an exception.

“Term and Amortization Term cannot be same.”

Resolution

Validation is changed to allow both the fields to have same value.

12.15.7 Close Lost Application was Still Counting in the Total Available Facility Calculation for LOC Application (Jira ID: GD-4331)

Issue Description

Application with status Closed-Lost are also calculated in the Total Available Amount.

Resolution

This issue is fixed. If in Custom Settings > Org Parameters > Closed Status, the value is "Closing Documents Generated" and "Approved Converted to Contract", then the system will exclude those applications for calculating the Total Available Amount.

12.15.8 Account Document Skuid Page Issue (Jira ID: GD-4314)

Issue Description

On the Composing - AccountDocumentManagement page, the model conditions need to be updated for DocCategoryAttachmentAsso and DocCategoryParentList so that unwanted data do not come.

Resolution

This issue is fixed.

12.16 Issues fixed in March 30, 2021 patches

12.16.1 Download and Preview not Working for Generated Financial Statement PDF Document (Jira ID: GD-4209)

Issue Description

When a financial statement is generated, it gets listed on the Documents tab. On the Documents tab, there is a download button to download the financial statement and a preview button to view the financial statement. On clicking these buttons, the system is throwing an error.

Resolution

With this fix, these two buttons are hidden. The users can download the financial statement PDF document using the Download option present on the document.

12.16.2 Append Timestamp on Financial Document Attachment (Jira ID: GD-4207)

Issue Description

When multiple financial statement report documents are generated, it is difficult to identify which statement is latest as all the documents are labelled with the same name.

Resolution

With this fix, a timestamp is appended to the financial statement.

12.16.3 Duplicate Entries are Creating while Clicking the Save Button Multiple Times (Jira ID: GD-4227)

Issue Description

While adding a new record in the financial statement, if the user clicks the Save button multiple times, then the same record is getting saved multiple times.

Resolution

This issue is fixed.

12.16.4 While Editing Rule Criteria the Lists are not Displaying Options (Jira ID: GD-3853)

Issue Description

While editing a rule criterion in the Criteria Details section, the options are not visible for the SEQUENCE RELATED OBJECT, FIELD NAME, and OPERATOR lists.

Resolution

This issue is fixed.

12.16.5 Negative Values are not getting saved in Financial Statements (Jira ID: GD-4221)

Issue Description

When a user is entering a negative value such as -123 in a field of a financial statement and saving it, the system is throwing an error.

Resolution

With this fix, the whole value of the field is getting selected and replaced with the user’s input.

12.16.6 All Page Element on the Financial Spreads Tab are Getting Selected (Jira ID: GD-4223)

Issue Description

While editing a financial statement for a specific field, the whole statement is getting selected, which in turn is not allowing the user to edit the field.

Resolution

This issue is fixed.

12.16.7 Incorrect Data is Displayed During Navigation on the Financial Spreads Tab (Jira ID: GD-4212)

Issue Description

When a user is navigating from the collateral’s Balance Sheet tab to the Global Cashflow tab and again to the Balance Sheet tab, the system is displaying the details of the account, and not of the collateral. But, in the top left corner of the page , it is displaying as Collateral.

Resolution

This issue is fixed.

12.16.8 Font on Column Header is Different from Row Header Font (Jira ID: GD-4172)

Issue Description

In the financial statement, column header text and row header text font styles are different.

Resolution

This issue is fixed.

12.16.9 Generate a Single PDF Report for Financial Statements (Jira ID: GD-4161)

Issue Description

Currently, CL Originate is generating pdf per statement type. It is not giving the option to the user to select the statement type and statement period. The generated pdf is not associated with any account.

Resolution

With this fix, the user has the option to select the statement type, the statement year, and to decide whether to include trend analysis in the pdf. The generated pdf is then listed on the Documents tab under the Financial Statement Reports category.

12.16.10 Alert Message not Showing while Moving Away from the Financial Spreads Tab (Jira ID: GD-4153)

Issue Description

On the Financial Spreads tab, when a user is moving from one statement type to another statement type without saving the data, neither the system is throwing any alert, nor the data is getting auto saved.

Resolution

With this fix, the system is throwing an alert message “You have unsaved changes, Please save before leaving this page.”

12.16.11 Unable to Select Parties in Global Cashflow (Jira ID: GD-4168)

Issue Description

When a user is selecting a party from the Select Parties list, it is not getting selected.

Resolution

This issue is fixed.

12.16.12 Loan Fee Enhancement (Jira ID: GD-3306)

Issue Description

User is not able to edit the Revised Original Amount field for Ad-hoc Fee.

Resolution

This issue is fixed.

12.17 Issues fixed in March 5, 2021 patches

12.17.1 Financial Spreads UI issues (Jira ID: GD-4144)

Issue Description

The following are the issues with the Financial Spreads UI:

• Balance Sheet-All-Tab Cursor Behavior – When the tab is moved to the adjacent column, the cursor placement is not correct. It is placed before 0 (the default value).

• Interim Statement – Annualized value is displayed on the screen when the Display Annual Values check box is not selected.

• UCA Cashflow Formatting – Suppresses decimals and shows the round-off values in the template.

• Balance Sheet – At the bottom of the balance sheet template, the Save icon is present at the bottom of the screen, and a + icon is present at the top of the screen.

• Statement Tab Order – Issue with the alignment of the tabs.

• UCA Cashflow – In the UCA cashflow template, all the numbers in a column are not aligned correctly, such as one number is center aligned whereas the other number is right aligned.

• Balance Sheet – In the balance sheet template, all the numbers should be in the xxx,xxx format.

• Overlay of Icons – The icons present in the top right corner are overlaying each other.

Resolution

These issues are fixed.

12.17.2 Financial Statement UI – Columns Misaligned when Tabbed Through (Jira ID: GD-4138)

Issue Description

While updating a financial statement, you can use the Tab key to enter all the data. While using the Tab key at the bottom row, the cursor is moving to the first roll up label where you can click the + sign to add a row. For the left column, the cursor is moving to that roll up label, whereas for right column it is not working as expected. Hence, the labels are not aligned with the correct values.

When the Tab key is pressed continuously, the cursor scrolls to the roll up add buttons, displaying a huge white space. Thus, the financial spread section is reduced in size.

Resolution

With this fix, when the navigation through the table is done using the Tab, all the cells of the table will remain aligned to each other.

13.   Change Record