Create a new message start event - Version Community

Submitted by patviaut on Tue, 12/12/2023 - 16:34
1
0
-1

Hello!

I wanted to know if in the community version you can use message start event to join 2 pools as indicated in the example. Because I am trying to join it with the Pool 1 task but it is blocked without being able to do it. I don't know if you can only do the subscription version. I attach the image that I want to make in Bonita Community
Regards

3 answers

Submitted by patviaut on Thu, 12/21/2023 - 15:39
1
0
-1

It doesn't give me an error. It doesn't allow me to join the events. I don't see the dotted line either. I am also doing it in a different way. Thank you.

Submitted by thalia.cruz on Thu, 12/21/2023 - 15:00
1
0
-1

Hi patviaut,

You can use the throw message and start message events on community edition.

I've done it on my side with a very simple sample and following the documentation: https://documentation.bonitasoft.com/bonita/latest/process/events#_messa...

Could you share the error message, please? You can get it under "Validation status" tab.

Thanks!

Comments

Submitted by patviaut on Thu, 12/21/2023 - 15:44

It doesn't give me an error. It doesn't allow me to join the events. I don't see the dotted line either. I am also doing it in a different way. Thank you

Permalink
Submitted by thalia.cruz on Thu, 12/21/2023 - 16:27

Have you configured the message on the "Throw message" event?

To configure a throw message event, select it in the diagram, go to the Details panel, General tab, Messages pane, and define the message that can be thrown. For each message, specify the following:

  1. The message name. You use this name to identify the message when you configure the message catching element, so a unique, descriptive name is best.

  2. The target pool. This identifies the target process. When you start to enter the target pool name, Bonita Studio offers a list of the pools in diagrams you currently have open. Double-click a name to select it from the list. You can also specify the name of a process that is defined in a diagram that is not currently open or that is in a different workspace.

  3. The target task. This is the name of the task or event that is listening for the message.

  4. The correlation level. If you want to use key-based correlation, specify the keys and their values. Define the value of a correlation key using the Expression Editor.

  5. The message content. The message content is a collection of id-value pairs. The simplest method is to use the relevant process variables, but you can use an expression to create message content in other formats. The Content item is the id and must be a string. The Content value must be serialized, so that it is kept in the database and persists even after a JVM restart.
    It can be contructed with a script or variable. it can also be a complex datatype as long as all its attributes are serializable. This value must not be longer than 255 characters.

Permalink

Submitted by Matayo on Tue, 12/12/2023 - 18:48
1
0
-1

When working with message flows between pools in BonitaSoft, I initially attempted to implement this in separate .proc files for each pool. However, this approach did not yield the desired outcome, as the message link between the pools was malfunctioning.

After experimentation, I discovered that incorporating both pools into a single .proc file resolved the issue. By designing the pools within the same process file, I was able to establish a working message link between them successfully. This approach seems to be more effective for managing inter-pool communications in BonitaSoft, especially when dealing with message events or signals that need to be passed between different process pools.

Based on this experience, I recommend consolidating pools that require message interaction into the same .proc file to ensure seamless message flow.

Notifications