Hello!

Please note that such logic can be implemented only by creating a business process. 

Best regards,

Mariia

Hi Team,

With our current process taking days to run, the system is overloaded. We need a faster solution. Can you propose an alternative approach?

Hello!

Could you please clarify how you imagine this being implemented? Do we need to restrict access rights to the entire record or just to specific fields, since the values of the fields can be hidden at the client logic level?

Hello,

Please note that this can be setup with the help of business rules, you can find the detailed instructions in this Academy article:
https://academy.creatio.com/docs/8.x/no-code-customization/customization-tools/ui-and-business-logic-customization/freedom-ui-business-rules

You can set it up either for the detail element or for the object itself, you can try the latter to achieve your business goal.

Hello,

Double-check that all elements involved are in the same package you're exporting. Missing elements might be in separate packages.

Review which page the problematic element belongs to and verify its referenced components are also included and accessible.

Review the Addon metadata to ensure the problematic element is correctly defined and linked to the appropriate page.

Examine the addon metadata to confirm the problematic element's existence and its proper association with the relevant page.

This works different for a chart since each series has it's own data and you can connect each series to the page data differently. You have to first define the series. Once you add a series, the name of the series will appear there and then you can click it to connect to page data. 

Ryan

Ryan Farley,

Thank you very much!

it works!

Hello,
Terrasoft.Configuration.Tests.csproj is just an example of how the project can be named. The needed csproj file should be located at this path \Terrasoft.WebApp\Terrasoft.Configuration\Pkg\{your package}\Files

Something Creatio miss to configure when add this feature. You must go to Object Permissions, search for "SysUserProfile" and add the permission there, search "Number Format" and add users

Thank you Julio, it worked.

Hello,

As the first step, we recommend you to check our Academy article on Script Task process element that includes both instructions and examples of working with it. You can also use Academy and Community for searching examples of implementation of some more specific requests using the key words.

https://academy.creatio.com/docs/8.x/no-code-customization/bpm-tools/pr…

Hello Mira,

Thank you for your reply. I have reviewed the Academy article on the Script Task Process element. Also, executed on Creatio platform.

I am now interested in learning more about what we can accomplish with the Script Task element. Is there any additional information or examples available for Script element? 

regards, 

Ajay

Hi Lucas,

1/ Regarding your filter, here are a few remarks:

1. 
   1.1 You need to use the OR operator in the root filter not ADND, so that the condition is: 
   
   3 years (1095 days) 
   OR 
   5 years (1825 days).
2.  

1.2 Currently, you are checking customers whose Contract Date field is within the range of the last 1095 days or 1825 days, meaning from today to 3/5 years back.
 

You need this to be a filter for Contract Date > the previous 1095 days.

3. 
   1.3 As I understand it, the task is to ensure the email is sent only once when users reach the 3/5 year mark. Instead of sending the email repeatedly, I recommend adding a field, such as a checkbox labeled "Anniversary Emails sent", and set this checkbox during the same process. 
   
   Then, add a condition to the business process trigger:

Anniversary Emails sent != true.

1.4  We recommend running the process on a timer rather than a signal, once a day at a specific hour. 

This way, the process will check all records where the Contract Date exceeds 3/5 years and send the email to those who haven't received it yet, doing this every day.
 

2. Overall, it's important to understand that such a filter won't account for leap years. Another possible solution:
 

1. 2.1 Add a column "Send anniversary email date" and populate this column using a process with a formula element where Contract Date.AddYears(3).
    

Then add a condition to the timer: "Send anniversary email date" = Today, and the process will send emails to all users whose "Send anniversary email date" is today.

Hello Satyam,

Could you please clarify how exactly you implemented the 'decimal number' in the label?

When you set the number in the attribute bound to the label you can use toLocaleString:

request.$context.MyAttribute = num.toLocaleString();

Ryan

.

Hello ,

Thanks for the response.
 

The below given code is how we are currently setting the value of the UsrAmount decimal field to be shown as a label caption.

{
                "operation": "insert",
                "name": "Label_td5mlo3",
                "values": {
                    "layoutConfig": {
                        "column": 1,
                        "row": 2,
                        "colSpan": 1,
                        "rowSpan": 1
                    },
                    "type": "crt.Label",
                    "caption": "$PDS_UsrAmount_7hu2ut1",
                    "labelType": "headline-1",
                    "labelThickness": "bold",
                    "labelEllipsis": false,
                    "labelColor": "#181818",
                    "labelBackgroundColor": "transparent",
                    "labelTextAlign": "center",
                    "visible": true
                },
                "parentName": "GridContainer_rpq3gxq",
                "propertyName": "items",
                "index": 1
            }

As a result, it picks the value from the decimal field and shows in the label as shown in the screenshot below:

I want to show the Label caption in the same format as that of the amount field. Also another thing that we have noticed is that when the amount is 1,000.00 , the caption shows 1000 instead of 1000.00. 

kindly help

Hello,

Unfortunately, there is no such option at the moment. 

However, we understand that this is not ideal for your specific needs.

We want to assure you that we have created a request for our development team to implement this functionality in future versions of our application. We understand the importance of providing our clients with the best possible experience and will work hard to implement the changes you have suggested.

Thank you again for bringing this to our attention, and please do not hesitate to reach out if you have any further questions or concerns.
However, we understand that this is not ideal for your specific needs.

 

Halyna Parkhomenko writes:

Hello,

Unfortunately, there is no such option at the moment. 

However, we understand that this is not ideal for your specific needs.

We want to assure you that we have created a request for our development team to implement this functionality in future versions of our application. We understand the importance of providing our clients with the best possible experience and will work hard to implement the changes you have suggested.

Thank you again for bringing this to our attention, and please do not hesitate to reach out if you have any further questions or concerns.
However, we understand that this is not ideal for your specific needs.

 

Thanks for the info! Is there an ETA on when the feature might be available? Also something like "not in the next x versions" would already be of help!

Thanks,

Robert

Robert Pordes,

Unfortunately, there is no ETA at the moment, but we have increased the priority of this implementation with your case.

Have a great day!

Best,

Alina