Note that i'add this code in the task script in the process 

var userConnection = Get<UserConnection>("UserConnection");
string messageText = "Successful";

Terrasoft.Configuration.MsgChannelUtilities.PostMessageToAll("ReloadDetail", messageText);
return true;    

i got this error message 
"The type or namespace name 'MsgChannelUtilities' does not exist in the namespace 'Terrasoft.Configuration' (are you missing an assembly reference?"

"The type or namespace name 'MsgChannelUtilities' does not exist in the namespace 'Terrasoft.Configuration' (are you missing an assembly reference?" - this error message will occur in case the business process is created in the assembly package. The only workaround is to uncheck the "Assembly package" property in the package settings or move the process to the regular package.

As for the possibilities and if LiveUpdate is not an option - yes, socket nessage to the client-side and triggering the LoadDataRequest with reload enabled is the only option.

I also encountered this same error, but in my case, it was due to a dependency issue. I resolved it by adding the 'crtBase' package as a dependency in the package containing the business process.

Would the code in this article be a solution, Saving a Page Before Some Action on a Creatio Freedom UI Page | Customer FX.

Interesting idea :)

We could do with this.  I think I may have implemented this in the past by disabling the button on calling the process, and using the Send Message element at the end of the business process to publish a message that the client module is subscribed to to re-enable the button.

Hello community,

Is there any other way besides the Backend-Frontend websocket (which I havent tried yet)?

Sasori

Sasori Oshigaki,

As long as the process is not set to run in background, and you're starting the process via code, you can use the method outlined in the article below to know that the process has completed and re-enable the button without the need for messages: https://customerfx.com/article/starting-a-process-from-client-side-code-on-a-creatio-freedom-ui-page-and-getting-back-outgoing-process-parameters/

Ryan

Yes, you have to populate the condition part. You can create an always true condition as a workaround (true == true).

Fyi this is fixed in 8.2.2. Release notes mention: Streamlined business rule setup. "Dynamic filter" and "Set value" business rules no longer need conditions to work

i had to add a condition then the rules works. i added if id is filled in.

I managed to filter a contact lookup using a business rule based on the contact's account name. For another contact lookup, I need to filter the contact ID to match the page's account ID.
can this filter be implemented as a business rule ?
after several days of research, I still don't see how to perform this filter without code...
Can someone help me please ?

Check out this CustomerFX article, Using the new Multiselect Control in Creatio 8.2.1 and Higher | Customer FX.

There have been some improvements to the control in the 8.2.2 release, 8.2.2 Energy changelog | Creatio Academy.

See also, New Multi Lookup Select Component in Creatio Freedom UI Usage and Workaround | Community Creatio.

You can just retrieve them as below, which will get their current value at the time of the save. 

const val = await request.$context.AttributeName;

Alternatively you could use a change request handler, which gives you both the new and old values as properties of the request. See https://customerfx.com/article/responding-to-an-event-when-a-field-is-changed-on-a-creatio-freedom-ui-page/

Ryan

Ryan Farley writes:

You can just retrieve them as below, which will get their current value at the time of the save. 

const val = await request.$context.AttributeName;

i ' m Querying Data Using Filter Conditions via the Model Class in the save handler request . that s whey i only get the old value..

How can i use the change field event request handler in the save request handler??

If you are looking into the direct way to get changed attributes values in the SaveRecordRequest - there is none documented on our side. But you can use HandleViewModelAttributeChangeRequest where request has the oldValue and value properties, save the original values of needed attributes into the separate parameters and use these parameters in your task.

Hello,

Thank you for your request. Unfortunately, it is not possible to change this behavior using custom methods.
 

As a workaround, you can achieve this using development methods.

To achieve this you can to implement custom handlers for two requests:

1. When saving changes in the detail list (crt.SaveRecordsRequest)

First, execute the default logic for saving the detail records.

Then, trigger crt.SaveRecordRequest to ensure that the master record is also saved.
 

Be careful not to confuse the requests—crt.SaveRecordsRequest is for saving multiple records, while crt.SaveRecordRequest is for a single record.
 

2. When deleting records from the detail list (crt.HandleModelEventRequest)

Execute the default logic first.

Then, check if request.modelEvent.type === 'delete'.

If it is a delete operation, trigger crt.SaveRecordRequest to save the master record as well.

Hello,
 

At the moment, the Message Composer element is not customizable in the system. We recognize that this limitation may affect your workflow and the flexibility you need to tailor the system to your specific business requirements.
 

That being said, we want to assure you that we are actively working toward enhancing this functionality. Based on the feedback we've received from you and other users, we've increased the priority of this task.

Your experience and satisfaction with the product are very important to us. We constantly strive to make Creatio more adaptable and user-friendly, and your feedback plays a key role in guiding these improvements

Thank you for your patience and understanding.
 

It would likely work to use requests with the correct scopes set for message exchange like how sandbox worked, but I've not really tried to implement that across different pages. It might also work to just use Javascript's built-in Broadcast Channel API for that as well. It exists for purposes like this, messaging between different contexts. See details here: https://developer.mozilla.org/en-US/docs/Web/API/Broadcast_Channel_API

Ryan