Hello,

Thank you for your report.

As for now, the lookups on the mini pages could be only as a dropdown list.

We have already registered the bug for our R&D team to fix this functionality in further releases. I will assign your case to this project in order to increase its priority.

Hello, 

If you check in the section wizard you can see that mini pages are enabled for the activities, however, for the visit, it is blocked.

It's because for the visit you must fill in the visit rule option inside a module window. 

But, when you click on the "New" button you won't see a visit rule selection or mini page, that is done on purpose because the system cannot open two module windows at the time. If you want to see a rule selection, disable the mini page in the section wizard.

If you want to open a mini page then you need to set a default business rule and then try to open a mini page.

Hello,

You can customize only the favicon and the company's name in the browser tab. Detailed instruction can be found in the Add corporate logo Academy article. 

Unfortunately, there are no ways to customize tabs according to your business task at the moment. The idea to extend the possibility of browser's tab customization is already accepted by our R&D team. 

Hi,

Is this still not doable in the current version? I forced Tab name updated but it kept reverting back to "Creatio"

Hello,

Unfortunately, there is no such option at this time. We've registered it in our R&D team backlog for consideration and implementation in future application releases. It may change in future releases.

Currently, you can only change it to another product name by changing the ProductName system setting.

Thank you for helping us to improve our product.

Hello,

Please be informed that the sole fact of the schemas being a bit different is not a problem, the question is does it cause any actual issues to the performance of the site? Also, please specify if the Test env is a full copy of Dev and if so, was that schema present on the Test env before copying? Also, did you make any changes to the schemas yourself?

Kind regards,

Mira

Hi Mansoor, 

The error occurs when the page that is referenced in SysModuleEdit (the table used by Section Wizard) does not exist. (for example, it was deleted from the configuration).



Please run this query in your database: 



Delete from "SysModuleEdit" WHERE "CardSchemaUId" = '<schemaUid>'; 



where 



<schemaUId> = the Id from the error message 



Also, we generally recommend to only delete unused pages using the Section Wizard. 



Best regards,

Yurii

Hi Ricardo,

Everything is simple - these specific circumstances should be included into the logic of custom method calls inside the JavaScript code. So the logic itself should be redesigned.

Best regards,

Oscar

Oscar Dylan,

Ok, but what I am looking for is a way of disabling the handler method activation in the attribute dependency, so that when the field is updated by the code the handler method will not be triggered... The Javascript code would first disable the dependency method call, update the field, and then enable the dependency control again.

Ricardo Bigio,

One way to accomplish that is to add a property or attribute to the code where you can set a flag that the field is being updated via code, then in the event handler, check this flag to see if you should exit or continue The flag would only get set by code, so the user entering a value the flag won't be set and the event handler will trigger normally. Something like this:

suppressEvent: false,
 
funcThatSetsDependentColumn: function() {
    this.suppressEvent = true; // set flag to suppress the event
    this.set("UsrDependentColumn", value); // set the column that will trigger the event
},
 
dependentColChangeHandler: function() {
    // check if flag is set to suppress the event
    if (this.suppressEvent) {
        this.suppressEvent = false; // unset the flag and exit
        return;
    }
 
    // do other stuff in the event handler here
}

Hope this helps,

Ryan

Hello Sarika, 

Unfortunately, the pre-configured pages and the dialog boxes (modal windows) are not presented in the default configuration of the mobile application yet. 

Detailed information about the mobile application interface (as well as information on how the edit data option works there) can be found in the Get started with the mobile app UI Academy article. 

Best regards, 

Olga. 

I don't know of a declarative way to do this. You'd need this in a few parts:

1. Add some text virtual attributes to the page and then add those to the diff as readonly
2. Populate those attributes when a lookup item is selected which could be done by adding the columns to the lookupListConfig columns. You'd need to wire up a change attribute for the lookup to retrieve those values and populate the attributes.
3. onEntityInitialized you'd need to retrieve those values using an ESQ to populate the virtual attributes again.

Ryan

As a side comment, I'd love to be able to declaratively add fields like this, the system could just make them read-only if they are on a connected entity. That would be fantastic.

Hi Ryan, thanks for the reply. Yeah, I have a way to populate the fields in code, but I was just wondering if there was a declarative way to do so - as you say, it would be a great addition to Creatio and I hoped I was just missing something already there!

For anyone else searching for this, my solution slightly differed from yours in using the lookupListConfig to pull the lookup entity's additional field(s) when loading the record, which means you don't have to run an additional ESQ, which saves hits on the DB. It also uses the dependencies attribute rather than the change attribute, but that's just my personal preference as I believe they'd work the same:

    attributes: {
        "Owner": {
            lookupListConfig: {
                columns: ["JobTitle"]
            }
        },
        "OwnerJobTitle": {
            type: Terrasoft.ViewModelColumnType.VIRTUAL_COLUMN,
            dataValueType: Terrasoft.DataValueType.TEXT,
            dependencies: [
                {
                    columns: ["Owner"],
                    methodName: "setPickMapFields"
                }
            ]
        }
    },
    methods: {
        onEntityInitialized: function() {
            this.callParent(arguments);
            this.setPickMapFields();
        },
 
        setPickMapFields: function() {
            const owner = this.get("Owner");
            if(owner) {
                this.set("OwnerJobTitle", owner.JobTitle.displayValue);
            } else {
                this.set("OwnerJobTitle", null);
            }
        }
    },
    diff: [
        {
            "operation": "insert",
            "parentName": "ContactGeneralInfoBlock",
            "propertyName": "items",
            "name": "OwnerJobTitle",
            "values": {
                "bindTo": "OwnerJobTitle",
                "layout": {
                    "column": 0,
                    "row": 4,
                    "colSpan": 12
                },
                "enabled": false
            }
        }
    ]

Does the job, but it does lack the clarity that a declarative system would provide!

Harvey Adcock,

That's great Harvey, thanks for the update. I was under the impression that adding columns to the lookupListConfig would only load them on selection, great to know that those come along when the lookup data is loaded as well!

Ryan

This article will show you how to refresh a page from a process

https://customerfx.com/article/how-to-refresh-a-page-from-a-process-in-…

Ryan

Hello Ricardo,

Please also refer to this community post https://community.creatio.com/questions/refresh-page-fields-after-proce…

Best regards,

Oscar