Hello Monika,

We don't have any examples available for this. The only example available with maps in the mobile app is the account addresses detail and maps on it (see this community thread).

Good day, Lucas,

"What is the result" section may further refine the results, but, if you are already filtering your audience using "Which conditions must the contacts meet to transition to the next step", this itself should be sufficient.

Seeing your filter presets, I would additionally advise to make sure that participants responses that are != Open are reviewed. If you leave it as is - this may include Delivered emails that have not been opened yet.

You may check out this article for additional information on delivery status and double-check the contents of "Response of participant in Bulk email" (BulkEmailResponse) to make sure you narrow down the responses according to your need.

I've found the reason for this. The table Data schema reference contains duplicate values, some of which don't have a value in the Column name (title) field. Deleting the duplicates fixes the issue.

Still not sure what the cause was.

Hello!

To remove the "+" and process buttons please, follow the instructions:
1) Add and enable the feature "AllowCreateAngularSchema"
2) Relogging to the app
3) In the configuration, replace the MainShell schema with the additional menu item "Angular replacing view model":

 

Parent object - "Main shell layout with vertical navigation":


4) Fill the new MainShell with the following code and save the module:

 define("MainShell", /**SCHEMA_DEPS*/["@creatio-devkit/common", "css!CardSchemaViewModule", "css!MainShellCSS"]/**SCHEMA_DEPS*/, function/**SCHEMA_ARGS*/(devkit)/**SCHEMA_ARGS*/ {
    return {
        viewConfigDiff: /**SCHEMA_VIEW_CONFIG_DIFF*/[
            {
                "operation": "merge",
                "name": "ShellHeaderToolbar",
                "values": {
                    "runProcessButtonVisible": false,
                    "quickAddMenuButtonVisible": false,
                    "helpMenuButtonVisible": true
                }
            }
        ]/**SCHEMA_VIEW_CONFIG_DIFF*/,
        viewModelConfig: /**SCHEMA_VIEW_MODEL_CONFIG*/{}/**SCHEMA_VIEW_MODEL_CONFIG*/,
        modelConfig: /**SCHEMA_MODEL_CONFIG*/{}/**SCHEMA_MODEL_CONFIG*/,
        handlers: /**SCHEMA_HANDLERS*/[]/**SCHEMA_HANDLERS*/,
        converters: /**SCHEMA_CONVERTERS*/{}/**SCHEMA_CONVERTERS*/,
        validators: /**SCHEMA_VALIDATORS*/{}/**SCHEMA_VALIDATORS*/
    };
});

5) Relogging to the app and check the result:



 

As for the Global Search - see this post https://community.creatio.com/questions/global-search-field

In your case if you need to hide it for all users - specify the "All employees" and "All external users" in the GlobalSearchInputVisible operation permission.

You can use this marketplace addon to hide UI elements without any additional code: https://marketplace.creatio.com/app/experceo-ui-wizard-creatio
 

Mohamed Ouederni,

It's an option, but we faced several tickets when 2 first DCM stages are not displayed in the UI on all Freedom UI pages when this addon is installed. So better hiding the elements using examples we shared above.

To add some details to what I'm seeing, this is the Read data step:

This is a formula step to try to see what should be coming out of this step in the Resulting collection:

And this is my User Task step which takes an EntityCollection parameter:

Before the Formula step, the value of the "Entity collection" parameter is null, afterwards it appears in the BP trace logs as being "", so something does change - below is shown what the User Task step's Inspect looks like after it fails:

So the BP parameter value is "" for the EntityCollection, but it's null for passing into the User Task, and that's what we see in the User Task debugging in Visual Studio (which causes the error, as we get an "Object reference not set to an instance of an object" error when trying to use it).

When checking what the OOTB ReadDataUserTask code is setting to the ResultEntityCollection parameter (which is the parameter for "Resulting collection") we can see that it is correctly being passed the EntityCollection:

It just doesn't seem to be able to be used afterwards in the BP.

Anyone have any knowledge on why the Resulting collection parameter from a Read data step in a BP would be null despite it seeming to come back populated from the C# code?

Hello!

Unfortunately, there is currently no way to add a new icon in the icon list for Freedom UI on the current configuration.

However, a task has already been registered in our R&D team to consider and implement such a feature in future releases. 

Hello,

Please try to do the following:

1) Unlock the package CrtNUI for hotfix.
2) Open SectionModuleV2 schema metadata
3) Delete the block with WebitelCtiProvider schema dependency (see screen below).
4) Lock the package CrtNUI back.
5) Compile system

Malika,

Hey , i'm unable to view the image that you have uploaded

First, enable debug mode by executing the following in the browser console:

See https://customerfx.com/article/debugging-client-side-code-in-creatio-fo…

Once enabled, open the code for the page and set some breakpoints. Is a dataSourceName for "LookupAttribute_85sj3qr_List_DS" getting triggered? Maybe the name is wrong?

Is request.$context.Parameter_q8l08xk correctly retrieving the account?

Ryan

Everything looks Correct , and the issue was that I forgot to add the SDK "@creatio-devkit/common" to the page .
Thank You 

Hello!

Please provide more detailed information – what errors are you encountering?

Hello,

In Creatio, you can manage user permissions to control access to various operations, including creating, editing, and deleting records. However, there isn't a specific permission to block users from copying records directly.

To achieve your goal of preventing users from copying records, you can consider the following approaches:

Custom Business Rules: Implement custom business rules or scripts that prevent the copying of records. This can be done by adding validation logic that checks if a record is being copied and then prevents the operation.

User Permissions: Review and adjust user permissions to limit access to certain records or fields. While this won't directly prevent copying, it can restrict what users can do with the records they have access to.

Training and Guidelines: Educate users on the importance of creating new records rather than copying existing ones. Provide clear guidelines and training to ensure they understand the process and the reasons behind it.

Audit and Monitoring: Implement auditing and monitoring to track record creation and copying activities. This can help you identify and address any instances where users are copying records inappropriately.