1.0 Bank.AI changelog

Release date: 04/23/2025

This document details the technical changes and enhancements introduced in Bank.AI 1.0. It is intended for developers, system administrators, and DevOps engineers responsible for maintaining and extending Creatio customizations. Changes are described relative to the Creatio Financial Services product, which the Bank.AI apps extend.

Important

Bank.AI 1.0 is compatible with Creatio platform 8.2.3 and later.

For a comprehensive overview of the new features, refer to the 1.0 Bank.AI release notes.

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

Finserv Customer Management

Feature	Status	Description
Contact page	Changed	Changed the contact page to bring the customer's profile, analytics, compliance, and financial data together in one place. Previously, the contact page had no overview, compliance, or financial summary tabs, and contact details were not grouped. This change reduces the time users spend switching between records when they assess a customer. More details Added: "Average transactions per month" (`AverageTransactionsPerMonth` code), "Churn risk, %" (`ChurnRisk` code), "Credit trend, %" (`CreditTrend` code), "Credit utilization, %" (`CreditUtilizationRatio` code), "Customer lifetime value (CLV)" (`CustomerLifetimeValue` code), "Customer profitability, %" (`CustomerProfitability` code), "Debt-to-Income (DTI), %" (`DebtToIncomeRatio` code), "Deposit trend, %" (`DepositTrend` code), "Engagement score, %" (`EngagementScore` code), "Net worth estimate" (`NetWorthEstimate` code), "Next payment amount" (`NextPaymentAmount` code), "Next payment date" (`NextPaymentDate` code), "Number of active accounts" (`NumberOfActiveFinAccounts` code), "Number of active products" (`NumberOfActiveProducts` code), "Preferred communication option" (`PreferredCommunicationOption` code, lookup to the `CommunicationType` object), "Risk score" (`RiskScore` code), "Spending trend, %" (`SpendingTrend` code), "Total accounts balance" (`TotalAccountsBalance` code), "Total available credit" (`TotalAvailableCredit` code), "Total available debit" (`TotalAvailableDebit` code), "Total loan amount" (`TotalLoanAmount` code), "Total outstanding loan balance" (`TotalOutstandingLoanBalance` code), and "Verification status" (`ContactVerificationStatus` code) columns to the "Contact" (`Contact` code) object in the `CrtFinservCstmr360ObjMdl` package. Contact info, Communication options, and Legal & identification profiles to the contact page. Preferred communication option and Verification status fields to the Contact info profile on the contact page. Overview tab to the contact page. The tab includes the AI insights and alerts and Analytics expansion panels. The Analytics panel includes the Customer profitability, %, Engagement score, %, Churn risk, %, Spending trend, %, Next payment date, Credit trend, %, Number of active products, Total outstanding loan balance, Next payment amount, Deposit trend, %, and Number of active accounts widgets. Compliance & risk monitoring tab to the contact page. The tab includes the Risk score, Debt-to-Income, %, Credit utilization, %, Churn risk, %, and Total outstanding loan balance widgets, as well as the Evaluation history expanded list. Financial summary tab to the contact page. The tab includes the Customer lifetime value, Net worth estimate, Debt-to-Income, %, Credit utilization, %, and Avg. monthly transactions widgets, as well as the Income, Expenses, Assets, and Liabilities expanded lists. Personal & business details and Consents expansion panels to the Contact info tab of the contact page. The Personal & business details panel includes the First name, Last name, Education, Social status, and Marital status fields next to the existing fields. The Consents panel includes the Consent to the verification of personal data, Consent to the processing of personal data, Do not use email, Do not use mail, Do not use phone, and Do not use SMS checkboxes. Documents expanded list to the Contact info tab of the contact page. The list displays the contact's documents and includes the Active documents quick filter. Total accounts balance, Total available credit, Total available debit, Total loan amount, and # of active accounts widgets to the Portfolio tab of the contact page. "Hide elements: PortfolioTab" page-level business rule to the "Contacts form page (Business rules)" (`Contacts_FormPageBusinessRule` code) addon in the `CrtFinservCstmr360` package. The Finserv Account Management app disables this rule in the `CrtFinservAccMgmt` package when the app is installed. Moved: SSN and Legal entity fields from the contact profile to the Legal & identification profile on the contact page. Citizenship field from the Contact info tab to the Legal & identification profile on the contact page. List of communication options from the contact profile to the Communication options profile on the contact page. Type, Segment, Branch, and Owner fields from the contact profile to the Contact info profile on the contact page. Title, Preferred language, Birthplace, Birth date, Gender, and Age fields from the Contact info tab to the Personal & business details expansion panel on the Contact info tab. Full job title field from the contact profile to the Personal & business details expansion panel on the Contact info tab. Removed the Recipient's name field from the Contact info tab of the contact page.
Contact page	Changed	Added the AI insights and alerts timeline to the Overview tab of the contact page. The timeline displays the five most recent AI-generated insights and alerts about the contact. Creatio stores these insights and alerts as records of a dedicated object. This change keeps AI findings visible to users and separate from emails, calls, and other timeline items. More details Added: "AI insights and alerts" (`AIInsightsAndAlerts` code) object with the "Contact" (`Contact` code), "Description" (`Description` code, rich text), and "Name" (`Name` code) columns. The object has a dedicated timeline icon. "VwAIInsightsAndAlerts" (`VwAIInsightsAndAlerts` code) database view object. The view returns the five most recently created records of the "AI insights and alerts" object for each contact. The view is created by the `VwAIInsightsAndAlerts_Top5RecordsMsSql` and `VwAIInsightsAndAlerts_Top5RecordsPostgreSql` SQL scripts. "AI insights and alerts (TimelineEntity)" (`AIInsightsAndAlertsTimelineEntity` code) and "VwAIInsightsAndAlerts (TimelineEntity)" (`VwAIInsightsAndAlertsTimelineEntity` code) addons that configure the timeline tiles.
Contact page	Changed	Added a Freedom UI mini page for contact addresses. Creatio filters the city and state/province on the mini page by the selected country and keeps the full address read-only. This change enables users to create and edit contact addresses in Freedom UI, including in the consultation flow that adds a customer's address. More details Added: "Customer address mini page" (`CustomerAddress_MiniPage` code) schema of the "Client module" type. The mini page includes the Country, Address type, City, State/province, Street, Building, Apartment/office, and ZIP/postal code fields and the Primary checkbox. "Contact address (Page settings)" (`ContactAddressRelatedPage` code) addon. The addon code keeps the former name of the mini page. "Make elements required: Address columns" page-level business rule to the "Update customer address mini page (Business rules)" (`UpdateCustomerAddress_MiniPageBusinessRule` code) addon. The rule makes the Country, Address type, City, Street, Building, and ZIP/postal code fields required. Appearance settings of the customer address mini page to the "Update customer address mini page (AppearanceSettings)" (`UpdateCustomerAddress_MiniPageAppearanceSettings` code) addon. The addon code keeps the former name of the mini page. "Contact address (Business rules)" (`ContactAddressBusinessRule` code) addon to the `CrtFinservCstmr360` package. The addon includes the "Make elements read-only: Full address" object-level business rule for saved addresses and the "Apply filter: City" object-level business rule. The "Apply filter: City" rule filters the city and state/province by country and the city by state/province. "Mailing" value to the Address types lookup.
Contact incomes, Contact expenses, Contact liabilities, Contact assets	Added	Added objects that store a customer's income, expenses, assets, and liabilities. Creatio stores each item with its type and amount, and, for income, expenses, and liabilities, its frequency. The items are displayed on the Financial summary tab of the contact page. This change gives users data they need to assess the customer's affordability and net worth. More details Added: "Contact income" (`ContactIncome` code) object. The object includes the "Amount" (`Amount` code), "Contact" (`Contact` code), "Frequency" (`Frequency` code), "Is taxable" (`TaxableStatus` code), "Name" (`Name` code), and "Type" (`IncomeType` code) columns. "Contact expense" (`ContactExpense` code) object. The object includes the "Amount" (`Amount` code), "Contact" (`Contact` code), "Frequency" (`Frequency` code), "Name" (`Name` code), and "Type" (`ExpenseType` code) columns. "Contact asset" (`ContactAsset` code) object. The object includes the "Contact" (`Contact` code), "Is taxable" (`TaxableStatus` code), "Name" (`Name` code), "Type" (`AssetType` code), and "Value" (`Value` code) columns. "Contact liability" (`ContactLiability` code) object. The object includes the "Amount" (`Amount` code), "Contact" (`Contact` code), "Frequency" (`Frequency` code), "Name" (`Name` code), and "Type" (`LiabilityType` code) columns. Income types lookup. The lookup includes the "Alimony/child support," "Business income," "Capital gains," "Government benefits," "Investment income," "Other income," "Pension/annuity," "Rental income," and "Salary & wages" values. Expense types lookup. The lookup includes the "Dining out," "Education," "Entertainment," "Groceries," "Healthcare," "Housing," "Insurance," "Loan payments," "Personal care," "Shopping," "Transportation," "Travel," and "Utilities" values. Asset types lookup. The lookup includes the "Cash & bank accounts," "Investments," "Real estate," "Retirement accounts," "Valuables," and "Vehicles" values. Liability types lookup. The lookup includes the "Auto loans," "Buy now, pay later," "Credit card debt," "Family/friends loan," "Medical debt," "Mortgage loans," "Payday loans," "Personal loans," and "Student loans" values. Frequency lookup. The lookup includes the "Annual," "Continuous," "Monthly," "One-time," "Quarterly," "Variable," and "Weekly" values. Taxable statuses lookup. The lookup includes the "No" and "Yes" values. Income types, Expense types, Asset types, Liability types, Frequency, and Taxable statuses lookups to the Contacts folder in the Lookups section.
Evaluation management	Added	Added evaluation management for customer compliance checks, for example, KYC onboarding. Creatio stores evaluation sessions together with their checks and verified documents. The checks are generated from an evaluation template, and earlier evaluations are marked as inactive when a user adds a new evaluation. This change gives users an auditable view of the checks performed for each customer on the contact and document pages. More details Added: "Evaluation history" (`EvaluationHistory` code) object to the `CrtFinservCstmr360ObjMdl` package. The object includes the "Active" (`IsActive` code), "Comment" (`Comment` code), "Contact" (`Contact` code), "Due date" (`DueDate` code), "Evaluation" (`Evaluation` code), "Evaluation date" (`EvaluationDate` code), "Evaluator" (`Evaluator` code), "Name" (`Name` code), "Risk score" (`RiskScore` code), and "Status" (`EvaluationStatus` code) columns. The Enable live data update checkbox in the Behavior property block of Object Designer for the object is selected. "Evaluation check history" (`EvaluationCheckHistory` code) object. The object includes the "Check" (`EvaluationCheck` code), "Comment" (`Comment` code), "Risk score" (`RiskScore` code), and "Status" (`EvaluationStatus` code) columns for each evaluation. "Evaluation document history" (`EvaluationDocumentHistory` code) object. The object includes the "Comment" (`Comment` code), "Document" (`Document` code), and "Status" (`EvaluationStatus` code) columns for each evaluation. "Evaluation template" (`EvaluationTemplate` code) object. The object links all checks from the Evaluation checks lookup to the KYC onboarding process. Evaluations lookup. The lookup includes the "KYC onboarding process" value. Evaluation checks lookup. The lookup includes the "Address verification," "Adverse media," "Communication channels verification," "Identity document verification," "PEP (Politically Exposed Person)," "Person verification," "Sanction lists," and "Suspicious activity" values. Evaluation statuses lookup. The lookup includes the "Approved," "Flagged," "Not started," "Processing," and "Rejected" values. The "Color" column for these values is set as follows: #198754 for "Approved." #FFAA00 for "Flagged." #6C757D for "Not started." #007BFF for "Processing." #DC3545 for "Rejected." Contact verification statuses lookup. The lookup includes the "Expired," "Rejected," "Verification required," and "Verified" values. Evaluations folder to the Lookups section. The folder includes the Evaluation checks, Evaluations, Evaluation statuses, and Evaluation templates lookups. "Evaluation history mini page" (`EvaluationHistory_MiniPage` code) schema of the "Client module" type to the `CrtFinservCstmr360` package. The schema includes the General information and Documents tabs. The General information tab lists the checks. The Documents tab lists the verified documents with their properties and files. "Create evaluation history mini page" (`CreateEvaluationHistory_MiniPage` code) and "Add evaluation document mini page" (`AddEvaluationDocument_MiniPage` code) schemas of the "Client module" type. "Generate evaluation for contact" business process that creates the evaluation and its checks from the template. "Create manual evaluation for contact" and "Create manual evaluation for document" business processes. "Deactivate old evaluation history" business process that clears the "Active" (`IsActive` code) column of previous evaluations when a user adds a new evaluation. "Make elements read-only: Check, Evaluation" object-level business rule to the "Evaluation check history (Business rules)" (`EvaluationCheckHistoryBusinessRule` code) addon. "Make elements read-only: Document" object-level business rule to the "Evaluation document history (Business rules)" (`EvaluationDocumentHistoryBusinessRule` code) addon. "Apply static filter: Evaluator" object-level business rule to the "Evaluation history (Business rules)" (`EvaluationHistoryBusinessRule` code) addon in the `CrtFinservCstmr360` package. "Show elements: Active label" and "Show elements: Inactive label" page-level business rules to the "Evaluation history mini page (Business rules)" (`EvaluationHistory_MiniPageBusinessRule` code) addon.
Document classification	Changed	Added document properties based on the document class. When a user saves a document, Creatio generates the properties defined for the selected class and keeps the filled values if the class changes. Users can edit the property values on the document page. This change standardizes data captured from identity documents and makes data reusable in evaluations and applications. More details Added: Document properties lookup. The lookup includes the "Country," "Date of birth," "Document number," "Expired on," "First name," "Gender," "Issued by," "Issued on," "Last name," "Nationality," "Place of birth," and "SSN" values. Document properties in class lookup. The lookup includes values that define the property sets for the "Passport," "ID card," "Residence permit," and "Driver's license" document classes. "Property value in document" (`DocumentPropertyValue` code) object. The object includes the "Date value" (`DateValue` code), "Document" (`Document` code), "Property" (`Property` code), and "Value" (`DisplayValue` code) columns. The object supports "Text" and "Date" type values. The Enable live data update checkbox in the Behavior property block of Object Designer for the object is selected. "Generate document properties" business process with the "Generate document property (sub-process)" sub-process. "Document property: convert date value into text value" business process. "Document (view)" (`VwDocumentViewModel` code) database view object to the `CrtFinservCstmr360ObjMdl` package. The view is created by install scripts for MSSQL and PostgreSQL. "Document (view) mini page" (`VwDocument_MiniPage` code) schema of the "Client module" type. The mini page displays the properties and attachments of a document in read-only mode.
Document classification	Changed	Changed the document page to display the document class, properties, and evaluations. The page refreshes document data in real time. This change keeps the classification, extracted data, and verification history of a document together on one page. More details Added: "Class" (`RegDocumentType` code) column to the "Document" (`Document` code) object in the `CrtFinservCstmr360ObjMdl` package. Class field to the document profile on the document page. Properties expanded list to the General information tab of the document page. The list displays the document properties. Evaluations tab to the document page. The tab includes the Evaluation history expanded list that displays the evaluation document history records. "Unuploaded" value to the Document statuses lookup. Changed the Enable live data update checkbox in the Behavior property block of Object Designer for the "Document" (`Document` code) and "Document attachment" (`DocumentFile` code) objects in the `CrtFinservCstmr360ObjMdl` package from cleared to selected.
Document classification	Changed	Changed the Document types lookup by deactivating outdated types and adding a new type. This change keeps historical records intact and offers only current document types for new documents. More details Added the "Contracts & Agreements" value to the Document types lookup. Changed: Allow records deactivation checkbox in the Behavior property block of Object Designer for the "Document type" (`DocumentType` code) object in the `CrtFinservCstmr360ObjMdl` package from cleared to selected. "Correspondence," "Decree," and "Protocol" values in the Document types lookup. The "Inactive" column is set to "Yes."
Document classification	Changed	Changed the Document classes lookup by deactivating outdated document classes and adding classes for deposit products and compliance. This change aligns document classification with retail banking onboarding. More details Added the "Account opening agreement," "Consent to electronic disclosures," "Deposit agreement," "Electronic funds transfer agreement," "General Terms & Conditions," "ID card," "Passport," "Privacy policy," "Proof of funds," and "Signature card" values to the Document classes lookup. Changed: Allow records deactivation checkbox in the Behavior property block of Object Designer for the "Document class" (`RegDocumentType` code) object in the `CrtFinservCstmr360ObjMdl` package from cleared to selected. "Application form," "Contract," "Diplomatic passport," "Income information," "International passport," and "National passport" values in the Document classes lookup. The "Inactive" column is set to "Yes." Title property value in the General property block of Object Designer for the `RegDocumentType` object in the `CrtFinservCstmr360ObjMdl` package from "Identity document" to "Document class." Renamed the Registration document types lookup to Document classes.

Finserv Product Catalog Management

Feature	Status	Description
Product catalog	Changed	Added product subtypes for more detailed product classification. The product page displays only the subtypes of the selected product type. This change enables users to classify loan and credit products more precisely. More details Added: "Product subtype" (`ProductSubtype` code) object. The object includes the "Product type" (`ProductType` code) column. "Adjustable-rate mortgage," "Auto loan," "Buy-to-let mortgage," "Credit card," "Debt consolidation loan," "Equity release / reverse mortgage," "FHA / VA / USDA loans," "Fixed-rate mortgage," "Home equity line of credit (HELOC)," "Lease buyout loan," "Motorcycle loan," "Overdraft protection loan," "Personal line of credit (LOC)," "RV / Boat / Recreational vehicle loan," "Secured personal loan," "Unsecured personal loan," and "Wedding / Vacation / Special purpose loan" values to the Product subtypes lookup. Out of the box, the lookup is not registered. To manage the values in the Lookups section, register a lookup based on the "Product subtype" (`ProductSubtype` code) object. "Subtype" (`ProductSubtype` code) column to the "Product" (`Product` code) object in the `CrtFinservPrdctMgmtObjMdl` package. Subtype field to the product profile on the product page. "Apply filter: Subtype" object-level business rule to the "Product (Business rules)" (`ProductBusinessRule` code) addon in the `CrtFinservPrdctMgmtObjMdl` package. The rule filters product subtypes by the selected product type.
Product catalog	Changed	Changed the Product categories lookup by deactivating outdated product categories and adding account-based product categories. This change gives deposits, loans, investments, and treasury services a clear structure. More details Added the "Business deposit accounts," "Digital & payment accounts," "Investment & wealth accounts," "Loan & credit accounts," "Retail deposit accounts," "Specialized & trust accounts," and "Treasury & liquidity management accounts" values to the Product categories lookup. Changed: Allow records deactivation checkbox in the Behavior property block of Object Designer for the "Product category" (`ProductCategory` code) object in the `CrtFinservPrdctMgmtObjMdl` package from cleared to selected. "Credit payment tools," "Finance accounts and investments," "Insurance product," "Loan services," "Payment tools," and "Product bundle" values in the Product categories lookup. The "Inactive" column is set to "Yes."
Product catalog	Changed	Changed the Product types lookup by deactivating outdated product types and adding product types for deposit, payment, investment, and credit products. This change enables banks to classify products using industry-standard types. More details Added the "401(k) accounts," "Auto & Vehicle loan," "Brokerage accounts," "Business checking accounts," "Business savings accounts," "Cash concentration accounts," "Certificates of deposit (CDs)," "Checking accounts (DDA)," "Corporate CDs," "Credit & Revolving credit," "Custodial accounts," "Digital wallets," "Education savings accounts (529 plans)," "Escrow accounts," "Health savings accounts (HSAs)," "IRAs," "Merchant payment processing accounts," "Money market accounts (MMA)," "Mortgage loan," "Personal loan," "Prepaid card accounts," "Savings accounts," and "Sweep accounts" values to the Product types lookup. Changed: Allow records deactivation checkbox in the Behavior property block of Object Designer for the "Product type" (`ProductType` code) object in the `CrtFinservPrdctMgmtObjMdl` package from cleared to selected. "Auto insurance," "Auto loans," "Business loans and Leasing," "Checking accounts," "Credit cards," "Debit cards," "Home and Property insurance," "Individual retirement accounts," "Merchant Services," "Mortgages and Real Estate loans," "Payroll card programs," "Personal and Consumer loans," "Personal insurance," "Savings accounts," and "Universal product bundle" values in the Product types lookup. The "Inactive" column is set to "Yes."
Product catalog	Changed	Added parameters for deposit products. When users add product features to a condition of a deposit product, the product page suggests the parameters of the product type. Creatio does not add these parameters to conditions automatically. This change provides the parameters that the application flow uses to open a deposit account. More details Added: "Deposit method," "Issue debit card," "Monthly withdrawal limit," and "Source of funds" values to the Parameters lookup. Out of the box, the lookup is not registered. To manage the values in the Lookups section, register a lookup based on the "Parameter" (`Specification` code) object. "APY," "Currency," "Deposit amount," "Deposit method," "Source of funds," and "Term, months" values to the Default feature lookup. The "Type" column for these values is set to "Certificates of deposit (CDs)." "Currency" and "Issue debit card" values to the Default feature lookup. The "Type" column for these values is set to "Checking accounts (DDA)." "APY," "Deposit amount," "Monthly fee," and "Monthly withdrawal limit" values to the Default feature lookup in addition to the existing values. The "Type" column for these values is set to "Savings accounts." Out of the box, the Default feature lookup is not registered. To manage the values in the Lookups section, register a lookup based on the "Default feature" (`DefSpecification` code) object. Values to the Parameter values lookup, for example, deposit methods ("Cash," "Check (personal)," "Check (bank/cashier's)," "ACH transfer," "Wire transfer," "Internal transfer (from existing account)," "Transfer from another bank," and "Direct deposit (payroll)") and sources of funds ("Salary / wages," "Personal savings," "Inheritance," "Gift," and "Business income"). Out of the box, the lookup is not registered. To manage the values in the Lookups section, register a lookup based on the "Parameter value" (`SpecificationListItem` code) object.
Document classification	Changed	Changed the Document groups lookup by linking each document group to a document type and adding groups for agreements and authorizations. This change organizes documents into a group, type, and class hierarchy. More details Added: "Document type" (`DocumentType` code) column to the "Document group" (`DocListGroup` code) object in the `CrtFinservPrdctMgmtObjMdl` package. "Authorization document," "Financial account agreement," and "Terms & Conditions / Policy acceptance" values to the Document groups lookup. The "Document type" column for these values is set to "Contracts & Agreements." Changed: Allow records deactivation checkbox in the Behavior property block of Object Designer for the "Document group" (`DocListGroup` code) object in the `CrtFinservPrdctMgmtObjMdl` package from cleared to selected. "Settlement" and "Submission" values in the Document groups lookup. The "Inactive" column is set to "Yes." "Identification" and "Income verification" values in the Document groups lookup. The "Document type" column is set to "Customer document." Title property value in the General property block of Object Designer for the `DocListGroup` object in the `CrtFinservPrdctMgmtObjMdl` package from "Registration document group" to "Document group." Renamed the Registration document groups lookup to Document groups.
Document classification	Changed	Changed the Document classes lookup by linking each document class to a document group. This change enables Creatio to filter document classes by group on documents and in required document packages. More details Added the "Document group" (`DocListGroup` code) column to the "Document class" (`RegDocumentType` code) object in the `CrtFinservPrdctMgmtObjMdl` package. Changed: "Driver's license," "ID card," "Passport," "Residence permit," and "Social security number" values in the Document classes lookup. The "Document group" column is set to "Identification." "Proof of funds" value in the Document classes lookup. The "Document group" column is set to "Income verification." "Consent to electronic disclosures," "General Terms & Conditions," and "Privacy policy" values in the Document classes lookup. The "Document group" column is set to "Terms & Conditions / Policy acceptance." "Account opening agreement," "Deposit agreement," and "Electronic funds transfer agreement" values in the Document classes lookup. The "Document group" column is set to "Financial account agreement." "Signature card" value in the Document classes lookup. The "Document group" column is set to "Authorization document."
Document classification	Changed	Changed the document page to require hierarchical classification of documents. The page filters document groups by type and document classes by group and type. This change ensures that every document is fully classified. More details Added: "Group" (`DocListGroup` code) column to the "Document" (`Document` code) object in the `CrtFinservPrdctMgmtObjMdl` package. Group field to the document profile on the document page. "Group: Add filter by Type," "Class: Add filter by Group," and "Class: Add filter by Type" object-level business rules to the "Document (Business rules)" (`DocumentBusinessRule` code) addon in the `CrtFinservPrdctMgmt` package. The rules filter the document groups by type and the document classes by group and type. "Make elements required: Class, Group" page-level business rule to the "Documents form page (Business rules)" (`Documents_FormPageBusinessRule` code) addon in the `CrtFinservPrdctMgmt` package. The rule makes the Class and Group fields in the document profile on the document page required.
Document in package page	Changed	Added a Freedom UI page for documents in the required document package of a product. The page filters document groups by the selected type and document classes by the selected type and group. This change keeps required document packages consistent with the document classification. More details Added: "Document in package form page" (`DocListInCondition_FormPage` code) schema of the "Client module" type. The page includes the Document parameters profile, Conditions block, and the Help toggle panel that explains how Creatio generates required documents. "Document in package (Page settings)" (`DocListInConditionRelatedPage` code) addon in the `CrtFinservAppMgmt` package. The addon registers the page for the "Document in package" (`DocListInCondition` code) object. "Document in package (Business rules)" (`DocListInConditionBusinessRule` code) addon. The addon includes the "Apply filter: Document group by document type," "Apply filter: Document class by document type," "Apply filter: Document class by document group," and "Apply static filter: Template" object-level business rules.

Finserv Account Management

Feature	Status	Description
Contact page	Changed	Changed the contact page to display the banking products and activity of the customer. Previously, the Portfolio tab listed only the applications, accounts, and cards of the customer. The contact page also includes lists of loans, insurances, investments, transactions, and contracts. This change gives users a complete view of the customer portfolio without leaving the contact page. More details Added: Recent transactions expanded list to the Overview tab of the contact page. Contracts & agreements expanded list to the Contact info tab of the contact page. Transactions expanded list to the Financial summary tab of the contact page. Investments, Loans, and Insurances expanded lists to the Portfolio tab of the contact page. Changed: Columns of the Financial accounts expanded list on the Portfolio tab of the contact page. The "Type" column displays the "Account type" (`ProductType` code) column of the financial account. The list includes the new "Balance," "Currency," and "Opened on" columns. The "Product" column is now displayed last in the list. Columns of the Cards expanded list on the Portfolio tab of the contact page. The list includes the new "Status" and "Currency" columns and no longer includes the "Payment system" and "Debt" columns. "Hide elements: PortfolioTab" page-level business rule of the "Contacts form page (Business rules)" (`Contacts_FormPageBusinessRule` code) addon in the `CrtFinservAccMgmt` package. The rule is disabled, so the contact page displays the Portfolio tab. Renamed the Accounts expanded list on the Portfolio tab of the contact page to Financial accounts.
Loan management	Added	Added the Loans section for credit products issued to customers. The section stores each loan with its contract, product, terms, and installment information, and a case manages the loan lifecycle. Users can also connect activities to loans. This change keeps loan servicing data in one place next to the other products of the customer. More details Added: "Loan" (`Loan` code) object to the `CrtFinservAccMgmtObjMdl` package. The object includes the "Branch" (`Branch` code), "Contact" (`Contact` code), "Contract" (`Contract` code), "Currency" (`Currency` code), "Installment frequency" (`InstallmentFrequency` code), "Installment type" (`InstallmentType` code), "Interest rate, %" (`InterestRate` code), "Loan amount" (`LoanAmount` code), "Maturity date" (`MaturityDate` code), "Name" (`Name` code), "Next installment amount" (`NextInstallmentAmount` code), "Next installment date" (`NextInstallmentDate` code), "Opening date" (`OpeningDate` code), "Outstanding amount" (`OutstandingAmount` code), "Overdue amount" (`OverdueAmount` code), "Product" (`Product` code), "Purpose" (`Purpose` code), "Status" (`LoanStatus` code), "Subtype" (`ProductSubtype` code), and "Type" (`ProductType` code) columns. The default value of the "Status" (`LoanStatus` code) column is "Active." The Enable live data update checkbox in the Behavior property block of Object Designer for the object is selected. Loan statuses lookup. The lookup includes the "Active" and "Closed" values. Out of the box, the lookup is not registered. To manage the values in the Lookups section, register a lookup based on the "Loan status" (`LoanStatus` code) object. Installment types lookup. The lookup includes the "Amortized installments," "Balloon installments," "Graduated installments," "Interest-only installments," and "Step-up / Step-down installments" values. Out of the box, the lookup is not registered. To manage the values in the Lookups section, register a lookup based on the "Installment type" (`InstallmentType` code) object. Installment frequencies lookup. The lookup includes the "Annual," "Monthly," and "Quarterly" values. Out of the box, the lookup is not registered. To manage the values in the Lookups section, register a lookup based on the "Installment frequency" (`InstallmentFrequency` code) object. "Loans list page" (`Loans_ListPage` code) and "Loans detail" (`Loans_Detail` code) schemas of the "Client module" type. "Loans form page" (`Loans_FormPage` code) schema of the "Client module" type to the `CrtFinservAccMgmt` package. "Loan management" (`LoanManagementCase` code) schema of the "Case" type. The schema includes the "Active" and "Closed" stages. "Loan (Business rules)" (`LoanBusinessRule` code) addon to the `CrtFinservAccMgmtObjMdl` package. The addon includes the "Apply filter: Product, Apply filter: Product," "Apply filter: Subtype," "Apply static filter: Product," and "Apply static filter: Type" object-level business rules. "Show elements: ContactProfileContainer" page-level business rule to the "Loans form page (Business rules)" (`Loans_FormPageBusinessRule` code) addon. The rule displays the contact profile on the loan page when a user selects a contact. "Loan" (`Loan` code) column to the "Activity" (`Activity` code) object in the `CrtFinservAccMgmt` package.
Insurances section	Added	Added the Insurances section for insurance policies linked to a customer. The section stores the policy period, carrier, product, premium, and commission of each policy, and a case manages the policy lifecycle. Users can also connect activities to insurance policies. This change enables users to see insurance policies next to the banking products of the customer. More details Added: "Insurance" (`Insurance` code) object to the `CrtFinservAccMgmtObjMdl` package. The object includes the "Carrier" (`Carrier` code), "Commission amount" (`CommissionAmount` code), "Commission rate, %" (`CommissionRate` code), "Contact" (`Contact` code), "Contract" (`Contract` code), "End date" (`EndDate` code), "Name" (`Name` code), "Premium amount" (`PremiumAmount` code), "Premium frequency" (`PremiumFrequency` code), "Product" (`Product` code), "Start date" (`StartDate` code), and "Status" (`InsuranceStatus` code) columns. The default value of the "Status" (`InsuranceStatus` code) column is "New." The Enable live data update checkbox in the Behavior property block of Object Designer for the object is selected. Insurance statuses lookup. The lookup includes the "Active," "Canceled," "Expired," and "New" values. Out of the box, the lookup is not registered. To manage the values in the Lookups section, register a lookup based on the "Insurance status" (`InsuranceStatus` code) object. Premium frequencies lookup. The lookup includes the "Annual," "Monthly," and "Single / One-time" values. Out of the box, the lookup is not registered. To manage the values in the Lookups section, register a lookup based on the "Premium frequency" (`PremiumFrequency` code) object. Insurance types lookup. Out of the box, the lookup includes no values and is not registered. To manage the values in the Lookups section, register a lookup based on the "Insurance type" (`InsuranceType` code) object. "Insurances list page" (`Insurances_ListPage` code) and "Insurances detail" (`Insurances_Detail` code) schemas of the "Client module" type. "Insurances form page" (`Insurances_FormPage` code) schema of the "Client module" type to the `CrtFinservAccMgmt` package. "Show elements: ContactProfileContainer" and "Show elements: CarrierProfileContainer" page-level business rules to the "Insurances form page (Business rules)" (`Insurances_FormPageBusinessRule` code) addon. The rules display the contact and carrier profiles on the insurance page. "Insurance management" (`InsuranceManagementCase` code) schema of the "Case" type. The schema includes the "New," "Active," "Expired," and "Canceled" stages. "Insurance" (`Insurance` code) column to the "Activity" (`Activity` code) object in the `CrtFinservAccMgmt` package.
Bank account management	Changed	Added the "Iterate financial number" (`IterateFinancialNumber` code) schema of the "User task" type. The user task generates sequential numbers for financial accounts and cards based on the last number issued. The application flow uses the user task when it creates a financial account and a card.
Financial account management	Changed	Changed the financial account page to classify accounts by product type and display interest terms. Previously, accounts were classified by a separate Financial account type lookup that was not linked to the product catalog. The page filters products by the selected account type. This change keeps financial accounts consistent with the product catalog. More details Added: "Account type" (`ProductType` code), "Annual percentage yield (APY), %" (`APY` code), and "Interest rate, %" (`InterestRate` code) columns to the "Financial account" (`BankAccount` code) object in the `CrtFinservAccMgmtObjMdl` package. The "Account type" column refers to the Product types lookup. Type field to the financial account profile of the financial account page. The field is bound to the "Account type" (`ProductType` code) column. Current balance, Interest rate, %, and APY, % fields to the Financial account info tab of the financial account page. "Status" column to the Transactions expanded list on the Financial account info tab of the financial account page. "Apply filter: Product" object-level business rule to the "Financial account (Business rules)" (`BankAccountBusinessRule` code) addon in the `CrtFinservAccMgmtObjMdl` package. The rule filters products by the selected account type. "Savings" value to the Financial account type lookup. Changed: Required property in the General property block of Object Designer for the "Type" (`Type` code) column of the "Financial account" (`BankAccount` code) object in the `CrtFinservAccMgmtObjMdl` package from "Yes" to "No." Order of columns in the Cards expanded list on the Financial account info tab of the financial account page. The "Status" column is displayed after the card number. Columns of the list in the "Financial account list page" (`FinancialAccount_ListPage` code) schema of the "Client module" type in the `CrtFinservAccMgmt` package. The "Type" column displays the "Account type" (`ProductType` code) column instead of the "Type" (`Type` code) column. Moved the Branch field from the Financial account info tab to the financial account profile of the financial account page. Removed the Account type field bound to the "Type" (`Type` code) column from the Financial account info tab on the financial account page.
Card management	Changed	Changed the card lifecycle by adding the closed status and a case that manages card stages. This change enables Creatio to close the linked cards when a user closes the related account. More details Added: "Closed" value to the Card status lookup. "Card" (`CardCase_CrtFinservAccMgmt` code) schema of the "Case" type. The schema includes the "Issued," "Active," "Locked," "Expired," and "Closed" stages and is registered for the "Card" (`BankCard` code) object.
Transactions	Changed	Added statuses to transactions. The transaction number is the primary display value of a transaction. This change makes the processing stages of transactions visible on the financial account, card, and contact pages. More details Added: "Status" (`TransactionStatus` code) column to the "Transaction" (`Transaction` code) object in the `CrtFinservAccMgmtObjMdl` package. Transaction statuses lookup. The lookup includes the "Blocked," "Cleared," "Pending," "Reported," and "Reviewing" values. The "Color" column for these values is set as follows: #6C757D for "Blocked." #28A745 for "Cleared." #FFA500 for "Pending." #DC3545 for "Reported." #007BFF for "Reviewing." Changed the Displayed value property in the Object settings property block of Object Designer for the "Transaction" (`Transaction` code) object in the `CrtFinservAccMgmtObjMdl` package to "Number."

Finserv Application Management

Feature	Status	Description
Contact page	Changed	Changed the contact page to display compliance alerts, applications, service requests, and consultations. Previously, applications and cases of the customer were displayed on different tabs. The contact page groups applications and service requests on one tab and displays widgets for each list. The page also includes the consultations and compliance alerts of the customer. This change gives users a single view of customer interactions and risk signals. More details Added: Unusual transaction patterns and Fraud alerts expanded lists to the Compliance & risk monitoring tab of the contact page. The lists include cases with the "Transaction monitoring" and "Fraud alert" services, respectively. "Fraud alert" and "Transaction monitoring" values to the Services lookup. Out of the box, the lookup is not registered. To manage the values in the Lookups section, register a lookup based on the "Service" (`ServiceItem` code) object. Consultations expansion panel to the Applications & services tab on the contact page. The panel displays the consultation themes of the cases of the contact and includes the Average consultation duration, sec, Total # of consultations, and # of consultations with need discovered widgets. Total # of applications, # of applications in progress, and # of new applications widgets to the Product applications expansion panel on the Applications & services tab of the contact page. Average customer satisfaction, # of cases in progress, and # of new cases widgets to the Service requests expansion panel on the Applications & services tab of the contact page. Identity documents quick filter to the Documents expanded list on the Contact info tab of the contact page. Renamed: Service tab of the contact page to Applications & services. Cases expansion panel on the Applications & services tab of the contact page to Service requests. Applications expansion panel of the contact page to Product applications. The expansion panel is moved from the Portfolio tab to the Applications & services tab.
Customer identification	Added	Added customer identification to consultations. Before the consultation flows make changes, the agent must confirm or reject the identity of the customer on a dedicated page. The page displays the communication options, documents, and previous identifications of the contact. The identification result is saved in the consultation. If the customer has already been identified in the same consultation, the flows skip identification. Rejecting the identification ends the consultation. This change supports KYC requirements in the consultation. More details Added: "Customer identification" business process. The process runs for contacts of the "Customer" type. "Customer identification form page" (`CustomerIdentification_FormPage` code) schema of the "Client module" type. "Customer identification rejection mini page" (`CustomerIdentificationRejection_MiniPage` code) schema of the "Client module" type. The mini page includes the Consultation theme, Rejection reason, and Comment fields. "Identification status" (`IdentificationStatus` code) and "Rejection reason" (`IdentificationRejectionReason` code) columns to the "Consultation theme in case" (`CaseConsultationTheme` code) object in the `CrtFinservAppMgmtObjMdl` package. Identification statuses lookup. The lookup includes the "Failed" and "Success" values. The "Color" column for these values is set as follows: #FFD9D0 for "Failed." #CCF4DC for "Success." Identification rejection reasons lookup. The lookup includes the "Document missing/incomplete," "Document suspicious," "Name mismatch," and "Photo mismatch" values.
Application management	Changed	Added Freedom UI pages for the Applications section. The section includes a list page, a mini page for manual creation, and two form pages. The submission page guides users through the application stages, and the full page displays the complete application. Applications in the "Submission" status open on the submission page, and applications in other statuses open on the full page. This change guides users through application processing step by step and gives them a complete view of applications after submission. More details Added: "Applications list page" (`FinApplications_ListPage` code) and "Applications detail" (`FinApplications_Detail` code) schemas of the "Client module" type. "Application mini page" (`FinApplication_MiniPage` code) schema of the "Client module" type. The mini page includes the Contact, Product category, Product type, Product, Source, Branch, Owner, and Stage fields. "Application submission page" (`FinApplication_SubmissionPage` code) schema of the "Client module" type to the `CrtFinservAppMgmt` package. The page includes the following tabs: Customer details. Includes the Identity documents expanded list and the Personal data, Communication options, Residence address, Previous residence address, Registration address, Previous registration address, Mailing address, Primary place of employment, and Employment address expansion panels. Product details. Includes the Product, Application parameters, and Required documents expansion panels. Agreement & signature. Includes the Documents for signing expansion panel. The page header displays the signing and evaluation statuses. The page actions move the application to the next or previous stage, as well as modify, complete, or decline the application. The E-signature action displays a message that an e-signature provider is required. The Wet signature action is inactive. "Application full page" (`FinApplication_FullPage` code) schema of the "Client module" type to the `CrtFinservAppMgmt` package. The page includes the Closing details, General information, and Personal information profiles, as well as the following tabs: Product. Includes the Product description expansion panel. Contact info. Includes the Personal information expansion panel and the Addresses, Job experience, Identity documents, and Financial accounts expanded lists. Documents. Includes the Application forms, Required documents, and Contracts & Agreements expanded lists. Timeline. "Application (Page settings)" (`FinApplicationRelatedPage` code) addon. The addon opens the application page based on the application status. Applications in the "Submission" status open on the submission page. Applications in other statuses open on the full page. Page-level business rules for the application pages: "Initial required fields" rule to the "Application mini page (Business rules)" (`FinApplication_MiniPageBusinessRule` code) addon. The rule makes the Contact and Product fields required. "Application submission page (Business rules)" (`FinApplication_SubmissionPageBusinessRule` code) addon. The addon includes the following rules: "Make elements required: Personal data," "Make elements required: Residence address," "Make elements required: Previous residence address," "Make elements required: Registration address," "Make elements required: Previous registration address," "Make elements required: Mailing address," "Make elements required: Employment," and "Make elements required: Product details." "Show elements: Customer details tab," "Show elements: Product details tab," and "Show elements: Agreement & Signature tab." "Show elements: Previous stage button," "Show elements: Next stage button," "Show elements: Complete button," "Show elements: Submit button," "Show elements: Modify button," and "Show elements: Decline button." "Make elements read-only: Previous stage button" and "Make elements read-only: Complete button." "Hide elements: Progress bar buttons container." "Show elements: Closing reason," "Show elements: Evaluation and signing statuses," "Show elements: Compliance check placeholder," and "Show elements: Signature container (Agreement & Signature stage)." "Show elements: Residence address question," "Show elements: Previous residence address," "Show elements: Registration address question," and "Show elements: Previous registration address." "Hide elements: Residence address," "Hide elements: Residence address same as primary," "Hide elements: Registration address," "Hide elements: Registration address same as primary," and "Hide elements: Mailing address." "Show and hide elements: Residence is primary" and "Show and hide elements: Registration is primary." "Make elements read-only, hide elements: Completed, Cancelled stages." "Show elements, make elements read-only: Closing reason," "Show elements: Decline button," and "Hide element: AppFormAddButton" rules to the "Application full page (Business rules)" (`FinApplication_FullPageBusinessRule` code) addon.
Application management	Changed	Added support for the guided application flow. Applications include new columns for closing, evaluation, and signing, as well as new stages, statuses, and sources. New applications receive numbers automatically, and a business rule sets the application stage. This change enables users to track each application from submission to closure. More details Added: "Closing reason" (`ClosingReason` code), "Closing reason details" (`ClosingReasonDetails` code), "Evaluation status" (`EvaluationStatus` code), and "Signing status" (`SigningStatus` code) columns to the "Application" (`FinApplication` code) object in the `CrtFinservAppMgmtObjMdl` package. The default value of the "Evaluation status" (`EvaluationStatus` code) column is "Not started." The default value of the "Signing status" (`SigningStatus` code) column is "Not signed." Automatic numbering for new records of the "Application" (`FinApplication` code) object in the `CrtFinservAppMgmt` package. "Agreement & Signature," "Customer details," "Declined," "Product details," and "Settled" values to the Application stages lookup. "Closure" and "Submission" values to the Application statuses lookup. "Call center," "Chat bot," "Email," "Referral," "Self-service banking," and "Social network" values to the Application origins lookup. "Color" (`Color` code) column to the "Application origin" (`ApplicationOrigin` code) object in the `CrtFinservAppMgmtObjMdl` package. "Apply filter: Owner by branch," "Apply filter: Product category, Product type, Product," "Apply static filter: Closing reason for rejected stage," "Apply static filter: Closing reason for declined stage," and "Set values: Stage" object-level business rules to the "Application (Business rules)" (`FinApplicationBusinessRule` code) addon. Changed: Required property in the General property block of Object Designer for the "Product category" (`ProductCategory` code) and "Product type" (`ProductType` code) columns of the "Application" (`FinApplication` code) object in the `CrtFinservAppMgmtObjMdl` package from "Yes" to "No." Enable live data update checkbox in the Behavior property block of Object Designer for the "Application" (`FinApplication` code) object in the `CrtFinservAppMgmtObjMdl` package from cleared to selected. Allow records deactivation checkbox in the Behavior property block of Object Designer for the "Application status" (`FinAppStatus` code) object in the `CrtFinservAppMgmtObjMdl` package from cleared to selected. "Canceled," "Closed," "In progress," "New detail," and "On verification" values in the Application statuses lookup. The "Inactive" column is set to "Yes." "Personal visit" and "Site" values in the Application origins lookup. The "Color" column for these values is set as follows: #00c753 for "Personal visit." #22ab12 for "Site." Removed the default values of the "Stage" (`Stage` code) and "Status" (`Status` code) columns of the "Application" (`FinApplication` code) object.
Application management	Changed	Added a closing flow for applications. When a user declines an application, a mini page requests the closing reason and details. The application moves to the "Declined" stage and the "Closure" status. The flow also sets the end date, cancels the related application forms with the "Application declined" reason, and updates the contract. This change makes closing scenarios traceable and reportable. More details Added: "Application closing" business process. "Application closing mini page" (`FinApplicationClosing_MiniPage` code) schema of the "Client module" type. The schema includes the Closing reason and Closing details fields. Reasons for application closing lookup. The lookup includes the "Stage" column and the "Application expired," "Declined by client," "Declined by us," "Incomplete data," "Invalid data," "No application form for applicant," and "Other reasons" values. "Reason for application closing" (`FinApplicationReasonForClosing` code) object. The Allow records deactivation checkbox in the Behavior property block of Object Designer for the object is selected.
Application management	Changed	Changed loans and insurance policies to store the source application. The loan and insurance pages display the application from which each product originates. This change enables users to trace each product back to its application. More details Added: "Application" (`FinApplication` code) column to the "Loan" (`Loan` code) and "Insurance" (`Insurance` code) objects in the `CrtFinservAppMgmtObjMdl` package. Application field to the loan profile on the loan page and insurance profile on the insurance page.
Application form management	Changed	Added a cancellation flow for application forms. When a user cancels an application form, a mini page requests the cancellation reason and details. Then, the form status changes to "Cancelled." If the user cancels the form of the applicant or the last remaining form, the application moves to the "Declined" stage. This change keeps the application consistent with its forms. More details Added: "Application form cancellation" business process. The process sets the "Cancelled" status for the application form. If the canceled form belongs to the applicant or is the last remaining form, the process moves the application to the "Declined" stage. The closing reason of the application is "No application form for applicant." "Application form cancellation mini page" (`AppFormCancellation_MiniPage` code) schema of the "Client module" type. The mini page requires the cancellation reason. Reasons for application form closing lookup. The lookup includes the "Application declined," "Form expired," "Incomplete data," "Invalid data," and "Other reasons" values. The "Application declined" value is set automatically when the application is declined and is not available on the mini page. "Reason for application form closing" (`AppFormReasonForClosing` code) object. The Allow records deactivation checkbox in the Behavior property block of Object Designer for the object is selected.
Application form management	Changed	Changed application forms to use Freedom UI and store the complete applicant data. Previously, application forms were available in Classic UI only, required multiple personal and document fields, and were identified by the participant. Application forms store the contact details, addresses, and employment of the applicant, as well as the form status and cancellation reason. When a user creates an application form for an existing contact, the form is populated with the contact data. When the form is submitted, the contact data is updated. Business rules make key applicant data required and make submitted and canceled forms read-only. This change gives users one place to collect and verify applicant data. More details Added: "Additional email" (`AdditionalEmail` code), "Additional phone number" (`AdditionalPhoneNumber` code), "Apartment/office (mailing address)" (`MailingAddressAptOffice` code), "Apartment/office (previous registration address)" (`PreviousRegistrationAddressAptOffice` code), "Apartment/office (previous residence address)" (`PreviousResidenceAddressAptOffice` code), "Apartment/office (registration address)" (`RegistrationAddressAptOffice` code), "Apartment/office (residence address)" (`ResidenceAddressAptOffice` code), "Building (employment address)" (`EmploymentAddressBuilding` code), "Building (mailing address)" (`MailingAddressBuilding` code), "Building (previous registration address)" (`PreviousRegistrationAddressBuilding` code), "Building (previous residence address)" (`PreviousResidenceAddressBuilding` code), "Building (registration address)" (`RegistrationAddressBuilding` code), "Building (residence address)" (`ResidenceAddressBuilding` code), "Cancellation reason" (`ClosingReason` code), "Cancellation reason details" (`ClosingReasonDetails` code), "City (employment address)" (`EmploymentAddressCity` code), "City (mailing address)" (`MailingAddressCity` code), "City (previous registration address)" (`PreviousRegistrationAddressCity` code), "City (previous residence address)" (`PreviousResidenceAddressCity` code), "City (registration address)" (`RegistrationAddressCity` code), "City (residence address)" (`ResidenceAddressCity` code), "Country (employment address)" (`EmploymentAddressCountry` code), "Country (mailing address)" (`MailingAddressCountry` code), "Country (previous registration address)" (`PreviousRegistrationAddressCountry` code), "Country (previous residence address)" (`PreviousResidenceAddressCountry` code), "Country (registration address)" (`RegistrationAddressCountry` code), "Country (residence address)" (`ResidenceAddressCountry` code), "Employer" (`Employer` code), "Employment start date" (`EmploymentStartDate` code), "Full job title" (`FullJobTitle` code), "Is previous registration address required" (`IsPreviousRegistrationAddressRequired` code), "Is previous residence address required" (`IsPreviousResidenceAddressRequired` code), "Mailing address same as primary address" (`IsMailingSameAsPrimary` code), "Name" (`Name` code), "Office/suite (employment address)" (`EmploymentAddressSuiteOffice` code), "Primary email" (`PrimaryEmail` code), "Primary phone number" (`PrimaryPhoneNumber` code), "Registration address is a primary address" (`IsRegistrationAddressPrimary` code), "Registration address same as primary address" (`IsRegistrationSameAsPrimary` code), "Residence address is a primary address" (`IsResidenceAddressPrimary` code), "Residence address same as primary" (`IsResidenceSameAsPrimary` code), "State/province (employment address)" (`EmploymentAddressRegion` code), "State/province (mailing address)" (`MailingAddressRegion` code), "State/province (previous registration address)" (`PreviousRegistrationAddressRegion` code), "State/province (previous residence address)" (`PreviousResidenceAddressRegion` code), "State/province (registration address)" (`RegistrationAddressRegion` code), "State/province (residence address)" (`ResidenceAddressRegion` code), "Status" (`Status` code), "Street (employment address)" (`EmploymentAddressStreet` code), "Street (mailing address)" (`MailingAddressStreet` code), "Street (previous registration address)" (`PreviousRegistrationAddressStreet` code), "Street (previous residence address)" (`PreviousResidenceAddressStreet` code), "Street (registration address)" (`RegistrationAddressStreet` code), "Street (residence address)" (`ResidenceAddressStreet` code), "ZIP/postal code (employment address)" (`EmploymentAddressZip` code), "ZIP/postal code (mailing address)" (`MailingAddressZip` code), "ZIP/postal code (previous registration address)" (`PreviousRegistrationAddressZip` code), "ZIP/postal code (previous residence address)" (`PreviousResidenceAddressZip` code), "ZIP/postal code (registration address)" (`RegistrationAddressZip` code), and "ZIP/postal code (residence address)" (`ResidenceAddressZip` code) columns to the "Application form" (`AppForm` code) object in the `CrtFinservAppMgmtObjMdl` package. The default value of the "Status" (`Status` code) column is "Draft." Application form status lookup. The lookup includes the "Cancelled," "Draft," and "Submitted" values. The "Color" column for these values is set as follows: #FF4013 for "Cancelled." #FFAC07 for "Draft." #A6DE00 for "Submitted." Application forms folder to the Lookups section. The folder includes the Application form status and Reasons for application form closing lookups. "Application forms list page" (`AppForms_ListPage` code), "Application form mini page" (`AppForm_MiniPage` code), "Application form edit page" (`AppForm_FormPage` code), and "Application forms detail" (`AppForms_Detail` code) schemas of the "Client module" type. "Populate application form name" business process. The process builds the form name from the application number and the contact name. "Populate contact data for existing contact in application form" business process. The process copies the contact data to the application form. "Submit application form" business process. The process checks the identity documents and submits an application form that has no application. "Process application form and update contact data" business process. The process updates the communication options, addresses, and job experience of the contact. "Apply filter: Employment address," "Apply filter: Mailing address," "Apply filter: Residence address," "Apply filter: Registration address," "Apply filter: Previous residence address," "Apply filter: Previous registration address," "Set values: Residence address is primary," and "Set values: Registration address is primary" object-level business rules to the "Application form (Business rules)" (`AppFormBusinessRule` code) addon. The rules filter the country, state/province, and city of each address and manage the primary address. "Application form edit page (Business rules)" (`AppForm_FormPageBusinessRule` code) addon. The addon includes the following page-level business rules: "Make elements required: Personal data," "Make elements required: Employment," "Make elements required: Residence address," "Make elements required: Registration address," "Make elements required: Mailing address," "Make elements required: Previous residence address," and "Make elements required: Previous registration address." "Make elements read-only, hide elements: Submitted, Cancelled statuses." "Show elements: Cancellation reason," "Show elements: Submit button," "Show elements: Decline button," "Show elements: Residence address question," "Show elements: Registration address question," "Show elements: Previous residence address," and "Show elements: Previous registration address." "Hide elements: Residence address," "Hide elements: Registration address," and "Hide elements: Mailing address." "Show and hide elements: Residence is primary" and "Show and hide elements: Registration is primary." "Contact" (`Contact` code) column to the "Obligation in application form" (`AppFormObligation` code), "Property in application form" (`AppFormProperty` code), and "Income and expenses in application form" (`IncomeAndExpenseInAppForm` code) objects in the `CrtFinservAppMgmtObjMdl` package. "Application form" (`AppForm` code) column to the "Contact address" (`ContactAddress` code) object in the `CrtFinservAppMgmtObjMdl` package. "Applicant" value to the Roles of participants lookup. Changed: Required property in the General property block of Object Designer for the "Application" (`FinApplication` code), "Birth date" (`BirthDate` code), "Birthplace" (`PlaceOfBirth` code), "Citizenship" (`Citizenship` code), "Department code" (`CodeDivision` code), "Education" (`Education` code), "First name" (`GivenName` code), "Gender" (`Gender` code), "Issue date" (`IssueDate` code), "Issued by" (`IssuedBy` code), "Last name" (`Surname` code), "Number" (`Number` code), "Participant role" (`ParticipantRole` code), "Series" (`Series` code), and "Social status" (`SocialStatus` code) columns of the "Application form" (`AppForm` code) object in the `CrtFinservAppMgmtObjMdl` package from "Yes" to "No." Required property in the General property block of Object Designer for the "Contact" (`Contact` code) column of the "Application form" (`AppForm` code) object in the `CrtFinservAppMgmtObjMdl` package from "No" to "Yes." Title property in the General property block of Object Designer for the `Number` column of the "Application form" (`AppForm` code) object in the `CrtFinservAppMgmtObjMdl` package from "Number" to "Government Id." Displayed value property in the Object settings property block of Object Designer for the "Application form" (`AppForm` code) object in the `CrtFinservAppMgmtObjMdl` package from "Participant" to "Name." Enable live data update checkbox in the Behavior property block of Object Designer for the "Application form" (`AppForm` code) object in the `CrtFinservAppMgmtObjMdl` package from cleared to selected. Title property in the General property block of Object Designer for the `AppForm` object in the `CrtFinservAppMgmtObjMdl` package from "Application Form" to "Application form." Title property in the General property block of Object Designer for the `ParticipantRole` object in the `CrtFinservAppMgmtObjMdl` package from "Role of participant" to "Application form participant role."
Application page	Changed	Added the Application parameters expansion panel to the application submission and full pages. On the submission page, the panel is on the Product details tab. On the full page, the panel is on the Product tab. Previously, editing the product parameters of an application was available in Classic UI only. The panel displays the parameters of the selected product as fields of the corresponding type. The fields take their limits from the active product condition and display icons that explain the requirements, errors, and locked values. Users can edit the parameters only on the application stages that allow editing. Creatio validates the values before saving the application and saves them as parameter records of the application. If the panel has no parameters to show, the panel displays a placeholder. This change enables users to capture application terms correctly, for example, the deposit amount and term, without knowing the rules of each product. More details Added: Support for the "Text," "Integer," "Decimal," "Boolean," and "Drop-down" parameter types. Out of the box, "Text" type parameters accept up to 250 characters. "Drop-down" type parameters filter their options as the user types. Limits from the product condition for the parameter fields. "Integer" and "Decimal" type parameters take the minimum and maximum values. "Drop-down" type parameters take the allowed values. A "Drop-down" type parameter with one allowed value is populated automatically and locked. A "Drop-down" type parameter without allowed values is locked. A "Decimal" or "Boolean" type parameter with a single fixed value is locked. Icons for the parameter fields: displays the parameter requirements, for example, required value, minimum, and maximum. explains why a value is invalid. marks a parameter that users cannot edit because its value is fixed or the application stage does not allow changes. Validation of parameter values. All parameters are required. If a value is missing or out of range, Creatio displays the "Application parameters not valid" message and does not save the application. Placeholders for the cases when no product is selected, the product has no parameters, or multiple active product conditions are found. "Editable application parameters" (`AreParametersEditable` code) column to the "Application stage" (`FinAppStage` code) object in the `CrtFinservAppPrms` package. Out of the box, users can edit parameters only on the "Product details" stage. "Clean application parameters" business process.
Application dynamic cases	Added	Added a guided case for retail deposit account applications. The case moves an application through the stages from "Customer details" to "Settled" and validates the required data at each stage transition. The case also creates the contract and the documents for signing. When an agent uploads the signed documents and clicks the Complete button, the case completes the application. This change enables agents to open a deposit account directly from the application. More details Added: "Retail deposit account application" (`RetailDepositAccountApplicationCase` code) schema of the "Case" type. The schema includes the "Customer details," "Product details," "Agreement & Signature," "Settled," and "Declined" stages. The stage steps create and process the application form and run the manual evaluation. Then, the steps process the "Agreement & Signature" stage, complete the application, and clear the application parameters. Creatio selects the case based on the "Product category" (`ProductCategory` code) column of the application. "Change application stage" business process. The process checks the identity documents, required documents, and documents for signing before the stage changes. "Process Agreement & Signature stage" business process. The process waits until the evaluation status is "Approved" and sets the decision date. Then, the process creates the contract and generates the documents for signing. "Complete application for retail deposit account" business process. The process sets the contract state to "Signed" and the signing status to "Signed on paper." Then, the process creates the financial account and, if required, the debit card. Finally, the process sets the end date of the application. "Create application form for application" business process. Application signing statuses lookup. The lookup includes the "Not signed," "Signed on paper," and "Signed with e-signature" values. The "Color" column for these values is set as follows: #FF6534 for "Not signed." #198754 for "Signed on paper." #A6DE00 for "Signed with e-signature."
Evaluation management	Changed	Changed customer evaluations to link them to applications. Users can view the evaluations of an application and start a new evaluation from the application submission page. The evaluation mini page displays only the applications of the evaluated contact. The evaluation result is copied to the evaluation status of the application. This change makes compliance results part of the application decision. More details Added: "Application" (`FinApplication` code) column to the "Evaluation history" (`EvaluationHistory` code) object in the `CrtFinservAppMgmtObjMdl` package. Application field to the General information tab in the "Evaluation history mini page" (`EvaluationHistory_MiniPage` code) schema of the "Client module" type in the `CrtFinservAppMgmt` package. "Apply filter: Application" object-level business rule to the "Evaluation history (Business rules)" (`EvaluationHistoryBusinessRule` code) addon in the `CrtFinservAppMgmt` package. The rule filters applications by the contact. "Evaluation history list mini page" (`EvaluationHistoryList_MiniPage` code) schema of the "Client module" type. The mini page lists the evaluations of the application and enables users to start a new evaluation. "Create manual evaluation for application" business process. "Update evaluation status in application" business process. The process copies the evaluation result to the "Evaluation status" (`EvaluationStatus` code) column of the application.
Financial account management, Card management	Added	Added automatic creation of the financial account and debit card from a deposit application. The financial account receives the product and terms from the application. If the application requires a debit card, the card is issued and linked to the account. After the account is created, users can open the account from a mini page. This change completes deposit account opening without manual data entry. More details Added: "Create financial account and card from application" business process. The process creates the financial account using the product, type, APY, currency, and deposit amount of the application. If the "Issue debit card" parameter requires a card, the process creates a debit card in the "Issued" status. Then, the process links the card to the account. The process assigns sequential numbers to the account and card. "Open financial account mini page" (`OpenBankAccount_MiniPage` code) schema of the "Client module" type. The mini page enables users to open the new financial account.
Consultation center	Changed	Added account opening and product advisory flows to the consultation center. Agents can start an application for a certificate of deposit, checking account, or savings account directly from a consultation. The product advisory flow enables agents to browse the product catalog, preview a product, and start an application for the selected product. This change shortens the path from a customer request to a submitted application. More details Added: "Launch deposit account application," "Launch checking account application," "Launch saving account application," and "Create application for product type" business processes. "Launch product advisory," "Create application for selected product," and "Fetch contact from consultation and launch application" business processes. "Product advisory page" (`ProductAdvisory_Page` code) schema of the "Client module" type. The page displays the product catalog. "Product preview mini page" (`ProductPreview_MiniPage` code) schema of the "Client module" type. "List page" (`ListPageWithNoDataSource` code) page template for pages without a data source.
Consultation center	Changed	Added financial account closure to the consultation center. The agent selects an active financial account, the closing reason, and the closure date. If the account balance is zero, the account and its linked cards are closed. If the balance is positive or negative, the account remains open. A notification informs the agent that the closure is on hold until the customer withdraws the funds or settles the debt. This change ensures that closure conditions are applied consistently. More details Added: "Financial account closure" business process. "Financial account closure mini page" (`FinancialAccountClosure_MiniPage` code) schema of the "Client module" type. "Financial account closure notification mini page" (`FinancialAccountClosureNotification_MiniPage` code), "Financial account closure positive balance notification mini page" (`FinancialAccountClosurePositiveBalanceNotification_MiniPage` code), and "Financial account closure negative balance notification mini page" (`FinancialAccountClosureNegativeBalanceNotification_MiniPage` code) schemas of the "Client module" type.
Consultation center	Changed	Added prebuilt banking flows to the consultation center. The flows are grouped into blocks for account opening, customer data adjustments, and financial account operations. The customer data adjustment flows enable agents to update the address, personal data, and identity documents of the customer. Each launched consultation theme is recorded in the consultation together with its start and end time. This change gives agents guided scenarios for the most common customer requests. More details Added: "Account opening," "Customer data adjustments," and "Financial account operations" values to the Consultation theme blocks lookup. "Account closure," "Address," "Certificates of deposit (CDs)," "Checking accounts (DDA)," "Customer identification," "Deposit accounts," "Personal data," "Product advisory," and "Savings accounts" values to the Consultation themes lookup. The "Customer identification" theme has no tile on the consultation center. The flows record this theme when they identify the customer. Out of the box, the lookup is not registered. To manage the values in the Lookups section, register a lookup based on the "Consultation theme" (`ConsultationTheme` code) object. "Add consultation theme in case" and "Add end date in consultation theme in case" business processes. The processes record the start and end time of each consultation theme. Removed the Sell block from the consultation center.
Document management	Changed	Added the creation of identity documents from the application and application form pages. A mini page enables users to create a document of the selected class with its properties and attachments. The application form is populated with data from the document properties. When a user adds or modifies an identity document, the other active documents of the same class that belong to the contact become inactive. This change enables users to capture identity data once and reuse data across the application. More details Added: "Create document (sub-process)" business process. "Create document mini page" (`CreateDocument_MiniPage` code) schema of the "Client module" type. "Create document from application from" business process. The process copies the first name, last name, gender, date of birth, place of birth, SSN, and country from the document to the application form. "Deactivate identification document" business process. When a user adds or modifies an identity document, the process finds the other active documents of the contact that have the same class. Then, the process sets the "Inactive" status for these documents.
Document management	Changed	Changed the required documents of an application to link them to document records. Previously, the attachments of a required document remained on the required document and were not available in the documents of the customer. The list of required documents is generated for each application, and each required document has its own status. Attaching a file to a required document creates a document record and copies the files to the document or contract. Deleting a required document also deletes the related document. This change keeps application documents consistent with the documents of the customer. More details Added: "Status" (`DocumentState` code) column to the "Required documents in application" (`DocListInFinApp` code) object in the `CrtFinservAppMgmtObjMdl` package. The default value of the "Status" (`DocumentState` code) column is "Unuploaded." "Generate required documents for application," "Create document from required document," and "Delete document after required document deletion" business processes. "Create required document from application" business process. The process uses the "Select document class mini page" (`SelectDocumentClass_MiniPage` code) schema of the "Client module" type. Changed: Title property in the General property block of Object Designer for the `Document` column of the "Required documents in application" (`DocListInFinApp` code) object in the `CrtFinservAppMgmtObjMdl` package from "Document" to "Document class." Title property in the General property block of Object Designer for the `DocumentLink` column of the "Required documents in application" (`DocListInFinApp` code) object in the `CrtFinservAppMgmtObjMdl` package from "Document link" to "Document." Title property in the General property block of Object Designer for the `DocListInFinApp` column of the "Document list in application attachment" (`DocListInFinAppFile` code) object in the `CrtFinservAppMgmt` package from "DocListInFinAppFile" to "Required document." Enable live data update checkbox in the Behavior property block of Object Designer for the "Required documents in application" (`DocListInFinApp` code) object in the `CrtFinservAppMgmtObjMdl` package and the "Document list in application attachment" (`DocListInFinAppFile` code) object in the `CrtFinservAppMgmt` package from cleared to selected.
Workplaces	Changed	Added a workplace, homepage, and desktop for CSRs (customer service representatives). The "CSR" organizational role has access to the "CSR" workplace that includes the sections CSRs use. The homepage displays application and consultation widgets, the appointments of the day, leads to process, and knowledge base articles. The desktop displays service widgets. This change gives CSRs a role-specific starting point. More details Added: "CSR" organizational role with the "CSR. Managers group" management role. The `DISABLE_TRIGGER_TRSysAdminUnitRoot_CrtFinservAppMgmt_MSSQL`, `ENABLE_TRIGGER_TRSysAdminUnitRoot_CrtFinservAppMgmt_MSSQL`, `DISABLE_TRIGGER_TRSysAdminUnitRoot_CrtFinservAppMgmt_PostgreSql`, and `ENABLE_TRIGGER_TRSysAdminUnitRoot_CrtFinservAppMgmt_PostgreSql` SQL scripts disable the trigger before the role installation and enable the trigger afterward. "CSR" workplace. The workplace includes the Calendar, Tasks, Contacts, Legal entities, Applications, Application forms, Financial accounts, Loans, Cards, Insurances, Documents, Contracts, Knowledge base, and Feed sections. "CSR homepage" (`CSR_homepage` code) schema of the "Client module" type. The homepage includes the New application button and the following tabs: My day. The tab includes the Applications started today, Applications completed today, Avg consultation duration, seconds, New leads assigned today, Applications started this week, Applications completed this week, Consultations completed today, and Consultations completed this week widgets, the My appointments and Leads to process expanded lists, and the Consultation themes by popularity and Products in my applications by popularity widgets. The Leads to process expanded list includes the Start application and Schedule follow-up buttons. Knowledge base. The tab includes the Application-related articles, Financial account-related articles, and Conflict resolution articles article blocks. "Application," "Conflict resolution," and "Financial account" values to the Knowledge base tags lookup. Out of the box, the lookup is not registered. To manage the values in the Lookups section, register a lookup based on the "Knowledge base article tag" (`KnowledgeBaseTag` code) object. "CSR desktop" (`CSRDesktop` code) schema of the "Client module" type. The desktop includes the Go to calendar button that opens the calendar page and the New application button that opens the application creation page. The desktop also displays the My customers, Accounts opened today, Account balance, Locked accounts, Applications by product category, Open tasks for today, Total appointments for today, Avg consultation time, and Avg CSAT widgets.

Finserv Customer Management​

Finserv Product Catalog Management​

Finserv Account Management​

Finserv Application Management​

Finserv Customer Management

Finserv Product Catalog Management

Finserv Account Management

Finserv Application Management