Hi Community,

I encountered an error while trying to change the Default Page in an object.

 

 

Does anyone know what might be causing this issue or how to resolve it? Any insights would be greatly appreciated.

Thank you in advance!

Like 0

Like

1 comments

Hello,

The issue can occur if you have two add-ons with different names referring to the same object. This typically happens when the object was renamed, and a new add-on was generated as a result. Or if duplicate add-ons were created for the same object in one package.

I'm also adding an example of how the addon will look in the system:

 

In order to solve this problem, it is necessary:
1. Identify and Remove the Conflicting Add-On
2. After removing the conflicting add-on, regenerate and compile the system to ensure all settings are correctly applied.

This should resolve the issue and ensure consistent behavior for your Default Page settings.

Show all comments

Hello, 

Are the instructions below still apply to add a edit page to a lookup or is there an easy way to do this on Freedom UI version 8.1.1?

 

Adding lookup with edit page | Community Creatio

 

Thanks,

Jose

Like 1

Like

1 comments
Best reply

It is still the same since the Lookups area is still classic UI.

Also, BTW I have the instructions with Postgresql instructions here, if interested/needed: https://customerfx.com/article/creating-an-edit-page-for-a-lookup-in-cr…

It is still the same since the Lookups area is still classic UI.

Also, BTW I have the instructions with Postgresql instructions here, if interested/needed: https://customerfx.com/article/creating-an-edit-page-for-a-lookup-in-cr…

Show all comments

You may encounter an issue when converting a detail into a section, where the pages do not change as expected. In the wizard, it appears as if it's a section, but the actual page that opens is the details page.

The issue was caused by the feature of the architecture of interaction of schemes in the application. The object will be able to contain one Edit page or more if the page type is enabled (different pages are designed for different use cases based on the information that is filled in while creating a record). The current configuration only permits the addition of one page to both a section and a detail of an object. The described situation arose because the detail page was created before the added section. As a result of creating a section, two pages were added for the object in the system tables.

Upon opening the wizard, the system returns the first random page from the select query. This is why you may not see the correct page in the wizard.



For the solution, I recommend saving one page for the detail and for the section.

 

To achieve this, you should delete the record from the system tables and then re-save the edit page:

1) Find all edit pages for the problem object using this script:

select * from "SysModuleEdit"
where "SysModuleEntityId" in (
select "Id" from "SysModuleEntity"
where "SysEntitySchemaUId" in (
select "UId" from "SysSchema"
where "Name" = 'objec_code'));

2) Find and delete the detail edit page:

delete from "SysModuleEdit" where "Id" = 'id_detail_schema';

Before deleting, make sure to save the value from the 'SysEntitySchemaUId' column.

 

3) Delete the record in the table that connects the edit page and detail itself:

delete from "SysModuleEntity" where "Id" = 'id_SysEntitySchemaUId_step_2';

4)  Re-save the edit page using the section wizard.

 

As a result, you will be left with one edit page for detail and section.

Like 0

Like

Share

0 comments
Show all comments

You can face the issue when some changes that you made in the section wizard aren't displayed on the page.

This can occur if the package set in the 'Current Package' system setting is not the last one in the hierarchy (typically 'Custom'), and changes have been made in packages lower in the hierarchy.

The Section Wizard displays the content of all the schemas till the package is indicated in the "Current package" system setting.

However, UI displays the content and logic from all the schemas of all the packages.

To confirm this, you can change the value of the "Current package" system setting to the "Custom" package.

The "Custom" package contains all dependencies of all packages of the application. All columns are the same and are visible both on UI and in the Section wizard once it's set as the current package.

Let's consider this in the example of the package dependency schema and how it will affect the display when setting a package different from the Custom Package:

In the provided schema, the Custom package is at the bottom and contains all of the dependencies from the schemas above it. However, if a different package is specified in the Current Package system setting, then it will be higher in the hierarchy and will not include any changes from the schemas below it. As a result, these changes (fields, details, etc.) will not be displayed in the section master but will be visible in the interface.

To resolve this issue, I recommend reviewing the dependencies of packages, establishing the correct hierarchy, and adjusting the 'Current Package' system setting as needed.



You can learn about package dependencies and hierarchy in this article on the Creatio Academy: 

https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platfor…

Like 2

Like

Share

0 comments
Show all comments



I have a section called 'Requests' that has 3 multiple edit pages based on a section FIELD value. Now, the parent edit page has been disabled (it is in a 'not in use' state). How can I enable it? I need a common page that is not based on a Field value.

Like 0

Like

2 comments

Dear Sam

 

I recommend you to keep the main base page unused.

The other three pages you can make inherit from this first one getting a base page for common problems, for example, you need to add a business rule or a field and you need it in three sections, you go to the base page, create what you need there and voila, all the pages get this new field or business rule....

 

See images:

1.- Client Model schemas  https://prnt.sc/4YfSmr4FPukL

2.- How to inherit https://prnt.sc/-owYS4INpiXe

3.- https://prnt.sc/69f_gvWJjxBW

 

Regards

Julio Falcón

Julio.Falcon_Nodos,

Thanks, Julio!

Your suggestion to keep the main base page unused and have the specific pages inherit from it makes sense. I implement it using another approach.

Thanks for your reply

 

Regards, Sam

Show all comments

Hi Community,

 

I have this requirement that should allow users to revert changes of a specific record value. For example:

 

I have a specific field (Amount), that changes value when a new state is triggered (ex: Processed). It should be possible for the user to revert the value after selecting the previous state.

 

State New  -> Amount 5

State Processed -> Amount 10

State New  -> Amount 5

 

Can you please help me achieve this requirement?

 

Thanks in advance.

 

Best Regards,

Pedro Pinheiro

Like 0

Like

4 comments

Hi!

 

You can configure business rules to set a value in a specific field when a condition is met. You can find an example of how to configure it in the manual - https://academy.creatio.com/docs/user/customization_tools/ui_and_busine…

 

Regards,

Anton

Hi Anton Starikov,

 

Is it possible to use business rules if the value is dynamic? 

 

For example, when a specific requirement is met I want the field to have the previous value, which was defined by the user.

 

Thank in Advance.

 

Best Regards,

Pedro Pinheiro

Hi! Pedro Pinheiro,

 

Unfortunately, you can't do this with the standard settings. Perhaps it can be implemented by custom development.

 

Regards,

Anton

Hi

Anton Starikov,

 

Do you have any steps that could help us implement this custom logic? 

 

Thanks in Advance.

 

Best Regards,

Pedro Pinheiro

Show all comments

Hi Community,

 

I have this requirement where I need to stay on the edit page after saving a new created record. Similar to what already exists on the old UI (https://community.creatio.com/questions/how-save-and-stay-edit-page-cli…).

 

However, I couldn't find the property "IsSilent" on the new Freedom UI pages.

 

Can you please help find a solution to this requirement?

 

Thank in advance.

 

Best Regards,

Pedro Pinheiro

Like 2

Like

5 comments

Hi Pedro,

 

Our R&D team has an opened task on this topic, there is a test solution, but it cannot be applied to productions. Once the task is completed we will notify all our customers and partners in the Release Notes for the app. Thank you for helping us in making the application better! 

Hey Oleg,

 

Any update on this? Is there a way to update a field, or save a record silently without triggering other events/handlers?

 

Thank you!

Chris

Chris Heyman,

This functionality has not yet been implemented, but we have already received many requests from users, so the R&D team should take this task into development. 

Hi all,

 

Any news on this?

 

April 2023 was the original request.

 

Almost one year in.

 

Thanks

Luis Tinoco Azevedo,

You can set 

request.preventCardClose = true;

in the "crt.SaveRecordRequest" request. See my post on this thread for more details: https://community.creatio.com/questions/dont-close-page-after-saving

Ryan

Show all comments

Hi Community,

 

I have this requirement where I need to refresh the form page of my record using the refresh button of the new Freedom UI. This button was created with the help of the page designer, as you can see on the image bellow.

 

 

However, when I try to refresh the page by clicking on the created button. Creatio, instead of refreshing the current page data, it loads the data from another record.

 

Before refresh:

 

After refresh:

 

Could you please help me understand this behaviour and explain me how can be solved.

Thank you in advance.

 

Best Regards,

Pedro Pinheiro

Like 2

Like

2 comments

Seems to be an 8.0.6 bug

Hello Pedro!

 

Thank you for your post and sorry for invonvenience caused by this problem. This behaviour was removed in version 8.0.7 which is going to be released very soon.

 

 

 

 

Show all comments

Hi Team,



How to change the label of the process in the section list page and record edit page.

when a Business Process is added to the section wizard, a "Run Process" drop-down button is displayed in both the edit page and section list.

 

How to rename or change the label to a different or meaningful name pertaining to the section.?



Below are the reference screenshot where the change is required

#REQ 1: Section List page

#REQ 2:  Record Edit page

 

 

BR,

Bhoobalan Palanivelu.

Like 0

Like

3 comments

Hello Bhoobalan,

Both the edit page and the section have a localizable string called "ProsessButtonCaption" which you can change to change this caption. You need to change this in both the section and the edit page. 

If you're wanting to change this for all sections/pages, you would need to do a replacing schema for BasePageV2 and BaseDataView and modify the ProsessButtonCaption string there. However, to just change it for one section you can change it in the specific section and edit pages. 

Ryan

Ryan Farley,



Thanks for the information

Where is the diff{} for this element and what is its structure?

Bhoobalan Palanivelu,

The element is named ProcessButton. For the page it is in BasePageV2 and the section it is in BaseDataView. You’ll find it in the diff there. 

Ryan

Show all comments

Hello Creatio community,



We're trying to hide/show items in print section button based on specific conditions. The filter works fine in section page and edit page but it doesn't work when we try to open the edit page from the section page.



When we try to open the edit page from the section list the filter that we have made in both section and page doesn't apply and all the items in print button are displayed. Examples below.

 

1. Print button in section list

2. Print button when we open edit page (from reload)

3. Print button when edit page is open from application section list

 

Application page:

        preparePrintFormsMenuCollection: function (printForms) {
                this.callParent(arguments);
                printForms.eachKey(function (key, item) {
                    if(key =="ebd9e198-9d05-21b7-6d30-4f79eb6cf2ea")
                    {
                        item.set("Visible", true);
                    }
                    else{
                        item.set("Visible", false);
                    }
                }, this);
            },

Application section:

            isSectionPrintFormEnabled: function(reportId) {
                if (!this.isAnySelected()) {
                    return false;
                }
                if (this.isSingleSelected() && !this.get("SelectAllMode")) {
                    var applicationId = this.$ActiveRow;
                    if(reportId == "ebd9e198-9d05-21b7-6d30-4f79eb6cf2ea"){
                        return true;
                    }
                    return false;
                } else {
                    const reportCollection = this.get(this.moduleSectionPrintFormsCollectionName);
                    const report = reportCollection.get(reportId);
                    return (report && report.get("PrintFormType") !== Terrasoft.ConfigurationEnums.ReportType.Word) || !this.get("SelectAllMode");
                }
            }, 

The function "preparePrintFormsMenuCollection" is called every time the application page is opened. When the application page is opened from the section list (combined mode) the print button is not reloaded and keeps the older values.



How can we reload the items of the print button when the edit page is opened from section page?



Regards,

Lirzae

Like 0

Like

3 comments

Hello Lirzae,

You could try the following. When a row is selected in the section, retrieve the collections of printables for the section, then look through and set the Visible property based on the values of the selected row. Something like this: 

rowSelected: function(primaryColumnValue) {
    this.callParent(arguments);
 
    // get data for selected row
    var row = this.getGridData().get(primaryColumnValue)
 
    // get printables collection
    var reportCollection = this.get(this.moduleSectionPrintFormsCollectionName);
    Terrasoft.each(reportCollection, function(report) {
            if (row.get("UsrSomeField") == "Some Value" && report.get("Id") == "TheReportId") {
                report.set("Visible", false);
            }
            else {
                report.set("Visible", true);
            }
    }, this);
}

Note, I've not tried that before so not sure if it will work, but that is what I would attempt first. Also, the fields available in the "row" variable would depend on the column layout of the section. If you need to ensure a value is available, you'll want to add that to the section ESQ like this: 

initQueryColumns: function(esq) {
    this.callParent(arguments);
 
    if (!esq.columns.contains("UsrSomeField")) {
        esq.addColumn("UsrSomeField");
    }
}

Ryan

Ryan Farley,

 

I tried using "rowselected" method but this only works in section list page. When I try to open the edit page from section list the print button shows all the items.

The other method that I used "preparePrintFormsMenuCollection" is called when the edit page is opened but doesn't reload the print button items. 

 

Is there any other method that can reload print button items when the edit page is opened from the section list?

put the same code i mean the Follwoing code in section page as well and it will works fine

  preparePrintFormsMenuCollection: function (printForms) {
               this.callParent(arguments);
               printForms.eachKey(function (key, item) {
                   if(key =="ebd9e198-9d05-21b7-6d30-4f79eb6cf2ea")
                   {
                       item.set("Visible", true);
                   }
                   else{
                       item.set("Visible", false);
                   }
               }, this);
           },

Show all comments