此内容没有您所选择的语言版本。

Chapter 5. Designing the case definition


You design cases using the process designer in Business Central. Case design is the basis of case management and sets the specific goals and tasks for each case. The case flow can be modified dynamically during run time by adding dynamic tasks or processes. In this procedure, you will create this same case definition to familiarize yourself with the case definition design process.

The IT_Orders sample project in Business Central includes the following orderhardware business process case definition.

Figure 5.1. orderhardware business process case definition

Prerequisites

Procedure

  1. In Business Central, go to Menu Design Projects and click IT_Orders_New.
  2. Click Add Asset Case Definition (legacy).
  3. In the Create new Case definition window, add the following required information:

    • Case definition (legacy): Input orderhardware. This is usually the subject of the case or project that is being case managed.
    • Package: Select com.myspace.it_orders_new to specify the location that the case file is created in.
  4. Click Ok to open the process designer.
  5. Define process-level and case-level variables.

    1. Click BUSINESS PROCESSES (LEGACY) orderhardware.
    2. Click left arrows on the right side of the designer to open the Properties (BPMN-Diagram) panel.
    3. Click the down arrow in the Variable Definitions field to open the Editor for Variable Definitions.
    4. Click Add Variable, and input the following values and click Ok:

      Figure 5.2. IT Orders variables

  6. Define the roles involved in the case.

    1. Click the down arrow in the Case Roles field to open the Editor for Case Roles.
    2. Click Add Case Role, and input the following values and click Ok:

      Figure 5.3. ITOrders Case Roles

      • owner: The employee who is making the hardware order request. The role cardinality is set to 1, which means that only one person or group can be assigned to this role.
      • manager: The employee’s manager; the person who will approve or deny the requested hardware. The role cardinality is set to 1, which means that only one person or group can be assigned to this role.
      • supplier: The available suppliers of IT hardware in the system. The role cardinality is set to 2, which means that more than one supplier can be assigned to this role.
  7. Click Save.

5.1. Creating the Place order subprocess

Create the Place order subprocess, which is a separate business process that is carried out by the supplier. This is a reusable process that occurs during the course of case execution as described in Chapter 5, Designing the case definition.

Prerequisites

Procedure

  1. In Business Central, go to Menu Design Projects IT_Orders_New.
  2. From the project menu, click Add Asset Business Process.
  3. In the Create new Business Process wizard, enter the following values:

    • Business Process: place-order
    • Package: Select com.myspace.it_orders_new
  4. Click Ok. The diagram editor opens.
  5. Click an empty space in the canvas, and in the upper-right corner, click the Diagram properties diagram properties icon.
  6. Scroll down and expand Process Data and click btn plus in the Process Variables section and enter the following values:

  7. Click the start event and create an outgoing connection from the start event to a task and convert the new task to a user task.

  8. Click the user task and in the Diagram properties panel, input Place order in the Name field.
  9. Expand Implementation/Execution, click Add below the Groups menu, click Select New, and input supplier.
  10. Click diagram properties in the Assignments field and add the following new conditions in the Place order Data I/O window. For the first input assignment, select Custom for the Data Type and input org.jbpm.document.Document.

  11. Click Save.
  12. Select the Skippable check box and enter the following in the Description field:

    Approved order #{CaseId} to be placed

  13. Create an outgoing connection from the Place order user task and connect it to an end event.

  14. In the diagram editor, click Save and click Save again to confirm your changes.

5.2. Creating the Manager approval business process

The manager approval process determines whether or not the order will be placed or rejected.

Figure 5.4. Business Process (legacy) editor

1: The canvas where you build your process diagram. Drag elements from the Object Library to the canvas to design your process.

2: The Object Library.

3: The Properties panel displays the properties of the selected element. If no element is selected, the panel contains process properties.

Procedure

  1. In Business Central, go to Menu Design Projects IT_Orders_New orderhardware Business Process (legacy).
  2. In the process designer, expand Tasks in the Object Library drag a new User task on to the canvas.
  3. Click the new user, click left arrows to open the Properties panel, and input the following values:

    • Groups - supplier
    • Name - Prepare hardware spec
    • Task Name - PrepareHardwareSpec
    • Description - Prepare hardware specification for #{initiator} (order number #{CaseId})
  4. Click the down arrow in the Assignments field, add the following new conditions in the Prepare hardware spec Data I/O window. For the first output assignment, select Custom for the Data Type and input org.jbpm.document.Document. Click Save.

  5. Click the Prepare hardware spec user task and create an new user task.

  6. Click the new user task, click left arrows to open the Properties panel, and input the following values:

    • Actors - manager
    • Name - Manager approval
    • Task Name - ManagerApproval
    • Description - Approval request for new hardware for #{initiator} (order number #{CaseId})
  7. Click the down arrow in the Assignments field, add the following new conditions in the ManagerApproval Data I/O window. For the first output assignment, select Custom for the Data Type and input org.jbpm.document.Document. Click Save.

  8. Click the Manager approval user task and create a Data-based Exclusive (XOR) gateway.

  9. Click right arrow to open the Object Library, expand Subprocesses, click Reusable, and drag the new element to the canvas on the right side of the Data-based Exclusive (XOR) gateway.
  10. Connect the Data-based Exclusive (XOR) gateway to the subprocess.

  11. Click the subprocess, click left arrows to open the Properties panel, and input or select the following values:

    • ActivityType - Sub-Process
    • Name - Place order
    • Called Element - Select place-order.bpmn from the Asset Name column, and click Save.
    • Independent - false
  12. Click the down arrow in the Assignments field, add the following new conditions in the Place order Data I/O window, and click Save.

  13. Click on the connection from the Data-based Exclusive (XOR) gateway to the subprocess and click left arrows to open the Properties panel.

  14. Click the down arrow in the Expression field and add the following Sequence Flow Conditions and click Ok.

  15. Click the Place order user task and create an end event.

  16. Click the Data-based Exclusive (XOR) gateway and create a new user task and drag the new task to align it below the Place order task.

  17. Click the new user task, click left arrows to open the Properties panel, and input the following values:

    • Actors - owner
    • Name - Order rejected
    • Task Name - OrderRejected
    • Description - Order #{CaseId} has been rejected by manager
  18. Click the down arrow in the Assignments field, add the following new conditions in the Order rejected Data I/O window, and click Save.

  19. Click on the connection from the Data-based Exclusive (XOR) gateway to the Order rejected task and click left arrows , click the down arrow in the Expression field, and add the following Sequence Flow Conditions and click Ok.

  20. Click the Place order user task, create an end event, click Save, and then Save to confirm your changes.

返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat