Add Application Service as object types that maps to BPMN Task Object

Antoon Van der Gouw

June 01, 2021 08:53

Currently we map a application component to a BPMN task, which is not always known to process consultants and/or business. In theory a (Application) Service should be connected to the above layer. 

As a work around we defined a Naming Convention to reflect a service description, which is in fact not the correct reflection of the real implementation of the Application Service.

Our request is to be able to Map the Application Service to the Task Object within BPMN.

6

• 

  Kim van Rooijen

  June 10, 2021 08:18

  Hi Antoon Van der Gouw

  Thanks for your wish. Gerard Michels can you please take a look at this one? 

  0
• 

  Gerard Michels

  June 10, 2021 09:20 Edited

  This wish will be communicated to the product owner. In our current design we indeed skip the more abstract application service layer to relate process tasks to the more concrete application components in the application layer.

  A suggestion is to find the right application to connect to a task and create the detailed relationships while doing so. The advantage is that your repository holds the required relations and objects - no workaround objects. The procedure when connecting the application layer to a task:

  Click on MyProcess and go to Relationships. If still needed, create a relationship with the application service for the task. See first screenshot. Click on the service object to navigate to the application component (possibly via relationships of the service with an application function or interface). Connect that application component to the task. See second screenshot. You may include the service name in the naming convention of the Task.  

  

  

  0
• 

  Eric Arts

  October 11, 2024 12:29

  Will it be enabled in the future in the new BPMN Editor?

  0

Please sign in to leave a comment.