Titanium 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 IntegrationsTitanium version (3.7000) 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 Titanium 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. System performance
To view the SOD batch jobs performance statistics for Q2 Integrations without customizations under test conditions, see the Q2 Performance Benchmarking Guide.
5. List of Abbreviations
| Abbreviated Term | Description |
|---|---|
| SOD | Start of Day |
| EOD | End of Day |
| UI | User Interface |
| FIs | Financial Institutes |
| KYC | Know Your Customer |
| KYB | Know Your Business |
6. New features and enhancements
This section briefly describes the new features and the enhancements added in the Titanium release of Q2 Integrations.
For a detailed description of the new features and enhancements, see the Q2 Integrations User Guide published over the Q2 Customer Portal:
6.1 ABBYY OCR (Issue key: INTCL-1226, INTCL-1015)
Feature Description
ABBYY FlexiCapture Cloud is a cloud solution based on ABBYY FlexiCapture Distributed that is hosted in the Microsoft Azure cloud environment. ABBYY FlexiCapture Cloud is a data capture service that uses ABBYY Content IQ technology to classify documents and extract data for further processing in document management systems.
This epic provides OCR capability for Tax Form 1040. The Tax Form 1040 is a federal income tax form that most people use to report their tax information to the Internal Revenue Service. The form contains income, any tax deductions or credits that could be claimed and the amount of taxes that would get refunded or the amount of taxes owed.
This feature allows the users to upload documents for OCR, view the status of the uploaded documents on the UI and download the results file. The user can see any errors and take appropriate action on them.
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 UI Redesign (Issue key: INTCL-1225, INTCL-1223, INTCL-1169, INTCL-1168)
Feature Description
This handles the UI redesign of the following integrations:
Coresmen
FICO Liquid Credit
SocureID+ - Parties Screen – KYC
LexisNexis InstantID - Parties Screen – KYB
6.3 Experian- Premier Profiles (Issue key: INTCL-1054, INTCL-1165, INTCL-1123)
Feature Description
Experian Premier Profile provides a full picture of each new business customer, highlighting their strengths and vulnerabilities and in-depth details of its financial activities. It provides the views of business payment performance, public record history, and company backgrounds, the Premier Profile lets the user precisely determine a business's creditworthiness.
This feature allows the user to check creditworthiness of a business by allowing the user to make a request, receive response, store the responses in the database, and see the information sent back from Experian Premier Profile on the UI.
The user has the option to view the pdf report for the credit details. This feature also allows the user to check on any errors which occurs and take appropriate actions on them.
6.4 Experian Business Search (Issue key: INTCL-1160, INTCL-1039)
Feature Description
The Business Search API allows the user to leverage Experian's powerful search match technology to find information on a business. The Search API presents a list of business that the user is searching for, ranked by match reliability code. Each business returned in the list includes the legal name, address, and phone number of the business Experian has on file, and optionally business geocode data.
This feature allows the user to do business search for a business by allowing the user to make a request, receive response, see the information on the UI, select a business with maximum confidence, and store the responses in the database.
The system also allows for calling this integration straight through without any user intervention. This feature also allows the user to check on any errors which occurs and take appropriate actions on them.
6.5 Experian - Commercial Scores (Issue key: INTCL-999)
Feature Description
The Commercial Scores API allows user to request Experian's Intelliscore Plus, premier business credit score model, and Financial Stability Risk score to be delivered directly into your application. Each score is returned with the top four score factors and with score trends to help assess whether the score was stable, improved, fluctuated, or declined over the previous 12 months.
This feature allow the user to get scores of a business by allowing the user to make a request, receive response, store the responses in the database, and see the information sent back from Experian Commercial Scores on the UI. This feature also allows the user to check on any errors which occurs and take appropriate actions on them.
6.6 LexisNexis Business InstantID (Issue key: INTCL-991)
Feature Description
InstantID Business is a suite of small business verification products that is used for doing KYB for the business. This also allows to verify (KYC) up to 5 authorized representatives (directors and owners).
This feature allows the user to do the KYC for the authorized representatives associated to a business by allowing the user to make a request ,receive response ,store the responses in the database and see the information sent back from LexisNexis on the UI.
This feature also allows the user to check on any errors which occurs and take appropriate actions on them.
The KYB for LexisNexis has already been implemented this epic is created for the implementation of KYC for authorized representatives along with the KYB through LexisNexis.
6.7 SocureID+ (Issue key: INTCL-962)
Feature Description
SocureID+ provides Identity (IDV) and Document Verification (DV) services through various modules using machine learning algorithms to perform KYC for individuals.
The modules KYC and Sigma Fraud were already implemented as a part of Titanium release. This feature deals with the implementation of Email risk, Address risk, Phone risk, Global watchlist and AlertList modules from SocureID + .
This feature allows 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 also allows the user to check on any errors which occurs and take appropriate actions on them.
6.8 CSI (Issue key: INTCL-948)
Feature Description
CSI adapter moved from integration adapter package into its own standalone package under the namespace q2adapters.
From this release the field migrations functionality available through migration scripts.
6.8.1 CSI-HELOC (Issue key: INTCL-495)
Feature Description
HELOCs are loans that are secured by a borrower's home. With a HELOC, you are borrowing against the available equity in your home and the house is used as collateral for the line of credit.
Equity is the difference between what is owed on the mortgage loan and the home's current market value.
HELOCs typically have lower interest rates than home equity loans and personal loans.
The following list of Use cases are certified:
Use Case 250: 15 Year Home Equity LOC, Variable-Rate with Interest Only
Use Case 251: 10 Year Home Equity LOC, Percentage of outstanding principal plus accrued interest
Use Case 252: Denial of Home Equity LOC
Use Case 253: 5YR HELOC Dollar Amount Plus Accrued Interest
Use Case 254: 20 Year (10yr draw/ 10yr repay) Home Equity LOC, 1st lien Purchase
Use Case 255: 15 Year HELOC Trust Ownership
Use Case 256: 10 Year loan with 60 months draw accrued interest only followed by 60 month amortized payments.
6.9 Coresmen (Issue key: INTCL-484)
Feature Description
Coresmen is a Q2 product that integrates with various bank core systems and normalizes their messages into a standard CUFX message that can be consumed by other products within Q2. Q2 Lending is building a productized integration to support real-time core booking (write to core).
About the Integration:
The Coresmen integration can be initiated in two ways:
-
User-initiated (on-demand)
For manually initiated vehicle valuations, a user clicks a button or icon to initiate the Coresmen API request.
-
Automated (Orchestrator flow)
Coresmen integration is initiated using a Process Builder flow or a trigger when a loan reaches a pre-configured stage.
6.10 Framework Enhancements (Issue key: INTCL-1164, INTCL-1112, INTCL-206, INTCL-781)
Feature Description
6.10.1 Cascaded Filters Support
The Request Mapping in Integration API Configuration only supported accumulating data from queries targeting from child to parent but not the other way around.
Because of this limitation, separate database calls were required through adapters for populating these objects, causing compile-time dependency from adapter package to clcommon or genesis packages.
With this new feature it is possible to accumulate all data available in Salesforce database and map them through request mapping without any limitations.
While filtering objects and fields data to be sent to third party via adapter request mapping, now the functionality to send parent-child relationships is available and that is up to any level of relationship.
6.10.2 Request Body Templatization
This gives more control on the request mapping configuration to determine and construct the payload request structure as desired providing proper hierarchy. This will remove the need to write lengthy adapter code to construct the request. Addition/Removal/Modification of any fields in the payload can be directly done from the request mapping file, no need to modify the adapter every time.
This is an optional feature and you may choose to not utilize and instead construct the request in the adapter using existing infrastructure.
6.10.3 Nested Array Feature
Nested Array Feature is introduced within JSON payload generated.
A new check box named ignoreInRequest has been added at Field, Dynamic Parameter as well as at Static Parameter level. If selected, the framework will not include it in the generated request payload.
The JsonAggregator class is enhanced further with introduction of new constructor and some minor changes.
6.10.4 Data Transfer APIs
Data transfer APIs are required to transfer data from Salesforce to external systems.
These can be used to fetch data from Application and its related objects like Party, Account, Contact, Business Info, Addresses, etc., in a predefined JSON format.
The response content for applications and borrower’s info APIs depends on the mappings set in the Custom_template__c field of the Data API Configuration object.
Introduced 3 APIs –
GetIds: /intframework/q2-dataApi/ids
GetApplications Info: /intframework/q2-dataApi/applications
GetBorrowers Info: /intframework/q2-dataApi/borrowers
7. Fixed issues
This section describes the issues fixed in the Titanium release of Q2 Integrations.
7.1 Error while performing Book To Core action (Jira ID: INTCL-1238)
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.
7.2 Create Collateral API is failing while performing Book To Core action (Jira ID: INTCL-1221)
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.
7.3 CSI: Adverse Action Reason Code mappings issue (Jira ID: INTCL-1262 / PDRFF-476)
Issue Description
In an application, all adverse action reasons in CL (Q2) are sent to CSI as reason code 99, which equates to the reason Other. The CL reason description is then written to the Other description. The adverse action reasons must be mapped with the appropriate reason codes.
Resolution
This issue is fixed by adding mappings for reason codes and by querying the description field in the request mapping.
7.4 CSI: Error in associating Resolving Party Certifier Signers to borrowers (Jira ID: INTCL-1263 / PDRFF-454)
Issue Description
If there are two Resolving Party Certifier Signers exist in an application, only one of the Resolving Party Certifier Signer is getting associated to the borrower.
Resolution
This issue is fixed in the translator tool by modifying the base xpath to accommodate multiple authorized signers for the resolving party.
7.5 CSI: Error while previewing the document of rejected application (Jira ID: INTCL-1320 / PDRFF-529)
Issue Description
When a rejected application is previewed in the CSI runtime, an error message related to amortization is displayed.
Resolution
This issue is fixed by adding a mapping in the CSI translator tool that sets the Amortization check box to get cleared when an application status changes to Rejected.
7.6 CSI: Error while previewing the document of rejected application (Jira ID: INTCL-1320 / PDRFF-529)
Issue Description
Error while adding party types to an application (Jira ID: INTCL-1240 / PDRFF-471).
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
7.7 Request mapping information is missing (Jira ID: INTCL-1323 / PDRFF-468)
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.
8. Known issues
This section describes the known issues in the Titanium release of Q2 Integrations.
8.1 Unable to add more than two parties while performing Book To Core action (Jira ID: INTCL-1239)
Issue Description
While performing Book To Core action with the more than two parties, the creation of Customer is successful but while creating an Account, the system is throwing the following errors:
{
"responseId": "c474f34523f64505a4f6c619d8b262e8",
"messages": [
{
"source": "Coresmen",
"message": "core error details : {'error_code': -1, 'message': '[
{\"error_code\": 40103, \"error_type\": 2, \"error_message\": \"Please Verify the APR\"},
{\"error_code\": 40186, \"error_type\": 2, \"error_message\": \"Loan Limit Amount equals 0\"},
{\"error_code\": 40219, \"error_type\": 2, \"error_message\": \"Original Amount exceeds Officer 's Lending Limit\"},
{\"error_code\": 55008, \"error_type\": 1, \"error_message\": \"Print Option used on multiple Secondaries\"},
{\"error_code\": 55008, \"error_type\": 1, \"error_message\": \"Print Option used on multiple Secondaries\"}]'}"
}
],
"data": null
}8.2 Error while performing Book To Core action if the different parties are added (INTCL-1235)
Issue Description
While performing Book To Core action, if the added parties are other than Borrower, Guarantor, and Cosigner Party types then the system is throwing the following errors:
{
"responseId": "57c6aa11a90f465b992cc7e8b7e52356",
"messages": [
{
"source": "Coresmen",
"message": "core error details : {'error_code': -1, 'message': '[
{\"error_code\": 40103, \"error_type\": 2, \"error_message\": \"Please Verify the APR\"},
{\"error_code\": 40186, \"error_type\": 2, \"error_message\": \"Loan Limit Amount equals 0\"},
{\"error_code\": 55008, \"error_type\": 1, \"error_message\": \"Print Option used on multiple Secondaries\"},
{\"error_code\": 55008, \"error_type\": 1, \"error_message\": \"Print Option used on multiple Secondaries\"},
{\"error_code\": 55008, \"error_type\": 1, \"error_message\": \"Print Option used on multiple Secondaries\"},
{\"error_code\": 55008, \"error_type\": 1, \"error_message\": \"Print Option used on multiple Secondaries\"},
{\"error_code\": 55008, \"error_type\": 1, \"error_message\": \"Print Option used on multiple Secondaries\"}]'}"
}
],
"data": null
}8.3 Unresponsive page error while performing Book To Core action (INTCL-1236)
Issue Description
While performing Book To Core action with the multiple parties and collaterals, the page is unresponsive with two buttons namely Wait and Close.
8.4 Error while performing Create Customer API (INTCL-1389)
Issue Description
While performing Create Customer API, the system is throwing the following error:
"Exception Message: Unexpected character ('u' (code 117)): expected a valid value (number, String, array, object, 'true', 'false' or 'null') at input location [1,2] .”9. New and modified objects
This section briefly describes the new and modified objects in the Titanium 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 Titanium release of Q2 Integrations.
| Object Name | Description |
|---|---|
| Credit_Check_c | This object holds fields to store credit checks of businesses and directors using the Equifax Commercial Link - Web Services. |
| Corporate_Information__c | This object holds fields for storing corporate information from various third-party vendors. |
| Score__c | This object holds fields to store score details sent by KYC or KYB providers. |
| Company_Persons_of_Interest__c | This object defines the company persons who might be of interest for a commercial credit check. |
| Tradeline__c | This object stores the summary information for all the tradelines for the customer. |
| Tradeline_Details__c | This object stores detailed information for the tradelines for the customer. |
| Credit_Public_Record__c | This object holds fields to store certain data fields for Public Records data from various vendors in a normalized manner so that use can use them for decisioning and compliance. |
| OCR_Tasks__c | This object keeps track of all the ABBYY OCR tasks and acts as a parent object to the corresponding OCR source and target files. |
| OCR_Task_Source_Files__c | This object stores the details of the files that were uploaded to ABBYY to perform an OCR. |
| OCR_Task_Target_Files__c | This object stores the details of the target files available post OCR processing by ABBYY on the uploaded files. |
| Tax_Form_1040__c | This object represents Tax Form 1040 details. |
| Tax_Form_1040_Dependents__c | This object represents Tax Form 1040 Dependents details. |
| Config_Detail_Connector__c | This object is used to connect the configs (forming an edge in the config graph). |
| Coresmen_Configuration__c | This object is defined to configure the standard message context info as well the security headers required to be sent along with each coresmen request. |
| Orchestrator_Config_Detail__c | This object stores the config for each stage involved in the flow. |
| Orchestrator_Runner_Detail__c | This object is different from "orchestrator config detail" which stores the values applicable to an org while "orchestrator runner detail" will store the values applicable to an application. Since per application, we can run a flow (for example, Update loan) multiple times, so we need to track status of each flow associated to an application. Records under it would be created while initiating the flow. Code will see the Orchestrator Config detail and create the runner detail records accordingly by considering the number of customers, collaterals, relationships involved. |
| Orchestrator_Runner__c | This object is different from "orchestrator" which stores the values applicable to an org while "orchestrator runner" will store the value applicable to an application. Since per application, we can run a flow (For e.g. Update loan) multiple times, so we need to track status of each flow associated to an application. Records under it would be created while initiating the flow. |
| Orchestrator__c | This object stores the name and config related values which is applicable to full flow. |
| Runner_Detail_Connector__c | This object is used to connect the Runner Detail records (forming an edge in the runner connect graph). |
| Coresmen_Event__c | This object is used by orchestrator to decide which adapter to execute next. |
| Ancillary_Data__c | This object is used to represent the core or FI-specific information. This will be a blank object with no fields, the implementor must add the fields according to the FI requirement with default values and those will get automatically populated in the "Book to core" screen |
| Config_Detail_Connector__c | This object is used to connect the configs (forming an edge in the config graph). |
| Orchestrator_Event__c | This object is used by orchestrator to decide which adapter to execute next. |
| Data_API_Configuration__c | This Salesforce object stores all the configs which is needed to call a REST / GLOBAL API from external systems. |
9.2 Modified objects
The following table describes the objects modified in the Titanium release of Q2 Integrations.
| Object Name | Field Name | Description |
|---|---|---|
| Corporate Information(intdm__Corporate_Information__c) | Product__c | This field indicates the name of the product. |
| Vendor__c | This field represents the name of the bureau or vendor. | |
| Credit_Check__c | This is the look-up field to Credit Check. | |
| genesis__Applications__c | Core_Creation_Date__c | This field identifies the application created time in core. |
| Core_Error__c | This field represents an error message from the core system. | |
| Overall_Booking_Status__c | This field represents the overall application created in core (Created account, contact and collateral). | |
| Does_Application_Exist_In_Core__c | This field represents if the application exists in core. | |
| Overall_Core_Booking_Status__c | This field represents the overall application created in core (Created account, contact and collateral). | |
| Core_Creation_Status__c | This field represents the status of application being created in the core. It can be Success, failure, or waiting. | |
| Account_c | Core_Creation_Date__c | This field represents the account created time in core |
| Core_Error__c | This field represents an error message from core system | |
| Core_Creation_Status__c | This field represents account created in core system or not. | |
| Core_Error_Message__c | This field represents an error message from the core system. | |
| Taxpayer_ID_Number__c | This field represents the Unique Taxpayer Number. | |
| Application_Collateral__c | Core_Creation_Date__c | This field identifies the Collateral created time in core. |
| Core_Error__c | This field represents an error message from core system. | |
| Core_Error_Message__c | This field represents an error message from the core system. | |
| Core_Creation_Status__c | This field represents collateral created in core system or not. | |
| Is_collateral_linked_to_Loan_in_core__c | This field identifies if the collateral linked to the loan application exists in core. | |
| Contact_c | Core_Creation_Date__c | This field identifies the Contact created time in core. |
| Core_Error__c | This field represents an error message from core system. | |
| Core_Creation_Status__c | This field represents contact created in core system or not. | |
| Core_Error_Message__c | This field represents an error message from the core system. | |
| genesis__Business_Information__c | CIF__c | This field represent the unique Id from the core system. |
| Does_Account_exist_in_core__c | This field is updated by "Get Customer" API and is used by rule engine to decide which next adapter to be run. | |
| clcommon__Personal_Information__c | CIF__c | This field represent the unique Id from the core system. |
| Does_Account_exist_in_core__c | This field is updated by "Get Customer" API and is used by rule engine to decide which next adapter to be run. | |
| clcommon__CL_Product__c | Core_Product_SubType__c | The product sub type identifies the specific product type that the back-core end system must recognize. |
| Core_Product_Type__c | This field represents the product type that the back-end core system must recognize. | |
| clcommon__Party__c | Does_Relationship_Exist_in_Core__c | This field is to determine whether the relationship in the core with the business is exists or not. |
10. New and modified REST APIs
This section briefly describes the new and modified APIs in the Titanium 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 Titanium 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. |
| OrchestratorService | The API service handles Orchestrator Service requests. |
| CoresmenIntegrationWebService | The API service handles integration service requests. |
10.2 Modified APIs
There are no APIs modified in the Titanium release of Q2 Integrations.
11. New and modified global methods
This section briefly describes the global methods that are added in the Titanium release of Q2 Integrations.
For details on all the Q2 Integrations global methods, see Q2 Integrations Global Methods Guide.
| Class Name | Method Name | Description |
|---|---|---|
| ABBYYAdapterHelper | getTaskTransactionId(String documentDefinitionName, List<String> contentVersionIds) | This method returns a base 64 encoded String of document definition name and content version IDs. |
| getActiveTaskId(String transactionId) | This method returns the Salesforce ID of the active OCR Task, if there is already an active task, else it returns null. | |
| getAbbyyTaskIdOfActiveOCRTask(String transactionId) | This method returns the Abbyy task ID of the active OCR task, if there is already an active task, else it returns null. | |
| getTaskIdToDelete(String transactionId) | This method returns the Salesforce ID of the first OCR task that has overall progress as "done" and has not yet been deleted, else it returns null. | |
| Framework Package | ||
| OrchestratorService | runOrchestratorInvocable(List<OrchestratorRequestMapping> requestParameters) | This method is invoked from a process builder to run the Orchestrator Service. |
| BaseAdapterRunner | run(String familyName, String apiType, Integer executionPriority,String objectApiName,String sourceId,List<Id> recordIds) | This method is used to call the appropriate adapter and update the status. |
| getOptionalRequestParams() | This method is used to populate OptionalRequestParams. | |
| getOptionalRequestParams(String objectApiName, String sourceId, List<Id> recordIds) | This method is used to populate OptionalRequestParams with addtional parameters. | |
| getIdsForFilters(String objectApiName, String sourceId, List<Id> recordIds) | This method is used to populate idsforfilters. | |
| updateExecutionPriority(Integer originalExecutionPriority) | This method is used to update the executionPriority. | |
| getRecordIdForRule(String objectApiName, String sourceId, List<Id> recordIds) | This method is used to get the record Id on which rule will run. | |
| getRunnerStatus(String runnerStatusValue) | This is an optional method which is used to set the status adapter runner. | |
| BaseRunnerGraph | createRunnerDetailAndConnectorsDynamically(Orchestrator_Runner__c runner,Orchestrator_Runner_Detail__c runnerDetail, List<Id> recordIds) | This method is used to update the Orchestrator_Runner_Detail__c nodes and the associated Runner_Detail_Connector__c dynamically, at the time of execution of the runner graph. |
| ExceltoJSONParser | parsetoJSON(Blob blobString,String rootNode,Boolean asArray) | This static method accepts blob data , root Node name for the json and as Array Boolean check box to convert .xlsx format to json |
| Coresmen Package | ||
| CoresmenAdapterHelper | setSecurityHeaders(intframework.BaseIntegrationRequest request, Map<String, Object> filledInRequestMap) | This method adds security headers to the request provided in the request parameters before sending the request. |
| addAllObjectFieldValues(System.JSONGenerator jsonGen, Map<String, Object> inputMap) | This method generically adds all the fields present in the Map to JSON. | |
| addMessageContextJSON(System.JSONGenerator jsonGen) | This method generically appends the message context within all the coresmen request required to be sent. | |
| signRequestString(String requestString, Map<String, Object> filledInRequestMap) | This method returns the JWT encoded string generated for the request string. | |
| encode (Blob input) | This method returns base64 encoded string for the input blob. | |
| getFieldValueFromResponseMap(Map<String, Object> responseMap, String fieldPath) | This method is responsible to return the value of the field defined in the fieldPath by traversing to the hierarchy defined by dot seperated notation in the fieldPath. | |
| checkResponseForErrors(intframework.BaseIntegrationResponse response) | This is a coresmen specific Error Response parser written to appropiately handle and define the Coresmen error structure. | |
| addCustomFields(Map<String,Object> requestMap, Map<String,Object> customMap) | This method is responsible to populate the custom Map with the custom mappings defined in the request mappings (defined with prefix "custom_"). | |
| addCustomDataToJSON(String jsonString, Map<String,Object> customMap) | This method appends all the custom fields collected within the customMap (usually defined with prefix "custom_" to the final request string generated from the adapter. | |
| OrchestratorService | runOrchestratorInvocable(List<OrchestratorRequestMapping> requestParameters) | This method is invoked from a process builder to run the Orchestrator Service. |
| BaseAdapterRunner | run(String familyName, String apiType, Integer executionPriority,String objectApiName,String sourceId,List<Id> recordIds) | This method is used to call the appropriate adapter and update the status. |
| getOptionalRequestParams() | This method is used to populate OptionalRequestParams. | |
| getOptionalRequestParams(String objectApiName, String sourceId, List<Id> recordIds) | This method is used to populate OptionalRequestParams with addtional parameters. | |
| getIdsForFilters(String objectApiName, String sourceId, List<Id> recordIds) | This method is used to populate idsforfilters. | |
| OrchestratorService | runOrchestratorInvocable(List<OrchestratorRequestMapping> requestParameters) | This method can be invoked from a process builder to run the Orchestrator Service. |
| CoresmenIntegrationWebService | runSynchronousIntegrationInvocable (List<intframework.RequestParametersMapping> requestParameters) | This method can be invoked from a process builder to run an integration service. |
12. Post GA release
Follow this section for the details on the issues fixed in the patches on the Titanium release of Q2 Integration.
13. Change record
| S.No | Change Date | Description of Change |
|---|---|---|
| 1. | December, 2021 | Published release notes for Titanium General Availability release. |