Hi Sebastian, 

Here are the example how you can do it:

Best Regards, 

Bogdan L

If this is a cloud system, and you don't have access to local tools, you can use the following commands via SQL Executor to get the SQL for the view.

If database is MSSQL:

SELECT
    definition
FROM
    sys.sql_modules
WHERE
    object_id = object_id('viewname');

If database is Postgresql:

select pg_get_viewdef('"viewname"', true)

Ryan

The new editor is based on the Code Mirror editor. I've outlined some of the most common shortcut keys here https://customerfx.com/article/tips-for-working-with-the-new-code-edito…

You can see the complete list of shortcut keys on the Code Mirror website in the Commands section, although not all of them are implemented in the Creatio editor (and I don't see one to comment/uncomment multiple lines although Code Mirror does have a comment addon and I've not checked if it implements this - or if the Creatio implementation includes that) https://codemirror.net/doc/manual.html#keymaps

Ryan

Thank you, Ryan. So far, I still wait for somebody from Creatio to tell if there is shortcut key for comment multiple lines, or a promise to include that feature in next release.

Van Ly,

We are using CodeMirror to write code in the designer so all shortcuts can be found here: https://defkey.com/codemirror-shortcuts

Unfortunately, comment out multiple lines shortcut is not present in the list. 

Best regards,

Angela

Hello Stefano,

Hope you're doing well.

If I understood your business task correctly, the next explanation should help you in this case:

https://community.creatio.com/questions/send-user-notification-notifica…

Best regards,

Roman

Thank you Roman for your answer.

I solved my problem using a script task with the following code inside

string processName = "process name";
string message = "bla bla";
var remindEntity = RemindingServerUtilities.GetRemindingByProcess(UserConnection, processName, message);
remindEntity.Save();

Hello Stefano,

Thank you for letting us know.

Have a nice weekend!

Best regards,

Roman

Hello Stephano,

Thank you for your question.

Please refer to this link for detailed instructions on how to perform such changes to the mini-page dropdown list:

https://community.creatio.com/questions/remove-customer-need-opportunity

Make sure to change the "LeadType" columnName to: "Contact" and the "LeadType" entitycolumnName to: "QualifiedContact" 



Hope this helps!

Danyil

Hi Danyil

I obtained what I wanted.

I added to the OpportunityMiniPage client schema the following code and all works well.

 attributes: {

            "Client": {

                    "multiLookupColumns": ["Account"]

            }

        }    

Hi,

You need to take a look at the SELECT query that is sent to the database when specifying a filter using this custom filtration by dates and see the SELECT query text. Try adding indexes (see the "Adding indexes to the object" paragraph) for the StartDate column and also for other columns that are used in the ESQ:

Also try parsing queries themeselves using SQL-server profiler and add indexes to the columns that are mentioned in the WHERE and OrderBy clauses. Indexes should help in optimizing SQL-queries (since the problem is definitely in them).

Best regards,

Oscar

Best route is likely to create a custom macro for the printable, you could pass it the DOB and it would return the age. See an example here: https://customerfx.com/article/creating-custom-macros-to-format-values-…

Ryan

Hello,

Here is an example of extending the modules:

define("UsrTestModuleV2", ["TestModuleV2"],
function() {
    Ext.define("Terrasoft.UsrTestModuleV2", {
        extend: "Terrasoft.TestModuleV2",
         
        // extend functions in TestModuleV2
     
    });
});

In the logic above the "UsrTestModuleV2" will use all the logic of "TestModuleV2" and also extended logic for "TestModuleV2" specified in the "UsrTestModuleV2". Also the parent is already added to "CenterNotificationModule" - it is done in this part of the schema definition:

 define("CenterNotificationModule", ["BaseSchemaModuleV2"]

so BaseSchemaModuleV2 is a dependency for the "CenterNotificationModule".

Best regards,

Oscar

No, I mean this parent:

The messages are inherited via metadata inheritance:

This is the error I get when I loaded the test module:

Basically, I can manual add those messages into the test module. However, if the BaseSchemaModuleV2 is updated with new messages, the error may happen again. Therefore, inheriting those metadata is the best way to make sure that the test module is forward-compatible. The CenterNotificationModule metadata exported shows that it inherited those metadata instead of redefining them. But it seems that I cannot do that from the developer console, although the built-in package already had ability to do that.

Is there any update?

Hello!

We would like to pay your attention, that unlocking and modifying the packages directly in the production environment may lead to system failure, that is why we recommend completing all changes in a package in one particular environment (for example, in the development one) to have it all tested and ready to be deployed properly in a production environment.

More detailed information on how to work with packages can be found in the Packages basics Academy article. 

Please, let us know in case any further assistance is required. 

Best regards,

Olga. 

Olga Avis,

thank you for your response.

Then the better way is export my customization as md file and import in the production environment ?

Hello Amritha,

The schema name that is to be modified is called ActionsDashboardItemContainer. Unfortunately, I was not able to find any examples of code that can change that functionality,

Best regards,

Bogdan