When a case is saved with a changed status, the deadlines are recalculated by the process ActualizeCalculationTermsAfterStatusChange.
If a case is created using the basic record addition functionality in the [Cases] section, selecting a service (or another field affecting the deadline calculation) will automatically populate the deadlines by calling the service CaseTermCalculationService/CalculateTerms.
Is it possible to use a business rule or some other tool to have alternative names for sections based upon user type or user role?
Example: If User 1 logs in they see the section Leads, but if User 2 logs in they see the same section but with a different name?
Reasoning:
In public sector different departments depending on their role may want to use the lead object for different reasons. IN the world of Economic development they may call it leads, but in the grants space they would call it funding considerations. They both would have different DCMs but we are trying to not duplicate the lead object. just use it in two different ways.
The simplest approach is to create a new section with a different title based on the same entity. This allows you to assign a separate workplace to each department role.
I am developing a custom Angular component to be used in a Creatio instance. As shown in the screenshot, it directly prompts for “Open source code.” Instead, I want to pass inputs to the component in the same way standard components handle input parameters.
Currently, in the Angular code, the input is being passed as shown below:
@Input() @CrtInput() url: string = "";
Questions:
What other approaches are available for passing input parameters to custom Angular components?
Also, which JavaScript library would you recommend for working with fillable PDFs?
The transfer of organizational structure settings and access rights from one stand to another can be implemented using SQL scripts. To do this on the reference environment, you need to generate insert queries based on records from the following tables:
- SysAdminUnit (Administration object: users and roles) - SysUserInRole (Direct user entries in roles) - SysFuncRoleInOrgRole (Entry of a functional role into an organizational role) - SysAdminOperation (System operations, if required) - SysAdminOperationGrantee (Access to system operations, if required) - SysEntitySchemaOperationRight (Access to objects) - SysEntitySchemaRecordDefRight (Access to default records) - SysEntitySchemaColumnRight (Access to object columns) - SysAdminUnitGrantedRight (Delegation) - SysWorkplace - (User Workplace) - SysAdminUnitInWorkplace - (Users in Workplace) - SysModuleInWorkplace - (Partition in Workplace)
You can use Microsoft SQL Server Database Publishing Wizard and similar tools to generate queries. The resulting SQL script must be attached to the package: "SQL script" type schema | Creatio Academy
I have a custom field called Start Date on my screen for Contact. All I want to do is to prevent users to be able to enter dates that are before 2026. The Start Date must be any dates in or after 2026.
I thought it would be a simple requirement that would have a no-code solution. Can you be kind enough to let me know if it's possible? I just cannot get that to work.
At this time, the behavior of the date picker itself cannot be adjusted using standard no-code or low-code tools in Creatio. The calendar interface does not currently support restricting or disabling specific date ranges, such as dates before 2026.
As a result, preventing users from selecting dates prior to 2026 directly in the calendar would require custom development.
Thank you for your answer. I'm not really just talking about date field, I'm talking about validation in general. For example, date must be 2026 or after; or user must enter either FieldA or FieldB; or text that should be between 5 to 10 characters, etc.
My question therefore is, if Creatio has a way to configure edits to make sure no bad data gets saved.
