We create and capture the ideas that deliver changes. What is your role in digital transformation? Speed up your learning process. Get the help you need quickly and easily with our online courses. We help organizations to transform into digital businesses.
|Published (Last):||13 November 2018|
|PDF File Size:||13.23 Mb|
|ePub File Size:||20.76 Mb|
|Price:||Free* [*Free Regsitration Required]|
Automation Service provides all the power of the Bizagi Digital Business platform directly in the cloud. With Automation Service, customers run applications with business processes in a secure, reliable and high performing cloud platform.
This tutorial illustrates how you, as a customer, would build those applications with business processes. This tutorial sets you up with the basics of producing a simple yet fully-functional process, considering a secure design, and through ten steps which you can complete within about an hour.
This tutorial does not by any means cover all the features and concepts supported by Bizagi as a platform. You build applications and business processes through the Bizagi Studio Windows desktop application. This tutorial presumes you have already installed Bizagi Studio and have created a Bizagi project to work on.
For information about how to install Bizagi Studio on your own desktop or servers on-premises , refer to the Bizagi Enterprise installation guide. For information about how to create a project in Bizagi Studio, refer to the Project creation guide. To illustrate how you can build process applications in Bizagi, we will create an application implementing a Help desk process.
This will be a typical Help desk process that one of your customers would use when they face a problem or difficulty and want to file a report or get help. With Bizagi, you can create an application with any number of processes, but for the sake of simplicity in this tutorial, we will create just this one. The Help desk process you develop this tutorial starting from its workflow is an oversimplified representation of a real Help desk process.
It only includes three activities on purpose, so you can complete the tutorial in a shorter period of time. For instance, the following image shows a different and more complete Help desk process sample that is available for download at the Bizagi Process Xchange:.
If you want to review this ready-to-use process, or others, visit the Bizagi Process Xchange. You may of course, further customize and extend this process by including additional activities and business scenarios. Through the Help desk sample process presented by this tutorial, you can see how different users having separate roles , work with Bizagi, while having ACL s in place to establish well-defined boundaries about what each role may and may not do.
This tutorial, will give you a good idea of how you build role-oriented, and secure process applications. Roles included in this tutorial, are:. A requester : is in charge of initiating the process and eventually confirming that it can be ended. The process starts when a requester fills out a ticket to seek for assistance using a Report ticket , as depicted by the simplified Help desk flow.
After receiving a response, the requester confirms whether the problem or difficulty has been resolved by completing Confirm resolution. A Help desk agent : is assigned to analyze the problem or difficulty recorded in the ticket and provide a solution. When a new ticket arrives, a help desk agent sends suggested steps to resolve the ticket by completing Analyze and resolve. An admin : Will not interact in the process. The admin will engage directly with a Help desk ticket, but will have sole access to:.
Open Bizagi Studio and open a project you have already created by clicking that project's name under Recent projects :. Bizagi presents presents a graphical Process wizard which guides you through a series of points to consider when building your applications. The Process wizard presents seven steps in a carousel, though we will not use all of them in this tutorial.
For detailed information about this guided assistant, refer to the Process wizard. Modeling the process means graphically diagramming the series of activities that make up the workflow of a process, from start to end.
For this tutorial, it means depicting and interconnecting the following logical steps as used by the Help Desk example: Report ticket, Analyze and resolve, Confirm resolution, Review and document , along with other secondary shapes.
Click New process in the Process wizard step number 1 "Model process" and give your process a name. For this tutorial, name it "Help desk" and click OK :. Right-click the name and select Edit text to change it:.
Rename default elements in the canvas using the right-click and Edit text options to have a tidier and self-descriptive process model. Delete the Milestone 1 default label by renaming it to blank , and use the labels as shown in the image below Requester, Help desk agent. You can also make the diagram tidier by resizing the lanes by clicking the Help desk process Pool , and then relying on standard mouse resizing options to shorten its height.
Start drawing the process diagram by dragging a Start Event into the top Lane Requester :. Add an Activity following Report ticket , by using the Pie menu. The Pie menu is the set of elements popping up to the immediate right, when you click a given shape. In the Pie menu, select Activity icon and drag and drop it into the bottom Lane Help desk agent :. The activity's default Task 1 text highlights and you can rename this shape. We suggest you name this Activity Analyze and resolve :.
Add another Activity after Analyze and resolve , using the Pie menu the same way as before. Add the new Activity inside of the top Lane Requester :. Name this new Activity as Confirm resolution. Using the Pie menu makes it quick and easy to draw the process diagram; however, dragging and dropping shapes from the Palette and connecting them afterward by using Sequence Flows is also an option.
Over the next steps, complete the process diagram, by using some of the features you have learned. Add a Gateway starting from Confirm resolution by using the Pie menu.
Add the Gateway right next to it, and still inside the top Lane Requester :. Add an Activity starting from Was the ticket resolved? Add the new Activity t o the bottom Lane Help desk agent :.
Add an End Event starting from Review and document using the Pie menu. Add the event next to it and inside the same Lane Help desk agent :. Label the End Event End - Ticket is closed. Connect Was the ticket resolved? Where the workflow continues from the Gateway , and because this specific shape is meant to support the process workflow splitting into more than one possible path, you can also use the Pie menu to include an additional Sequence Flow that automatically draws a connection to an existing shape.
To make sure that while dragging and dropping, it connects to an existing shape and does not simply create a new one , release the mouse button when the target shape i. Label both paths parting from Was the ticket resolved? Double-click the newly created Sequence Flow and label it No:. Repeat the procedure with the other Sequence Flow and label it Yes :. You can fine-tune some minor visual aspects of your diagrammed process for clarity purposes.
This means repositioning some labels by selecting and moving them to the new location , and reorganizing how the Sequence Flows routes appear especially the one labeled No. To reorganize a Sequence Flow , relocate where the end of it connects, by dragging it and making sure you release the mouse button when its endpoint highlights in green:.
Include SLA s for your Activities. As a final step, define the estimated time for completion of each of the three Activities. Right-click Analyze and resolve and then click Properties.
For this tutorial, set a hour duration for Analyze and resolve. Inputted values or changes to them are temporarily saved, and permanently saved when you save the whole process diagram. For Confirm resolution, click it and set a hour duration. Finally, for Review and document, click it and set an 8-hour duration. Close the Process Modeler and click Yes when prompted to save changes:.
Once the process diagram is closed, you return to the Process wizard. Click the Model data icon to move into the step two or click the Next arrow to the right :. Design how to store your information. Modeling data involves defining structures to hold information that your business requires. With Bizagi, you do this by defining entities and their inner attributes, to organize how information will be stored, as well as defining possible relationships between entities.
For further information and concepts about this step, refer to Modeling data. For this tutorial and for simplicity, we define a very basic Help desk data model that contains the ticket's subject, a description, and file attachments for starters, as well as other bits of information involved further on during the process such as: which are the suggested solution steps, whether the ticket is resolved, and documentation comments. Even though this tutorial does not focus on it, you could make the most of the potential of data modeling within Bizagi by features like defining multiple-to-multiple relationships between entities, defining entities which inherit from others, and involving system entities which already manage information used by Bizagi "metadata".
Click Model data at the Process wizard step 2 to define the name of your main process entity. Once you define the process entity's name, you see a visual representation of the Help desk process' data model based on the concepts of entity-relationship diagrams ; displaying initially only the process entity you just defined. Right-click the HelpDesk entity and select Edit attributes to specify how and where business information used by the process is stored:.
Click Add to include four new attributes and give them names. Add these as String type attributes to store text. After clicking Add each time, provide the Display Name for each attribute the Name you may leave it as it is automatically generated.
For this new one, change the type of data it manages from String to File. By clicking Add , naming the attribute as Ticket attachments , and in the third column Type selecting File so this attribute supports having the user upload documents or file attachments in general.
For this new one, change its data type to one that is not from the Common Types list. When you click New entity , a new wizard appears, in which you can define the structure of Severity as a separate entity. In general, defining Entity data types lets you define reusable entities which you can navigate into, starting from the one currently standing on HelpDesk.
The Severity entity used in this tutorial stores a preset list with values to choose from in this case, a Critical, Medium or Low qualification that enables a classification of tickets. Each instance of a Help Desk entity will have an attribute of type Severity to store the level of severity of the case. The possible severity levels are predefined, as you will see later in the tutorial. Click Next to move to defining attributes applicable to Severity.
Click Add to define two new String attributes. When you have created the Severity entity, Bizagi takes you back to the attributes definition of the main HelpDesk entity.
Bizagi is one of the BPM software in the market. With Visual Paradigm , you can import Bizagi's. In this tutorial, you can learn how to migrate the work from Bizagi to Visual Paradigm. Compatible edition s : Enterprise , Professional , Standard , Modeler. Teaching with Visual Paradigm is a pleasure. It is easy-to-use, it is intuitive, and above all it does not get in the way of conveying the semantics of object oriented modeling.
How to Import Bizagi Project into Visual Paradigm?