Category | Feature | Description |
|---|
Contact management | Contact page | Added the Application forms expanded list to the Compliance & risk monitoring tab of the "Contacts form page" (Contacts_FormPage code) schema of the "Client module" type in the CrtFinservAppMgmt package. Previously, the application forms of a contact were reachable only from the Applications or the Application forms sections. Creatio now lists every application form whose applicant is the contact, of all form types. The  button creates an application form of the "Individual" type with the contact pre-set as the applicant, and opening a row navigates to the form page. |
Applications and credit processing | Application management | Changed how the crt.DynamicParameters type of Freedom UI component stores its parameter rows, so that saved parameters are self-describing and resilient to catalog changes. Previously, the identity of a component instance and the classification of its rows were one overloaded identifier. A saved product parameter also validated against the live product condition, so a later change or removal of the condition altered the constraints of already saved values. Creatio now identifies every instance by a client-side name, and persists its rows under a configurable classification. It also snapshots the type, range constraints, and allowed options of a product parameter at the moment of saving, so a saved value no longer depends on the current state of the product catalog. Install scripts classify and snapshot the rows saved by earlier versions. This change keeps saved parameter values and their constraints stable over time, independent of later changes to the product catalog. More details
-
Added:
-
Constraint snapshot for product parameters in the crt.DynamicParameters type of Freedom UI component to the crt_ui_components bundle of the CrtFinservCommonInputUtils package, through the following configuration objects:
constraintColumns that includes the CurrentType column with its single and range values, the MinIntegerValue, MaxIntegerValue, MinFloatValue, MaxFloatValue bounds, and the IsEmptyMinValue and IsEmptyMaxValue properties.allowedValuesTarget that references the "Application parameters values" (FinApplicationSpecValue code) object.
Saving an "Integer" or "Decimal" type parameter writes its current mode and bounds. Saving a dropdown parameter writes one allowed-option record per option, including a single-option dropdown, which renders read-only. "String" and "Boolean" type parameters write no constraint data, and the empty-value flag is never modified by the snapshot. A persisted parameter with a populated snapshot validates against it. A persisted parameter with an empty snapshot and an unsaved parameter validate against the live source.
-
"Application parameters values" (FinApplicationSpecValue code) object to the CrtFinservAppMgmtObjMdl package. The object includes the "Application parameter" (ApplicationParameter code) and "Value" (Value code) columns.
-
UpdateSpecInConditionTypeInFinApplicationSpec_MSSQL and UpdateSpecInConditionTypeInFinApplicationSpec_Postgre SQL scripts to set the classification of every parameter row saved by earlier versions, for both the Customer need and Product fields, when the classification is missing, based on the row's own specification, so the values saved before the update are shown again. The scripts are idempotent.
-
UpdateParameterConstraintsInFinApplicationSpec_MSSQL and UpdateParameterConstraintsInFinApplicationSpec_Postgre SQL scripts to populate the snapshot of existing product parameter rows owned by an opportunity. They take the numeric constraints from one deterministic product condition row per parameter, and the allowed values as "Application parameters values" (FinApplicationSpecValue code) object records, touching only rows whose snapshot is empty. The scripts are idempotent.
-
Changed:
-
crt.DynamicParameters type of Freedom UI component of the crt_ui_components bundle of the CrtFinservCommonInputUtils package to split the former componentId configuration key into the instance name:
instanceName, client-side only, used for the registry, dirty events, and cross-source deletions, never persisted.classification, featureTypeId, written to the "Parameter classification in product condition" (SpecInConditionType code) object.
A page that configured the crt.DynamicParameters type of Freedom UI component with componentId in version 1.4 must switch to instanceName and featureTypeId when updating to version 1.5. The key is deliberately not named name, which Freedom UI reserves and which broke saving the page in the designer. The classification is required. An instance without a name or with an all-zeros or malformed classification fails validation (missingInstanceName, missingFeatureTypeId, invalidFeatureTypeId), renders the invalid-configuration state, and neither loads nor saves. Reusing a name with a different classification is logged as a warning.
-
"Opportunities form page" (Opportunities_FormPage code) schema of the "Client module" type in the CrtFinservAppMgmt package. Both LeadTypeDynamicParameters and ProductDynamicParameters instances are configured with the "Product features" classification and the Specification.SpecInConditionType classification column. The add window filter lists only specifications of that classification. The product instance is the only instance that opts into the snapshot using the constraintColumns and allowedValuesTarget configuration objects. The button of the parameters in the Customer request expansion panel has the New caption. A Customer need field whose specification carries another classification is intentionally not shown.
|
Applications and credit processing | Application page | Added a confirmation before an application is completed from the application submission page in the retail flow, mirroring the existing confirmation on the Submit button. Previously, clicking the Complete button settled the application and created the bank account or loan immediately. Creatio now shows a confirmation before completing the application. Confirming moves the application to the "Settled" stage and creates the product as before, while cancelling leaves the application on its current stage. This change prevents front-office users from completing an application and creating a financial record by accident. More detailsAdded:
- "Complete application" (
FinApplication_CompleteApplication_Dialog code) schema of the "Client module" type. The schema includes the Complete and Cancel buttons and the "After this step, the application will be completed and a financial record will be created" message. Complete saves the record without a success message.
- Complete application dialog user task to the "Change application stage" business process for transferring the application to the "Settled" stage. The Complete result continues the completion, the Cancel result aborts the stage change. The existing Confirm application submit pre-configured page remains unchanged.
|
Applications and credit processing | Application page | Changed the application full page and the application submission page to manage application parameters with the crt.DynamicParameters type of Freedom UI component. Previously, the application pages relied on the deprecated crt.ApplicationParametersModule, which was tightly coupled to the application data model, while the opportunity page already used the new component. This change gives Creatio a single, consistent way to manage product parameters across opportunities and applications, and keeps the application pages free of the deprecated parameter module. More details
-
Added the crt.DynamicParameters type of Freedom UI component to the Application parameters expansion panel on the Product tab of the "Application full page" (FinApplication_FullPage code) and "Application submission page" (FinApplication_SubmissionPage code) schemas of the "Client module" type in the CrtFinservAppPrms package. The panel shows the selected product parameters based on the product. Its allowed values and constraints are configured via constraintColumns and allowedValuesTarget configuration objects. Adding new parameters is disabled, i.e., "allowAdd": false, and deleting parameters is not allowed, i.e., "deleteMode": "none". The isReadonly property is bound to the inverse of Stage.AreParametersEditable forward reference, so the panel becomes read-only whenever the current application stage does not allow editing parameters, and editable otherwise. The Save and Cancel buttons are shown only when there are unsaved changes in the parameters (bound to CrtDynamicParametersSaveControlsVisible attribute). When there are no changes, the Close button is shown instead.
-
Changed:
- "Pull application parameters for credit cards and lines of credit" and "Pull application parameters from credit card" business processes to add the values of the pulled Currency, Loan purpose, Revolving status, Card category, Multicurrency enabled, PayPass / PayWave enabled, Payment system, Type of rewards program parameters. Additionally, the "Application parameters values" records of the "Dropdown" type parameters were added to the "Pull application parameters for credit cards and lines of credit" business process, so that a credit-card limit-change request shows its parameters in the component.
- "Confirm application submit" (
FinApplication_ConfirmSubmit_Dialog code), "Financial records required" (FinApplication_FinRecordsRequired_Dialog code), "Modify customer data" (FinApplication_ModifyCustomerData_Dialog code), "Loan offer acceptance required" (FinApplication_Validation_OfferAcceptance_Dialog code), "Required documents not uploaded" (FinApplication_Validation_RequiredDocumentsNotValid_Dialog code), "Required signature documents not uploaded" (FinApplication_Validation_RequiredSignatureDocumentsNotValid_Dialog code), and "Signed documents and loan offer acceptance required" (FinApplication_Validation_SignedDocsAndOfferAccptnc_Dialog code) schemas of the "Client module" to save the record without the record-saved message, i.e., showSuccessMessage: false.
-
Removed the deprecated crt.ApplicationParametersModule with its handlers, source attributes, placeholders, and converter, from the "Application full page" (FinApplication_FullPage code) and "Application submission page" (FinApplication_SubmissionPage code) schemas of the "Client module" type.
|
Applications and credit processing | Application form management | Added the Modify action that returns a submitted application form to the "Draft" status. Previously, a submitted individual or legal entity application form could not be corrected, and a new form had to be created. Creatio now shows the Modify button on a submitted form that is not linked to an application, asks for confirmation, cancels the evaluations in progress, and reopens the form for editing so it can be re-submitted. A form that belongs to an application is modified from the application page instead, where the existing Modify data button reverts the connected form without a second confirmation. This change enables front-office users to correct applicant data without losing the application form history. More details
-
Added:
- "Modify application form data" business process that opens the "Confirm modify application form data" (
AppForm_ConfirmModifyData_Dialog code) schema of the "Client module" type when the form has no connected application. The process re-reads the form status after the confirmation and opens the "Application form cannot be modified" (AppForm_Validation_ModifyBlocked_Dialog code) schema of the "Client module" type when the form has left the "Submitted" status meanwhile. The process cancels the linked evaluations that are still active and not approved, cancelled, or rejected, and sets the form status to "Draft."
- Modify button to the "Application form edit page" (
AppForm_FormPage code) and "Legal entity application form edit page" (AccountAppForm_FormPage code) schemas of the "Client module" type.
- "Show elements: Modify" page-level rule to the "Application form edit page (Business rules)" (
AppForm_FormPageBusinessRule code) and "Legal entity application form edit page (Business rules)" (AccountAppForm_FormPageBusinessRule code) addons that shows the Modify button only when the status is "Submitted" and the form is not linked to an application.
-
Changed:
- "Application submission page" (
FinApplication_SubmissionPage code) schema of the "Client module" type and the "Make elements read-only: Modify data" page-level business rule to make the Modify data button at the "Agreement & Signature" stage read-only when the evaluation is approved.
- "Change application stage" business process to revert the connected application form when the application is modified.
- "Process ownership structure contacts in application form" business process to reuse an existing individual application form of an ownership structure contact instead of creating a duplicate.
- "Confirm application form submit" (
AppForm_ConfirmSubmit_Dialog code) schema of the "Client module" type to no longer show a record-saved message.
|
Applications and credit processing | Application form management | Changed the application form model, naming, and data synchronization. Previously, the form name carried no unique number and was recalculated whenever the linked application changed, contacts and legal entities could accumulate duplicate phone records when a form was approved repeatedly, and the ownership structure of a legal entity form offered every contact regardless of the selected legal entity. Creatio now numbers application forms automatically and names them from the number, the participant role, and the applicant. It treats phone numbers that differ only in formatting as the same number when synchronizing form data to a contact or legal entity, and connects the "Legal entity" (Account code) and "Contact" (Contact code) columns of the "Ownership structure in application form" (OwnershipStructureInAppForm code) object. This change gives every application form a stable, unique name, keeps contact and legal entity phone data clean, and speeds up filling out an ownership structure. More details
-
Added:
- "Number" (
AppFormNumber code) column to the "Application form" (AppForm code) object.
- "Normalize value to number for search" (
NormalizeToSearchNumber code) schema of the "User task" type to the CrtFinservCstmr360 package. The schema keeps the digits of a phone value, reverses them, and trims the result to the "Number of digits for search" (SearchNumberLength code) system setting, the key format of the search-number column of communication records, so numbers are matched by a prefix comparison regardless of formatting. Out of the box, the system setting value is set to "10." A non-numeric value returns an empty key.
- "Ownership structure in application form (Business rules)" (
OwnershipStructureInAppFormBusinessRule code) addon for the "Ownership structure in application form" (OwnershipStructureInAppForm code) object with the "Apply filter: Contact" rule, where the Contact lookup is filtered by Contact.Account column equal to the Account column of the legal entity. The rule has generated child rules: populate "Legal entity" (Account code) column from the selected contact, and clear the "Contact" (Contact code) when the "Legal entity" (Account code) column changes. The rule is defined on the object, so it applies wherever an ownership structure record of an application form is edited.
-
Changed:
- "Populate application form name" business process to build the name as {Number / Participant role / contact full name or legal entity name}. The process reads the legal entity for a legal entity form and the contact for an individual form, and it runs when the form is created or its contact or legal entity changes. The trigger on a change of the linked application was removed, so the form name no longer follows the linked application.
- "Application full page" (
FinApplication_FullPage code) schema of the "Client module" type in the CrtFinservAppMgmt package to show the forms whose applicant is the application's contact or its legal entity in the Application forms expanded list on the Documents tab.
- "Process application form and update contact data" business process to normalize the primary and additional phone numbers of the form before matching them against the contact's phones, and to store the additional phone in the Other phone field. An existing phone of the alternative type with the same number is re-typed instead of duplicated.
- "Process application form and update legal entity data" business process to normalize the primary, alternative, and fax numbers before matching.
- "Populate contact data for existing contact in application form" business process to read the contact's other phone instead of the additional phone.
|
Applications and credit processing | Application form management | Changed the application workflow to be typed by product type instead of product category, in line with the restructured product catalog. Previously, the dynamic case of an application and its stage transitions were selected by the product category, and an application did not record the product family. Creatio now selects the application case and the stage transition map by the product type, and stores the product family on the application. The application name is now built from the product type, and the product family is passed into every launch process, whether started from a product, a lead, an opportunity, or a consultation theme. Products whose type has no dedicated flow, for example, mortgage loans, home equity loans, health savings accounts, or commercial deposit products, create and save an application without stage progression. Important Before updating to version 1.5, we recommend reviewing your existing dynamic case configurations for applications to ensure their start signals do not overlap with the re-typed application cases, so that only one dynamic case launches per record. More details |
Applications and credit processing | Application form management | Fixed a runtime issue where the Submit button of the application form page opened during the conversion of a retail lead with several products closed the page before the form was submitted. Previously, the lead conversion process completed its interactive step on the button click, and the Submit button of the pages ran an extra save request. Creatio now opens the page through a dedicated sub-process that completes on the status of the form rather than on a button click, and the Submit button of both application form pages runs only the form submission process. An invalid form is blocked with its validation message and the page stays open. A single-product lead still creates the application immediately. This change prevents front-office users from losing application form data when converting a multi-product lead. More details
-
Added the "Complete application form in lead (sub-process)" business process. The process includes the "Lead" and "Application form" parameters and opens the "Application form edit page" (AppForm_FormPage code) as a process page titled "Complete application form: {form name}" without a completion button, assigned to the lead owner, and ends when the "Application form is completed or cancelled" signal fires, closing the page without terminating the parent process.
-
Changed:
- "Application form edit page" (
AppForm_FormPage code) and "Legal entity application form edit page" (AccountAppForm_FormPage code) schemas of the "Client module" type. The Submit button no longer sends a separate save request and runs only the "Submit application form" business process, which saves the record at start, validates it, and sets the status.
- "Lead conversion to application" business process to remove the inline preconfigured-page step with its "Submit completion" binding and the intermediate signal. The process now calls the sub-process with the created application form and then creates an application per selected product.
|
Opportunity management | Opportunity page | Changed the "Offer structuring" and "Proposal" stages of the "Opportunity management for commercial sales" (FinservOpportunityManagementCommercialSalesCaseCrtFinservAppMgmt1 code) schema of the "Case" type. Creatio now runs an internal risk assessment with an approval by the "Credit risk analyst" organizational role in parallel with the offer structuring tasks, and validates the completeness of the opportunity in a reusable sub-process. It generates a financial proposal document at the start of the "Proposal" stage, emails it to the customer or creates a task to present it, captures the customer's decision, and only then submits the opportunity for underwriting. This change gives commercial sales a controlled path from structuring an offer to a customer-approved proposal. More details
-
Added:
- "Internal risk assessment in opportunity" business process that opens the "Submit opportunity for internal risk assessment" (
Opportunity_SubmitForInternalRiskAssessment_Dialog code) schema of the "Client module" type, runs the completeness validation, creates the "Assess internal risk and approve financial proposal" approval for the "Credit risk analyst" organizational role, and routes the result. A positive decision moves the opportunity to the "Proposal" stage, a negative decision returns it to the offer structuring tasks, and cancellation cancels the opportunity.
- "Opportunity completeness validation" business process that checks whether the product is filled out, all product parameters are filled out, all required documents are uploaded, and an approved KYB evaluation exists, and shows the matching blocking notification when a check fails.
- "Proposal stage in opportunity" business process that generates the "Financial proposal" report as a file named "Financial proposal for {legal entity} {date}" and attaches it to the opportunity. If the "Mailbox for sending customer notification" (
CustomerNotificationMailboxSettings code) system setting is filled out, it creates the "Send financial proposal to the customer" email task with the attached proposal and the "Financial proposal for customer (US)" template, otherwise the "Financial proposal presentation" task. It then creates the "Confirm the customer's decision on the proposal" task in the "Paper work" category, whose Requires modification conditional flow returns the opportunity to the "Offer structuring" stage and whose cancellation cancels the opportunity.
- "Financial proposal" report to the Report setup section in the System Designer. The report lists the product parameters sorted by parameter and excludes the customer-request parameters.
- "Financial proposal for customer (US)" email template to the Message templates section.
-
Changed:
- "Offer structuring stage in opportunity" business process, reduced to the sequential "Capture customer request," "Define product parameters," and "Upload required documents" tasks. The "Assess the need for compliance and risk monitoring" task and the move to the "Proposal" stage were taken out of it and are handled by the internal risk assessment.
- "Submit opportunity for underwriting" business process to call the "Opportunity completeness validation" business process instead of its own checks, and to generate the document package and move the opportunity to the "Underwriting" stage only when the validation passes.
- "Opportunity management for commercial sales" (
FinservOpportunityManagementCommercialSalesCase code) schema of the "Case" type. The internal risk assessment starts at the beginning of the "Offer structuring" stage alongside the offer structuring process, the proposal process starts at the beginning of the "Proposal" stage, and the submission for underwriting runs after it completes. The case passes the opportunity identifier and the "Mailbox for sending customer notification" (CustomerNotificationMailboxSettings code) system setting to the processes.
- "Opportunities form page" (
Opportunities_FormPage code) schema of the "Client module" type in the CrtFinservAppMgmt package to show the Approvals expanded list on the Compliance & risk monitoring tab. The list supports data refresh and search.
- "Opportunities form page (Business rules)" (
Opportunities_FormPageBusinessRule code) addon to add stage-dependent rules, including making the Customer need and Product fields in the Products expansion panel on the Product details tab read-only on the "Proposal" stage.
- "Opportunity stage" data binding so that the "Proposal" stage locks the dynamic parameters.
|
Opportunity management | Opportunity page | Changed the crt.DynamicParameters type of Freedom UI component and the opportunity page so that the parameters of an opportunity are locked by its stage. Previously, the Customer request and Product parameters expansion panels stayed editable at every stage of the opportunity, a read-only parameter revealed its  icon only on pointing, and read-only and editable parameters were mixed in one alphabetical list. This change prevents accidental edits to opportunity parameters once a deal reaches a locked stage, so data stays consistent through underwriting and closing. More details
-
Added:
- Page-bindable, per-instance
isReadonly property to the crt.DynamicParameters type of Freedom UI component. A read-only instance renders every row through the locked path (a dropdown shows its label, a boolean shows text), skips parameter generation, ignores value changes and adding or deleting parameters, does not mark the page dirty, does not validate or persist anything, so it never blocks saving, even with pre-existing invalid values, and discards unsaved edits when it becomes read-only. Unlocking regenerates the rows, so an instance mounted read-only shows its parameters once it is unlocked. Unlocked instances keep their validation, display, save, and reload behavior.
- "Dynamic parameters locked" (
AreDynamicParametersLocked code) column to the "Opportunity stage" (OpportunityStage code) object through a replacing object in the CrtFinservSalesMgmtObjMdl package, delivered set for the "Proposal," "Underwriting," "Contracting," "Closed won," "Closed lost," and "Canceled" stages. The out-of-the-box stages are force-updated, so the lock also applies when updating to version 1.5.
-
Changed:
- "Opportunities form page (Business rules)" (
Opportunities_FormPageBusinessRule code) addon to hide the button of the customer request parameters on the "Proposal," "Underwriting," "Contracting," "Closed won," "Closed lost," and "Canceled" stages. The rule keeps its own stage list, so extend both data and the rule when adding a locking stage.
- icon of a read-only parameter in the
crt.DynamicParameters type of Freedom UI component. The icon was made permanently visible instead of pointing-only. The list order for display was changed: editable parameters first, read-only parameters after them, each group alphabetically by label. The order is presentation-only and identity-based, so an edit or delete always applies to the intended parameter. A read-only field is never flagged invalid, even when its value violates a rule or a required value is empty.
- "Opportunities form page" (
Opportunities_FormPage code) schema of the "Client module" type in the CrtFinservAppMgmt package to expose the AreDynamicParametersLocked property through the Stage.AreDynamicParametersLocked forward reference and bind the isReadonly property of both Customer request and Product parameters expansion panels to it.
- "Opportunities form page (Business rules)" (
Opportunities_FormPageBusinessRule code) addon to block the fields on the "Canceled" stage.
|
Opportunity management | Opportunity page | Fixed a runtime issue where the parameter list of an opportunity did not refresh after the parameter collection of a Customer need and Product fields on the Product details tab of the opportunity page changed. Previously, clearing a source did not delete its saved parameters. The cleared source unmounted its fields, and the queued deletion was committed only through a still-mounted field, so stale rows persisted and re-selecting the source kept showing the old set. Creatio now deletes the parameters of a cleared or changed source when the record is saved, scoped to that record, so re-selecting the source re-reads and shows its current parameter collection. Cancelling the record changes after clearing a source restores the parameters instead of deleting them, and a save never affects another opportunity. The change applies identically to the Customer need and Product fields. This change enables front-office users to trust that an opportunity's parameter list always reflects the current parameter collection of the selected customer need or product, without having to create a new opportunity to see it. More details
-
Added the crt.DynamicParametersCancelRecordHandler handler on the crt.CancelRecordChangesRequest request, and a bundle-owned save handler, for the save and cancel handling of dynamic parameters.
-
Changed:
crt.DynamicParameters type of Freedom UI component so that the component registry flushes the orphaned cross-source deletions of the saved record even when no field is mounted, i.e., saveAll with the record identifier. The cross-source delete holder stores its entries per record and field, and the saver deletes each entry by its own durable key. resetAll with the record identifier drops the pending deletions on cancel.- Save order of the
crt.DynamicParameters type of Freedom UI component. The record is saved first, and the parameters are persisted right after it. This fixes the foreign-key error that occurred when a new opportunity was saved with parameters. If persisting the parameters fails, the record save is no longer blocked. Creatio displays the "Failed to save. Please try again." notification when the crt.DynamicParameters type of Freedom UI component provides no message of its own.
-
Removed the page-level save and cancel handlers from the "Opportunities form page" (Opportunities_FormPage code) schema of the "Client module" type in the CrtFinservAppMgmt package, so a host page no longer needs custom handler code to save or revert the component's parameters.
|
Opportunity management | Opportunity page | Fixed a runtime issue where the crt.DynamicParameters type of Freedom UI component did not render a saved parameter whose specification was removed from the parameter collection of its Customer need or Product fields on the Product details tab of the opportunity page. Previously, such an orphaned parameter had no generation definition, its type could not be inferred when the value was empty, and the row fell into the unrenderable "Type isn't set" state. Creatio now recovers the type and label of an orphaned parameter from the "Feature" (Specification code) object by its identifier, or from the populated value column when no catalog source is configured. A recovered dropdown stays editable with a fallback option list, the custom flag of the row is left unchanged, and the load completes even when the catalog lookup fails for some rows. The value of an orphaned parameter is preserved and editable, though its constraints are not enforced (they are covered by the constraint snapshot introduced in this release). Boolean parameter fields now also match the out-of-the-box checkbox styling. This change ensures users never lose sight of a previously saved parameter value, even after the underlying specification is deleted. More details
-
Added:
specificationSource configuration object to both Customer need and Product fields on the Product details tab of the "Opportunities form page" (Opportunities_FormPage code) schema of the "Client module" type in the CrtFinservAppMgmt package. It references the "Feature" (Specification code) object, its "Value type" (Type code) and "Name" (Name code) columns, and a typeMap configuration object that maps the specification types to the "Dropdown," "Decimal," "Integer," "Boolean," and "String" parameter types.- Optional
specificationSource configuration object to the crt.DynamicParameters type of Freedom UI component, normalized independently of the add toggle and defaulting from the add catalog when not set explicitly.
-
Changed:
- Definition loader of the
crt.DynamicParameters type of Freedom UI component to recover, in one batched load by primary key, every saved row that lacks a generation definition (custom and non-custom). The recovery is best-effort, i.e., failing identifiers are logged, and the load completes.
- Value resolution of the
crt.DynamicParameters type of Freedom UI component so a populated value column wins over a catalog type that resolved to the string fallback, so a saved value is never hidden (the conflict is logged as a warning). An unrecognized non-empty parameter type code is logged as a warning instead of being coerced to string.
- The visual style of the "Boolean" type field in the
crt.DynamicParameters type of Freedom UI component to the platform crt-checkbox look, and made the row divider under an editable boolean transparent (row height unchanged, dividers of side-by-side components stay aligned).
|
Apps and packages | App management | Changed how the delivered apps are displayed in Application Hub, showing a single tile for the app family. Previously, the Application Hub showed Finserv Application Management, Finserv Account Management, Finserv Customer Management, Finserv Product Catalog Management, and Finserv Sales Management tiles, even though four of them are installed and updated only as part of the family. Creatio now hides the Finserv Account Management, Finserv Customer Management, Finserv Product Catalog Management, and Finserv Sales Management apps in their app descriptors. Only the Finserv Application Management tile is shown on a clean install and when updating to version 1.5. All sections, pages, and processes of the hidden apps remain available. More detailsAdded the "IsHidden": "true" value to the "app-descriptor.json" file in the CrtFinservAccMgmtApp, CrtFinservCstmr360App, CrtFinservPrdctMgmtApp, and CrtFinservSalesMgmtApp packages. The flag is applied by the Application installer microservice when updating to version 1.5 as well, so no install script is needed. |
Schema design and management | Object Designer | Fixed a runtime issue where "Boolean" and "String" parameter types with default values were not populated when generated from a product condition. Previously, the read-side generation mapping of the Product instance of the crt.DynamicParameters type of Freedom UI component covered only "Integer" and "Decimal" parameter types, so a single-mode "Boolean" or "String" parameter value defined in the product condition was never read, and the generated parameter rendered empty. Creatio now correctly maps boolean and string parameter values when generating them from a product condition. A migrated single-mode boolean or string value is displayed read-only, consistent with numeric single values. Single mode means a fixed value from the product condition, not an editable default. Integer, decimal, and dropdown values migrate as before. More detailsChanged the generation configuration (validation.constraintMappings.byType) of the "Opportunities form page" (Opportunities_FormPage code), "Application full page" (FinApplication_FullPage code), and "Application submission page" (FinApplication_SubmissionPage code) schemas of the "Client module" type in the CrtFinservAppMgmt package, to map boolean values to the "Logic value" (BooleanValue code) column and string values to the "Text value" (TextValue code) column of the "Application parameter" (FinApplicationSpec code) object, together with the shared "The value is not filled in" (IsEmptyValue code) column. |
User and access management | Access rights | Changed system settings created by the app family to deliver with explicit access rights. Previously, these settings had no access-rights records, so any user could change them. Creatio now delivers a rights record for each setting. Reading stays open so the dependent processes keep working. Modification is managed by the "Access to manage "System settings" (CanManageSysSettings code) system operation. Out of the box, only users with the "System administrators" and "Creatio ALM Integration" organizational roles in Creatio and the "Developer" and "Administrator" roles on ALM Portal can modify these settings. Users without access to the system operation lose the ability to edit system settings when updating to version 1.5. A new system setting added in version 1.5 is delivered with its own rights record, which gates both reading and modification by the same operation. This change protects business-critical system settings from unauthorized changes. More detailsAdded:
- "Product holding status backfill completed" (
ProductHoldingStatusBackfillCompleted code) system setting to gate both reading and modification by the "Access to manage "System settings" (CanManageSysSettings code) system operation.
SysSettingsRights_CrtFinservAppMgmt schema of the "Data" type to bind the "Mailbox for sending customer notification" (CustomerNotificationMailboxSettings code) system setting.SysSettingsRights_CrtFinservAccMgmtObjMdl schema of the "Data" type to bind the "Unusual transaction threshold" (UnusualTransactionThreshold code) system setting.SysSettingsRights_CrtFinservCstmr360 schema of the "Data" type to bind the "Default primary contact role in household" (DefaultPrimaryContactRoleInHousehold code) system setting. The "Data" type schemas are installed as regular package data without forced update. When updating to version 1.5, existing environments receive the schemas if they are missing. |
UI and navigation | Pages | Added the Service representative desktop, a Freedom UI home page for a front-line service representative in the dark glassmorphed theme. Previously, the application provided the CSR desktop only, and a service representative had to track cases, SLA risks, tasks, and the calendar in separate sections. Creatio now gives the service representative a single home page with quick actions, key case metrics, and their tasks and calendar in one place. The existing CSR desktop remains available and unchanged. More detailsAdded:
-
"Service representative desktop" (ServiceRepresentativeDesktop code) schema of the "Client module" type to the CrtFinservAppMgmt package. The page includes:
- Header with the "Hello, {current user}!" greeting.
- New button menu with the "New lead," "New case," and "New task" items. The items open the corresponding creation page.
- Go to calendar button that opens the calendar page.
- Cases at SLA risk (open cases (not canceled or closed) whose resolution deadline has passed), Average case age (the sum of the case lifecycle durations in hours divided by the number of cases resolved in the current week, shown in hours), Resolved today, SLA attainment (the share of cases resolved on time among the cases resolved in the current month, shown in percent) metrics for the current user. A user with no matching cases sees empty values without errors.
- A read-only My tasks expanded list of the user's activities in the "Not started" and "In progress" statuses. The list includes the Overdue (due date before today) and Due today quick filters.
- My calendar, the standard calendar over the user's activities with a Date quick filter that defaults to today.
- My open cases by category, a horizontal bar chart of the user's open cases with a category, grouped by category.
-
"Service representative desktop CSS" (ServiceRepresentativeDesktopCSS code) schema of the "Client module" type to the CrtFinservAppMgmt package. The schema implements glass background for the My tasks expanded list and My calendar, white quick filters, hidden scrollbars, and a dark restyle of the calendar (transparent grid, dark header and day cells, white text, distinct tile colors for past, current, and future events). The schema is attached to the "Service representative desktop" (ServiceRepresentativeDesktop code) schema.
|
UI and navigation | Pages | Added the Sales representative desktop, a Freedom UI home page for a sales representative that shows the personal pipeline and deal activity. Previously, the application provided the CSR desktop only, and a sales representative had to gather pipeline health, deals at risk, goals, and the day's work from several sections. Creatio now gives the sales representative a single home page with key pipeline metrics, deals that need attention, and their tasks, all scoped to the current user as the owner. More detailsAdded:
-
"Sales representative desktop" (SalesRepresentativeDesktop code) schema of the "Client module" type to the CrtFinservAppMgmt package. The page includes:
- Header with the "Hello, {current user}!" greeting.
- New button menu with the "Opportunity" and "Task" items. The items open the corresponding creation page.
- Go to calendar button that opens the calendar page.
- Open pipelines (the sum of the amount of the user's open opportunities, closed won, closed lost, and canceled excluded), Won this quarter (the number of the user's opportunities won in the current quarter), Average won deal size (the average amount of the user's closed-won opportunities), Sales velocity (the average number of days a won deal spent in the active stages, calculated on the "View for analysis of sales by stages" (
VwOpportInStageForAnalysis code) object as the sum of number of days in the stage over the non-final stages of the user's closed-won opportunities divided by their count), and Meetings this month (the number of the user's completed meetings on deals due in the current month) metrics. The Open pipelines and Average won deal size metrics show two decimal characters and a "$" suffix.
- Forecast gauge of the won amount of the current quarter against a 150,000 target with color thresholds.
- Sales pipeline widget with Number of opportunities, Stage conversion rate, and Pipeline conversion tabs, scoped to the user and measuring the opportunity amount.
- A read-only Need attention expanded list of the user's opportunities that stayed in an active stage for more than three weeks or had no activity in the last three weeks.
- A read-only My tasks expanded list of the user's activities in the "In progress" and "Not started" statuses that are linked to an opportunity.
-
"Sales representative desktop CSS" (SalesRepresentativeDesktopCSS code) schema of the "Client module" type to the CrtFinservAppMgmt package. The schema applies the dark theme to the desktop and restyles the out-of-the-box Sales pipeline widget (glass background and blur, transparent header and button bar). The styles target internal classes of the widget and must be re-checked when that widget changes. The schema is attached to the "Sales representative desktop" (SalesRepresentativeDesktop code) schema.
|