Hi Kevin, you need to disable the Feature called UseSchemaDesignPackageUIdByHierarchy. In yor instance must add this "/0/Shell/#Section/AppFeature_ListPage" after cretio.com to open the Features Page, search the feature, disable (turning off the “Is enabled” and “Is enabled for current user”), save and click on  button "Clear Cache".

Regards

Julio Falcón

Julio.Falcon_Nodos,

Are there any caveats to doing this Julio?

Gareth Osler,

This basically just reverts the behavior to use the "Current Package" system setting, even for all Freedom UI stuff. I have more info on that here: https://customerfx.com/article/reverting-the-behavior-for-saving-pages-in-the-creatio-freedom-ui-designer-to-use-current-package-setting/

Ryan

Hello!

The new package is creating if changes have been made to the application, but its main package is locked.

When developing an application, you can force the application not to create a new empty package, but to save changes to the package you created.
This can be done by disabling the UseSchemaDesignPackageUIdByHierarchy system feature - it is responsible for the logic of checking and creating a new package for the application, as well as the CurrentPackageId system setting and the Installed application and Package lookups. 

Now you will need to specify the package (recommended Custom) in the CurrentPackageId setting.

Hello,

Generating source code for all schemes and fully compiling the system usually helps to resolve this error. In this case, the OData entity will be rebuilt and you should not get this error. So your actions:
1. Generate the source code for all schemas


2.  Perform a full compilation of the site

If this does not help you solve the issue, please create a separate ticket for the Creatio support team.
 

Thank you.

Greetings,
 

Could you please tell me what you mean by "why my object is not saved"? 

Hi,

1. Define a new functional role.
  
2. Assign specific users to the functional role (Users tab).
  
3. Users can be assigned to the functional role, replacing existing administrator and employee roles.
  
4. Create one new workplace setup and add the section and user groups  

Hello,

You need to create a new user workplace with the type "Limited internal."  

Then, add the desired section to this workplace. 

After that, create a specific role where you will add users with this type of license.

Finally, add this role to the "User groups" detail.


You can get more information by watching this part of the instruction video.

Bala Koteswarareddy,

Thank you!  This worked perfectly.  I made a new Limited Internal workplace and gave access to a new functional role which I'm assigning the Limited internal users to.

Antonii Viazovskyi, Thank you!  This worked perfectly.  I made a new Limited Internal workplace and gave access to a new functional role which I'm assigning the Limited internal users to.

Hello Jelenko,
To implement your logic you can do the following:
1) Create replacing view model for CtiPanel object.
2)  Implement CtiPanel  
define("CtiPanel", [],
    function() {
        return {
            attributes: {},
            methods: {
                answerCallCustom: function() {

                    // your logic here

                    // get call id from your cti provider to pass to business process
                    var args = {
                        sysProcessName: "customProcess",
                        parameters: {
                            callId: callId
                        }
                    };
                    ProcessModuleUtilities.executeProcess(args);
                }
            },
            diff: [
                {
                    "operation": "merge",
                    "name": "AnswerButton",
                    "parentName": "ButtonsPanel",
                    "propertyName": "items",
                    "values": {
                        "click": {"bindTo": "answerCallCustom"}
                    }
                },
            ]
        };
    }
);

3) Create business process with callId parameter that opens the page you need
Hope this helps

Yevhenii Grytsiuk,

Thank you Yevhenii,

after your suggestion to use business process and start it from client side, I changed my implementation approach and managed to do it with following trigger, which starts business process when call is picked up:

Maybe someone finds it useful for future reference.

Thanks.

Hello,
The reason lies in the type (UsageType) of the RecordInactive= "Advanced" column, which is why the system does not display it in the designer. Unfortunately, there is no way to change this column type.

However, there is a workaround that will allow you to use the feature, namely the "DisableBlockingSystemColumns" feature that needs to be created and enabled for users that you need to have the rights to use such system fields.
1. Go to the link: https://SITENAME.creatio.com/0/Features
2. Add a new parameter:

3. Create a new parameter called "DisableBlockingSystemColumns", then add the role that well have the access to it, enable the checkbox and save the changes:

4. Relogin to the site.

However, this will allow users who have this option enabled to see other restricted and system columns in the system. We recommend using this approach in the "extreme" case, if the work of this functionality is critically important.

In addition, we have already created a task for our development team to fix this issue. Unfortunately, we have no exact ETA at the moment, since the task is at the initial stage, but it may be included into one of the next releases.

Hello,

To be able to see these emails, you need to enable logging in the advanced settings in the Email Sending process element. 
After that, you can find the emails in the Activity table or set up a dashboard to view them.

Good day,


In the .NET Core version, we do not have separate settings for different services; instead, we have a single setting for the entire application. The default value is 30,000,000. You can modify this setting by adding a new row to the <appSettings> section in the Terrasoft.WebHost.dll.config file:

<add key="MaxRequestBodySizeBytes" value="100000000" />

This will change the maximum request body size to 100,000,000 bytes.

Thank you for reaching out!

Instead of adding the lookup column to the grid layout, expand that to get the display value to add to the grid instead. For example, instead of adding "Account", click the plus button then select Account, the choose the Name column to add to the grid, then it won't be clickable.

Ryan

Ryan Farley, thank you for your answer.

In the grid, the button + must be active to allow users to add necessary columns. Therefore, I need to display the main account on the grid without a link.

Hi!

You can make this detail editable. In this mode, all columns in the detail won't be clickable.

More details about editable details here:

https://academy.creatio.com/docs/8.x/no-code-customization/8.0/customization-tools/ui-and-business-logic-customization/page-layout/create-new-detail

Best regards,

Kate

Kate Karpik,

Hi Kate Karpik,

I need to do this in Freedom UI. Are there any features in Freedom UI for datatables similar to the showValueAsLink feature available for fields on a page?

Ryan Farley,

Thanks Ryan, and in case the column isn't a lookup, I mean the default Name column always was clickable, but I need in some cases not be clickable, is it possible (Freedom UI)

Thank in advance

Julio

Lia,

I'm curious as to have did you approach this? I have plans on doing something like this as well.

Hello,

While DCM lacks a direct feature to check another object's values and restrict access based on that data, a simple no-code workaround can be implemented. Add a subprocess as the initial step in the DCM stages. This subprocess will check the related contract status, and if it's not 'Active,' it will notify the user and revert the stage to the previous one.

Alternatively, you can create a button that allows the user to select the desired stage. The system will then verify if the record can be transferred to the selected stage.

Kalymbet Anastasia,

Thank you for your input. Appreciated.