1.3 Creatio Financial Services CRM changelog

Release date: 03/12/2025

This document details the technical changes and enhancements introduced in Creatio Financial Services CRM 1.3. It is intended for developers, system administrators, and DevOps engineers responsible for maintaining and extending Creatio customizations.

Important

Creatio Financial Services CRM 1.3 is compatible only with Creatio platform 8.3.3.

The update guide for the on-site applications is available in a separate article.

Finserv Customer Management

Category	Feature	Status	Description
Contact management	Contact page	Changed	Changed the contact page to use the standardized "Document" (Document code) timeline object on the Timeline tab. This change provides a unified overview of customer-related information on the contact page and ensures consistent document representation. More details Added the "Document (TimelineEntity)" (DocumentTimelineEntity code) addon to remove deprecated columns and standardize document-related information on the Timeline tab of the contact page. Out of the box, the addon includes "Status" (State code), "Type" (Type code), and "Class" (RegDocumentType code) columns.

Finserv Product Catalog Management

Category	Feature	Status	Description
Contact management	Contact page	Changed	Changed the contact page to use the standardized "Document" (Document code) timeline object on the Timeline tab. This change provides a unified overview of customer-related information on the contact page and ensures consistent document representation. More details Added the "Document (TimelineEntity)" (DocumentTimelineEntity code) addon to remove deprecated and irrelevant columns and standardize document-related information on the Timeline tab of the contact page. Out of the box, the addon includes "Status" (State code), "Type" (Type code), "Class" (RegDocumentType code), and "Group" (DocListGroup code) columns.

Finserv Account Management

Category	Feature	Status	Description
Contact management	Contact page	Changed	Changed the contact page to use the standardized "Loan" (Loan code), "Bank account" (BankAccount code), and "Card" (BankCard code) timeline objects on the Timeline tab. This change provides a unified overview of customer-related information on the contact page. More details Added: "Loan (TimelineEntity)" (LoanTimelineEntity code) addon that includes "Status" (LoanStatus code), "Type" (ProductType code), and "Product" (Product code) columns. "Financial account (TimelineEntity)" (BankAccountTimelineEntity code) addon that includes "Status" (Status code), "Type" (ProductType code), "Product" (Product code), "Opened on" (OpenedOn code), and "Closed on" (ClosedOn code) columns. "Card (TimelineEntity)" (BankCardTimelineEntity code) addon that includes "Status" (BankCardStatus code), "Category" (BankCardCategory code), "Type" (BankCardType code), "Product" (Product code), "Start date" (StartDate code), and "End date" (EndDate code) columns.

Finserv Application Management

Category	Feature	Status	Description
Contact management	Contact page	Changed	Changed the contact page to use the standardized "Application" (FinApplication code) timeline object on the Timeline tab. This change provides a unified overview of customer-related information on the contact page and ensures consistent application representation. More details Added the "Application (TimelineEntity)" (FinApplicationTimelineEntity code) addon to remove deprecated columns and standardize application-related information on the Timeline tab of the contact page. Out of the box, the addon includes "Status" (Status code), "Stage" (Stage code), "Product type" (ProductType code), and "Product" (Product code) columns.
Lead management	Lead page	Changed	Added automated lifecycle management for the Referral status field in the lead profile of the lead page through dedicated business processes. The field value is now updated automatically based on lead, application, and financial product-related events. This change ensures consistent and rule-based evaluation of referral outcomes, improves transparency of reward eligibility, and reduces manual errors in referral processing. More details Added the following business processes: "Set referral status to pending" that sets Referral status to "Pending" when a lead whose Lead type field is set to "Referrals" is created without a populated Referral status. "Set referral status to unsuccessful" that sets Referral status to "Unsuccessful" when a lead whose Lead type field is set to "Referrals" moves to the "Closed lost" stage, when a converted B2C referral lead has no matching products with the linked reward program, or when all related applications are declined and no active applications remain. "Set referral status to successful" that sets Referral status to "Successful" when an active or open related bank account or loan is created or updated and is linked through an application to a B2C referral lead whose Referral status field is set to "Pending." The process validates reward program validity period and product matching before updating the status.
Applications and credit processing	Application management	Changed	Changed application creation processes to explicitly display the Complete application pre-configured page when creating applications from the lead page and the Consultation center sidebar. Previously, pre-configured elements of the Complete application page were not clearly visible during application creation from related processes. The page now opens with a dynamic title in the format "Complete application: {ApplicationNumber}," providing clear context to the user. This change improves transparency of the application creation step, ensures consistent behavior across application creation flows, and provides clear visibility of pre-configured page elements. More details Changed the "Create application for product type" and "Create application for selected product" business processes to explicitly open the Complete application pre-configured page for the user with a contextual title that includes the application number.
Applications and credit processing	Application management	Fixed	Fixed validation logic in the "Create application for selected product" business process to prevent the submission of applications without all required documents. Creatio now blocks the Complete button if required documents are missing and keeps the application submission page open until all required documents are uploaded. Previously, users could complete and close the application submission page even if required documents were not provided. This change ensures completeness of application data, reduces follow-up corrections, and improves compliance with document requirements.

Finserv Sales Management

Category	Feature	Status	Description
Contact management	Contact page	Changed	Added the Programs & rewards tab to the contact page. The new tab provides a consolidated view of referral performance and incentive activity filtered by the current contact. Previously, this information was distributed across different sections and required manual navigation. This change improves visibility into referral activity, simplifies monitoring of incentive outcomes, and supports better decision-making in sales operations. More details The Programs & rewards tab includes: Completed incentive payments amount, Incentive payments amount in progress, Total referred leads, Successful referred leads, Pending referred leads, and Unsuccessful referred leads metrics Read-only Reward program participation expanded list filtered by the current contact Read-only Referred leads expanded list filtered by the current contact as referrer Read-only Incentive payments expanded list filtered by the current contact as reward program participant Status colorization for the "Status" column in the expanded lists is aligned with the defined dynamic case status colors.
Contact management	Contact page	Changed	Changed the lead creation flow from the contact page to standardize lead handling across sales and marketing contexts and improve automation logic. Previously, lead creation from contact page relied on MQL/SQL naming and legacy automated processes, and lead-related expanded lists were not unified across tabs. Lead management is now unified under the Leads expanded lists on the Sales and Marketing tabs of the contact page, supporting both manual and score-based automated lead creation. This change clarifies the lead-related UI and streamlines manual and automated lead creation from the contact page. More details Added: CrtFinservSalesMgmtInMarketing package to manage marketing-related lead logic. "Manual lead creation from contact" business process that is launched from the Create lead button on the Leads expanded list on the Marketing tab of the contact page. "Automated lead creation from contact" business process that creates a lead automatically when the lead conversion score is greater than or equal to 80. Logic to automatically populate the Sales motion field in the lead profile of the lead page. If the Legal entity field in the Lead & identification profile of the contact page is populated, the Sales motion field is set to "B2B." Otherwise, the Sales motion field is set to "B2C." "Lead is not created" (LeadIsNotCreated_Validation_Dialog code) mini page. Renamed the MQL/SQL expanded list to Leads on the Marketing tab of the contact page, including updates in the CrtFinservSalesMgmt package. Deactivated the "Contact to Lead: automated MQL Lead creation" business process.
Lead management	Lead page	Changed	Added the Sales motion field to the Leads mini page and the lead page and made it required through business rules to ensure its completion during lead creation and editing. This change ensures consistent lead classification, supports accurate execution of sales processes, and improves data quality for analytics and automation. More details Added: "Make elements required: Sales motion" page-level business rule to the "Leads mini page" (Leads_MiniPage code) schema. The rule makes the Sales motion field required on the mini page. "Make elements required: Sales motion" page-level business rule to the "Leads form page" (Leads_FormPage code) schema. The rule makes the Sales motion field required in the lead profile of the lead page.
Lead management	Leads section	Changed	Changed the lead management flow to use a new dynamic case lifecycle that contains updated stages, validation logic, and conversion behavior. Previously, lead progression relied on the legacy dynamic case model and lead management process that had limited stage control and validation logic. This change improves consistency of lead processing, reduces incomplete lead data at key stages, and aligns lead progression with financial sales scenarios. More details Added: "Finserv lead management" (FinservLeadManagementCase code) schema of the "Case" type. Supported stages: "Initial contact," "Qualification," "Converted," and "Closed lost." Each stage triggers a dedicated business process. "Lead initiation processing," "Lead qualification processing," "Lead conversion processing," and "Lead closed lost processing" business processes Product validation during the "Qualification" stage "Products missing in lead notification mini page" (ProductsMissingInLeadNotification_MiniPage code) mini page that guides users in adding required products within the "Lead qualification processing" process. Lead type filter to the Similar leads expanded list on the Overview tab of the lead page. "Make elements required: Sales motion" page-level business rule to the "Leads mini page" (Leads_MiniPage code) schema. The rule makes the Sales motion field required on the mini page. "Show elements: Opportunities by customer, Opportunity planning" page-level business rule to the "Leads form page" (Leads_FormPage code) schema. The rule displays the Opportunity planning expanded list on the Sales tab and the Opportunities by customer expanded list on the History tab of the lead page. "Make Product required" object-level business rule to the "Product in lead" (LeadProduct code) schema. The rule makes the Product field required in the Products expanded list on the Sales tab of the lead page. "Make Lead required" object-level business rule to the "Product in lead" (LeadProduct code) schema. The rule makes the Lead field required in the Products expanded list on the Sales tab of the lead page. Changed: Default value of the "Default Lead Stage" (DefaultLeadStage code) system setting from "Marketing qualified lead" to "Initial contact." Conversion logic when the Sales motion field in the lead profile of the lead page is set to "B2C." Creatio now enforces product presence and creates applications based on the number of products from the Products expanded list on the Sales tab of the lead page. Conversion logic when the Sales motion field in the lead profile of the lead page is set to "B2B." Creatio now creates an opportunity and links it to the lead. Deactivated the "Lead processing" business process.
Lead management	Leads section	Changed	Added incentive payment tracking for referral leads to support reward program execution. Previously, incentive payments for referral leads were not managed through a dedicated data model and UI, which limited visibility into incentive execution and payment state tracking. This change improves auditability of referral incentives, supports consistent reward execution, and reduces manual tracking effort for sales operations. More details Added: "Incentive payment" (IncentivePayment code) object that manages incentives for referral leads Incentive payment status lookup that defines payment states. The lookup includes "Approved," "Failed," "Processing," "Completed," "Pending," and "Canceled" statuses. "Referrer" (Referrer code) column to the "Lead" (Lead code) object to support referral attribution. Referrer field to the lead profile of the lead page. Creatio displays the field for leads whose Lead type field is set to "Referrals." Required Referrer field on the Leads mini page. Creatio displays the field for leads whose Lead type field is set to "Referrals." Incentive payments expanded list to the Overview tab of the lead page. Creatio displays the list for leads whose Lead type field is set to "Referrals." Incentives tab to the reward program page. The tab includes Completed incentive payments amount, Incentive payments amount in progress, Canceled incentive payments amount metrics and the Incentive payments expanded list. "Generate incentive payment for referral lead" business process that automatically creates an incentive payment according to reward program setup when the Referral status field in the lead profile of the lead page changes to "Successful."
Lead management	Lead page	Changed	Changed the lead assignment logic to automate lead distribution and owner assignment during the "Initial contact" stage. Previously, leads created without an owner required manual assignment, and initiation logic did not support group-based ownership transfer. This change ensures timely lead distribution, reduces manual intervention, and improves accountability in early-stage lead processing. More details Added the "Lead distribution processing" business process that is triggered when a lead is created in the "Initial contact" stage and the Owner field on the Overview tab of the lead page is empty. The process launches the "Lead distribution" sub-process to perform automatic distribution. If the Assignees group field is specified on the Overview tab of the lead page, the initial processing task is assigned to the group, and the first user who completes the task is set in the Owner field automatically.
Lead management	Lead page	Changed	Changed stage transition behavior on the lead page to make "Closed lost" a terminal stage and enforce mandatory loss information when closing leads as lost. Previously, users could move a lead out of the "Closed lost" stage and complete the closing process without entering required loss details. The update restricts dynamic case transitions from the "Closed lost" stage to prevent further movement once the lead reaches this status. This change improves data integrity, ensures accurate reporting of lost leads, and prevents inconsistent stage transitions. More details Added the "Lead closed lost processing" business process that validates whether the Loss reason field is completed and the Status field is set to "Lost" on the lead profile of the lead page. If the required information is missing, Creatio displays a notification and requires the Loss reason field to be populated before the lead can be closed as lost.
Lead management	Reward programs	Added	Added reward program management to enable configuration and tracking of referral-based and incentive programs. Previously, reward and referral programs were not centrally managed and relied on manual configuration and tracking. This change provides a structured and controlled way to run reward and referral programs, reduces manual configuration errors, and improves transparency of reward eligibility and outcomes. More details Added: "Reward programs" workplace that includes the Reward programs and Leads sections Reward programs section. The reward program page includes the following tabs: General information Participants. The Participants expanded list on the tab is linked to the "Reward program participant" (RewardProgramParticipant code) object and Leads expanded list on the tab is linked to the "Lead" (Lead code) object. Both lists are read-only and display calculated metrics for the current reward program. Incentives. The Incentive payments expanded list on the tab is linked to the "Incentive payment" (IncentivePayment code) object. The list is read-only and displays calculated metrics for current reward program. "Reward program" (RewardProgram code) and "Reward program participant" (RewardProgramParticipant code) objects Reward program type, Reward program statuses, Reward types, Reward recipients, and Reward program eligibility statuses lookups "Reward program" (RewardProgram code) and "Referral status" (RewardProgramEligibilityStatus code) columns of the "Lookup" type to the "Lead" (Lead code) object "Reward program case" schema of the "Case" type. The case manages the reward program lifecycle from "Draft" to "Active" and "Closed." "Update reward program dates on status change" business process that populates the Start date and End date fields on the reward program profile on the reward program page based on status changes "Make elements required: Reward type, Reward recipient, Reward amount" page-level business rule to the "Reward programs form page" (RewardPrograms_FormPage code) schema. The rule makes the Reward recipient, Reward amount, and Reward type fields required in the Rewards conditions expanded list on the General information tab of the reward program page. "Show elements and make required: Currency" page-level business rule to the "Reward programs form page" (RewardPrograms_FormPage code) schema. The rule makes the Currency field required for reward programs whose Reward type field in the Rewards conditions expanded list on the General information tab of the reward program page is set to "Cash."
Lead management	Reward programs	Added	Changed the lead page to display reward program participation for referral leads and enforce referral-specific rules. Previously, lead pages did not expose reward program information or referral eligibility status, and users had to verify referral participation and eligibility manually. This change improves transparency of referral processing, reduces configuration errors, and simplifies tracking of reward program participation for sales teams. More details Added: Reward program field to the Leads mini page and to the lead profile on the lead page. Referral status field to the lead profile of the lead page. The field has the Read-only checkbox selected and the "Indicates whether the referral meets all required conditions to qualify for the reward program." tooltip. "Apply static filter: Reward program" page-level business rule to the "Leads mini page" (Leads_MiniPage code) schema. The rule makes the Reward program field required for leads whose Lead type field in the lead profile of the lead page is set to "Referrals." "Make elements required: Referrer, Reward program" page-level business rule to the "Leads form page" (Leads_FormPage code) schema. The rule makes the Reward program and Referrer fields required for leads whose Lead type field in the lead profile of the lead page is set to "Referrals."
Lead management	Reward programs	Added	Added product-to-program linking to configure eligible products for reward programs. Previously, reward programs could not be restricted to specific products, and incentives were applied without explicit product eligibility configuration. This change improves control over reward applicability, reduces configuration errors, and ensures that incentives are applied only to relevant products. More details Added: "Reward program eligible product" (RewardProgramEligibleProduct code) junction object that links reward programs to products. Eligible products expanded list to the General information tab of the reward program page. The list is linked to the "Reward program eligible product" (RewardProgramEligibleProduct code) object. "Add eligible product mini page" (AddEligibleProduct_MiniPage code) mini page that enables users to select eligible products from the Eligible products expanded list. The mini page supports multi-selection and filtering by product categories and prevents duplicate product associations. Only products whose Inactive checkbox is cleared on the product profile of the product page are available for selection.
Lead management	Reward programs	Added	Added automation to create reward program participants automatically during lead creation. This change ensures data integrity, eliminates duplicate participants, and reduces manual effort when managing reward and referral programs. More details Added the "Create reward program participant from lead" business process that checks reward program participation during lead creation and creates a record in the Participants expanded list on the Participants tab of the reward program page only if the lead is not already linked to the selected reward program.
Applications and credit processing	Applications section	Fixed	Fixed the status update sequence in the "Process application form and update contact data" and "Submit application form" business processes to ensure that the "Status" column in the Applications section is set to "Submission" only after successful synchronization. Previously, the application status was updated before data synchronization was completed, which could result in an inconsistent state even if data migration failed or was not finalized. This change improves data consistency, ensures that the "Submission" status reflects a fully completed data migration, and reduces the risk of incomplete application processing.