Platinum 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.
The contents of this document are applicable to all the customers who have installed the Q2 IntegrationsPlatinum version (3.6004) 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.
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.
1.1 Purpose of this document
This document provides information on the following for the Platinum release:
1.2 Intended audience
The audience of this document includes business users, implementers, and system administrators.
1.3 Prerequisites for use
This document assumes a basic knowledge of the product concepts, the product release, and the Salesforce platform.
2. 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 Integrations.
3. Upgrade considerations
For information on the upgrade steps, see release-related steps in the Q2 Product Upgrade Guide.
4. List of Abbreviations
| Abbreviated Term | Description |
|---|---|
| SOD | Start of Day |
| EOD | End of Day |
| AMZ | Amortized |
5. System performance
To view the SOD batch jobs performance statistics for Q2 Integrations without customizations under test conditions, see the Q2 Performance Benchmarking Guide.
6. New features and enhancements
There are no new features and enhancements added in this release.
For a detailed description of the new features and enhancements, see the Q2 Integrations User Guide published over the Q2 Customer Portal:
6.1 Integration Framework: Add new fields in Integration Logs (Issue key: INTCL-872)
Feature Description
As a part of this feature, some new fields are included in the Integration Logs object to give a 360-degree view of the Third-party API data received by Integration framework. Some of those fields includes HTTP code, HTTP status, the embedded third-party code, third-party error message, overall status. This also enhance the way we display various responses on our UI screen.
6.2 Request Log Feature - Data value too large error in Integration Framework (Issue key: INTCL-856)
Feature Description
If the request body is too large to fit in a field, then request string gets stored in the content version and contentVersionId is provided in the request log field of integration log or Integration request.
6.3 Addition of External ID in All the Integration Specific Objects for SMB Workflow (Issue key: INTCL-772)
Feature Description
This feature generates a unique ID for all the records created for all the different objects of Integration Framework to uniquely identify the given record. This unique ID field namely "External Id" under no circumstances should be modified once created, however, the name of any integration object records can be changed if required. This allows to identify any provider, family, and so on uniquely using External ID and does not impact even if the names are modified.
6.4 Error Handling in Integration Framework (Issue key: INTCL-700)
Feature Description
Currently, there is no mechanism in framework to track the request and associated response for an application or borrower or collateral. Implementor is not able to identify the success or failure of request and response.
Framework provides a way to store the request and associated response. We are creating two objects: Integration Request and Integration response which are used to store request and response string and error related to them if any. This request and response objects are attached to the application or party (Account or contact ID) or collateral involved via Integration request parameters which is ease to track the success and failures of request and response.
6.5 Amortization Schedule (Issue key: INTCL-572)
Feature Description
This feature allows Q2 to use CSI's Sherman Calculations that produce the amortization schedules. The CSI Sherman Calculations produce these amortization fields: Due_Date__c,Due_Interest__c, Total_Due_Amount__c, Opening_Principal_Balance__c, Closing_Principal_Balance__c.
On click of generate documents, any old existing amortization schedules get deleted and is replaced with new records from CSI Sherman Calculations. The field genesis_Total_Estimated_Interest_c is also updated on the application object. Ensure that the 'csi run time session' api config's response mapping has all the parameters set to true.
6.6 Commercial Use Cases Certification (Issue key: INTCL-518)
Feature Description
Asset classes supported are Commercial Unsecured, Commercial Secured and Commercial Real Estate.
6.7 DocuSign: Esignature (Issue key: INTCL-515)
Feature Description
DocuSign is a service provider which allows users to send and sign documents for digital signature (eSigning).
Majority of our customers use a digital service provider to gets their contract documents eSigned and most of them use Docusign, via Docusign for Salesforce app or Docusign portal.
Sometimes, the use case requires using Docusign’s APIs to be used to send document(s) for eSigning.
This integration is done to provide such customers the flexibility to call Docusign APIs.
This feature provides an Envelope Id for each request made by the users so that users can track status of the envelope on docusign portal
once all the documents got eSigned, users can be able to view signed documents undersigned closing documents folder on application page.
6.8 SBSS Business Credit: FICO (Issue key: INTCL-466)
Feature Description
FICO Liquid Credit is a FICO service that provides the ability to use consumer and commercial credit data to generate predictive scores. For the purposes of this epic the focusing on the SBSS 7 predictive scorecard and the Business Lookup function.
The enhancements can allow the user to request, receive, store, and view the information sent by FICO for business details.
This feature also allows the user to see any errors which come back and take appropriate action.
The enhancement can also allow users to do straight through processing by configuring certain parameters that automatically order principals associated to the business for which credit is being requested by FICO.
6.9 KYB: BusinessInstantID: LexisNexis (Issue key: INTCL-450)
Feature Description
LexisNexis InstantID Business is a suite of small business verification products that you can use to improve your verification processes and perform KYB. This also allows to verify up to five business owners (auth reps) along with the KYB request.
This feature can allow the user to perform KYB by allowing the user to make a request, receive response, store the responses in the database and see the information sent back from LexisNexis Business InstantID on the UI.
This feature can also allow the user to see any errors which come back and take appropriate action.
6.10 KYC/Fraud Vendor Implementation: Socure (Issue key: INTCL-376)
Feature Description
Socure ID+ provides Identity (IDV) and Document Verification (DV) services through various modules (such as Fraud, KYC, Email risk, Address risk, Phone risk, Global watchlist, Alert list, Social, and Document Verification) using machine learning algorithms to perform KYC for individuals.
This feature can allow the user to perform KYC by allowing the user to make a request, receive response, store the responses in the database and see the information sent back from SocureID+ on the UI.
This feature can also allow the user to see any errors which come back and take appropriate action.
6.11 EquifaxID Matrix Integration (Issue Keys: INTCL-819, INTCL-470)
Feature Description
Equifax ID Matrix is a KYC provider in Australia. IDMatrix Australia couple’s identity verification with a fraud assessment and compile the results into a single outcome.
This feature can allow the user to do KYC for an individual by allowing the user to make a request, receive response, store the responses in the database and see the information sent back from equifax ID matrix on the UI.
This feature can also allow the user to see any errors which come back and take appropriate action.
6.12 ABN Lookup Integration (Issue key: INTCL-727)
Feature Description
ABN Lookup is the free public view of the Australian Business Register (ABR). It provides access to publicly available information supplied by businesses when they register for an Australian Business Number (ABN).
This feature can allow the user to view and confirm corporate information by allowing the user to make a request, receive response, store the responses in the database and see the information sent back from ABN on the UI.
This feature can also allow the user to see any errors which come back and take appropriate action.
7. Fixed issues
For the details of the issues fixed in a release of Q2 Integrations, see the Post GA section of that particular release's Release Notes.
This section describes the issues fixed in the Platinum release of Q2 Integrations.
7.1 [FICO Business Credit]: Generic error message in the UI (Jira ID: INTCL-681)
Issue Description
If there is an error in integration log after clicking the Fico Request button, the system shows the generic error message in the UI.
Resolution
This issue is fixed.
7.2 Business Established Date CSi (Jira ID: INTCL-890)
Issue Description
For CSi mapping need to pass the Business Established Date field for a Resolution, which is captured in the Originate but it is not mapped to CSi.
Resolution
This issue is fixed.
7.3 No integration log is generated on specifying incorrect zip code (Jira ID: INTCL-870)
Issue Description
If the zip code in the address of any entity is less than or more than six digits and when you click the Fico Request then no change is observed in the UI as well as no integration log is generated.
Resolution
This issue is fixed.
7.4 Same entity name is displayed multiple times (INTCL-871)
Issue Description
If the entity is assigned with different party types, the same entity name is displaying multiple times on the Generate Score Card screen.
Resolution
This issue is fixed.
7.5 [FICO]: Error handling for Mandatory fields (INTCL-875)
Issue Description
There needs to handle the errors for mandatory fields when you specify the incorrect data.
Resolution
This issue is fixed.
7.6 [FICO]: The Purchase check box is enabled and is not editable (Jira ID: INTCL-909)
Issue Description
After purchasing new report for unique principals, the Purchase check box is enabled and is not editable.
Resolution
This issue is fixed.
7.7 [FICO]: Rescore fails to function (INTCL-915)
Issue Description
When the Fico request is executed with business the Rescore fails to function. It works fine when Fico request is executed with principals only.
Resolution
This issue is fixed.
7.8 Facing salesforce governor limits for contact address (INTCL-919)
Issue Description
When selecting the Business, the system is throwing the salesforce governor limits for contact address.
Resolution
This issue is fixed.
8. Known issues
This section describes the known issues in the Platinum release of Q2 Integrations.
8.1 The Notary Acknowledgment Display Type field is shows mandatory (Jira ID: INTCL-774)
Issue Description
In CSI's run time screen the Notary acknowledgment display type field is showing as mandatory on the Loan Details tab.
9. New and modified objects
This section briefly describes the new and modified objects in the Platinum release of Q2 Integrations.
For details on all the Q2 Integrations objects, see Q2 Integrations Data Dictionary.
9.1 New objects
The following table describes the new objects added in the Platinum release of Q2 Integrations.
| Object Name | Description |
|---|---|
| intdm__Corporate_Information__c | This object holds fields for storing corporate information from various third-party vendors. |
| intdm__Corporate_Information_ABN_Details__c | This object holds fields for storing certain business information specific for ABN lookup. |
| clcommon__Application_Properties__c | This will be majorly used by integrations. This object will be overridden in Integrations data model where all the fields will present to avoid dependency of integrations on common. There will be a look-up added in genesis Application to this object to avoid dependency of originate going forward |
| clcommon__Funding_Transaction_Properties__c | This will be majorly used by integrations. This object will be overridden in Integrations data model where all the fields will present to avoid dependency of integrations on common. There will be a look-up added in genesis Funding Transactions to this object to avoid dependency of originate going forward |
| clcommon__Asset_Information_Properties__c | This will be majorly used by integrations. This object will be overridden in Integrations data model where all the fields will present to avoid dependency of integrations on common. There will be a look-up added in genesis Asset Information to this object to avoid dependency of originate going forward |
| clcommon__Liability_Properties__c | This will be majorly used by integrations. This object will be overridden in Integrations data model where all the fields will present to avoid dependency of integrations on common. There will be a look-up added in genesis Liability to this object to avoid dependency of originate going forward |
| intdm__Financial_Institutions_Information__c | This object stores the configuration fields for Closing document generation. |
| intdm__Personal_Demographic_Information__c | This object stores the demographic information of the Individual namely race, ethnicity, and other related information. |
| intdm__Bureau_Information__c | This object stores the bureau configuration information. Bureau is an agency that collects and researches individual/business information. |
| intdm__Characteristic__c | List of score reason codes and data source. Max 4 occurrences. May match the ModelReason, but not always. |
| intdm__Scorecard_Details__c | SBSS 7 can return two scores, we need to present both in scorecard if present. |
| intdm__KYB_Fraud__c | Store certain data fields for KYB and Fraud data from various vendors in a normalized manner so that can use for decisioning and compliance. |
| intdm__Risk__c | This object holds fields for storing Risk related details sent by KYB/KYC providers. |
| intdm__KYC_Fraud__c | Store certain data fields for KYC and Fraud data from various vendors in a normalized manner so that can use for decisioning and compliance. |
| intdm__Recommendations__c | This object holds fields for storing recommendations sent from the Vendor. This could be overall result, KYC result or Fraud Assessment. |
| intdm__Risk__c | This object holds fields for storing Risk related details sent by KYB/KYC providers. |
| intdm__Score__c | This Object holds fields to store score details sent by KYC/KYB providers. |
| intdm__Recipient_Information__c | Used by Create Envelope Adapter to get details of Recipient to be sent to Docusign. |
| intdm__Tab_Information__c | Used by Create Envelope Adapter to get details of Tab to be sent to Docusign. |
| intdm__Template_Informations__c | Used by Create Envelope Adapter to get details of Templates to be sent to Docusign. |
| intFramework__Integration_Request__c | This object represents the request string and errors related to it if any. |
| intFramework__Integration_Request_Parameter__c | This object represents the request parameters related to a request. |
| intFramework__Integration_Response__c | This object represents the response string and errors corresponding to a request if any. |
9.2 Modified objects
The following table describes the objects modified in the Platinum release of Q2 Integrations.
| Object Name | Field Name | Description |
|---|---|---|
| genesis__Business_Information__c | intadapter__Fico_Score_Date_Time__c | This is used to store date and time of Fico response. |
| clcommon__Personal_Information__c | intadapter__Fico_Score_Date_Time__c | This is used to store date and time of Fico response. |
| genesis__Funding_Transaction__c | intadapter__Payee_Name__c | This is the name of the payee to whom the payments are being made |
| intadapter__TRID_Non_Purchase_Payments__c | This checkbox will identify all non-purchase payments/payoffs that needs to be made as part of TRID Loan Closing | |
| genesis__Applications__c | genesis__Application_Properties__c | This is a reference to the application properties that will hold application related data specific to integrations |
| genesis__Funding_Transaction__c | genesis__Funding_Transaction_Properties__c | THis is a reference to the Funding Transactions properties that will hold Funding Transactions related data specific to integrations |
| genesis__Asset_Information__c | genesis__Asset_Information_Properties__c | This is a reference to the Asset Information Properties that will hold Asset information related data specific to integrations |
| genesis__Liability__c | genesis__Liability_Properties__c | THis is a reference to the Liability properties that will hold Liability related data specific to integrations |
| User | intdm__NMLS_ID__c | This is the unique NMLS ID assigned to the mortgage loan user |
| intdm__Closing_Cost_Expiration_Date__c | This is the date after which the closing costs disclosed in loan estimate will expire. This date is usually 10 business days from loan estimate date. | |
| intdm__Credit_Insurance_Offered__c | This indicates if the lender will solicit, offer, or sell any insurance or annuity product (or both) in connection with this loan transaction. A disclosure required by law will automatically be provided when credit insurance is offered. If the lender does offer credit insurance, then all parties to the loan transaction must sign acknowledging receipt of the disclosure. | |
| intdm__Credit_insurance_products_offered_type__c | This indicates the credit insurance products by the lender, if any. If products are listed this information will populate on applicable documents | |
| clcommon__Application_Properties__c | intdm__HELOC_Early_Disclosure_Date__c | This is the date on which the HELOC early disclosure was generated for HELOC Applications |
| intdm__Home_Improvement_Loan__c | This indicates whether this loan will be classified as a home improvement loan. | |
| intdm__Is_High_Cost_Loan__c | This checkbox will determine if the Loan Application has been classified as a high cost loan. This flag will be set to true if Loan is subject to Section 32 | |
| intdm__Notice_Days_For_Change_Or_Cancellation__c | This data is necessary to indicate the number of days in which the borrower/collateral owner must notify the lender of any change in coverage or cancellation of the insurance policy that is covering the collateral property. | |
| intdm__Periodic_Interest_Rate_Change_Cap__c | This is the maximum incremental interest rate change that can occur within one period of rate change. If rate revision frequency is Annual, then this is the maximum incremental increase that can happen within one year. | |
| intdm__Proceeds_Use_Type__c | This is how the borrower has stated the loan proceeds will be used. | |
| intdm__Reissue_Revised_Loan_Estimate__c | This checkbox will determine if key loan data elements have been modified after the first loan estimate was issued | |
| intdm__Recission_Date__c | This date is the date by which the borrower can cancel the loan after closing. This date is calculated as Expected Close Date + 3 Business Days. | |
| intdm__Settlement_Agent_Contact__c | This is the individual contact person acting on behalf of the settlement agent who is conducting the loan settlement. | |
| intdm__Settlement_Agent_File_Number__c | This is the number assigned to the transaction by the settlement agent for identification purposes. | |
| intdm__Settlement_Agent__c | This is the business name of the settlement agent who is conducting the loan settlement. | |
| clcommon__CL_Purpose__c | intdm__Purpose_Type__c | This indicates the purpose for which the loan was requested by the borrower. This information is included in the Loan Estimate and the Closing Disclosure. |
| clcommon__Company__c | intdm__Governing_Law_State__c | |
| clcommon__Floating_Rate_Index__c | intdm__Index_Description__c | This is the description of the Index being used in Lending |
| clcommon__CL_Product__c | intdm__HELOC__c | This field will store the corresponding CS HELOC product code |
| intdm__CS_HELOC_Product_Code__c | This field will store the relationship between draw and repayment period calculation methods. The value selected here will drive the Payment calculation methods | |
| intdm__Relationship_Between_Draw_And_Repayment__c | This field will store if the HELOC product will be a fully Fixed Rate or fully variable rate. The rate cards associated with this product must be all "fixed rate" or "variable rate" depending on the value selected here. | |
| intdm__Interest_Rate_Options__c | This field will determine if insiders/employees will be allowed to apply for the product. If this is "yes”, then | |
| intdm__Insider_Loans_Allowed__c | This field captures the minimum payment calculation method for the repayment period. The value selected here must default to the Application | |
| intdm__Payment_Calc_Method_Repayment_Period__c | This field captures the minimum payment calculation method for the draw period. The value selected here must default to the Application | |
| intdm__Payment_Calc_Method_Draw_Period__c | This field will store the fixed payment amount that needs to be repaid during Draw period. This field is applicable only if Minimum payment calculation method (draw period) is any of the following: | |
| intdm__Fixed_Payment_Amount_Draw_Period__c | This field will capture umber of term periods of the Repayment Period. This will be "2" if Repayment Period is 2 Months | |
| intdm__Repayment_Period_Term_Unit__c | This field will capture if the Repayment Period is in Months or Years. This will be "Months" if Repayment Period is 2 Months | |
| intdm__Repayment_Period_Term_Periods__c | This field will capture the payment frequency in the Repayment Period | |
| intdm__Payment_Frequency_Repayment_Period__c | "This field will store the percentage of outstanding that needs to be repaid during Repayment Period. This field is applicable only if Minimum payment calculation method (Repayment Period) is any of the following: Fixed fraction of outstanding principal balance Greater of a percentage of the outstanding balance or a Dollar Amount Greater of a percentage of the outstanding balance plus accrued interest or a Dollar Amount Greater of a percentage of the outstanding balance or accrued interest. Percentage of the outstanding balance Percentage of the outstanding balance plus accrued interest" | |
| intdm__Payment_Percentage_Repayment_period__c | "This field will store the fixed payment amount that needs to be repaid during Repayment Period. This field is applicable only if Minimum payment calculation method (Repayment Period) is any of the following: 1) Fixed Amount Plus Accrued Interest 2) Fixed Amount 3) Fixed Amount per $1000 of Outstanding Balance 4) Greater of Fixed Amount or Accrued Interest" | |
| intdm__Fixed_Payment_Amount_Repayment_Period__c | This will store if Initial discount rate or premium rate is applicable for this product. Corresponding Rate cards have to be defined and mapped to the product | |
| intdm__Initial_Interest_Rate_Options__c | This field will store the default interest rate revision frequency in a variable Rate loan. This field is applicable only if Interest Rate Type is "Variable" | |
| intdm__Rate_Revision_Frequency__c | This field will store the accrual method/day counting convention for this product | |
| intdm__Days_Convention__c | This is the minimum interest rate that will be charged for the application associated to the product | |
| intdm__Floor_Rate__c | This is the maximum interest rate that will be charged for the application associated to the product | |
| intdm__Ceiling_Rate__c | This field will capture number of term periods of the draw period. This will be "2" if draw period is 2 Months | |
| intdm__Draw_Period_Term_Unit__c | This field will capture if the draw period is in Months or Years. This will be "Months" if draw period is 2 Months | |
| intdm__Draw_Period_Term_Periods__c | "This field will store the percentage of outstanding that needs to be repaid during Draw period. This field is applicable only if Minimum payment calculation method (draw period) is any of the following: Fixed fraction of outstanding principal balance | |
| intdm__Payment_Percentage_Draw_period__c | "This field will store the percentage of outstanding that needs to be repaid during Draw period. This field is applicable only if Minimum payment calculation method (draw period) is any of the following: Fixed fraction of outstanding principal balance Greater of a percentage of the outstanding balance or a Dollar Amount Greater of a percentage of the outstanding balance plus accrued interest or a Dollar Amount Greater of a percentage of the outstanding balance or accrued interest. Percentage of the outstanding balance Percentage of the outstanding balance plus accrued interest" | |
| intdm__Fixed_Payment_Amount_Draw_Period__c | "This field will store the fixed payment amount that needs to be repaid during Draw period. This field is applicable only if Minimum payment calculation method (draw period) is any of the following:
1) Fixed Amount Plus Accrued Interest 2) Fixed Amount 3) Fixed Amount per $1000 of Outstanding Balance 4) Greater of Fixed Amount or Accrued Interest" |
|
| clcommon__Collateral__c | intdm__Is_trailer_included_in_watercraft__c | This field is to identify if trailer included in watercraft |
| intdm__Mechanically_Propelled_Watercraft__c | This field is to identify if the watercraft is mechanically propelled | |
| intdm__Navigation_Equipment_Included__c | This field is to identify if the watercraft has a navigation equipment | |
| intdm__New_Manufactured_Home__c | This field is to identify if the Manufactured Home is new | |
| intdm__Outboard_Motor_in_Watercraft__c | This field is to identify if the watercraft has an outboard motor | |
| intdm__Sailboat__c | This field is to identify if the watercraft is a sailboat | |
| intdm__RealEstate_Legal_Description__c | This field describes the Real Estate Property. | |
| intdm__Escrowed_Number_Of_Months__c | This is the period for which the fee is escrowed. This field is applicable only if the TILARespa Fee category = Initial Escrow Payment at Closing | |
| intdm__TILA_RESPA_Fee_Category__c | This picklist identifies the different fee categories applicable for TRID Loan. | |
| intdm__TILA_RESPA_Fee_Type__c | This picklist identifies the different Fee types for Escrow and prepaid fees. This picklist is applicable only if TILARESPA fee catgeory is Initial Escrow Payment at Closing or Prepaids | |
| intdm__Type_of_service_borrower_shopped_for__c | This picklist identifies the different services that a borrower did not shop for. Only applicable if TILA RESPA Fee catgeory =Services Borrower Cannot/Did not Shop For | |
| intdm__Type_of_services_added_by_the_Lender__c | This picklist identifies the different services that a borrower did not shop for. Only applicable if TILA RESPA Fee catgeory =Services Borrower Cannot/Did not Shop For | |
| intdm__Description_of_Other_taxes_insurance__c | This field is mandatory if the TILA RESPA Fee Type = Other. This field will capture any other type of taxes and insurance to be included in estimates | |
| intFramework__Integration_Log__c | intFramework__Third_Party_Http_Code__c | The HTTP response code received in the third-party Response header. |
| intFramework__Third_Party_Http_Status__c | The HTTP response status received in the third-party Response header. | |
| genesis__Applications__c | intadapter__Envelope_Id__c | Specifies the Envelope Id of the esignature. |
| intadapter__Is_Closing_Documents_Signed__c | Specifies the eSignature on the documents has been completed. |
10. New and modified REST APIs
This section briefly describes the new and modified APIs in the Platinum release of Q2 Integrations.
For details on all the Q2 Integrations REST APIs, see Q2 Integrations REST APIs Guide.
10.1 New APIs
This section briefly describes the APIs that are added in the Platinum release of Q2 Integrations.
| API Name | Description |
|---|---|
| IntegrationWebServiceV2 | This API is used to invoke third-party services defined under integrations framework from a process builder, UI or API. |
10.2 Modified APIs
There are no APIs modified in the Platinum release of Q2 Integrations.
11. New and modified global methods
There are no global methods added or modified in the Platinum release of Q2 Integrations.
For details on all the Q2 Integrations global methods, see Q2 Integrations Global Methods Guide.
12. Post GA release
Follow this section for the details on the issues fixed in the patches on the Platinum release of Q2 Integration.
12.1 Issues fixed for December 24, 2021 patches
12.1.1 Refactoring of RATA Geocoding Integration from SOAP to REST API (Jira ID: INTCL-1330)
Fixed Version
This issue has been fixed in the following version:
Q2 Integration Adaptor (3.6010.3)
Enhancement Description
Geocoding is the process of converting addresses such as a street address into geographic coordinates such as latitude and longitude, which is used to place markers on a map, or position the map. In this patch the RATA Geocoding integration code is refactored from SOAP (XML code) to REST (JSON code) API.
Resolution
To configure this change, perform the following steps:
-
Activate Geocoding Integration Provider
Log in to your Salesforce account and go to Integration Configuration Setup > Activate/Deactivate Provider.
-
Select Active checkbox of Geocoding as the Provider Name, and then click Save.
Note:If the Active checkbox is selected, please clear and reselect the check box again.
-
Create Named Credential Instance
Log in to your Salesforce account and go to Q2 Integration > Setup.
In the Quick Find box, search for Named Credentials, and then click it.
-
Create two new credentials with the following details:
-
Configure the Created Named Credentials
-
Configure the Authentication Named Credential:
-
Log in to your Salesforce account and go to Q2 Integration > Integration API Configuration. Create or update Integration Configurations with the following created Authentication Named Credential detail:
Note:The Authentication Named Credentials is the named credentials which has the token URL detail.
-
-
Configure the API Named Credential:
Log in to your Salesforce account and go to Q2 Integration > Integration API Configuration.
-
Create or update Integration Configurations with the following created API Named Credential detail:
-
Configure Connection Configurations
Log in to your Salesforce account and go to Q2 Integration > Connection Configuration.
-
Create or update Connection Configurations with the following details:
-
12.2 Issues fixed for December 10, 2021 patches
12.2.1 Error when single collateral is associated with multiple applications (Jira ID: INTCL-1405 / PDRFF-609)
Fixed Version
This issue has been fixed in the following version:
CL Integration Coresmen (3.6081.2)
Issue Description
While performing Book To Core action, if a single collateral is associated to multiple applications and those associated applications do not exist in the core then the system is throwing the following error:
"Invalid Collateral Tracking Account."
Resolution
A collateral can be associated with multiple applications, but those applications must already exist in the core.
All adapters needs to be deactivated and activated upon installing new coresmen package.
12.2.2 Call to the Create Collateral API is failing (Jira ID: INTCL-1393)
Fixed Version
This issue has been fixed in the following version:
CL Integration Coresmen (3.6081.2)
Issue Description
When the orchestrator is run with missing personal information for an account, the
call to Create Collateral API is failing with the following third-party message:
“{"responseId": "477bbfcf152d4ee9ab6c491c351dc9b9", "messages": [{"source": "Coresmen",
"message": "core error details:
Unknown macro: {'error_code'}
]'}"}], "data": null}.”
Resolution
The code is fixed to address the issue.
All adapters needs to be deactivated and then activated upon installing new Coresmen package.
12.2.3 Issue in generating Update Collateral APIs (Jira ID: INTCL-1411)
Fixed Version
This issue has been fixed in the following version:
CL Integration Coresmen (3.6081.2)
Issue Description
While performing Book To Core action on two applications with the same collateral, the only one Update Collateral API is getting generated. The system must generate two Update Collateral APIs for both the applications.
Resolution
Now the Update Collateral API is generated for each application that is booked to the core.
All adapters needs to be deactivated and activated upon installing new coresmen package.
12.3 Issues fixed for October 29, 2021 patches
12.3.1 Error while adding party types to an application (Jira ID: INTCL-1240 / PDRFF471)
Fixed Version
This issue has been fixed in the following version:
CL Integration Coresmen (3.6069)
Issue Description
While performing Book To Core action, if the added parties are other than Borrower, Co-Borrower, Payee, Agent, Guarantor, and Grantor Party types then the system is throwing Party Type is missing or invalid message.
Resolution
The code is fixed to address the issue. All Party Types are now supported from Create Account Coresmen Adapter as Secondary Relationships.
An application can now have two parties; a primary party, Borrower, and a secondary party as one of the following:
Guarantor
Signer
Cosigner
Beneficial owner
Beneficial Owner Certifier
Beneficial Owner Manager
12.3.2 Request mapping information is missing (Jira ID: INTCL-1323 / PDRFF-468)
Fixed Version
This issue has been fixed in the following version:
CL Integration Coresmen (3.6069)
Issue Description
While performing Book To Core action for Create Collaterals Request API, few
collateral does not have the request mapping in Integration API configuration.
Need to have request mapping information for the following Collateral Types:
Inventory,
All Assets,
Accounts,
Equipment,
Household Goods (purchase money),
General Intangibles
Resolution
The code is fixed to address the issue.
12.4 Issues fixed for October 14, 2021 patches
12.4.1 Error while performing Book To Core action (Jira ID: INTCL-1238)
Fixed Version
This issue has been fixed in the following version:
CL Integration Coresmen (3.6059)
Issue Description
While performing Book To Core action, the system is throwing the following exception for the collateral type Real Estate – Construction:
“Attempt to de-reference a null object.”
Resolution
This issue is fixed by adding the missing Unimproved Real Estate and Real Estate -
Construction collateral types to ResponseProcessor.
12.4.2 Create Collateral API is failing while performing Book To Core action (Jira ID: INTCL-1221)
Fixed Version
This issue has been fixed in the following version:
CL Integration Coresmen (3.6059)
Issue Description
While performing Book To Core action with missing mandatory fields in collateral, the call to Create Collateral API is failing.
Resolution
This issue is fixed by adding Collateral ID check to ensure proper processing
13. Change record
| S.No | Change Date | Description of Change |
|---|---|---|
| 1. | July, 2021 | Published release notes for Platinum General Availability release. |
| 2. | October 14, 2021 | Added section 12.4 |
| 3. | October 29, 2021 | Added section 12.3 |
| 4. | December 10, 2021 | Added section 12.2 |
| 5. | December 24, 2021 | Added section 12.1 |