Hello Petrika,

Could you please elaborate more about your business task?

Thank you,

Artem.

Dear Pratik,

Please note that our application doesn't support designing business processes that are triggered by a modification in system objects. The core of business process mechanisms works on low-level API which doesn't support start signal's functionality. This is done in order to avoid any kind of accidents with business process mechanisms and also for performance maintaining reasons.

However, you can try designing a process that runs, for example, every day and checks Process log records for errors, and then sends this information to a specific mailbox.

Kind regards,

Mira

Hi Pratik,

I had a similar issue, and that's the solution I came up with: 

My process is scheduled to run every 4 hours and the read data searches for process marked with the "Error" status, which name starts with a custom prefix (that I assigned to identify my processes). The subprocess is used to log the error in another custom section.

Hope it helps! 

Hi Mira and Federica Cattani,



Thanks for the help and explanation. 

Hi Julien,

Could you change your schema definition as the following (swap "MultiChoiceMixin" and "ProcessModuleUtilities")?

define("MTF_Candidat1Page", ["ProcessModuleUtilities", "MultiChoiceMixin"], function(ProcessModuleUtilities) 

regards,

Cheng Gong

Cheng Gong,

 It works, thank you !

Hi Pratik, 



This is the know issue of the version. 

Our R&D team is working on this to be fixed in the future releases. 

There's a workaround to this issue. To implement it please create following request to support team (since your instance is cloud) :

1) set "false" to following keys in  Terrasoft.WebApp\web.config 

<add key="Feature-UseSeparatedOdataEntitiesDll" value="false" />

<add key="Feature-ODataEntitiesCompilationInSeparatedDll" value="false" />

if such keys don't exist, they can be added to  the block <appSettings>;

2) Generate source code for all schemas and compile all. 





Please note, that this fix is only applicable for 7.18.1. Please remove this tags from web.config when updating to newer versions of the application, as it will cause the Odata functionality to not work. 



You can also refer to this community post in your support request. 

Best regards,

Yurii

 

Hi Yurii,

It Worked, Thanks for the help. 

Hi. 

This solution is for version 7.18.1 only.

Hi,

I have the same issue as Patrik, but I am using version 8.1.2.3942. Could you please suggest a solution? 

P.S. This logic worked for me before the upgrade.

Aurora Leka,

Hello!

If you are expecting such an issue using version using version 8.1.2.3942. Please take the next steps:

1. 1. Ensure that the update was successful (double-check Update extended logs).
2. 2. Run full schema generation and compilation process.

If those recommendations do not help you to solve the issue please contact support@creatio.com with information about this issue.

The issue is that the process will execute asynchronously. The only way to get the value back from the process is, instead of using it as an output param, to send it as a message using a script task in the process that you will retrieve with client-side code on the page. 

You can see an article outlining how to do this here: https://customerfx.com/article/sending-a-message-from-server-side-c-to-…

Basically, at the end of your process, you'll add a script task. In that script task you'll get the param value, then send it as a message (as outlined in the article). Then, in your page code, you'll listen for that message, check to make sure it's the message sent from your process, and then read the value and do whatever is needed with it.

Ryan

Dear Pedro,

This business task can be implemented in several ways depending on the conditions of the task. You can either create a process that will be triggered on record modification or record adding and check if the record has a tag in with date like current date (since import creates a tag with the date and time) and change fields or you can read process log - if import process was started wait for some period of time and update all records with tag.

Best regards,

Angela

 

Angela Reyes,

I have tried to update my page using a process like you said but I'm facing the same issue. The process is not able to know whitch record page it needs to update. If I try to search by record modification or record adding it will generate problems in the future because it is possible for more than one user to import excel at the same time and each file imported has a lot of products.

Best regards,

Pedro Pinheiro

Pedro Pinheiro,

The easiest solution will be to import data using web-service instead of Import tool. The import process will never tell what data was imported - import tag is the only track that could show that records were imported. Import log contains more detailed information but it also does not contain information about import end.

Best regards,

Angela

Dear Janine, 

To do this you need to create a replacing schema for FileDetailV2 and override method deleteRecords, starting process inside this method. To start process from the js code you can try the article below: 

https://customerfx.com/article/programmatically-starting-a-process-from-client-code-in-bpmonline/

Best regards,

Dennis 

Hi Luciano, 

Please advise if you created your UsrIncomingEntity business process beforehand and if you added the usrNewInsertedEntityId parameter into it. Make sure you do that first.

If you did it, kindly provide us with the whole code so that we could have a look into it and advise on possible errors.

Thanks

Hello Luciano,



Basically, the code should work in appropriate way. As S.Kobizka said, you should check that business process with code "UsrIncomingEntity" exists and has  "usrNewInsertedEntityId" parameter. 

Also, I recommend try to choose "compile all" option in configuration, it may help because source code will be regenerated.



If you will have further difficulties, please, send the entire code of webservice and screenshots of the businessprocess.



Regards,

Alex

Alex_Tim,

Hi,

Thank you both for the answer, the BP exists prior to the webservice as well as the parameter. If i debug the code both the bp and the parameter are available to inspect. As soon as the line:

process.SetPropertyValue("UsrNewInsertedEntityId", msgId);

is executed i get the error.

I'll try the compile all option and then retest to  see if that helps.

Thanks

Luciano De Munno,

 

It seems that the reason of the issue is that msgId variable and UsrNewInsertedEntityId parameter in business process have different types. Please make sure that msgId is Guid and UsrNewInsertedEntityId is unique identifier http://prntscr.com/n0yt77



Regards,

Alex

Alex_Tim,

Hi Alex,

Thank you for the answer, i checked and msgId is a Guid and the parameter UsrNewInsertedEntityId has the type "Unique Identifier". AS far as i know that's the correct type i can try chaning both the string and text and then converting to guid inside the process to see if that helps.

Same thing, now i'm sending a string and expecting a string but the error is the same. 

Hello Luciano,



Here is the example of how to start business process with parameter from server side code.

If you will have further difficulties, please contact support team support@bpmonline.com





using Terrasoft.Core;

using Terrasoft.Core.Process;

using Terrasoft.Core.Process.Configuration;

 

ProcessSchema schema = UserConnection.ProcessSchemaManager.GetInstanceByName("LeadManagement");

//schema = UserConnection.ProcessSchemaManager.GetInstanceByUId(leadManagementProcessUId);

 

//different engines for interpretable and compiled BP

bool canUseFlowEngine = ProcessSchemaManager.GetCanUseFlowEngine(UserConnection, schema);

if(canUseFlowEngine) {

    var flowEngine = new FlowEngine(UserConnection);

    var param = new Dictionary<string, string>();

    param["LeadId"] = Entity.Id.ToString();

    flowEngine.RunProcess(schema, param);

} else {

    Process process = schema.CreateProcess(UserConnection);

    process.SetPropertyValue("LeadId", Entity.Id);

    process.Execute(UserConnection);

}        

Hi Alex,

The FlowEngine part did the trick. Thank you so much

This is solved

In order to trigger business process in Client Code, take the following actions: 1. Connect ProcessModuleUtilities module to a module of the page, from which the business process will be called.

2. Call executeProcess(args) method from ProcessModuleUtilities module by 

transferring args object with such properties.

Example

define("AccountPageV2", ["ProcessModuleUtilities"], function(ProcessModuleUtilities) {
    return {
        entitySchemaName: "Account",
        methods: {
            // Проверяет, заполнено ли поле [Основной контакт] страницы.
            isAccountPrimaryContactSet: function() {
                return this.get("PrimaryContact") ? true : false;
            },
            // Переопределение базового виртуального метода, возвращающего коллекцию действий страницы редактирования.
            getActions: function() {
                var actionMenuItems = this.callParent(arguments);
                actionMenuItems.addItem(this.getActionsMenuItem({
                    Type: "Terrasoft.MenuSeparator",
                    Caption: ""
                }));
                actionMenuItems.addItem(this.getActionsMenuItem({
                    "Caption": { bindTo: "Resources.Strings.CallProcessCaption" },
                    "Tag": "callCustomProcess"                
                }));
                return actionMenuItems;
            },
            // call you porcess
            callCustomProcess: function() {
                var contactParameter = this.get("PrimaryContact");
                var args = {
                    // Process name
                    sysProcessName: "UsrCustomProcess",
                    // parameters process
                    parameters: {
                        ProcessSchemaContactParameter: contactParameter.value
                    }
                };
                // run process
                ProcessModuleUtilities.executeProcess(args);
            }
        }
    };
});