If what you're after is the ability to navigate to the correct page, you can do that with the NetworkUtilities module. It allows you to get the hash to navigate to based on an entity object name and an Id. 

// entitySchemaName = "Account"
// entityId = An account Id
 
var hash = NetworkUtilities.getEntityUrl(entitySchemaName, entityId);
this.sandbox.publish("PushHistoryState", { "hash": hash });

If the entity has different pages based on an field, such as Type, you can also pass that like this: 

// entitySchemaName = "Case"
// entityId = A case Id
// typeValue = the Id/value of a field that determines the page, such as Type
 
var hash = NetworkUtilities.getEntityUrl(entitySchemaName, entityId, typeValue);
this.sandbox.publish("PushHistoryState", { "hash": hash });

You can determine if the entity has multiple pages, and the field used to determine which page by looking at the object attribute here (this will give you the field used to determine the page):

// entitySchemaName = "Case"
 
Terrasoft.configuration.ModuleStructure[entitySchemaName].attribute
 
// example for Landing pages (since they have multiple pages: 
var columnName = Terrasoft.configuration.ModuleStructure.GeneratedWebForm.attribute;
 
// Now columnName has the name of the field used to determine the page, in this case it is "Type"

So, the complete picture would look something like:

 

var entityName = "Account";
var entityId = "SomeAccountIdValue";
var typeValue = null;
 
// check if has multiple pages
var col = Terrasoft.configuration.ModuleStructure[entityName].attribute;
if (col) {
    // get the type value however based on your scenario
    typeValue = this.get(col);
}
 
// now get the url hash
var hash = NetworkUtilities.getEntityUrl(entityName, entityId, typeValue);
// navigate to record
this.sandbox.publish("PushHistoryState", {hash: hash});

Dear Shrikanth,

1.  It is triggered for all entity objects present in the configuration section.

2. It gets triggered by any CRUD operations performed using DataServevice (Entity and EntitySchemaQuery), OData, and OOTB business process elements. It will not get triggered if data is changed using Insert, Update, Delete classes, and if data is changed directly on the DB level.

3. It works the same as the Event subprocess https://academy.creatio.com/documents/technic-bpms/7-16/event-sub-process-element

Best regards,

Angela

Angela Reyes,

Thank you Angela for your clear responses.



I am presuming that there are no special settings to be done to enabled for them to be triggered on System objects. Hence, our errors are not the expected behavior is what I understand.

Angela Reyes,

Hi Angela. Quick follow up question - 



1. Do entity events get triggered for virtual objects & views as well? Virtual objects are also objects displayed in Configuration. So going by your explanation, It should. Can you confirm?

2. Are entity events listenable on the Client side? I do not think so. Can you confirm?

M Shrikanth,

1) I have not checked it - try to create a test process and check it. 

2) If you set up sending of an event it can be done. 

Best regards,

Angela

Arsenii Pelekh,

Hello,

 

You can find information on this subject here:

https://academy.creatio.com/docs/developer/back_end_development/objects…