Defining the application business logic through processes

BMC Helix Innovation Studio provides Process designer, a graphical-based interface, to create and customize the  business processes of a digital service application. Processes are the named services of an application. Business logic is the core of each application, and a process is an application service that runs this business logic, and achieves the application purpose. You can invoke business logic for an application by calling the processes of that application. Each process has a name, input, and output. For example, Approval is the only service of the Approval application, which can be invoked by calling the Approval process through REST API or metadata.

Using the Process designer, you can design processes to accomplish a business goal. You can also use RESTful APIs to modify processes. APIs give you more power and control over managing processes and performing actions that might not be possible through the UI.

Before you begin

Before you create a process, make sure that:

• You understand the process objective, required inputs, and desired output.
• You have all the elements required to create or modify your process. If the required element is not available, request that your developer create and deploy it.
  For more information about process elements and an example of a process created in BMC Helix Innovation Studio, see Process designer elements.

Best practices for designing a process

The following best practices are a few that you must follow when designing a process:

• Do not create processes with many steps and actions. Process definitions represent a business procedure virtually. When the process definition becomes too big, it loses the benefit of a visual workflow. Instead, use a modular approach to divide the steps into smaller subprocesses. By using the Sub Process or Call Activity element.
• Make sure that you have planned adequately between writing code by using @Action and creating a process definition. Consider the following scenarios when selecting the correct option to write code or use the Process designer:
  
  • Design a process using the Process designer if the business logic needs to be visually described or if your users can configure it.
  • Use service tasks to perform a self-sustained unit of work and let the process manage states.
  • Write the code if it is faster to implement a complicated logic than using the Process designer.
• When creating a new process, concentrate on laying out the flow first. Do not focus on configuring each element. When the flow is completed, save the process and then continue to configure each element one by one.

Workflow for defining the business logic

The following table lists the different tasks that are involved in defining a business logic: