Hello,

I have confirmed that this functionality is working correctly in the latest out of the box version of Creatio. 

Below, you will find an example of how this type of business rule should be configured.



I verified this in Creatio version 8.3.2 (web) and version 8.3.7 of the mobile application. Please ensure that your mobile app is updated to the latest version.

If you continue to experience problems, please contact the Creatio Support team directly so your site configuration can by reviewed. Don't forget to provide the steps to reproduce the issue.

I trust this helps.

Best regards,
 

Hello,

At the moment, the only officially supported way to connect Creatio to Power BI is via the Marketplace connector, which has limitations. Unfortunately, Creatio does not offer alternative OOTB solutions for connection. 

I had that issue twice: a) the column was added on the list by code and then removed (renamed) from the configuration. b) on the list in the designer was added subordinate column...

The thing is this happens when you add a new list for Agent desktop queue element. No previous configuration at all. I even tried this on demo environment and it is the same. This seems to be an issue with ootb functionality but maybe there is a known fix?

Greetings,

This type of issue usually occurs when columns configured in the user’s runtime settings are no longer available in the system. It appears that the columns previously configured for this user may have been deleted, which is why they can no longer be displayed.

In this case, we recommend either resetting the column configuration to the default settings or removing the affected columns and adding the required ones again.

If the issue still persists,  please feel free to contact us at support@creatio.com, and we will be happy to assist further.

First of all, how are you loading the orders/invoices? It should be creating these numbers unless you're going directly to the database (or the numbers are being created using the older method on the client-side page only).

I assume that somewhere you're setting the nextValue in the Number field and that just isn't showing in the code?

Ryan Farley,

We are currently performing a direct SQL insert using the following code:

Guid newRecordId = Guid.NewGuid();
var insertQuery = new Insert(userConnection).Into(objectName).Set("Id", Column.Parameter(newRecordId));

foreach (var property in objectData.Properties())
{
    string propertyName = property.Name;
    string propertyValue = property.Value.ToString();
    insertQuery.Set(propertyName, Column.Parameter(propertyValue));
}
int affectedRows = insertQuery.Execute();

However, in the online environment, the order number is not incrementing as expected. Instead, all orders are being created with the same number (ORD-0).

Hello,
Perhaps the issue with the trial might be that it uses a PostgreSQL DB that is not compatible with your SQL script.

Chetana Gharat,

Dmytro is likely correct. If the system is Postgresql (if it's a cloud hosted Creatio, it likely is), then you need to generate the next ordinal number using the Postgres way, see here: https://customerfx.com/article/resetting-the-value-of-autonumber-fields-in-creatio/

For example: 

SELECT nextval('ed398640-de69-842b-c50c-6c673da5aa98')

That would explain why it's working in your local environment and not in the cloud, assuming that is MSSQL.

Ryan

Hello,

The easiest and most reliable way to implement this is by using the Send Email element in the business process.

You can configure it as follows:

1. "From" Field:

Add the Send Email element to your business process.

In the element setup, locate the From parameter.

Select a mailbox that is configured in the Mailbox synchronization settings,
or map this field to a process parameter that contains the mailbox information (this parameter should reference the Mailbox synchronization settings lookup).

2. "To" Field:

In the same Send Email element, locate the To parameter.

Map this field to a process parameter of type Contact or Account. In this case, the system will automatically use the primary email address specified in the Communication options of that Contact or Account.

Alternatively, you can manually specify the target email address or map the field to a parameter that contains the required email value.

Additionally, you can select the required email template within the Send Email element.

Anastasiia Zhmud,

Thanks Anastasiia - Just to clarify, we need to give a button on the UI for sending emails manually to the user. I want the email mini page to open with autofilled To and From. The user can then put subject and email body and send manually. To and From parameters are not visible on the email mini page. Am I missing anything here?

Puneet Mehta,

You can use "Send email" process task. Smth like this:

and this is the result:

So you have both filled email address and link to the contact

Dmitry S,

This was helpful - thank you

Hello Puneet Mehta,

You can check whether the changes were applied to Lookup 1 in the crt.HandleViewModelAttributeChangeRequest handler and trigger your crt.LoadDataRequest from there using sdk.HandlerChainService to filter your multiselect lookup

Hello,
Currently, there are some issues with the default tab logic, and our R&D team is working on a global solution for it. As for now, the recommended approach is the following:
The current mechanism relies on saving the selected tab through the page configuration (viewConfig), which may lead to conflicts and incorrect behavior.
To ensure stable operation, the default tab must be controlled at the ViewModel level.
As a workaround for now, you can apply the following steps:
- Use the SelectedTabIndex property instead of SelectedTab. 

- Store the tab index in a dedicated ViewModel attribute.

- Disable saving the selected tab in the profile to prevent conflicts. (DisableSaveToProfileSelectedTabIndex)

Dmytro Vovchenko,

Thanks for the guidance, that clarifies the ViewModel‑side approach a lot.

Quick follow‑up: could you also please point me to the correct way to unsubscribe from request.$context.events$ in Freedom UI (8.3.2)?

Right now I’m doing something like this inside crt.HandleViewModelInitRequest:

{ 
  request: "crt.HandleViewModelInitRequest",
  handler: async (request, next) => {
    await next?.handle(request);
 
    const sub = request.$context.events$.subscribe(async (evt) => {
      const modelMode = await request.$context.getPrimaryModelMode();
 
      if (evt?.type === "finish-load-model-attributes") {
        if (modelMode === "update" || modelMode === "create") {
          request.$context.Tabs_SelectedTabIndex_Profile = 0;
 
          // I want this to run only once, then stop listening
          sub.unsubscribe?.();
        }
      }
    });
  }
}

Any small code snippet or hint for 8.3.x specifically would be really helpful.

Hi Vladimir. The best way to solve this case without coding (using esq or smth) is to do the following:

1. In Account schema add a column with no use in UI - UsrCodeLower.
2. Create some event-based process to fill this value in case of saved new Account record with Code filled or changed Code field in existing account with the following parameter [#Read account.First record in the resulting collection.Code#].ToLower() then modify Account's UsrCodeLower with it's value:

3. Add to your process for looking for an account by code (this one on the screen) some parameter for "lowered" code value: UsrDistributionNumberLower = UsrDistributionNumber.ToLower(). 

4. In the Read data element replace Code with UsrCodeLower and the parameter to UsrDistributionNumberLower. 

As both values will be in lower case, this should do.

I had that happening on after an upgrade to 8.3.2. It is caused by an issue with a new feature called DisableGenerateViewModuleScriptOptimization, which by default id disabled. You can resolve the issue by enabling that feature. 

The DisableGenerateViewModuleScriptOptimization feature is new in 8.3.2 and is a new feature meant to optimize page opening/reopening. With the feature enabled, the site is no longer using the optimization. The issue is resolved in 8.3.3, so for now, enable the feature, but when 8.3.3 comes out you'll want to disable the feature again so you can use the page optimizations.

This information is from support, my case was SR-01476352 if you end up discussing with support.

Ryan

Ryan Farley,

Thanks for the prompt response, Ryan! I don't see this feature in feature list. Where can I enable this feature?

Puneet Mehta,

This is all for 8.3.2, just FYI, so wanted that to be clear. Also, I don't believe the feature is added in 8.3.2 (although the capabilities are there), so you can just add it, then enable it. 

Don't forget to disable it once your system is upgraded to 8.3.3.

Hi, Sergejs. You should do it as following:

{
	request: "crt.HandleViewModelResumeRequest",
	handler: async (request, next) => {
		await next?.handle(request);
		setTimeout(() => {
			request.$context.Param1 = someValue1;
			request.$context.Param2 = someValue2;
		}, 300);	
	}
}

Dmitry S,

Can you please clarify what is someValue1 and someValue2 in your example? As far as I can understand, you are setting attribute value inside same page in the HandleViewModelResumeRequest.

My scenario is slightly different, I am trying to pass the attribute value from another page. So for instance - I have a button on a page1, this button has a custom click handler, where I call CreateRecordRequest with some parameters. In result page2 opens and I want to set it attribute with the value from the parameter i passed in CreateRecordRequest. I hoped it works automatically, but it's not. I tryed your HandleViewModelResumeRequest code with little modification, but attribute value still is null for me.

			{
				request: "crt.HandleViewModelResumeRequest",
				handler: async (request, next) => {
					await next?.handle(request);
					setTimeout(() => {
						const a = request.$context.SomeAttribute; //a is null here
					}, 300);
				}
			},

Sergejs Sokolovs,

You are sending something from parent page to child page ok. So in data model of the created child page you have them, yes? And page is opened.

So, you can get them on the created page as 

const attribute = await request.$context.UsrAttributeName; 

or the problem occurs when you're trying to fill smth virtual? Which exists on the page, but not present in the entity itself? if so, I'll check this tomorrow.

BTW. 

as a workaround you can do the following:

1. You can create some process like this one with open preconfigured page element. You can configure some process parameters, which will receive data you want to display. You can link these process parameters to the desired page. On the page are all of those parameters accessible.

2. Instead of using record handlers you can run this process from some custom handler on the page somehow like this (also not forget to define ProcessModuleUtilities). Process should open page with all required fields filled. 

["@creatio-devkit/common", "ProcessModuleUtilities"], function (sdk, ProcessModuleUtilities)

You can use something similar from FD sdk indeed, this example was taken from FD page, but it uses CI logic.

const printableId = reportTemplate.value;
const args = {
	sysProcessName: "UsrGenerateContractByTemplate",
	parameters: {
		ContractId: contractId,
		PrintableId: printableId
	}
};
ProcessModuleUtilities.executeProcess(args); 

As a workaround approach, I've been using BroadcastChannel API to pass other attribute (non-model) values to the opened page. See the comment in this thread from Edward https://community.creatio.com/questions/open-custom-freedom-ui-page-custom-button-opportunity-edit-page-and-pass-opportunity

Ryan

Ryan Farley,

Yeah, already started to think about that solution, but hoped there is more native one. It's little bit frustrating, that params are not supported, but it's great that we have a workaround. Thanks!

Yes, the current way to implement the desired logic is to use a workeround, more on it here https://community.creatio.com/articles/passing-data-between-freedom-ui-pages-creatio.
As for a more native approach, it is still in development.