Winter 2022 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 OriginationWinter 2022 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.

1.1 Purpose of this Document

This document provides information on the following for the Winter 2022 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 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.   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 Winter 2022 release of Q2 Origination.

6.1 Tax ID on Business Information Record (Jira ID: GD-7017)

Feature Description

When an Account record is created via Standard Salesforce UI, the Business Information record is created automatically.

6.2 Download Application Snapshot as a PDF (Jira ID: GD-7011)

Feature Description

Application snapshot can now be downloaded as a PDF File.

6.3 Change Product on an Application (Jira ID: GD-990)

Feature Description

Q2 Origination has been enhanced to support changing of products on an application. When the product is changed, all the associated functionalities are regenerated:

• Default values on to the Application from the new Product

• Documents, Policy Conditions, and Tasks are re-evaluated, and irrelevant records are archived. Policy Conditions are re-evaluated, and any policy condition that is no longer required is archived.

• If the change in product results in a change in product type – Loan v/s LOC – then page layouts on the application are changed.

• If the old application had collateral and the new product is an unsecured product (Product belonging to consumer unsecured and commercial unsecured), the application collateral is deleted and all the steps applicable for the deleted collateral are to be performed.

The following functions must be handled by the implementation/ solution package with reference to the Change Product. This won't be done as part of the Change Product transaction:

• When in the workflow, the change product transaction should be allowed (in addition to application status)

• Regenerate Pricing – the generated pricing API must be invoked

• Regenerate scorecards

• Generate adverse action reasons

• Regenerate approvals

6.4 Assign Task to Queues (Jira ID: PD-1137)

Feature Description

Q2 Origination has been enhanced to support the assignment of queues to tasks within a stage/department. With this enhancement, FIs can now configure a specific set of tasks that need to be performed by a different set of users to separate queues. These users can be different from the users who perform tasks for the application stage/department. Q2 Origination now will enable users from that specific queue to complete the task from the "Required Actions" on the dashboard.

6.5 Approval Management Enhancements (Jira ID: PD-1139)

Feature Description

Approval Management has been enhanced to support the following:

• A new approval instance record is to be created for every update of the primary object record that satisfies the rule.

• Approval instances are now generated on the creation of records as well, prior to this release, it was generated only on the update of the record.

• Approval instances can now be regenerated for approved and rejected instances as well. Prior to this release, there was a restriction on the creation of approval instances when the criteria fields are updated to previously approved or rejected values. This check has now been removed. This is also configurable at the approval definition.

• An API to generate the Approval instance manually has also been introduced.

Please refer to the Upgrade Guide for upgrade steps on this functionality.

7.   Fixed Issues

8.   Known Issues

This section briefly describes known issues known in the Winter 2022 release of Q2 Origination.

9.   New and Modified Objects

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

9.1 New Objects

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

9.2 Modified Objects

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

10.   New and Modified APIs

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

10.1 New APIs

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

10.2 Modified APIs

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

11.   Global Methods

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

11.1 New Global Methods

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

11.2 Modified Global Methods

The following table describes the global methods modified in the Winter 2022 release of Q2 Origination.

12.   Post GA Release

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

12.1 Enhancement made in the April 17, 2024 patches

12.1.1 Creation of Document Categories (Jira ID: GD-8636)

Fixed Version

This enhancement has been made in the following versions:

• Q2 Origination: Winter'22 (4.1014.36)

• CL Originate Skuid Extension: Winter'22 (4.1014.12)

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.

12.2 Issues fixed in the March 28, 2024, patches

12.2.1 Users are not receiving email notifications (Jira ID: PDRFF-2959, GD-8384)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.35)

• CL Common: Winter'22 (4.1013.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.

12.2.2 Team communication messages history is not loading (Jira ID: PDRFF-2948, GD-8363)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.35)

• CL Common: Winter'22 (4.1013.19)

Issue Description

The history of the team communication messages is not loading after upgrading to Winter 2022 release.

Resolution

This issue is fixed now, and the history of the team communication messages is loading.

12.3 Issues fixed in the November 15, 2023 patch

12.3.1 Unable to view Application Snapshot (Jira ID: PDRFF-2536/GD-7941)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.29)

Issue Description

While trying to view the Application Snapshot, the system is displaying an error message in the following two scenarios:

• When the ApplicationSnapshotQuery is the only query listed under the Application Snapshot of the Dynamic Query Sets.

• When no Fee is added to the application.

Resolution

This issue is fixed and the users are now able to view the Application Snapshot in the given scenarios.

12.4 Issues fixed in the October 31 patches

12.4.1 While adding a fee to an application, the Fee Definition values are not updating correctly (Jira ID: PDRFF-2468/GD-7900)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.28)

• CL Originate Skuid Extension: Winter'22 (4.1014.3)

• CL Common: Winter'22 (4.1013.13)

Issue Description

When a fee is added to an application, the added fee is not inheriting the values from the fee definition associated with it.

Let us understand the issue with the following example:

Example

1. Create a Fee Definition with one the following fee types:

   • One Time

   • Monthly

2. Now, in the Fee Definition mark the following fields as true:

   • Include in Dues

   • Capitalized

   • Include in APR

3. Add the created fee in an existing application by selecting the available fee definitions and click Apply Charge.

   The field values for which the Fee Definition was marked as true, is reflecting as false during the fee addition.

Resolution

This issue is fixed as now the application is inheriting equivalent correct values from the Fee Definition.

12.4.2 Unable to view Application Snapshot (Jira ID: PDRFF-2525/GD-7930)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.28)

• CL Originate Skuid Extension: Winter'22 (4.1014.3)

• CL Common: Winter'22 (4.1013.13)

Issue Description

The created Application Snapshot was only visible to the user who created it or to the user with System Administrator profile.

Resolution

This issue is fixed and the Application Snapshot created after the patch installation can be viewed by all users with view permission of the Snapshot object.

12.5 Issues fixed in the September 15 patch

12.5.1 Document categories are not getting deleted correctly (Jira ID: GD-7790/PDRFF-2406)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.27)

• CL Originate Skuid Extension: Winter'22 (4.1014.2)

• CL Common: Winter'22 (4.1013.12)

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:

1. Create a document definition with the Document Definition Name as Identity Documents and keep the Document Type field empty.

2. 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.

3. 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.

4. 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

5. The Parent Category Name field must display as Identity Documents for the Identity Documents Child1 and Identity Documents Child2 document categories.

6. 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.

12.6 Issues fixed in the September 1 patch

12.6.1 An error is displayed once the Approval Definition is saved (Jira ID: PDRFF-2255, PD-1662)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.26)

• CL Originate Skuid Extension: Winter'22 (4.1014.2)

• CL Common: Winter'22 (4.1013.12)

Issue Description

Once the approval definition is saved, the following error message is displayed:

Example to understand this issue

Let us perform the following steps to understand this issue:

1. Go to the  (App Launcher).

2. In the Search apps and items... box, enter Approval Definition and then click it.

3. Click New to define a new approval definition.

4. Specify the details as required and click Save.

   The approval definition is saved, but, an error message is displayed.

Resolution

This issue is fixed by reducing the view state size in the controller class.

An Edit button is also introduced to edit the fields of the Criteria Details section. Earlier, these fields could be edited without clicking any button.

12.7 Issues fixed in the June 30 patches

12.7.1 Clicking the Add New Statement button under the Financial Spreads tab is resulting in an error (Jira ID: PDRFF-2125, GD-7574)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.26)

• CL Originate Skuid Extension: Winter'22 (4.1014.2)

• CL Common: Winter'22 (4.1013.10)

Issue Description

While adding a new statement under the Financial Spreads tab for all the applications that are upgraded from (3.5054.150) to (4.1012.41) release, the following error is displayed:

Example to Understand the Issue

1. Open an application and navigate to the Financial Spreads tab.

2. Click the + button.

3. Click the Add New Statement button.

   The following error is displayed:

   Error Message

   Collection size 19,529 exceeds maximum size of 1,000.

Resolution

This issue is fixed as no error is displayed after clicking the Add New Statement button.

12.8 Issues fixed in the June 1 patches

12.8.1 Maturity Date is not changing when the Term is changed (Jira ID: GD-7216)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.25)

• CL Originate Skuid Extension: Winter'22 (4.1014.2)

• CL Common: Winter'22 (4.1013.9)

Issue Description

When the term of an application is changed, the Maturity Date is not changing accordingly.

Example to Understand the Issue

Let us perform the following steps to understand this issue:

1. Create an application.

2. Edit the Term.

   Expected behavior: The system must update the Maturity Date automatically when the Term is changed.

   
   

   Observed behavior: The system is not updating the Maturity Date when the Term is changed.

   
   

Resolution

This issue is fixed. The system is now updating the Maturity Date when the Term is changed.

12.8.2 Null pointer when an application is moved to previous department (Jira ID: GD-7520)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.25)

• CL Originate Skuid Extension: Winter'22 (4.1014.2)

• CL Common: Winter'22 (4.1013.9)

Issue Description

Observed behavior: While trying to move an application to previous department from a current department, if any changes are done on a task, the system is throwing a Null Pointer Exception. 

Expected behavior: The application must successfully move back to a previous department irrespective of task changes in the Product Department Task Junction.

Resolution

This issue is fixed and the system does not throw any exceptions while moving an application from a current department to a previous department.

12.9 Issues fixed in the March 31 patches

12.9.1 Unable to hide tabs on the Financial Statement page (Jira ID: GD-7342/PDRFF-1803)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.23)

• CL Common: Winter'22 (4.1013.9)

Issue Description

The user is no longer able to hide the tabs on the Financial Statement page like before. This is because the Financial Statement page has been changed from a Skuid page to a VF (Visualforce) page. Due to this, the user is unable to hide the tabs.

Resolution

This issue is now fixed. To be able to hide the tabs on a Visualforce page, the user needs to perform the following steps:

1. Go to (App Launcher).

2. In the Search apps and items... box, enter Skuid and then click it.

3. From the list of Skuid pages, search for the page named ApplicationView_Q2Originate and then click it.

   
   

4. On the Edit Page, in the Skuid Page - ApplicationView_Q2Originate section, scroll down to look for Template and then click it.

   
   

5. In the Template Properties section, in the Template text area, update the source URL by adding the following parameter with the required values:

   • &hiddenTabs='RATIO,UCACASHFLOW,GLOBALCASHFLOW'
     
     

     Note:

     This will hide the following tabs: RATIO, UCACASHFLOW, and GLOBALCASHFLOW. The values of the &hiddenTabs parameter can be any of the following: BALANCESHEET, CASHFLOW, GLOBALCASHFLOW, INCOME, RATIO, UCACASHFLOW, SENSITIVITY. This hides the corresponding tabs that are highlighted in the following image:
     
     
     
     

6. Click Save.

12.10 Issues fixed in the February 28 patches

12.10.1 The Payment of Fee Proceeds field in Fees is not getting updating as per the value in the corresponding Fee Definition Name (Jira ID: GD-7279)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.20)

Issue Description

The Payment of Fee Proceeds field of Fees is not getting updated as per the value in the corresponding Fee Definition Name.

Resolution

This issue is fixed and the Payment of Fee Proceeds field of Fees is now getting updated correctly as per the value in the corresponding Fee Definition Name.

12.10.2 After adding a Party to an Application, the value of Type gets incorrectly updated to Account (Jira ID: GD-7274)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.20)

• CL Common: Winter'22 (4.1013.7)

Issue Description

Upon adding a Party to an Application, the value of the Type field is getting updated to Account even when the Account was created with Type as none or any other value. The value of the Type field must remain the same even after a Party is added.

For example, let's say an Application is created with the value of Type as Customer - Direct or None. Now let us say we add a Party. After adding the Party, the value of Type is getting updated to Account. The value of Type must remain as Customer - Direct or None.

Resolution

This issue is fixed and the Type field displays the correct value.

12.10.3 Maturity Date reverts to the original date for a single payment frequency after trying to update it to the required date (Jira ID: GD-7273)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.20)

Issue Description

After changing the Payment Frequency to a single payment frequency and updating the Maturity Date to the required date, on clicking Generate Schedule, the system reverts the Maturity Date to the original date. The system must retain the new value of the Maturity Date entered.

For example, let us say we have a loan application for a 12-month Term with a Maturity Date of 02/03/2023. Now let us say, on the Application Dashboard, we go to Pricing > Payment Schedule and click Edit to change the loan application to a single payment frequency loan with a Maturity Date of 01/03/2024. Then on saving this and then clicking Generate Schedule, the system is reverting the Maturity Date to 02/03/2023 instead of keeping it as 01/03/2024.

Resolution

This issue is fixed and the system retains the newly updated value of the Maturity Date after rescheduling.

12.10.4 New equipment is created for the Package Application instead of the child Application (Jira ID: PDRFF-1669/GD-7257)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.20)

• CL Common: Winter'22 (4.1013.7)

Issue Description

When trying to create new Equipment in a child Application of a Package Application, the system is creating it for the Package Application instead of creating it for the child Application.

For example, let's say an Application of the Record Type, Package, is created. Then, in this Application, let us say we create a child lease Application and then try to add New Equipment to this lease Application. The system is creating the new equipment in the Package Application, instead of creating it in the child lease Application.

Resolution

This issue is fixed and the system is now correctly creating the new equipment in a child Application.

12.10.5 The Maturity Date field is not modifiable to update the required Maturity Date when the payment frequency is changed to a single payment (Jira ID: GD-7215)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.20)

Issue Description

When trying to create new Equipment in a child Application of a Package Application, the system is creating it for the Package Application instead of creating it for the child Application.

For example, let's say an Application of the Record Type, Package, is created. Then, in this Application, let us say we create a child lease Application and then try to add New Equipment to this lease Application. The system is creating the new equipment in the Package Application, instead of creating it in the child lease Application.

Resolution

This issue is fixed and the Maturity Date is now modifiable when the payment frequency is changed to a single payment.

12.10.6 Changing any detail of the Loan Summary or any detail of the Fee resets the Days Convention to 365/365 (Jira ID: GD-7194)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.20)

Issue Description

When you change any details of the Loan Summary by going to Application Dashboard > Loan > Edit and then saving, or when you change the details of the Fee by going to Application Dashboard > Pricing > Fee, then the system is resetting the value of the Days Convention field to 365/365. The Days Convention field must have the same value as the one before the update.

Resolution

This issue is fixed and the Days Convention field value does not change when any detail of the Loan Summary or the Fee is changed.

12.11 Issues fixed in the February 15 patches

12.11.1 The system lists all parties in the Other FI Contracts section even when only party is selected while creating a Global Debt Service (Jira ID: GD-7076)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.17)

• CL Originate Skuid Extension: Winter'22 (4.1014)

• CL Common: Winter'22 (4.1013.3)

Issue Description

In financial spreads, while creating a global debt service statement, if you have selected just one party, the system lists contracts from all parties in the Other FI Contracts section.

Resolution

This issue is now fixed and the system lists only those parties in the Other FI Contracts section that were selected while creating a global service debt.

12.11.2 The system is throwing an exception while creating the CL Originate Application (Jira ID: PDRFF-1661/GD-7255)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.17)

• CL Originate Skuid Extension: Winter'22 (4.1014)

• CL Common: Winter'22 (4.1013.3)

Issue Description

After upgrading to Winter'22 release, while creating a CL Originate Application, the system is throwing the following exception:

"Interest Only Period should be less than Application Term."

Resolution

This issue has now been fixed by adding additional conditions to be checked in the internal logic before the system decides to throw this exception.

Earlier, the system was throwing the exception when the following conditions were met:

• If the Interest Only Period is not null.

• If the Term of the Application is less than or equal to the Interest Only Period.

Now, the list of conditions have been updated as follows, and the system now throws the exception when all of the following conditions are met:

• If the Interest Only Period is not null.

• If value of both the Term of the Application and Interest Only Period is not zero.

• If the Term of the Application is less than or equal to the Interest Only Period.

12.11.3 The system is throwing a Null Pointer Exception while creating an Application when Fee Set is not defined in the CL Product (Jira ID: PDRFF-1668/GD-7266)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.17)

• CL Originate Skuid Extension: Winter'22 (4.1014)

• CL Common: Winter'22 (4.1013.3)

Issue Description

After upgrading to Winter'22 release, while creating a CL Originate Application, when the Fee Set is not defined, the system is throwing the following Null Pointer Exception:

"Attempt to de-reference a null object."

This issue was occurring because the system was encountering a null value while calculating the loan amount and the loan amount also included the total fee amount which was null. The total fee amount had a null value because a Fee Set was not defined.

Resolution

This issue has been fixed. The checks in the internal logic have now been updated to accept the loan amount even when it amounted to zero.

12.11.4 Q2 Originate upgrade to Winter'22 is failing (Jira ID: PDRFF-1634/GD-7231)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Winter'22 (4.1014.17)

• CL Originate Skuid Extension: Winter'22 (4.1014)

• CL Common: Winter'22 (4.1013.3)

Issue Description

While trying to upgrade to Winter'22, the upgrade is failing with the following error message:

"Error: (Applications_c.Loan_Review_Summary_c) 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.

(Applications_c.Other_Reasons_c) 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."

You may face this error if you add custom fields that are Large Text Area or the Rich Text and then upgrade to Winter'22 that has some new fields too. When the number of the characters in the Large Text Area or the Rich Text custom fields on the Application object is exceeding the limit of the total number of characters for the Application object, the system throws this error.

Resolution

This issue is mitigated by reducing the length of characters of the following added fields to 32768:

• genesis_Borrowing_Entity_Summary_c

• genesis_Financial_Information_c

• genesis_Loan_Review_Summary_c

• genesis_Risk_Assessment_c

12.11.5 The system is throwing an error message while creating an Application and Party with the Record Type as Person Account (Jira ID: PDRFF-1529/GD-7191)

Fixed Version

This issue has been fixed in the following version:

• Q2 Origination: Winter'22 (4.1014.17)

• CL Common: Winter'22 (4.1013.3)

Issue Description

While creating the Application and Parties or while editing Parties, if the type of the Account (Legal Class Name) for the Application or the Party is Individual and if the Record Type is Person Account, then the system is displaying the following error messages:

• During Application creation, the error message is: "Unable to insert/update Account - Unable to create/update fields: Name. Please check the security settings of this field and verify that it is read/write for your profile or permission set."

• During Party creation or update, the error message is: "Unable to insert/update Contact-Account pair - Unable to create/update fields: Name. Please check the security settings of this field and verify that it is read/write for your profile or permission set."

This is because when the Record Type is Person Account, the Salesforce expects the First Name and Last Name but when the API (BankingModelBorrowerAPIImpl) creates a Name field by combining the First Name and the Last Name and then inserts this record to the database, the system displays the preceding error messages.

Resolution

This issue has been fixed by modifying the API (BankingModelBorrowerAPIImpl) such that before doing a DML operation on the database, it checks for the following conditions:

• Person Account is enabled

• Record Type of the account passed is Person Account

If the preceding conditions are true, then the API uses the First Name and Last Name for inserts or updates to the database and not the Name field.

13.   Change Record