inubit Suite 6 Tutorials

Transcription

1 inubit Suite 6 Tutorials

2 Copyright inubit AG Schöneberger Ufer Berlin Germany Phone: Fax: URL: inubit AG 2011 Legal Provisions The information and data, including URLs and other references on an Internet basis, contained in this documentation may be changed without prior notice. The product documentation was carefully prepared. However, the information contained therein cannot be guaranteed to reflect the properties of inubit Suite 6. The liability of inubit AG encompasses only the provisions stated in the sales and delivery conditions. The users are responsible for compliance with all applicable copyrights. Regardless of applicability of the respective copyright laws, no portion of this document may be reproduced or transferred for any purpose, regardless of the means or resources used, electronically or automatically, without prior explicit written approval from inubit AG. inubit AG may be the owner of patents, patent applications, trademarks, copyrights or other rights of intellectual property that concern the content of this document. The provision of this document does not grant license rights to these patents, trademarks, copyrights or other intellectual property, unless this was explicitly granted by inubit AG in a written license agreement. Software provided by inubit may include software components of other producers. inubit is a registered trademark of inubit AG. All other product and company names listed in this document may be registered trademarks of their respective owners.

3 Table of Contents 3 Table of Contents Notes on the Tutorials...7 Scope of the Documentation...7 Tips, Notes and Links in the Documentation...8 Further Information and Support First Steps Overview of inubit Suite Components Using Example Diagrams and Users Staging: Creating, Testing and Executing on Different Systems Creating a Diagram Inserting and Connecting Elements Publishing a Diagram Opening a Diagram for Editing Modeling Business Processes using the Workbench Depicting the Structural Organization Providing Documents in the Organization Diagram Depicting the IT Organization as a System Diagram Depicting the Work Process Organization as Business Process Diagram Refining Business Process Diagrams Validating Diagrams Modularizing Business Process Diagrams: Linking Sub-Processes Simulating Business Processes Application Example: Using the BPD of an Order Process Defining Duration and Costs of Individual Tasks Creating Metadata Types Assigning Values to Costs and Duration of Tasks Defining Material Resources Defining Employee Resources for each Department Defining Employee/Material Requirements per Task Configuring the Order Volume Simulating the Order Process Improving the Order Process...55 inubit Suite 6: Tutorials

4 4 Table of Contents 3.9 Simulating the Improved Order Process Creating a Data-Centric Business Solution Basics Creating a Domain Model in the WebModeler Creating Classes and Defining the Root Instance Adapting Relationships and Adding Associations Defining Attributes for Classes Deploying and Activating the Domain Model Creating Business Objects Assigning Business Objects: Establishing Relationships Creating a View for all Business Objects of the Vehicle Class Adding the FleetManagement Business Solution to the Menu Closing the Solution Center Creating a Process Solution Basics Creating a Business Process Diagram (BPD) in the Workbench Creating a BPD as a Solution Center Process Model Defining the Process Expanding the Business Object Diagram (BOD) Adding the Enumeration Class for the Vacation Type Linking External Class Person Adding Attributes for the Class ApplicationForLeaveBO Publishing the BOD, Validating and Publishing the BPD Adapting the Process Solution Submitting Leave Applications Approving an Application for Leave Integrating Systems and Automating Processes Application Example Creating a Technical Workflow 1: Reading a File from the File System Testing the Workflow Creating a Technical Workflow 2: Converting a CSV File to CSV-XML Creating a Technical Workflow 3: Converting CSV-XML to opentrans Excursus: XSLT Creating a Technical Workflow 4: Storing the File in the File System inubit Suite 6: Tutorials

5 Table of Contents End-to-End Navigation: Connecting Technical Level with Business Level Developing a Web Application in inubit Workbench Workflow Management Developing Your Own Web Application Creating the Form Mapping Creating Output Mapping Inserting Additional Modules Adding a Web Application to a Portal Page as a Portlet Granting Web Application Permissions, Assigning Them to Portal Roles inubit Suite 6: Tutorials

6 6 Table of Contents inubit Suite 6: Tutorials

7 Notes on the Tutorials 7 Target group The tutorials help you getting started with using the inubit Suite 6 by explaining important and fundamental work steps and concepts in a concise way. Scope of the Documentation inubit Suite 6 provides comprehensive documentation and is available as a printed manual, a PDF file and as online help in the inubit Workbench. The documentation covers the following content: inubit Suite 6 - Quick Start Describes the hardware and software prerequisites, the installation and the first steps. - Migration Guide - Tutorials For novices. Using technical scenarios the tutorials detail the use of the most important components of inubit Suite 6. inubit Workbench, inubit Process Engine und inubit Enterprise Portal: - User Guide Explains how to work with the inubit Workbench, the Designer, working with different diagram types, modules, with metadata and workflow variables, simulations, tests, technically-based monitoring and reporting. - Administrator and Developer Guide Administrative topics such as the configuration of inubit Process Engine, backup and restore, user administration, security aspects, monitoring and clustering, development of plug-ins and Thin Clients. - Modules Guide Use and configuration of Data Converter, Format Adapter, Utilities, Workflow and Web Service Controls. - System Connectors Guide Everything involving the use and configuration of system connectors. inubit Solution Center User Guide Information about creating business models, working with Business Solutions, creating views, integrating processes and default models and the REST interface. - Administrator Guide inubit Suite 6: Tutorials

8 8 Explains how to backup and restore data, to install the Solution Center as a service, to adjust ports, to configure the portal, the database and HTTPS, to manage users and import diagrams. inubit WebModeler Administrator and User Guide Everything about creating and editing models, adjusting ports, configuring the database and HTTPS. You can download the most current documentation in the inubit User Portal from the "software tab at Further information The following information is enclosed as a booklet with the DVD, or as files in the installation package: readme.txt Notes on the installation and migration of inubit Suite 6. Read this file thoroughly before installing or updating inubit Suite 6! Quick Start System requirements and installation instruction as booklet delivered with the inubit Suite 6-DVD. API documentation for plug-in software development kit Found under <is-installdir>/documentation/apidoc/ index.html. JavaScript-Framework of the inubit Suite 6 Found under <is-installdir>/documentation/jsdoc/ index.html Tips, Notes and Links in the Documentation Tips offering useful information for working with inubit Suite 6. Notes that must be read and observed. Failure to follow the instructions may lead to data loss or may cause serious system problems. References to other text locations within this or any other inubit manual are labeled with an arrow. Links to external web pages inubit Suite 6: Tutorials

9 9 Further Information and Support Press releases and white papers are available from our website For further inquiries, please contact our support by: inubit support: Telephone: We wish you every success in working with inubit Suite 6 Your inubit team! inubit Suite 6: Tutorials

10 inubit Suite 6: Tutorials

11 1 First Steps 11 This section details the following topics: Overview of inubit Suite 6, p. 11 Components, p. 12 Using Example Diagrams and Users, p. 13 Staging: Creating, Testing and Executing on Different Systems, p. 13 Creating a Diagram, p. 14 Inserting and Connecting Elements, p. 16 Publishing a Diagram, p. 19 Opening a Diagram for Editing, p. 20 You should master the processes described in this tutorial since knowledge of them is a prerequisite for the following tutorials. 1.1 Overview of inubit Suite 6 Overview The inubit Suite 6 consists of different components which can be combined with each other for use in the most diverse application scenarios due to their consistency: Business Analyst Mobile Clients inubit Workbench inubit WebModeler inubit Enterprise Portal inubit Process Cockpit Task list inubit Solution Cockpit iphone Modeling & Simulation inubit Process Engine inubit Enterprise Service Bus View Engine Business Repository Legacy Application Legacy Application Legacy Application inubit Suite 6: Tutorials

12 12 First Steps Components 1.2 Components inubit Workbench The inubit Workbench is a J2SE based client with a graphical user interface for the following tasks: Business modeling and simulation Technical configuration of the integration segments between the different systems and business partners Administration of the inubit Process Engine/Enterprise Service Engine and its users Technical monitoring of the inubit Suite 6 and its processes Refer to - General Settings of the inubit Suite 6 (inubit Process Engine: Administrator and Developer Guide, chap. 2, p. 21) - Managing Users (inubit Process Engine: Administrator and Developer Guide, chap. 6, p. 63) - Technical Monitoring (inubit Process Engine: Administrator and Developer Guide, chap. 7, p. 83) inubit Process Engine / Enterprise Service Bus (ESB) The inubit Process Engine/ESB are the core components of the inubit Suite 6. They ensure the process execution and the technical integration of systems and services. Refer to - Configuring the Tomcat Application Server (inubit Process Engine: Administrator and Developer Guide, chap. 4.1, p. 51) - Configuring the JBoss Application Server (inubit Process Engine: Administrator and Developer Guide, chap. 4.2, p. 52) inubit Enterprise Portal The inubit Enterprise Portal can be used as a basis for a corporate intranet and for interacting with business partners. In the inubit Enterprise Portal the inubit WebModeler, the inubit Process Cockpit and the inubit Solution Cockpit can be integrated and aggregated in a uniform and user-friendly interface. Refer to Using inubit Enterprise Portal (Workbench: User Guide, chap. 20, p. 461). View Engine The View Engine is a part of the inubit Solution Center and allows for automatized generation and customization of user interfaces when implementing Business Solutions inubit Suite 6: Tutorials

13 First Steps Using Example Diagrams and Users 13 Business Repository The Business Repository is used for central storing and managing data and information. Refer to Repository: Managing Files Centrally (Workbench: User Guide, chap. 19, p. 445). Mobile Clients Processes executed by the inubit Suite 6 can also be controlled, edited and monitored via mobile terminals, for example iphones. 1.3 Using Example Diagrams and Users The inubit Suite 6 contains several example users and diagrams, which you can use in the following tutorials. Proceed as follows Log in to the inubit Workbench with the user miller and the password inubit. The user miller is a system administrator and therefore has extensive administrative permissions. 1.4 Staging: Creating, Testing and Executing on Different Systems The inubit Suite 6 has a three-level staging process that supports creating, testing, and executing diagrams and modules on separate systems: 1. Creating locally Diagrams and modules are created in the inubit Workbench in a local directory and stored on the computer on which the inubit Workbench is installed. Refer to - Creating a Diagram (Tutorials, chap. 1.5, p. 14) - Testing with inubit Suite 6 (Workbench: User Guide, chap. 16, p. 379) 2. Publishing to the inubit Process Engine and testing Once you have finished creating and editing your diagram/ modules, you publish them on an inubit Process Engine. The diagrams and modules are then in the so called server mode. inubit Suite 6: Tutorials

14 14 First Steps Creating a Diagram In the server mode you can additionally use the watch mode and let scheduled diagrams execute. Refer to Publishing Modules and Diagrams (Workbench: User Guide, chap. 1.5, p. 35). 3. Revising locally and publishing again Each time you publish your diagram/module, a new version is created. All versions are retained and can be displayed or activated from the version history whenever you want. The diagram/module is copied back to the local host for editing. The version on the inubit Process Engine is retained. Refer to Opening a Diagram for Editing (Tutorials, chap. 1.8, p. 20). 4. Deploying on production system After having finished your tests successfully, you can deploy your diagrams and, by doing so, define on which inubit Process Engine your diagrams are to be executed. Refer to Deployment of Diagrams, Modules and Repository Files (Workbench: User Guide, chap. 1.6, p. 36). 1.5 Creating a Diagram All inubit Suite 6 diagrams start with an empty diagram containing different properties that you can configure. Proceed as follows 1. In the inubit Workbench, open the Designer > Local tab. The local working directories on the Local tab contain all diagrams of the user who is currently logged in, sorted by type. 2. Select the System diagrams folder inubit Suite 6: Tutorials

15 First Steps Creating a Diagram Open the context menu and select New. The following dialog opens: 4. Enter the name of the diagram and a comment (for example, the use of the diagram). 5. Click OK. The dialog closes. An empty workspace is displayed: inubit Suite 6: Tutorials

16 16 First Steps Inserting and Connecting Elements At the bottom left, the Comment tab displays the comment you entered when you created the diagram. In the workspace, you create the actual diagram using the elements displayed in the sidebar to the right of the workspace. 1.6 Inserting and Connecting Elements You insert elements into a system diagram to describe how the inubit Process Engine is protected by firewalls inubit Suite 6: Tutorials

17 First Steps Inserting and Connecting Elements 17 Prerequisites You have already created an empty system diagram. Refer to Creating a Diagram (Tutorials, chap. 1.5, p. 14). Proceed as follows 1. In the sidebar, click Tools. The docking window "Tools" opens. 2. Click Artifacts and drag the Frame element to the workspace: The Frame element is inserted. 3. Double-click the element. A dialog opens in which you can enter a name for the element and define the background color and position of the name. 4. Call the element DMZ (abbreviation for Demilitarized Zone = safe zone), define the color background pink, and position the name on the top left. 5. Click on Tools in the Tools docking window. 6. Drag two Firewall elements and an is element into the border element: inubit Suite 6: Tutorials

18 18 First Steps Inserting and Connecting Elements The elements are grouped automatically with the frame; if you now move the frame, the elements contained within the frame are also moved. 7. Connect the upper Firewall element with the is element: a. Select the Firewall element using the mouse. b. Press the SHIFT key and hold it down. c. Drag the cursor out of the selected element onto the is element. The two elements are connected with an arrow. After connecting the two elements, the arrow always points at the element that was the last to be selected. You have different options for connecting elements or modules in a diagram: either by using the mouse and keyboard as described above or by using the context menu, refer to Connecting/ Disconnecting Modules and Elements (Workbench: User Guide, chap. 3.8, p. 113). You can assign a name to a connection and edit a displayed connection, refer to Editing Connections between Diagram Elements (Workbench: User Guide, chap. 2.9, p. 79). 8. Connect the is element with the second Firewall element in the same way. The result looks like this: inubit Suite 6: Tutorials

19 First Steps Publishing a Diagram 19 The diagram created in this manner is only available on your local computer at the moment. To make it accessible to other users, you have to publish it. Refer to Publishing a Diagram (Tutorials, chap. 1.7, p. 19). 1.7 Publishing a Diagram When you publish a diagram, you transfer it from your local working directory to a directory on the inubit Process Engine to make it available for another user group, for example. Proceed as follows 1. Select the system diagram in your local working directory. 2. Open the context menu and select Publish. The following dialog appears: inubit Suite 6: Tutorials

20 20 First Steps Opening a Diagram for Editing In this dialog you define the target directory. You can publish, for example, the diagram in your own user directory on the inubit Process Engine or in the directory of your user group. Select your user directory. The name of the system diagram is displayed in green. This indicates that the system diagram does not yet exist in the target system. 3. Click OK. The dialog closes. The diagram is published in the selected directory and displayed. This process creates a new version of the diagram. The local version of the diagram is deleted. For more information, refer to - Publishing Modules and Diagrams (Workbench: User Guide, chap. 1.5, p. 35) - Versioning, Tagging and Revision (Workbench: User Guide, chap. 18, p. 421) 1.8 Opening a Diagram for Editing You can open one or more diagrams at the same time for editing. Diagrams can only be edited in local directories. Thus, diagrams stored on the inubit Process Engine are copied to a local directory. While a diagram is being edited, other users receive a warning message if they try to edit the same diagram inubit Suite 6: Tutorials

21 First Steps Opening a Diagram for Editing 21 Diagrams are released for editing by other users only after they have been published or deleted in the local directory. Proceed as follows 1. Select one or more diagrams in the Server tab. 2. Open the context menu then select Edit diagram. The diagrams are copied, the copies are moved into the appropriate local directory and displayed. You can now edit the diagrams. inubit Suite 6: Tutorials

22 22 First Steps Opening a Diagram for Editing inubit Suite 6: Tutorials

23 2 Modeling Business Processes using the Workbench 23 This section details the following topics: Depicting the Structural Organization, p. 23 Providing Documents in the Organization Diagram, p. 26 Depicting the IT Organization as a System Diagram, p. 28 Depicting the Work Process Organization as Business Process Diagram, p. 30 Refining Business Process Diagrams, p. 34 Validating Diagrams, p. 37 Modularizing Business Process Diagrams: Linking Sub- Processes, p. 38 There are example diagrams for all tutorials in the inubit Suite 6, refer to Using Example Diagrams and Users (Tutorials, chap. 1.3, p. 13). Prerequisites You have installed one of the following installation sets of the inubit Suite 6: - Full installation - Process Center - Modeling Center You have added a valid license. You find further installation instructions in the Quick Start: - Installing from DVD (Quick Start, chap. 2, p. 4) - Requesting a License Key (Quick Start, chap. 3, p. 5) - Adding the License Key (Quick Start, chap. 4, p. 7) You have logged in to the inubit Workbench with the user miller in order to access to the example diagrams. Refer to Using Example Diagrams and Users (Tutorials, chap. 1.3, p. 13). 2.1 Depicting the Structural Organization The structural organization is the hierarchical framework of a company. In the inubit Workbench, you visualize the structural organization using an organization diagram, showing reporting lines and the roles occupied by employees. inubit Suite 6: Tutorials

24 24 Modeling Business Processes using the Workbench Depicting the Structural Organization A complete and up-to-date organization diagram is an important prerequisite for the modeling and subsequent optimization of your business processes, since it requires the recording of all human resources, dependencies, and activities involved in the execution of a business process. Organization diagrams Organization diagrams consist of elements such as organization units, roles, substitutes, and people. Naturally, you can also depict different structural principles of, for example, matrix or functional organizations. Refer to Modeling Elements (Workbench: User Guide, chap. 8.1, p. 207). Proceed as follows 1. Display the Designer > Server tab in the inubit Workbench. 2. Open the folder Diagrams of group: tutorial > Organization Diagrams > Tutorial-Organigramme. 3. Click the Assembler-AG-Organigramm organization diagram. 4. Open the organization diagram for editing. Refer to Opening a Diagram for Editing (Tutorials, chap. 1.8, p. 20). The organization diagram is displayed in the Local tab. You can now remove existing elements or add new ones. 5. Add another member to the inubit IS Team: a. In the sidebar, click Tools. The Tools docking window opens. b. Click the Person button in the sidebar and drag it onto the workspace beneath the team member that already appears there ( Bob Brown ) inubit Suite 6: Tutorials

25 Modeling Business Processes using the Workbench Depicting the Structural Organization 25 c. Double-click the Person element. A dialog opens. Enter the name of the team member in the Name field. d. Click OK. The dialog closes. e. Assign the new member to the team member role by connecting the team member role element with the Person element. Refer to Inserting and Connecting Elements (Tutorials, chap. 1.6, p. 16). f. To name the connection, double-click it. Enter a name in the Name field. The result should look like this: inubit Suite 6: Tutorials

26 26 Modeling Business Processes using the Workbench Providing Documents in the Organization Diagram 2.2 Providing Documents in the Organization Diagram You can provide additional information for organization diagram elements in the form of metadata. Metadata can, for example, contain single-line or multi-line text or links to external documents with role descriptions. Proceed as follows Create metadata type 1. In the inubit Workbench, display the Configuration > Meta Data Manager tab. a. Open the context menu of the left area and select Add. The following dialog opens: b. Enter Job description as the name and select External document as the data type. c. Click OK. The dialog closes and the new metadata type is displayed: Allocate metadata type to element type 2. Use the mouse to drag the newly created metadata type to the right-hand area ( Allocation to the diagram elements ) and drop it onto the Role element below the Organization Diagram folder inubit Suite 6: Tutorials

27 Modeling Business Processes using the Workbench Providing Documents in the Organization Diagram 27 The metadata type is displayed in green below the Role element. 3. Press CTRL+S to save the assignment. The metadata type is now displayed in black and available in all Role elements in all organization diagrams. Define a role description 4. To define a role description, create an organization diagram. a. Add a new Role element named team member. b. Double-click the team member Role element. The Element properties dialog opens. c. Display the Metadata tab. The metadata type you just created is displayed in the table. d. Click the button. The dialog for defining the properties of the external document appears. e. Select the Generic Application profile from the Application profile list. This profile assigns the file type to the application as registered in you operating system. On Windows systems, for example, files with the.doc extension are always associated with the MS Word application. f. In the Address field, enter the path to an (arbitrary) HTML document: g. Confirm the dialog by clicking OK. The specified information is displayed in the Value field. inubit Suite 6: Tutorials

28 28 Modeling Business Processes using the Workbench Depicting the IT Organization as a System Diagram Test 5. Click the button. Your standard Web browser opens and displays the file and the role description. 6. Click OK to close the properties dialog. A document symbol on the role element team member indicates that there is an external document for this role: You can also use metadata in the form of external documents to define forms in business process diagrams that describe activities belonging to a quality management system or to define documentation on systems in system diagrams. Also refer to - Using Metadata (Workbench: User Guide, chap. 17, p. 413) - Application Profiles (inubit Process Engine: Administrator and Developer Guide, chap. 11.1, p. 135) 2.3 Depicting the IT Organization as a System Diagram Your company's IT organization includes your internal IT systems (for example, your inubit Suite 6 and your ERP system), the external IT systems of your customers and partners, and the relationships between these systems. You can depict the entire IT organization in a system diagram, thus fulfilling an important prerequisite for the modeling and optimizing your business processes. To do this, you have to enter all technical systems and dependencies as well as human resources. Proceed as follows 1. Display the Designer > Server tab in the inubit Workbench inubit Suite 6: Tutorials

29 Modeling Business Processes using the Workbench Depicting the IT Organization as a System Diagram Open the folder Diagrams of group: tutorial > System Diagrams > Tutorial-Systemdiagramme. 3. Display the Assembler-AG-IT-landscape diagram by clicking it. The system diagram shows that the inubit Process Engine gets its data from the company s ERP system and exchanges data with suppliers (Supplier A and Supplier B) and traders via the Internet. For security reasons, all systems are protected by firewalls. 4. Open the system diagram for editing. Refer to Opening a Diagram for Editing (Tutorials, chap. 1.8, p. 20). The system diagram is displayed in the Local tab. 5. Add a freight company as an additional partner. This company uses a Web-based fleet management system that requires user interaction and is also protected by a firewall. Refer to Modeling Elements in System Diagrams (Workbench: User Guide, chap. 9.3, p. 229). 6. Change the background color of the partner element to make it easier to identify. a. Double-click the Partner element. b. Open the Style tab. c. Select a color in the Background area and click it. d. Close the dialog by clicking OK. 7. Connect the various elements within the Partner element with a dotted line with points at its beginning and end to differentiate internal communication from communication via the Internet. a. Double-click the connection. b. Display the Line type tab. c. Configure the line. d. Close the dialog by clicking OK. 8. Label the connection to the Internet with the protocol used, for example, via https. a. Double-click the connection. b. Enter an element name. c. Close the dialog by clicking OK. As a partner, the freight company can be depicted as follows, for example: inubit Suite 6: Tutorials

30 30 Modeling Business Processes using the Workbench Depicting the Work Process Organization as Business Process Diagram 2.4 Depicting the Work Process Organization as Business Process Diagram The work process organization comprises the business processes of a company from a business point of view. You can depict these processes in a business process diagram (BPD), thus providing a further important component for subsequent process automation. BPD notation complies with the BPMN standard, is easily readable, and can be used to depict complex business processes and businessto-business processes. Also refer to - BPD Modeling Elements (Workbench: User Guide, chap. 6, p. 136) - Creating Business Process Diagrams (Workbench: User Guide, chap. 6.1, p. 134) for information about business process modeling with BPD. For details about the BPD modeling elements, refer to - (standard document, beta version (poster of a well arranged summary of all elements) For useful process modeling patterns, refer to Modeling BPDs are independent of modeling methods such as LOVeM or EPC. They can therefore be used to depict the results of all modeling methods. The following procedure for the formalized depiction of a business process has been tried and tested: 1. Ask the owner of the business process about their actual procedure. 2. Document the as is state of the process. Record a. all events starting the process, b. all actions, which are executed, and their dependencies, c. all process results. 3. Record the most important information (such as response and processing times, quality specifications, and limitations) about the process. Among other things, the selected method determines which information is relevant. 4. Link the information as artifacts with decision points or activities. Proceed as follows 1. Create an empty business process diagram. Refer to Creating a Diagram (Tutorials, chap. 1.5, p. 14) inubit Suite 6: Tutorials

31 Modeling Business Processes using the Workbench Depicting the Work Process Organization as Business Process Diagram 31 Choose Standard mode on the Business Process Diagram tab. 2. Make sure the menu entry View > Profile > Full is selected. Depict organizations 3. Assembler AG (department Production) and their supplier (department Accounting) are involved in the process. The two process participants are part of two different organizations. Insert a pool for each process participant. a. In the sidebar, display the docking window Tools. b. Open the Processes and Activities area. c. Drag two horizontal pools into the working panel. d. Double-click a pool and rename it to Assembler AG. e. Do the same for the other pool, naming it Supplier. The result looks like this: Depict departments 4. The process is performed by the two departments Production and Accounting in both organizations. The departments are depicted as lanes in a pool: a. Open the context menu of the pool Assembler AG and select Add lane. A lane is added. b. Double-click the lane and rename it to Production. c. Do the same with the supplier pool and name the department Accounting. Depict the process start as start event 5. The process starts periodically on the first of each month, when Assembler AG places an order with the supplier in order to request more product parts. The start event is a periodical, time event. a. Insert a Timer start event from the Start Events panel into the Production lane. b. Name the start event. Describe the process steps as tasks 6. The order process includes the following steps: a. Assembler AG sends the order to the supplier. inubit Suite 6: Tutorials

32 32 Modeling Business Processes using the Workbench Depicting the Work Process Organization as Business Process Diagram b. The supplier processes the order. c. The supplier sends an invoice to Assembler AG. d. Assembler AG receives the invoice. Each of these steps is depicted as a task. A task is a single-step activity that cannot be described in any further detail. e. Insert a task for each step in each case in the lane of the department, which is to execute this task. f. Name the steps. The result should look like this: Depict the task order per organization 7. Connect the tasks in each lane, thus creating a so-called sequence flow in each pool. A sequence flow defines the order in which activities are executed in an organization. Define the message stream 8. Both organizations need to communicate in the order process to achieve a successful process end. This information exchange across organization borders is depicted by dashed lines inubit Suite 6: Tutorials

33 Modeling Business Processes using the Workbench Depicting the Work Process Organization as Business Process Diagram 33 Connect the tasks as given in the graphic. The connection is displayed as dashed line automatically, as soon as it crosses the pool border. End of process 9. The process end must be depicted by an end event explicitly. Insert a simple end event from the end event panel and name it. Now, proceed with refining the diagram. Refer to Refining Business Process Diagrams (Tutorials, chap. 2.5, p. 34). inubit Suite 6: Tutorials

34 34 Modeling Business Processes using the Workbench Refining Business Process Diagrams 2.5 Refining Business Process Diagrams The modeling language BPMN offers powerful constructs. Complex business processes can be depicted. This section explains data objects, sub-processes, two specific task types and intermediate events to you. Depicting information as data objects Proceed as follows At the message streams you can specify explicitly what information is transferred. 1. Insert two data objects from the artifacts panel. 2. Name the two objects with Order and Invoice. 3. Connect the data objects with the corresponding message streams between the activities. The connection is automatically displayed as dotted line and is named association in the BPD context. The result should look like this: Converting a task into a subprocess The task Process order is not really a single-step task, but rather a sequence of tasks. This element should therefore be a subprocess. Proceed as follows 1. Open the context menu of the task Process order. 2. Select Refactoring > Convert to Sub-Process. The task now is displayed as sub-process inubit Suite 6: Tutorials

35 Modeling Business Processes using the Workbench Refining Business Process Diagrams 35 Sub-processes can be linked to other BPDs. Using this feature improves the readability of diagrams, because you can, e.g., divide complex processes into an overview and some detail BPDs and use sub-processes in the overview BPD to link to detail BPDs. Refer to Modularizing Business Process Diagrams: Linking Sub-Processes (Tutorials, chap. 2.7, p. 38). Converting task types There is a more specific construction than the general task for both tasks Create order and Send invoice. Change both tasks to the task type Task (send). Proceed as follows 1. Click the task. A graphical context menu is displayed: 2. Point at the refactoring symbol and select Task (Send). The task is displayed with an additional symbol: 3. Do the same for the other task. inubit Suite 6: Tutorials

36 36 Modeling Business Processes using the Workbench Refining Business Process Diagrams Modeling alternative: Intermediate event instead of task The task Receive invoice can be replaced by a message intermediate event (receiving). Proceed as follows 1. Delete the Receive invoice task. 2. Drag the Message Intermediate Event (Catching) from the Intermediate Events panel in the Tools docking window to the former position of the task deleted before. 3. Name the Message Intermediate Event. 4. Connect the Message Intermediate Event (Catching) with the Create order task, the Send invoice task, and the Production completed end event. 5. Connect the data object Invoice with the message flow between the Create order and Send invoice tasks. Now, the diagram should look like this: Modeling alternative: message instead of data object The data objects Order and Invoice can be replaced by a Message artifact. Proceed as follows 1. Delete the Order data object and the Invoice data object. 2. Drag two Message elements from the Artifacts panel in the Tools docking window to the former positions of the data objects. 3. Name the message elements like the data object were named before. 4. Connect the Order message with the message flow between the Create order and Process order tasks. 5. Connect the Invoice message with the message flow between the Send invoice and Receive invoice tasks inubit Suite 6: Tutorials

37 Modeling Business Processes using the Workbench Validating Diagrams 37 Now, the diagram should look like this: 2.6 Validating Diagrams You can validate the diagram to find out if it meets the BPMN 2.0 standard. Starting the validation Proceed as follows Click the icon in the toolbar. The validation returns two notes that the start event and the end event are missing in the Accounts department lane. The notes are displayed in the Validation result window. When you click on an entry in the window, the related element is marked in the diagram and a detailed description of the problem and notes how to solve the problem is displayed. Inserting missing start event and end event Proceed as follows 1. Drag and drop a message start event from the area "Start Events" onto the lane Accounts department. 2. Name the message start event. 3. Connect the message start event with the Process order subprocess. inubit Suite 6: Tutorials

38 38 Modeling Business Processes using the Workbench Modularizing Business Process Diagrams: Linking Sub-Processes 4. Drag and drop the arrow of the message flow from the Process order sub-process to the message start event using the middle mouse key. 5. Click on the Send invoice task. 6. Choose the end event in the graphical context menu. Now, the diagram should look like this: If you validate the diagram again now, a message should be displayed stating that the diagram is valid. 2.7 Modularizing Business Process Diagrams: Linking Sub-Processes You can arrange complex business process diagrams (BPDs) more clearly by depicting the process roughly in an overview BPD and then modeling the details in separate BPDs. Then, you link the detailed BPD to the overview BPD. Thus, you can structure the BPDs hierarchically. Apart from the clearer arrangement, there is one more advantage of re-using BPDs: Process fragments can be re-used in a process and thereby standardized and quality assured. Also refer to inubit Suite 6: Tutorials

39 Modeling Business Processes using the Workbench Modularizing Business Process Diagrams: Linking Sub-Processes 39 - Restructuring and Modularizing BPDs (Workbench: User Guide, chap. 6.4, p. 151) - End-to-end Navigation between Diagrams (Workbench: User Guide, chap. 2.12, p. 81) Prerequisites You require the BPD from section Depicting the Work Process Organization as Business Process Diagram (Tutorials, chap. 2.4, p. 30) as an overview BPD. If you have not created this BPD by yourself, you can find it in the folder Diagrams for user: miller > Business process diagrams > Main- Order-Transaction. Proceed as follows 1. Open the BPD from section Depicting the Work Process Organization as Business Process Diagram (Tutorials, chap. 2.4, p. 30) for editing. 2. Open the context menu of the sub-process element Process Order and select Refactoring > Convert to Call Activity. 3. In the sidebar, open the docking window Links. The docking window displays all diagrams available on the inubit Process Engine: 4. Drag the Order Processing BPD onto the Call Activity Process order. The sub-process element is highlighted. inubit Suite 6: Tutorials

40 40 Modeling Business Processes using the Workbench Modularizing Business Process Diagrams: Linking Sub-Processes Once you drop the Order Processing BPD, a window appears displaying this BPD. 5. In the window, select the start event which you want to assign to the reusable sub-process. 6. Click OK to close the window. A dialog opens. 7. Specify if the existing name of the Call Activity should be replaced. At the bottom right, a link point on the Sub-process element indicates that detailed information is available for the sub-process: If you double-click the link symbol, the Order Processing BPD is displayed. Displaying a subprocess If you click the plus sign in the Call Activity, a thumbnail view of the BPD appears and the plus sign is replaced by a minus sign. Refer to End-to-End Navigation: Connecting Technical Level with Business Level (Tutorials, chap. 6.8, p. 123) inubit Suite 6: Tutorials

41 3 Simulating Business Processes 41 This section details the following topics: Application Example: Using the BPD of an Order Process, p. 42 Defining Duration and Costs of Individual Tasks, p. 44 Defining Material Resources, p. 46 Defining Employee Resources for each Department, p. 47 Defining Employee/Material Requirements per Task, p. 48 Configuring the Order Volume, p. 50 Simulating the Order Process, p. 51 Improving the Order Process, p. 55 Simulating the Improved Order Process, p. 57 For this tutorial, you should already know how to model business processes with the inubit Suite 6 as taught in the Modeling Business Processes using the Workbench (Tutorials, chap. 2, p. 23) tutorial and in the Simulating Business Process Diagrams (Workbench: User Guide, chap. 7, p. 185) simulation documentation! Prerequisites You have installed one of the following installation sets of the inubit Suite 6: - Full installation - Process Center - Modeling Center You have added a valid license. You find further installation instructions in the Quick Start: - Installing from DVD (Quick Start, chap. 2, p. 4) - Requesting a License Key (Quick Start, chap. 3, p. 5) - Adding the License Key (Quick Start, chap. 4, p. 7) You have logged in to the inubit Workbench with the user miller in order to access to the example diagrams. Refer to Using Example Diagrams and Users (Tutorials, chap. 1.3, p. 13). Use The simulation of a business process model provides information about the efficiency of the mapped process. You can use the simulation results to identify the areas that are responsible, for example, for high costs or resource bottlenecks. Before the modeled business processes go into production, they should always be simulated in detail, in order to identify any problems in advance and to improve processes. inubit Suite 6: Tutorials

42 42 Simulating Business Processes Application Example: Using the BPD of an Order Process In addition to the cost and duration of activities, the extended simulation includes the available resources (e.g. number of employees and their working times) and determines bottlenecks as well as actual lead times for a process. The objective of simulation is to check hypotheses that are presented to it as scenarios. The business analyst needs to optimize processes. He/she does so by approaching the optimal solution step-by-step after changing the process model. This tutorial uses a modeling example to guide you through the extended simulation of the inubit Suite 6. You use the cost and duration of individual activities and resources to simulate the process flow of an order process and improve this process by taking into account the simulation results. There are example diagrams for this tutorial in the inubit Suite 6, refer to Using Example Diagrams and Users (Tutorials, chap. 1.3, p. 13). These are stored under OrderProcess-1 and OrderProcess-2 (improved process) under Diagrams of user:miller > Business Process Diagrams > Tutorial-Business-Process-Diagrams. In order to be able to simulate the example diagrams, you have to import the metadata types Costs and Time, if they are displayed in red, in Edit mode (Importing Unregistered Metadata (Workbench: User Guide, chap , p. 419)) in one of the two diagrams OrderProcess-1 or OrderProcess-2 and then configure and start the simulation run in server mode, refer to Simulating the Order Process (Tutorials, chap. 3.7, p. 51). 3.1 Application Example: Using the BPD of an Order Process An application example illustrates the simulation. The exemplary process that is depicted in the Business Process Diagram (BPD) below is the order transaction of the fictitious home order company Good Goods. In the process, orders are accepted exclusively via a call center. A material requirements planner enters the orders in the system. In doing so, the weight of the ordered goods is determined using a Web service with a connected inubit Suite 6 and, depending on the weight, the MRP coordinates a possible heavy load delivery. The delivery data is then transferred to an order database and the order transaction is complete inubit Suite 6: Tutorials

43 Simulating Business Processes Application Example: Using the BPD of an Order Process 43 You use the order process as modeled above to simulate it with regard to an increasing order volume of 50 orders per day over a period of 5 days. The objective of the simulation is to simulate the effects of this higher volume of orders and, for example, check the capacity load of the employees as well as identify the costs of the process and improve them both. In order to be able to configure and execute the simulation with the required business process, choose one of the following options: Show the included BPD OrderProcess-1_unconfigured in local mode. Refer to Using Example Diagrams and Users (Tutorials, chap. 1.3, p. 13). If you have sufficient knowledge of the modeling of Business Process Diagrams (BPD), create the above displayed BPD in the Business Process Diagrams of your group or higher-level group using the inubit Suite 6 tools for modeling business processes. Refer to Creating Business Process Diagrams (Workbench: User Guide, chap. 6.1, p. 134). inubit Suite 6: Tutorials

44 44 Simulating Business Processes Defining Duration and Costs of Individual Tasks 3.2 Defining Duration and Costs of Individual Tasks This section details the following topics: Creating Metadata Types, p. 44 Assigning Values to Costs and Duration of Tasks, p. 45 A certain duration and a certain cost factor are designated for each task in the process that is to be completed by employees. In our process, for example, 20 minutes are estimated for each order accepted by a call center employee and the transaction is priced at Creating Metadata Types In order to be able to create costs and processing times for the individual tasks in the order process and thus receive, for example, precise values regarding the costs of the process after the simulation, create the metadata types Costs_Task and Duration_Task. Proceed as follows 1. In the inubit Workbench, display the Configuration > Metadata Manager tab. 2. Click the left area, open the context menu and choose Add. The following dialog opens: a. Enter Duration_Task as the name and select the Duration data type. b. Click OK. The dialog closes and the new metadata type is displayed inubit Suite 6: Tutorials

45 Simulating Business Processes Defining Duration and Costs of Individual Tasks 45 Link metadata type with the BPD element Task 3. Click the left area again, and choose Add from the context menu. 4. This time, enter Costs_Task as the name and select the Costs data type. 5. Click OK to close the dialog. 6. Use the mouse to drag the two newly created metadata types one by one into the right area Allocation to the diagram elements and drop them on the BPD element Task : The metadata types are displayed underneath the Task element. 7. Press CTRL+S or alternatively click the button to save the assignment. The metadata types are now available in all Task elements in all BPDs Assigning Values to Costs and Duration of Tasks On the tasks in the Business Process Diagram, store concrete values for the designated costs and estimated time. Refer to Assigning Values to Metadata in Diagrams (Workbench: User Guide, chap. 17.4, p. 417). Proceed as follows 1. In the Designer, open the OrderProcess-1_unconfigured BPD for editing. 2. In the BPD of the order process, open the context menu of the Accept order task and choose Edit. 3. Select the Simulation tab and then the Costs and times tab. 4. Enter 50 for Costs_Task. inubit Suite 6: Tutorials

46 46 Simulating Business Processes Defining Material Resources 5. In the Duration_Task row, click the button. The dialog for specifying the duration of a task is displayed. 6. As the duration for the process of accepting the order, enter 20 minutes and close the dialog by choosing OK. 7. Close the Properties dialog. 8. Open the context menu of the Inform customer of heavy load order task and choose Edit. 9. Select the Simulation tab and then the Costs and times tab. 10. Enter 10 for Costs_Task. 11. As the duration for the process of informing the customer, enter 5 minutes and close the dialog by choosing OK. 12. Close the Properties dialog. 13. Publish the diagram and confirm the displayed confirmation prompt. 3.3 Defining Material Resources To be able to record purchase orders and send information to customers, the employees need office material, such as fax paper, to be able to perform their task. The material resources available for the process must be created centrally in the pool for tool and material resources so that they can be assigned to the individual tasks as required. Proceed as follows 1. In the Designer, open the OrderProcess-1_unconfigured BPD for editing. 2. Open the Simulation docking window in the sidebar. A blank table appears in which you enter the available office material: inubit Suite 6: Tutorials

47 Simulating Business Processes Defining Employee Resources for each Department To create new resources, click the button. 4. Enter Office material as the name and 500 as the number. 5. Click OK to close the dialog. 6. Publish the diagram. Also refer to - Configure the pool of material/tools (Workbench: User Guide, chap. 7, p. 191) - Initializing Resources with Technical Workflows (Workbench: User Guide, chap. 7, p. 189) 3.4 Defining Employee Resources for each Department In order to be able to realistically simulate your order process and, for example, be able to determine bottlenecks due to employee capacities, you have to configure the employee resources in the call center that are available in the process and configure them for each department or lane in material requirements planning. Both in the call center and in material requirements planning, 1 employee each with daily working hours from a.m. to 5.00 p.m. is available for handling the order process. Proceed as follows 1. Open the OrderProcess-1_unconfigured BPD for editing. 2. Select the Call center employee lane and choose Edit from the context menu. inubit Suite 6: Tutorials

48 48 Simulating Business Processes Defining Employee/Material Requirements per Task 3. Choose the Simulation tab. A dialog for employee configuration opens: This is where you enter the number of employees available to the department. In this case, the values for number of employees and weekly working hours entered by default correspond to the required values and you do not have to make any changes. 4. Click OK to close the dialog for employee configuration. 5. Publish the diagram. Since the order process is also staffed with 1 employee in material requirements planning, you can also leave the default values here. For detailed information about the configuration of employee pools, refer to the simulation documentation in Configure the pool of employees (Workbench: User Guide, chap. 7, p. 191). 3.5 Defining Employee/Material Requirements per Task You now define how many employees and how much office material are required for each task performed by employees inubit Suite 6: Tutorials

49 Simulating Business Processes Defining Employee/Material Requirements per Task 49 Proceed as follows 1. Open the OrderProcess-1_unconfigured BPD for editing. 2. Open the context menu of the Accept order task and choose Edit. 3. Choose the Simulation tab and then the Resources tab. The following dialog is displayed: 4. Leave the default number of employees as 1 because a call center employee accepts the incoming orders in the process. 5. Assign the employee the resource required to process this task and the amount in the form of an office material set for order acceptance. a. Click the button. A window for selecting the required resource opens: b. Select Office material and then click OK to close the dialog. inubit Suite 6: Tutorials

50 50 Simulating Business Processes Configuring the Order Volume c. In the Number column, enter the figure 1. For each order, the employee needs one set of office material. 6. Click OK to close the dialog. 7. Open the context menu of the Inform customer of heavy load order task and choose Edit. 8. Now repeat the last four steps starting with step 3 in order to assign the task an MRP and a set of office material. 9. Save your entries. 10. Publish the diagram. 3.6 Configuring the Order Volume The simulation process is determined by the order volume at the start of the order process. In this order process, the call center is supposed to receive 50 orders per day. To do so, you have to configure the number of process instances (here: orders) that are received within one day on the start event of the process. Proceed as follows 1. Open the OrderProcess-1_unconfigured BPD for editing. 2. Open the context menu of the start event and choose Edit. 3. Select the Simulation tab. A weekly view opens: inubit Suite 6: Tutorials

51 Simulating Business Processes Simulating the Order Process Hold down the left mouse button and draw the process exactly as shown in the following screenshot where the total number of orders received per day is 50, i.e. where the process is started 50 times. This should look as follows and have a total of 50 : 5. Activate the Same configuration for all days option because 50 orders are to be received each day. 6. Click OK to close the dialog. 7. Publish the BPD and confirm the confirmation dialog. Configure process instances at start events (Workbench: User Guide, chap. 6., p. 192) 3.7 Simulating the Order Process You have now completed all configuration steps in the diagram that are required for the simulation. The costs and times as well as material and employee resources for tasks that are performed by employees and the number of orders received per day are taken into account. Proceed as follows 1. Display the Business Process Diagram on the Designer > Server tab. 2. Open the Simulation docking window. inubit Suite 6: Tutorials

52 52 Simulating Business Processes Simulating the Order Process 3. Set the slider to the required speed (0 = very slow; 10 = very fast). The speed affects how fast the simulation is executed and how you can follow the process flow through the diagram as well as the display of markings. You can change the speed by moving the slider at runtime. You can also interrupt the simulation by clicking the Pause button and then restart it by clicking the Play button. 4. Activate the Resource-based option. 5. Leave the default settings for Start time. You want to start the simulation directly after activation and therefore do not have to make any changes here. 6. You want to simulate a period of 5 days for receiving 50 orders per day. Enter 5 days as the runtime: 7. Under Start options, choose Use input data configuration. You thus specify that the order volume per day defined on the start event is used as the basis for executing the simulation. Refer to Configuring the Order Volume (Tutorials, chap. 3.6, p. 50). 8. To start the simulation, execute one of the following actions: - Open the context menu of the element and choose Simulation > Start simulation. - Select the start element and click the button in the simulation toolbar of the menu bar. As soon as the simulation has been processed, you see the message Simulation finished. Unfinished processes: OrderProcess-1_unconfigured and the processed elements are highlighted in color and displayed with the following execution information: inubit Suite 6: Tutorials

53 Simulating Business Processes Simulating the Order Process 53 Reading execution information on elements The displayed information indicates that after running through the simulation not all received orders were processed and the order process could therefore not be finished completely. You can see initial reasons for the simulation result in the diagram by looking at the displayed execution information that is highlighted in color on the elements. On the Accept order task, the exclamation mark signals a resource bottleneck because there are not enough employees in the call center. On the Accept order task, there are still 100 unprocessed orders at the end of the simulation. At the end point of the process, after a simulation duration of 5 days, only 149 orders have been processed out of the 250 that have been received (50 orders per day on 5 simulation days). Refer to Execution information (Workbench: User Guide, chap. 7, p. 197) Displaying simulation results The simulation automatically generates a number of detailed results that are displayed in the Simulation results docking window and that enable you to get a detailed overview of the simulation result. Refer to Displaying Simulation Results (Workbench: User Guide, chap. 7.5, p. 199). inubit Suite 6: Tutorials

54 54 Simulating Business Processes Simulating the Order Process Since the process is unfinished, it might be possible that some activities still display unprocessed orders. These are listed in the reports in the category Theoretical results as end points and under the Actual results in the table Processing and waiting time. To show and analyze the decisive bottleneck in the employee resources in the call center in the result, look at the Workload event table, which shows the workload for all employees and reusable resources. Proceed as follows 1. Open the Simulation results docking window in the sidebar. 2. Choose the Graphical analysis tab. 3. Choose the Workload tab. You see that the decisive bottleneck in the order process is in the call center. The average workload of the available employee is 100%. This points to an overload of the resource while the other employee resource in materials requirements planning only has an average workload of 10%. The improvement in the order process should therefore aim primarily at easing the workload in the call center so that the order volume can be processed through a better workload for the employee resources and without a bottleneck inubit Suite 6: Tutorials

55 Simulating Business Processes Improving the Order Process 55 In the next step, improve the order process so that the workload of the employee resource in the call center is reduced. Continue with Improving the Order Process (Tutorials, chap. 3.8, p. 55) 3.8 Improving the Order Process After analyzing the simulation results, you now improve the order process so that the order volume is no longer received exclusively by the call center employee. The order process should no longer start with the order receipt via the call center employee. Instead, customers should be able to choose whether they wish to order through the call center or an online shop. Proceed as follows 1. Open the Business Process Diagram for editing. Create the Web shop as a new lane 2. Select the Call center employee lane and choose Add lane before from the context menu. A new lane with the standard name Lane is inserted above the selected lane. 3. Open the new lane for editing. The Properties dialog opens: 4. On the Element tab, enter Customer as the element name. 5. Delete the Sequence Flow between the Start time and the Accept order task in the Call center employee lane. 6. Drag the start point into the Customer lane. Create the order option as a gateway 7. Use the graphical context menu of the start time or the Tools docking window to insert a data-based, exclusive gateway after the start event. 8. To the right of the gateway, insert the task Order online. 9. For the Order online task, set the number of employee resources to 0 because this task is not performed by an employee. a. Open the Order online task for editing. b. Open the Simulation tab. c. Open the Resources tab. d. Set the number of employees to 0. e. Click OK to close the dialog. 10. Connect the start event with the gateway via a Sequence Flow. 11. Connect the gateway with the Accept order task as well as the Order online task using normal Sequence Flows. inubit Suite 6: Tutorials

56 56 Simulating Business Processes Improving the Order Process Create gateway before Determine weight Create probabilities for order options 12. Drag an exclusive gateway from the Tools docking window on the Sequence Flow between the Accept order and the Determine weight tasks. 13. Connect the Order online task with the the new gateway via a Sequence Flow. 14. Move the gateway located before the Determine weight task until it is located above the Determine weight task. 15. Connect the Order online task with the Determine weight task using a Sequence Flow. 16. On the Sequence Flows from the first gateway in the diagram to the two subsequent tasks, enter probabilities for the online order and the order via the call center. Through the new order option, we now assume that the probability that customers will order through the Web shop is 80% and only 20% of customers will order via the employee in the call center. a. Open the context menu of the connection from the gateway to the Order online task and choose Edit probability.... A dialog opens: b. Enter 80 as the probability. c. Click OK to close the dialog. d. Open the context menu of the connection from the gateway to the Accept order task and choose Edit probability.... e. Enter 20 as the probability. f. Click OK to close the dialog. g. Name the two Sequence Flows Probability. h. On the connection from the second gateway to the Inform customer of heavy load order task, enter the probability 15. i. On the connection from the second to the third gateway, enter the probability 85. Refer to Defining Probabilities for Execution Alternatives (Workbench: User Guide, chap. 7.6, p. 202). The result of the remodeled process should look like this: inubit Suite 6: Tutorials

57 Simulating Business Processes Simulating the Improved Order Process Publish the diagram. You can also directly display the improved order process. You can find it as the sample diagram OrderProcess-2 among the example diagrams for the simulation, refer to Using Example Diagrams and Users (Tutorials, chap. 1.3, p. 13) 3.9 Simulating the Improved Order Process Now simulate the improved order process again to see improved results displayed. You can also use the sample diagram OrderProcess-2 to simulate the improved process, refer to Using Example Diagrams and Users (Tutorials, chap. 1.3, p. 13). inubit Suite 6: Tutorials

58 58 Simulating Business Processes Simulating the Improved Order Process Simulating To simulate the improved process, you proceed in exactly the same way as in the prior simulation of the process modeled originally. Proceed as follows Refer to Simulating the Order Process (Tutorials, chap. 3.7, p. 51). After processing the simulation, the system displays the message Simulation finished successfully! and the processed elements are highlighted in color and displayed with the following execution information: Displaying improvements on elements The displayed information Simulation finished successfully indicates that after running through the simulation all received orders were processed and the order process could therefore be finished completely. For details about the simulation result, refer to the diagram by looking at the execution information that is displayed in color on the elements inubit Suite 6: Tutorials

59 Simulating Business Processes Simulating the Improved Order Process 59 There are no unprocessed orders on any task. This would be indicated by a circle in the bottom left corner of a task where the corresponding number would also be displayed. There are no more resource bottlenecks. This would be signalized by an exclamation mark in the top right corner of a task. At the end of the process, all orders have been processed. In a circle at the end point, 250 executed process instances are displayed, which corresponds exactly to the number of orders received (50 orders per day on 5 simulation days). Refer to Execution information (Workbench: User Guide, chap. 7, p. 197). Displaying improved simulation results You can also display a detailed report of the simulation results for the simulation of the improved process. Refer to Displaying Simulation Results (Workbench: User Guide, chap. 7.5, p. 199). Proceed as follows 1. Open the Simulation results docking window in the sidebar. 2. Select the Actual results tab. inubit Suite 6: Tutorials

60 60 Simulating Business Processes Simulating the Improved Order Process You see that the decisive bottleneck in the order original process was in the call center. The employee there had an average workload of 100% and was therefore overburdened, which is why many of the incoming orders got stuck at this point in the process. After remodeling the order process, this overload of the employee resource has been reduced by the new order option in the Web shop and the order volume can be processed without a bottleneck. As planned, the decisive improvement in the order process is primarily in the reduction of the workload in the call center. Overall, the Web shop option has managed to achieve, for example, improvements in the employee resources (better workload) and processing times of the process as well as savings in material resources (lower consumption of office material): inubit Suite 6: Tutorials

61 4 Creating a Data-Centric Business Solution 61 This section details the following topics: Basics, p. 62 Creating a Domain Model in the WebModeler, p. 63 Creating Classes and Defining the Root Instance, p. 65 Adapting Relationships and Adding Associations, p. 67 Defining Attributes for Classes, p. 69 Deploying and Activating the Domain Model, p. 71 Creating Business Objects, p. 73 Assigning Business Objects: Establishing Relationships, p. 76 Creating a View for all Business Objects of the Vehicle Class, p. 78 Adding the FleetManagement Business Solution to the Menu, p. 81 Closing the Solution Center, p. 83 Prerequisites You have installed one of the following installation sets: - Solution Center - Full installation You have uploaded a valid license. Information about the installation and adding of Solution Center and WebModeler portlets is available in the Quick Start, refer to Installing from DVD (Quick Start, chap. 2, p. 4). Use You use the Solution Center to create business solutions. Business solutions are data-centric, web-based applications in which you can manage business objects, such as customers, invoices or purchase orders. The Solution Center is available as a portlet in the inubit Enterprise Portal. About this tutorial This tutorial uses an exemplary domain model Fleet Management to explain working with the Solution Center and guides you to the finished business solution step-by-step. Execute the steps in this tutorial in the specified order. inubit Suite 6: Tutorials

62 62 Creating a Data-Centric Business Solution Basics 4.1 Basics Business objects You use a business solution to manage business objects. Business objects represent real life business objects, for example, a vehicle or sales contract of a fleet management company. For each individual vehicle and each purchase contract invoice, a separate business object is created, which contains the individual vehicle or contract data. Business objects are related to each other: For example, each contract is clearly assigned to one vehicle and each vehicle can have a contract. Technically speaking, business objects are instances of a class. You create business objects in the Solution Center in your business solution. Classes The class to which the business object belongs determines which data a business object can contain and which relationships it can have with other business objects. All business objects of the same type, for example, all purchase contracts belong to the same class, e.g. the Contract class. This class thus forms a template for the individual business objects, i.e. the actual purchase contracts. Attributes The information which data a contract contains is defined as properties of the class, also called attributes. The Vehicle class can, for example, have the attributes Chassis Number and Vehicle Type. The relationships between the classes are called associations. The attributes and associations of a class are automatically inherited by the corresponding business objects. In addition to a simple association, e.g. A contract refers to exactly one vehicle, there are the following special cases: Aggregation Aggregations describe partial/whole relationships, e.g. the relationship between a fleet, which represents the whole, and the vehicles that belong to the fleet and are therefore part of the fleet. Compositions Compositions also describe part/whole relationships with the distinction that parts existentially depend on the whole, like e.g. the relationship between a vehicle and its individual parts. Inheritance An inheritance relationship exists, e.g. between the higher class Contract and the two sub-classes Sales contract and Leasing contract inubit Suite 6: Tutorials

63 Creating a Data-Centric Business Solution Creating a Domain Model in the WebModeler 63 Domain model All classes together form the domain model. A domain model is therefore a formal description of all business objects of a certain business solution, for example: You create the domain model with its classes in this tutorial in the WebModeler of the inubit Suite 6. Domain: Domain model plus views Once you have completed your domain model, you deploy it as a domain in the Solution Center. In addition to the domain model, this domain also includes views. In the Solution Center, a view is automatically created for each class. This view is called the generic view. This view is a form in which business objects are displayed and maintained. In addition, you can create your own individual view for each class to facilitate the entering and editing of business objects for the key users for the business solution. Proceed with section Creating a Domain Model in the WebModeler (Tutorials, chap. 4.2, p. 63). 4.2 Creating a Domain Model in the WebModeler Proceed as follows 1. In the inubit Enterprise Portal, display the WebModeler page. 2. Click New. A context menu opens. inubit Suite 6: Tutorials

64 64 Creating a Data-Centric Business Solution Creating a Domain Model in the WebModeler 3. Choose the Domain Model entry: In the WebModeler, a blank work area is displayed: 4. On the right, in the Basic Properties area, fill out the following input fields: - author: Enter your name. - name: Call your domain model Fleet Management. This name must be unique in Solution Center since it is also used as the name of the business solution. - namespaceprefix: Enter FMgmt. - namespaceuri: Enter 5. In the toolbar, click Save to save the domain model. A confirmation prompt appears. 6. In the confirmation prompt, click Save again. The dialog closes. The blank domain model has been saved. Proceed with section Creating Classes and Defining the Root Instance (Tutorials, chap. 4.3, p. 65) inubit Suite 6: Tutorials

65 Creating a Data-Centric Business Solution Creating Classes and Defining the Root Instance Creating Classes and Defining the Root Instance In this section, you model your domain model by creating classes and defining a class as the root instance. Proceed as follows 1. Drag the class icon from the left area to the work area. 2. In the Basic Properties area, adjust the properties of the new class as follows: - Text: Enter FleetManagement and finish the entry by pressing ENTER. The new name is displayed in the new class. - Stereotype: Choose root_instance from the list. The name of the class is highlighted in orange. 3. Click the root-instance class. A graphical context menu appears. 4. Point the mouse to the arrow icon. A class icon is displayed: 5. Click the class icon. Another class is inserted and automatically connected to the root-instance class via a composition relationship. 6. Drag the class to the following position: inubit Suite 6: Tutorials

66 66 Creating a Data-Centric Business Solution Creating Classes and Defining the Root Instance You will change the relationship type later. 7. Give the class a name: a. Select the new class. b. In the Text field in the Basic Properties area, enter the name Vehicle. c. Press ENTER to save your input. 8. Select the root-instance class and insert a Contract class. Defining an abstract class 9. The Contract class is to be defined as an abstract class so that no business objects can be derived directly from this class. The only purpose of this tasks is to bequeath its attributes and associations to sub-classes. a. Select the Contract class. b. In the Basic Properties area, select the Abstract option. The class name Contract is displayed in italics. 10. Select the Contract class and insert the following two classes one after the other: - Sales contract - Lease contract 11. Position the classes as in the following figure: inubit Suite 6: Tutorials

67 Creating a Data-Centric Business Solution Adapting Relationships and Adding Associations 67 Proceed with section Adapting Relationships and Adding Associations (Tutorials, chap. 4, p. 67). 4.4 Adapting Relationships and Adding Associations Next, you adapt the existing relationships and define an association between Vehicle and Contract. Proceed as follows Creating aggregations 1. Click on the relationship between FleetManagement and Vehicle. 2. In the Basic Properties area, select the composition option. On the relationship, a blank diamond shape is now displayed instead of filled one: The blank diamond shape signalizes that the relationship is an aggregation and that there is thus a part/whole relationship between the two classes. inubit Suite 6: Tutorials

68 68 Creating a Data-Centric Business Solution Adapting Relationships and Adding Associations 3. Repeat this action for the connection between root-instance and Contract. Creating an association 4. To create an association, proceed as follows: a. Press the SHIFT key and hold it down. b. Use the mouse to drag the Vehicle class onto the Contract class until this has a green frame. c. Release the SHIFT key and the mouse button. The two classes are now connected via a composition relationship with a filled diamond shape icon. d. Select the composition relationship. A graphical context menu appears. e. Click on the wrench icon to be able to edit the relationship. A menu opens. f. Choose Association. The relationship is changed to an aggregation. An arrow icon is displayed, which points to the Contract class: The association is now a directed association and expresses that there is a relationship between Vehicle and Contract, for example, A vehicle has a contract. Creating inheritances 5. The two classes Sales contract and Lease contract are supposed to inherit attributes and relationships from the Contract class. To change the existing composition relationships, proceed as follows: a. Select one of the two relationships: The graphical context menu appears. b. Click the wrench icon. A menu opens. c. Choose Inheritance. d. Repeat these steps for another relationship. Your domain model should now look like this: inubit Suite 6: Tutorials

69 Creating a Data-Centric Business Solution Defining Attributes for Classes 69 Proceed with section Defining Attributes for Classes (Tutorials, chap. 4, p. 69). 4.5 Defining Attributes for Classes You now create the attributes of the classes. By doing so you specify which information the corresponding business objects are supposed to receive later. Proceed as follows 1. Select the Vehicle class. 2. Click the pen icon. The dialog for adding and editing attributes opens: inubit Suite 6: Tutorials

70 70 Creating a Data-Centric Business Solution Defining Attributes for Classes 3. On the Attributes tab, click. In the table, a new attribute is displayed. 4. Add a second attribute. 5. To change the attribute name, double-click the Name field; you select the attribute type from the list. Set the following values: Leave the Multiplicity and Default fields unchanged. The small red triangles in the fields signalize that the values have not been saved yet. 6. Click OK to save the attributes and close the dialog. 7. Define the following attributes for the other classes: - Contract class: - Name: ContractNumber, Type: text - Name: Checked, Type: boolean - Sales contract class: Name: Purchase date, Type: date - Lease contract class: Name: LeaseType, Type: text Your domain model now looks like this: inubit Suite 6: Tutorials

71 Creating a Data-Centric Business Solution Deploying and Activating the Domain Model 71 Proceed with section Deploying and Activating the Domain Model (Tutorials, chap. 4.6, p. 71). 4.6 Deploying and Activating the Domain Model Proceed as follows 1. In the toolbar, click Save. The confirmation prompt appears. Since you are now saving the model for the second time, the Save as new option is active. 2. Click Save. Your current domain model is saved as a new version. Deploying the domain model 3. You now deploy the domain model. In doing so, a domain is generated in the Solution Center: a. In the toolbar, click. The following dialog opens: b. Click Submit. Deployment starts. As soon as your domain model is deployed a corresponding message is displayed. inubit Suite 6: Tutorials

72 72 Creating a Data-Centric Business Solution Deploying and Activating the Domain Model c. Click OK to close the message. Activating the domain 4. You now activate your domain. This generates the desired business solution: a. Display the Solution Center page. b. In the object browser, in the Solution Center Home > Domain Library folder, select your FleetManagement domain. c. At bottom right, click. As soon as the domain is activated, a corresponding message is displayed. Your new business solution is now displayed in the folder Solution Center Home > Solutions > FleetManagement : inubit Suite 6: Tutorials

73 Creating a Data-Centric Business Solution Creating Business Objects 73 If your business solution is not displayed, press F5 to refresh the view. Proceed with section Creating Business Objects (Tutorials, chap. 4.7, p. 73). 4.7 Creating Business Objects In this section, you create the business objects that represent the vehicles and contracts in the Solution Center. Proceed as follows 1. In the Solution Center Home > Solutions folder, click your FleetManagement business solution. Creating the LeaseContract_Miller business object 2. In the toolbar, click to switch to Edit mode: 3. In the Outgoing Associations area, next to the Contract entry, click. A context menu opens. Choose the FMgmt:LeaseContract entry: The FMgmt prefix corresponds to the value of the Namespace- Prefix attribute that you have defined in the WebModeler. inubit Suite 6: Tutorials

74 74 Creating a Data-Centric Business Solution Creating Business Objects A new business object called New Lease contract is created (blue font). 4. Click the name. A text field opens. 5. Call the new contract LeaseContract_Miller. 6. Point the mouse to the new business object. A graphical context menu appears above the object: 7. Click the arrow icon. The properties of the new business object are displayed: In the object browser, the new business object is displayed underneath your FleetManagement business solution. If this is not the case, press F5. 8. Now enter the data for LeaseContract_Miller : a. In the Properties area, click in the first row next to the Checked property. A checkbox appears. Select it. b. Enter a value for the ContractNumber. c. Specify the LeaseType. The result looks like this, for example: inubit Suite 6: Tutorials

75 Creating a Data-Centric Business Solution Creating Business Objects 75 The red triangles signalize that the entries have not been saved yet. 9. At the bottom right, click Apply to save the changes. 10. Repeat step 1 to step 9 to create the following business objects: - SalesContract SalesContract_Smith a. Next to the Contract(s) entry, click. b. From the context menu, choose the FMgmt:SalesContract entry. c. Call the object SalesContract_Smith. d. Fill the object with data. e. Save the changes. - Vehicle Mercedes01 a. Next to the Vehicle(s) entry, click. b. From the context menu, choose the FMgmt:Vehicle entry. c. Call the object Mercedes01. d. Fill the object with data. e. Save the changes. - Vehicle Mercedes02 Create a second vehicle called Mercedes Click OK to close edit mode. Since you have not defined any specific views yet, the objects are displayed in generic views. If you have created all contracts and vehicles and select the FleetManagement folder, your business solutions should look as follows: inubit Suite 6: Tutorials

76 76 Creating a Data-Centric Business Solution Assigning Business Objects: Establishing Relationships If the new objects are not displayed in the object browser, press F5 to refresh the view. Proceed with section Assigning Business Objects: Establishing Relationships (Tutorials, chap. 4.8, p. 76). 4.8 Assigning Business Objects: Establishing Relationships In this section, you assign every vehicle business object to a contract business object according to the relationships defined for the Contract and Vehicle classes in your domain. Proceed as follows 1. In the object browser, in the Solution Center > Solutions > FleetManagement folder, click the business object LeaseContract_Miller. The detail view appears. 2. In the toolbar, click Edit to activate edit mode. 3. In the Incoming Associations area, next to the Vehicle(s) entry, click. The following dialog opens: This dialog displays all business objects that can be connected to the current business object; according to the relationships between the classes that are defined in your domain. 4. Select the vehicle Mercedes01. The dialog closes. In the Incoming Associations area, the object Mercedes01 is displayed next to the Vehicle(s) entry: inubit Suite 6: Tutorials

77 Creating a Data-Centric Business Solution Assigning Business Objects: Establishing Relationships Click Apply to save the changes. 6. In the object browser, select the business object SalesContract_ Smith and assign the second vehicle to this contract. 7. Click OK to save the changes and close edit mode. The outgoing associations, i.e. the vehicles' relationships to the contracts are created automatically. In the object browser, click on a vehicle object to display its associations, for example: inubit Suite 6: Tutorials

78 78 Creating a Data-Centric Business Solution Creating a View for all Business Objects of the Vehicle Class Proceed with section Creating a View for all Business Objects of the Vehicle Class (Tutorials, chap. 4.9, p. 78). 4.9 Creating a View for all Business Objects of the Vehicle Class In this section, you create a new view that is displayed as the default for all business objects of the Vehicle class instead of the automatically generated generic view. Views You can create separate views for each class to facilitate the creation and editing of business objects and give them an individual look and feel. The easiest way to create a view is in View Designer, provided an example business object already exists for the class in question. A view always consists of at least a section element, e.g. a list, a data sheet or a tab in which the data of the business object is displayed. You can also add a header using the header element. Proceed as follows 1. In the object browser, select the folder Solution Center Home > Solutions > FleetManagement > Mercedes In the toolbar, click View. A menu opens inubit Suite 6: Tutorials

79 Creating a Data-Centric Business Solution Creating a View for all Business Objects of the Vehicle Class Choose Create New View. A dialog opens. 4. Enter the following name: Leave all other entries unchanged. 5. Click OK. The dialog closes and View Designer opens: inubit Suite 6: Tutorials

80 80 Creating a Data-Centric Business Solution Creating a View for all Business Objects of the Vehicle Class Adding a header 6. From the top left area, drag the Header element into the right area View Structure and drop it on the (view) element as soon as a green plus icon and the text 1 selected row are displayed. The result looks like this: 7. Click the Header (section) element. 8. In the bottom left area Vehicle, click the Eigenschaften tab. 9. Drag the Title element into the View Struktur area and drop it on the Header (section) element. The element is displayed underneath Header (section). The following header is now displayed in the center part of View Designer: Defining header properties Adding a data sheet Adding an association 10. Click on the Title (atomic value) element. In the bottom right Title (atomicvalue) area, you can now define the properties of the title. Change these as follows: - Hide the label: Set labelhidden to true. - Protect the header from changes: Set readonly to true. The label is hidden in the center part of View Designer. 11. From the top left area, drag the Factsheet element into the View Struktur area and drop it in the (view) folder. In the central area, another area is displayed: the fact sheet. 12. Select the Factsheet element. 13. In the bottom left area, in the Value column, change the value for label to Vehicle Details. 14. In the bottom left area Vehicle, click the Eigenschaften tab. 15. Drag the following elements into the View Struktur area and drop them onto the Vehicle Details (section) entry, one after the other: - Title - VehicleNumber - VehicleType - Description 16. In the bottom left area Vehicle, click the Assoziationen tab inubit Suite 6: Tutorials

81 Creating a Data-Centric Business Solution Adding the FleetManagement Business Solution to the Menu Drag the Contract association into the View Struktur area and drop it onto the Vehicle Details (section) entry. A window for adding a (list) view appears. 18. In the bottom selection list, choose Csv and click OK. 19. In View Designer, click Übernehmen at the bottom right. The result looks like this: 20. To save this in View Designer, click OK at the bottom right. The dialog closes. All business objects of the Vehicle class are now displayed in the view you just created. To test this, click the business object Mercedes01, for example. If the new view is not displayed immediately, press F5 to refresh the view. In Edit mode you can also edit the attribute values and associations. Proceed with section Adding the FleetManagement Business Solution to the Menu (Tutorials, chap. 4.10, p. 81) Adding the FleetManagement Business Solution to the Menu In this section, you add a new menu item to the accordion menu in the object browser. This new item will give you a convenient way to call up your business solution. Proceed as follows 1. In the object browser, in the Solution Center Home > Solutions folder, click your FleetManagement business solution. 2. Open the context menu and choose Add to Menu. The following dialog opens: inubit Suite 6: Tutorials

82 82 Creating a Data-Centric Business Solution Adding the FleetManagement Business Solution to the Menu 3. In the Menu Name field, enter the name under which your business solution is supposed to be displayed in the menu, e.g. FleetManagement. 4. Click OK. The dialog closes. At the bottom of the object browser, an additional item called FleetManagement is displayed in the accordion menu inubit Suite 6: Tutorials

83 Creating a Data-Centric Business Solution Closing the Solution Center 83 For information about closing the Solution Center, refer to Closing the Solution Center (Tutorials, chap. 4.11, p. 83) Closing the Solution Center Proceed as follows 1. In the inubit Enterprise Portal, click Log off. The log off process starts; following that the login page is displayed again. You can now close the browser if you wish. 2. Close the inubit Process Engine. Installation set Full installation: Only close the inubit Process Engine when you no longer wish to work with other components of the inubit Suite 6, e.g. the Workbench. inubit Suite 6: Tutorials

84 84 Creating a Data-Centric Business Solution Closing the Solution Center - Windows: In the start menu, choose Start > [All] Programs > Solution Center Program Group > Stop Process Engine. - Linux: Start the script <SC Program Directory>/server/ Tomcat/bin/shutdown.sh inubit Suite 6: Tutorials

85 5 Creating a Process Solution 85 This section details the following topics: Basics, p. 85 Creating a Business Process Diagram (BPD) in the Workbench, p. 86 Expanding the Business Object Diagram (BOD), p. 89 Submitting Leave Applications, p. 99 Approving an Application for Leave, p. 101 Prerequisites You have installed one of the following installation sets: - Full installation You have loaded a valid license. Information about installation and adding Solution Center portlets is available in the Quick Start; refer to Installing from DVD (Quick Start, chap. 2, p. 4). Use Process solutions are process-centered, web-based applications in which processes such as creating and approving positions, purchase requisitions, applications for leave, and rental applications can be mapped using automatically generated workflows. The Solution Center is available as a portlet in the inubit Enterprise Portal. About this tutorial This tutorial uses the exemplary Business Process Diagram Application for Leave to show how an application for leave is submitted by the employee and how this application is approved by the supervisor. It takes you step by step from the creation of the BPD in inubit Suite 6 to the finished process solution in the Solution Center. Execute the steps in this tutorial in the specified order. 5.1 Basics Transactional data A process solution is primarily used for the administration of transactional data. Transactional data results from processes such as filling a position, a purchase requisition, an application for leave, or a rental application. inubit Suite 6: Tutorials

86 86 Creating a Process Solution Creating a Business Process Diagram (BPD) in the Workbench In each process there are several roles involved (applicant, reviewer) that are created using the lanes of a pool in a Business Process Diagram. <Process>BO Top class for the business objects of the process generated automatically from the name of the pool in the BPD. <Process>Homepage Homepage for the process in Solution Center generated automatically from the name of the pool in the BPD. bfm3 Prefix of the classes that are automatically linked with the BPD and are part of the scope of delivery. More information about the business objects, classes, attributes, etc., is available in the tutorial Creating a Data-Centric Business Solution (Tutorials, chap. 4, p. 61). Refer to Basics (Tutorials, chap. 4.1, p. 62). Start with the creation of a BPD. Refer to Creating a Business Process Diagram (BPD) in the Workbench (Tutorials, chap. 5.2, p. 86). 5.2 Creating a Business Process Diagram (BPD) in the Workbench This section details the following topics: Creating a BPD as a Solution Center Process Model, p. 86 Defining the Process, p Creating a BPD as a Solution Center Process Model Proceed as follows 1. Open the Designer in the Workbench. 2. Create a new Business Process Diagram. 3. Enter a name and a group inubit Suite 6: Tutorials

87 Creating a Process Solution Creating a Business Process Diagram (BPD) in the Workbench Go to the Business Process Diagram tab. 5. Choose the option Solution Center process model. Leave all predefined values unchanged. 6. Click Finish. The new BPD is displayed with a predefined pool and three lanes. inubit Suite 6: Tutorials

88 88 Creating a Process Solution Creating a Business Process Diagram (BPD) in the Workbench Continue with section Defining the Process (Tutorials, chap , p. 88) Defining the Process In this section you create the process model. Proceed as follows 1. Name the lane Role1 in Employee. 1. Name the lane Role2 in HR manager. 2. Name the start event in New application for leave. 3. Add to the BPD as shown in the following screenshot. Configure the two tasks for the roles Employee and HR manager as task (user) inubit Suite 6: Tutorials

89 Creating a Process Solution Expanding the Business Object Diagram (BOD) 89 The optionally available inubit process package Build+ simplifies the creation of BPDs through several included templates. Then you expand the automatically generated Business Object Diagram. Expanding the Business Object Diagram (BOD) (Tutorials, chap. 5, p. 89). 5.3 Expanding the Business Object Diagram (BOD) This section details the following topics: Adding the Enumeration Class for the Vacation Type, p. 90 Linking External Class Person, p. 91 Adding Attributes for the Class ApplicationForLeaveBO, p. 93 inubit Suite 6: Tutorials

90 90 Creating a Process Solution Expanding the Business Object Diagram (BOD) Publishing the BOD, Validating and Publishing the BPD, p. 94 Adapting the Process Solution, p. 95 When you create a Solution Center process model, a linked BOD diagram is generated automatically. You only need to add your specific classes and links to existing external classes Adding the Enumeration Class for the Vacation Type Proceed as follows 1. Hold down the CTRL key while carrying out step 2 below. 2. In the lane is Engine, double-click the link icon of the data object ApplicationForLeaveBO. The generated BOD is displayed: 3. Open the Tools docking window and drag a new class into the Master data frame from the Tools area. 4. Name the class Type of vacation. 5. Choose the option Simple type / Enumeration. 6. Click the Add entry icon. 7. Enter the name of the vacation type. 8. Repeat step 6 and step 7 for two additional vacation types: inubit Suite 6: Tutorials

91 Creating a Process Solution Expanding the Business Object Diagram (BOD) Click OK to close the dialog for defining classes. Your BOD should now look like this: Continue with linking of the external class Person. Linking External Class Person (Tutorials, chap. 5, p. 91) Linking External Class Person In base schema BusinessFoundationModel3.xsd, the Person class is predefined, which you can use in your diagram. inubit Suite 6: Tutorials

92 92 Creating a Process Solution Expanding the Business Object Diagram (BOD) Proceed as follows 1. On the right side of the External elements docking window, open the Base schemas tab. 2. Open the schema BusinessFoundationModel3.xsd. 3. Drag the class bfm3:person into the master data area Open the Tools area on the right side of the Tools docking window. 5. Click the Association button. 6. Hold down the SHIFT key while you carry out step Drag the class ApplicationForLeaveBO to the bfm3:person class in the Master data area. This class is used for selecting a vacation replacement for the applicant. 8. Name the association Vacation replacement. Your BOD now looks like this: inubit Suite 6: Tutorials

93 Creating a Process Solution Expanding the Business Object Diagram (BOD) 93 Add the attributes to the class ApplicationForLeaveBO. Refer to Adding Attributes for the Class ApplicationForLeaveBO (Tutorials, chap , p. 93) Adding Attributes for the Class ApplicationForLeaveBO Proceed as follows 1. Open the ApplicationForLeaveBO class for editing. 2. Click the Add attribute icon. 3. Name the attribute Vacation from. 4. Select the type date. 5. Select the multiplicity Click OK to close the attribute dialog. 7. Repeat step 2 to step 6 with the following information: - Name: Vacation to, type: date, multiplicity: 1 - Name: Type of Vacation, type: afl:typeofvacation, multiplicity: 1 inubit Suite 6: Tutorials

94 94 Creating a Process Solution Expanding the Business Object Diagram (BOD) - Name: Comment, type: string, multiplicity: 0..1 Continue on with the publishing of the BOD and the validation of the BPD. Refer to Publishing the BOD, Validating and Publishing the BPD (Tutorials, chap , p. 94) Publishing the BOD, Validating and Publishing the BPD Proceed as follows 1. Select the created BOD on the Local tab. 2. Publish the diagram. 3. Go to the Local tab. 4. Display the Application for Leave BPD. 5. Click the Validate icon. 6. Publish the BPD using the menu item Edit > Publish. 7. Click the Solution Center deployment button to deploy the diagram in the Solution Center. A dialog for selection of the deployment steps is displayed inubit Suite 6: Tutorials

95 Creating a Process Solution Expanding the Business Object Diagram (BOD) Leave the settings unchanged and click Perform selected actions. Next you adapt your new process solution in the Solution Center. Refer to Adapting the Process Solution (Tutorials, chap , p. 95) Adapting the Process Solution In diesem Abschnitt erstellen Sie für Ihre Solution einen Menüeintrag und passen die Ansicht an. Prerequisites You have added the Solution Center portlet to your Enterprise Portal. Refer to Activating the Solution Center and the WebModeler (Install Sets Full Installation, Modeling Center, Solution Center) (Quick Start, chap. 10, p. 11). In the Enterprise Portal, you have assigned the users to the roles in use (James Smith: role HR manager, Bob Brown and Max Miller: role Employee ). Refer to Assigning Users to an Organization, a Community or a Role (inubit Process Engine: Administrator and Developer Guide, chap , p. 208). inubit Suite 6: Tutorials

96 96 Creating a Process Solution Expanding the Business Object Diagram (BOD) Create menu entry Proceed as follows 1. Log on to the Enterprise Portal as administrator James Smith (login: root, password: inubit) (standard address: localhost:8000). 2. Go to the page with the Solution Center portlet. 3. In the object browser, navigate to the homepage of your process solution in the folder Solution Center Home > Solutions > Business Foundation > ApplicationForLeaveHomepage. 4. Open the context menu for the process solution homepage and select the menu item Add to menu. 5. In the field Menu name, select an existing menu or enter the name HR processes to recreate this menu. 6. In the Name field, enter Application for leave as the name of the new menu entry. The new menu appears in the menu bar of the Solution Center. Start new (test) process Proceed as follows 1. In the HR processes menu, select the Application for leave menu item to go to the homepage of your process solution. 2. Start the new (test) leave application process by clicking the button New application for leave. A new business object for a leave application is created. 3. Click the Edit button on the toolbar to switch to editing mode. 4. Name the new leave application. 5. Click Save to save the changes and leave edit mode inubit Suite 6: Tutorials

97 Creating a Process Solution Expanding the Business Object Diagram (BOD) 97 Adapt view 1. Select the Edit current view menu item from the View menu. The View Designer opens. 2. In the View Structure area, click Expand all. 3. Navigate to the Process data node. 4. In the lower left area of the Properties tab, click the column header Defined on to sort the column in ascending order so that the entries with the prefix afl are at the top of the table. 5. Use the mouse to select all four entries with the prefix afl while holding down the CTRL key. inubit Suite 6: Tutorials

98 98 Creating a Process Solution Expanding the Business Object Diagram (BOD) 6. Drag and drop the selected entries on the Process data (section) node in the View Structure area. 7. Move the Comment node to the last position. 8. Click the Type of Vacation node in the View Structure area. 9. In the area with the element properties (lower right), select the value enum_dropdown for the attribute viewstyle. 10. In the View Structure area, select the Process data node. 11. Drag the entry Vacation replacement from the Associations tab onto the Process data (section) node in the View Structure area. The Views for linked objects dialog opens. 12. Select Create new view and give it a name. 13. Select the CSV view type for comma-separated enumeration. 14. Click OK. Your preview and the structure of the view should appear as follows: inubit Suite 6: Tutorials

99 Creating a Process Solution Submitting Leave Applications Click OK to save the view and switch to view mode. Next you enter the data for a leave application of an employee. Refer to Submitting Leave Applications (Tutorials, chap. 5.4, p. 99) Submitting Leave Applications After you have defined the attributes to be displayed in the view, you can enter and send the data for leave applications. The entries then appear in the task list of the HR manager, who can approve or reject them. Proceed as follows 1. Log off as James Smith and log on as Bob Brown. 2. Select the menu item Application for leave in the HR processes menu to switch to the homepage of your process solution. 3. Click the New application for leave button. 4. Entering the leave data a. Name the new leave application. b. In the Type of Vacation field, select the type of vacation. c. In Vacation from field, enter the first day of the vacation. d. In Vacation to field, enter the last day of the vacation. e. In the Comment field, enter a comment. f. Click the plus icon next to the Vacation replacement field name to select a person as a vacation replacement. inubit Suite 6: Tutorials

100 100 Creating a Process Solution Submitting Leave Applications 5. Click Send to save the application and send the approval to the HR manager. The following options are also available: - Apply: Save the application data, make changes later, and then send - Cancel: Cancel the process without saving 6. Log off as Bob Brown and log on as James Smith. 7. Select the menu item Application for leave in the HR processes menu to switch to the homepage of your process solution. 8. Start a new process by clicking the button New application for leave and repeat step Click Apply. The application remains in the task list for further processing. Next you open the task list of James Smith. Refer to Approving an Application for Leave (Tutorials, chap. 5.5, p. 101) inubit Suite 6: Tutorials

101 Creating a Process Solution Approving an Application for Leave Approving an Application for Leave Proceed as follows 1. Navigate to the folder Solution Center Home > Solutions > Business Foundation > James Smith. The task list of the HR manager is displayed. For the Employee role, the application submitted by James Smith appears; for the HR manager role, the application for leave of Bob Brown appears for approval. 2. Click the icon at the beginning of the Approve application for leave line. The application is displayed. inubit Suite 6: Tutorials

102 102 Creating a Process Solution Approving an Application for Leave 3. Click Approve to approve the application. The attendance record is updated in the workflow, and the application is assigned the status Approved in Bob Brown s task list. Now other users can record their leave applications, and the HR manager can reject or approve them inubit Suite 6: Tutorials

103 6 Integrating Systems and Automating Processes 103 This section details the following topics: Application Example, p. 104 Creating a Technical Workflow 1: Reading a File from the File System, p. 106 Testing the Workflow, p. 108 Creating a Technical Workflow 2: Converting a CSV File to CSV- XML, p. 110 Creating a Technical Workflow 3: Converting CSV-XML to opentrans, p. 111 Excursus: XSLT, p. 121 Creating a Technical Workflow 4: Storing the File in the File System, p. 122 End-to-End Navigation: Connecting Technical Level with Business Level, p. 123 There are example diagrams for all tutorials in the inubit Suite 6, refer to Using Example Diagrams and Users (Tutorials, chap. 1.3, p. 13). Prerequisites You have already installed one of the following installation sets: - Full installation - Process Center - Integration Center You have added a valid license. For information about the installation refer to the Quick Start, Installing from DVD (Quick Start, chap. 2, p. 4). You have logged in to the inubit Workbench with the user miller in order to access to the example diagrams. Refer to Using Example Diagrams and Users (Tutorials, chap. 1.3, p. 13). Enterprise Application Integration The inubit Suite 6 enables the automation of business processes, incorporating internal IT systems, employees, external customers, and partners. Numerous standard modules and support for a large number of communication protocols enable the direct integration of systems such as SAP and databases. The individual modules are assembled into Technical Workflows in a workflow designer using Drag n Drop. Error branches, alternative connectors, and error scopes enable error situations to be handled easily; functions range from notification via , SMS, or SNMP to complex error workflows. The Technical Workflows can be closely linked with the business process diagrams. inubit Suite 6: Tutorials

104 104 Integrating Systems and Automating Processes Application Example Converting data The handling of data in Technical Workflows is universally based on XML. Format adapters convert non-xml to XML and vice versa. Inhouse formats can be freely defined in a flat file adapter and used. The data structures are depicted in a converter using Drag n Drop. This converter returns standard-compliant XSLT. The XSLT converter provides an integrated test environment along with checks against schemas and DTDs. Navigation and debugging You can navigate in a top-down way from the technical business process to the technical implementation in a Technical Workflow to classify errors that occur during routine operation. The integrated test environment enables the convenient debugging of the Technical Workflows; the transfer of workflows from the development to the production system is supported by the integrated deployment process. Running workflows can be monitored in real time in watch mode. Refer to - Technical Workflow Diagrams (Workbench: User Guide, chap. 12, p. 269) - XSLT Converter (Data Converter) (Workbench/Process Engine: Modules Guide, chap. 5, p. 125) - Testing with inubit Suite 6 (Workbench: User Guide, chap. 16, p. 379) 6.1 Application Example A Technical Workflow is the technical implementation of a business process. It contains one or more modules that fetch messages from a source system or receive messages from a source system, convert and modify them, and then pass them to a subsequent target system. The system connectors are responsible for communication between the source and target systems and the inubit Suite 6. Numerous adapters and converters are available for converting and modifying messages. The order in which the modules are executed is defined by the workflow control. The workflow control also defines the conditions under which a module is executed and how often it is executed. The execution of a workflow does not have to be linear - branches and loops are possible. In addition to simple 1:1 transformations that convert an input message to an output message, the use of workflow controls such as multiplexers and demultiplexers also enables N:M transformations inubit Suite 6: Tutorials

105 Integrating Systems and Automating Processes Application Example 105 Example The depicted Technical Workflow - "Order Supplier A" - sends an order from Assembler AG to supplier A. The supplier requires the order as a CSV file that can be processed in its warehouse management system. Both business partners exchange data via FTP. Assembler AG issues the order in opentrans format in their ERP system. The ERP system is connected to the inubit Suite 6. The order is first converted to a CSV-XML format in the workflow. It is then converted to CSV and sent to the supplier by FTP. The Technical Workflow consists of the following modules (from left to right): File Connector "Order opentrans input" This system connector loads the order to be processed from the Assembler AG file system. XSLT Converter "Order opentrans - CSV-XML" This converter converts the order from one XML format into another XML format. XML-CSV Adapter "Order XML - CSV" This format adapter transforms the data from XML format to CSV format. FTP Connector "Order CSV output" This system connector transfers the data to the FTP server of Supplier A. File Connector "Order CSV outputfile" This connector serves as an alternative connector. It is used if e. g. the FTP server is not available. The file is then stored in the Assembler AG file system. The depicted Technical Workflow serves only as an example and is not included in the tutorial as executable Technical Workflow! inubit Suite 6: Tutorials

106 106 Integrating Systems and Automating Processes Creating a Technical Workflow 1: Reading a File from the File System 6.2 Creating a Technical Workflow 1: Reading a File from the File System Assembler AG receives invoices from the supplier in CSV format but requires invoices in opentrans format. A Technical Workflow therefore fetches all invoices from the file system using a File Connector. The workflow then converts them from CSV-XML format to CSV format and then from CSV format to opentrans format. Your task is to recreate the depicted workflow in a functional way. Creating a diagram Proceed as follows 1. Create an empty Technical Workflow diagram: a. On the "Designer" tab, display the local directory. b. Select the "Technical Workflows" folder and open the context menu. c. Select "New " from the context menu. The diagram wizard opens: inubit Suite 6: Tutorials

107 Integrating Systems and Automating Processes Creating a Technical Workflow 1: Reading a File from the File System Specify the properties of the new workflow diagram here: a. Call the workflow "1_Invoice Supplier A". b. Select "1_Supplier A Workflows" as the workflow group. Leave the other settings as they are. 3. Click "Next". The page "Execution" is displayed. 4. In the "Workflow status" area select the checkbox Active. 5. Click "Next", until the page "Metadata is displayed. There is no need to change any settings on these pages. 6. Click "Finish. The wizard closes and the workflow is generated in your local directory. Creating modules Proceed as follows 1. To the right of the workspace in the sidebar, click "Tools". The docking window "Tools" opens. 2. Click the "System Connector" group and drag a File Connector onto the diagram's workspace. A wizard opens to guide you through the module configuration steps. Make entries for the following fields in the first dialog: - Name: 1_invoice CSV input - Input: csv - Output: csv 3. Click "Next". inubit Suite 6: Tutorials

108 108 Integrating Systems and Automating Processes Testing the Workflow The "Input Connector" option is already preselected correctly, since the File Connector should actively fetch data from the directory. The status can remain as "inactive" as long as the workflow is started manually rather than being scheduled. Ignore all further fields in this dialog. 4. Click "Next". You can ignore the "Scheduler" dialog for the time being. 5. Click "Next". - Make sure, the "File mode" option is selected. - Enter <is-installdir>\client\tutorial\miller as the directory and Invoice.csv as the file name. - De-select the option "Delete files after reading". If this option is selected, you can only test this module once, because after the first test the test file is missing. 6. Click "Next". The default settings in the dialog that now appears are correct. 7. Click "Finish". The wizard closes and the configured File Connector is displayed in the workspace. Refer to File Connector (Workbench/Process Engine: System Connectors Guide, chap. 10, p. 115) for detailed information on the File Connector. 6.3 Testing the Workflow All workflows with at least one module can be tested. Refer to Testing with inubit Suite 6 (Workbench: User Guide, chap. 16, p. 379). Testing the workflow Proceed as follows 1. Open the context menu of the "Invoice CSV input" File Connector and select "Set start point". A green start point is displayed. 2. Click in the workspace and select "Start test without file" from the context menu inubit Suite 6: Tutorials

109 Integrating Systems and Automating Processes Testing the Workflow 109 The test starts. The test file is found and read using the path specification defined in the File Connector. A small green dot moves through the workflow and displays the current processing state. After the test a yellow dot is displayed to the right of the connector, this is a so called watch point. You can display the current interim result of message processing at each watch point. Once the workflow has successfully run, a corresponding message appears. If an error occurs, the processing of the workflow stops and a red highlighting is displayed along with an error message. Displaying interim results Proceed as follows 1. Select the watch point and open the context menu. 2. Select "Display result file(s)". A dialog displaying the read CSV file appears: inubit Suite 6: Tutorials

110 110 Integrating Systems and Automating Processes Creating a Technical Workflow 2: Converting a CSV File to CSV-XML 6.4 Creating a Technical Workflow 2: Converting a CSV File to CSV-XML This section explains how to convert the CSV file into an interim XML format using the CSV-XML adapter. This interim format is required to enable the generation of the opentrans format in the next step; opentrans format is required by the Assembler AG EAI system. Proceed as follows 1. In the sidebar click "Tools" and open the "Format Adapter" folder. 2. Drag a CSV-XML Adapter onto the workspace. The module wizard opens. 3. Fill in the fields as follows: - Name: 1_Invoice CSV-XML - Input: csv - Output: xml 4. Click "Next". The "Module Editor" page is displayed: Change the following entries: - "XML Root Tag" field: Name of the root node in the XML file to be generated. Enter "Invoice". - "Segment name" field: inubit Suite 6: Tutorials

111 Integrating Systems and Automating Processes Creating a Technical Workflow 3: Converting CSV-XML to opentrans 111 Name of the child element (here: the invoice item). Enter "Item". 5. Select the "Field names" checkbox. 6. Next to "Field names from CSV file", click the "Import" button to load the file from which the CSV field names are to be read. A file explorer dialog opens. 7. Navigate to the <isinstalldir>tutorial\miller\invoice.csv CSV file and load it. A prompt appears. Confirm the prompt by clicking "Yes". The field names are adopted from the CSV file in the order in which they occur and then displayed. When the adapter is executed, an XML element is generated from each field name. Now, the configuration of the CSV-XML Adapter is complete. 8. Click "Finish". The module wizard closes. The "CSV-XML Adapter" icon is displayed on the workspace. 9. Connect the File Connector with the CSV-XML Adapter. Test both modules again and display the generated interim XML format. 6.5 Creating a Technical Workflow 3: Converting CSV-XML to opentrans This section explains how to convert the interim XML format to opentrans format using an XSLT converter. The XSLT converter provides a graphical interface that you can use to easily create an XSLT style sheet via Drag n Drop. The XSLT style sheet is used to convert the XML input message to the opentrans output message (which is also XML-based). Refer to XSLT Converter (Data Converter) (Workbench/Process Engine: Modules Guide, chap. 5, p. 125). Proceed as follows 1. In the sidebar click "Tools" and open the "Data Converter" folder. 2. Drag the XSLT Converter onto the workspace. The module wizard opens. 3. Fill in the following fields: - Name: 1_Invoice - CSV-XML - opentrans - Input: xml - Output: xml 4. Click "Next". The next page is displayed. There is no need to change any settings on this page. inubit Suite 6: Tutorials

112 112 Integrating Systems and Automating Processes Creating a Technical Workflow 3: Converting CSV-XML to opentrans 5. Click "Next". The "Module Editor" tab is displayed: Specify the input and target message The XSLT Converter has a three-part interface: - Top: Displays the style sheet - Bottom left: Displays the source message - Bottom right: Displays the target message The source and target message serve as templates for the structure of the output message. The XSLT style sheet is applied to the XML input message and generates the XML output message in accordance with the structure of the XML target message. 6. Specify the input and target message: a. Click the button at the bottom left and select "Open > File" inubit Suite 6: Tutorials

113 Integrating Systems and Automating Processes Creating a Technical Workflow 3: Converting CSV-XML to opentrans 113 Navigate to the message CSV-XML_Invoice.xml file and load it. You find the message in the <is-installdir>\client\tutorial\miller\ directory. You can create the required input message yourself by testing the workflow (File Connector and CSV-XML Converter) and saving the result file from the last watch point on your PC. b. Proceed in the same way to load the opentrans_ Invoice.xml target file at the bottom right. This file is located in the same directory. Once the file has been opened, the relevant XML root nodes are displayed. To view the entire structure of the source and target file, select "Expand all" from the context menu of the root node in question. Once you have expanded both XML files, you can see that the target file in opentrans format has a more nested, significantly more complex structure than the input message: inubit Suite 6: Tutorials

114 114 Integrating Systems and Automating Processes Creating a Technical Workflow 3: Converting CSV-XML to opentrans - Source message (left): In the CSV-SML file, an invoice item is represented by <Item>. Data is assigned within a line on the basis of the items, which are separated using semicolons. The data is represented by the XML elements displayed below <Item>. Each <Item> element has the same children (the elements <Invoice_Id> to <Tax>. This means that each <Item> contains the same basic information. A large proportion of this data is therefore redundant. - Target message (right): The top level is broken down into <INVOICE_HEADER>, <INVOICE_ITEM_LIST>, and <INVOICE_SUMMARY>. <INVOICE_ITEM_LIST> contains multiple <INVOICE_ITEM> (the individual items to be placed into the invoice). The <INVOICE_HEADER> element contains the basic invoice information, which, in opentrans, appears only once and not for every invoice item. Now map the elements from the input message to the elements in the target file. In the case of the two files in the example, you can easily find certain correlations between the source and target file thanks to the similar element names, e. g.: Element in input message Invoice_Id Invoice_Date Position_Id Currency Item Element in target file INVOICE_ID INVOICE_DATE LINE_ITEM_ID PRICE_CURRENCY INVOICE_ITEM Prepare the target file 7. Prepare the target file: inubit Suite 6: Tutorials

115 Integrating Systems and Automating Processes Creating a Technical Workflow 3: Converting CSV-XML to opentrans 115 a. Only the structures are important in the target file, not the data contained therein. You can therefore click the button in the "XML target file" area and select "Remove data from structure" to gain a better overview of the file. b. The target file contains multiple <INVOICE_ITEM> elements. However, the number of invoice items in the output message should dynamically change to the number of items in the input message. You therefore only require a single <INVOICE_ ITEM> element to serve as a structural template. Click the button again and activate the "Only distinct nodes" option. Map the target structure 8. Map the target structure. The basic structure of the XSLT style sheet is already specified in the upper area: a. First, define which elements are to be generated. To do so, drag the <INVOICE> element from the "XML target file" area up to the yellow "XML target" area and drop it onto the xsl:template element. inubit Suite 6: Tutorials

116 116 Integrating Systems and Automating Processes Creating a Technical Workflow 3: Converting CSV-XML to opentrans b. Expand the <INVOICE> element in the style sheet. You can now see that the element with all its child elements has been appended to the xsl:template element: Now you have defined the opentrans structure in the XSLT style sheet. <xsl:value-of> 9. Map input message elements to the target structure: a. Start with the basic invoice information. Drag the <Invoice_ ID> element from the "XML source file" area up to the "XML source" area. Drop the element onto the <INVOICE_ID> line. The following menu opens: inubit Suite 6: Tutorials

117 Integrating Systems and Automating Processes Creating a Technical Workflow 3: Converting CSV-XML to opentrans 117 b. Select "Assign value (value-of)". The result looks like this: You use the xsl:value-of command to define that the content of the target element should be the same as the content of the source document. c. The Invoice/Item//Invoice_Id element appears several times in the input message. To select only the Invoice_Id of the first Item element you must modify the XPath syntax to look like this: You can test each work step by clicking the button in the toolbar. The XSLT processor then generates an output message that appears at the bottom right on the "Mapping results" tab. You will notice that a test with the current XSLT style sheet for the <INVOICE_ID> element returns the value R as expected. inubit Suite 6: Tutorials

118 118 Integrating Systems and Automating Processes Creating a Technical Workflow 3: Converting CSV-XML to opentrans Create a loop with <xsl:for-each> d. Proceed in the same way for subsequent elements up to and including <Currency>: Find the correlations between "XML source" and "XML target" and map them using the "Assign value (value-of)" function. Afterwards, define that only the first Item element should be used. e. The nodes from <Position_Id> to <Tax> contain data that is different for each <Item> element. In addition, each invoice may have more than one article (here: 5 <Item> elements). It therefore makes sense to use a loop to map recurring child elements with different elements. Drag a <Item> element from the "XML source file" area and drop it onto the <INVOICE_ITEM> line (below <INVOICE_ ITEM_LIST>). The selection menu opens. f. Select "Iterate on this node (for-each)". This defines that all statements below this command are to be repeated. An <INVOICE_ITEM> element is therefore created for each Item element in the input message, including all child elements Test the XSLT style sheet to reproduce the loop effect. Use attributes <xsl-variable> g. Map the elements from <Position_Id> to <Tax>. To do so, use the <xsl:value-of> command again. 10. Assign static attribute values: Some nodes in the target document contain attributes. For example, the <INTERNATIONAL_AID> element contains the type attribute, thus indicating the type of the article ID. The corresponding element in the input message is <Article_ EAN>, which tells you that the type of the article ID is EAN (European Article Number). Double-click the line next to the attribute and enter the value "EAN". 11. Use variables to pass on values: The output message contains the elements <PRICE_LINE_ AMOUNT>, <TAX>, and <TAX_AMOUNT> below the <ARTICLE_ PRICE> node. There is no corresponding element in the input message for the <TAX_AMOUNT> element. However, this value can be calculated by multiplying the <PRICE_LINE_AMOUNT> element and <TAX> element. In principle, this does not require variables; however, this instance serves to demonstrate their use. The values of the <Position_Price> and <Tax> elements from the input message are to be passed as variables. a. Click the button in the center of the <ARTICLE_PRICE> element line inubit Suite 6: Tutorials

119 Integrating Systems and Automating Processes Creating a Technical Workflow 3: Converting CSV-XML to opentrans 119 The XSLT command wizard opens. The command wizard supports you when using all common XSLT commands. You can select the required command, configure it, and insert it into the XSLT script. b. Click the variable command. An explanation of the command is displayed with a list of the command's attributes below it. c. Enter "varlineamount" as the value of the name attribute and click "OK". The command wizard closes and the variable appears beneath <ARTICLE_PRICE>. d. Use ALT+ to move the variable to the position above the <PRICE_LINE_AMOUNT> element. Since the variable value is to be assigned to the <PRICE_ LINE_AMOUNT> element, the variable declaration must be moved above this element. e. Assign the value of <Position_Price> to the variable using the value-of command. f. Assign the value of the varlineamount variable to the <PRICE_LINE_AMOUNT> element using the value-of command. When you call a variable, you have to prefix it with $: $varlineamount. g. Proceed in the same way for the <TAX> element. "XML target" should look like this: XSLT operators XSLT functions 12. Calculate the value Because the <TAX_AMOUNT> element has no corresponding element in the input message, its value must be calculated. To do so, you multiply the variables for the position price and tax rate. a. Add the value-of command below <TAX_AMOUNT>. b. In the corresponding "XML source" line, enter the formula: $varlineamount * $vartax. 13. Test the style sheet Display the result of the calculation carried out. You will notice that the tax amount has only a single decimal place. inubit Suite 6: Tutorials

120 120 Integrating Systems and Automating Processes Creating a Technical Workflow 3: Converting CSV-XML to opentrans Format numbers 14. XSLT provides the format-number() function for formatting numbers. Use the format-number($varlineamount * $vartax, 0.00 ) command to generate a result with two decimal places that uses a period as the decimal separator: Count elements Calculate the sum 15. The elements beneath <INVOICE_SUMMARY> also have no corresponding elements in the input message and must therefore be calculated. The <TOTAL_ITEM_NUM> element should specify the number of invoice items in the invoice. This value corresponds to the number of elements in the input message. You can use the count() function to count the elements. Use count(invoice/item) to count the number of invoice items. 16. The <TOTAL_AMOUNT> element specifies the total net amount for the invoice and is calculated from the sum of all position net amounts in the <Position_Price> elements. The sum of all values of a node set is calculated using the sum() function. The sum is specified as a number (number); if values that are not numbers exist in the elements, NaN (Not a Number) is output as the sum. Use constants The calculated sum must also be formatted as follows: format-number(sum(invoice/item/position_price), '0.00') 17. To depict the <TOTAL_TAX_AMOUNT> element, the values of <Position_Price> and <Tax> within each position must be multiplied. The results must then be added together. However, the sum() argument may only contain a node set and not a mathematical expression. We therefore assume that the tax rates within an invoice are identical and use a constant: format-number(sum(invoice/item/position_price) * Invoice/Item[1]/Tax, '0.00') The Invoice/Item[1] XPath expression causes the <Tax> value to be read from the first <Item>. This value is multiplied with the sum of the values of the <Position_Price> element. The result is formatted using the format-number() function. 18. Click "Finish". The module wizard closes and on the workspace an XSLT Converter icon is displayed. Test your style sheet and connect the XSLT converter module with the CSV-XML module inubit Suite 6: Tutorials

121 Integrating Systems and Automating Processes Excursus: XSLT Excursus: XSLT Important XSLT commands xsl:value-of: A value assignment. The value of the element in the incoming message is mapped to the corresponding element in the outgoing message. xsl:for-each: For the selected element, the same number of elements is created in the target structure as can be found in the incoming message. Example: If the value of the "Item" element in the incoming message is mapped to the "Article" in the outgoing message, this transformation is performed as often as the "Item" element is found in the incoming message. The "Item" elements must be found under the exact XPath indicated in the mapping. xsl:copy-of: Copies a node, including its subordinate nodes and attributes, from the source file to the result. xsl:if: Indicates a condition. If this condition has been met, the corresponding structure is created on the right side. The condition is an XPath expression. Example: If there is a <Price_Currency> element in the source structure, then the value of this element can be analyzed: Price_ Currency='EUR'. xsl:choose-when: This instruction allows multiple cases to be differentiated. Enter an xsl:choose on the right side. Enter an xsl:when and an xsl:otherwise element below the xsl:choose. The xsl:when element can then be inserted as often as needed. The xsl:otherwise element is optional. For each xsl:when element, enter a condition on the left, as described for the "if" instruction. The target node is still below xsl:choose, and must now be moved below xsl:when or xsl:otherwise. xsl:result-document href= myvar (XSLT 2.0) This instruction writes the content to an output file saved in the myvar variable. To make the variable available to the entire process, you must define it at the module. Refer to Defining Variables (Workbench: User Guide, chap. 14.1, p. 334). Optimizing XSLT style sheets Two aspects are key to improving performance: efficient code efficient use of the code The following rules of thumb were created by Dr. Michael Kay. This recognized XSLT expert and developer of the Saxon XSLT processor is a member of the XSLT workgroup of the World Wide Web Consortium (W3C). inubit Suite 6: Tutorials

122 122 Integrating Systems and Automating Processes Creating a Technical Workflow 4: Storing the File in the File System Writing efficient XSLT: To output the text value of a simple #PCDATA element, it is better to use <xsl:value-of> instead of <xsl:applytemplates>. Do not sort the same node-set more than once. If necessary, save it as a result tree fragment and access it using the node-set() extension function. Do not evaluate the same node-set more than once. Save it in a variable. Avoid complex patterns in template rules. Instead, use <xsl:choose> within the rule. Avoid the use of //item. If possible, avoid <xsl:number> by using position(). Use <xsl:key> for groupings. Be careful when using the preceding or following axes of coordinative nodes. This often indicates an algorithm with n- squared performance. Using XSLT efficiently: If you use the same source document repeatedly, keep it in memory. If you have to perform the same transformation repeatedly, don t. Use the result immediately instead. Keep the source documents small. If necessary, split the documents. Do not validate the same source more than once. Keep the result file small. Split complex transformations into several steps. 6.7 Creating a Technical Workflow 4: Storing the File in the File System The invoices now exist in the correct format and need to be written to the Assembler AG file system using another File Connector. Proceed as follows 1. In the sidebar click "Tools", open the "System Connectors" folder and drag a File Connector onto the diagram. The module wizard opens. 2. Enter the following: - Name: 1_Invoice opentrans output inubit Suite 6: Tutorials

123 Integrating Systems and Automating Processes End-to-End Navigation: Connecting Technical Level with Business Level Input/output: xml 3. Click "Next" and select "Output connector" as the type in the next dialog, since the connector is to output the invoices. The connector status can remain as "inactive" as long as the workflow is not scheduled. Ignore all further options and click "Next" to move to the next but one dialog. You can skip the "Configure scheduled processing" dialog. 4. Enter "Invoice*.xml" into the "Name" field in the "File" area of the "Output format configuration" dialog. If you enter the file name without a path, the File Connector writes to the export directory of the workflow: <isinstalldir>\server\ibis_root\tutorial\inubit IS Team\miller\workflow\invoice supplier a\export. 5. Close the dialog by choosing "Finish". 6. Connect the File Connector with the previous module. Publish your modules after important configuration steps to save different work states. Testing of the complete Technical Workflow can only be successful if all elements and the workflow itself have been published. Test the Technical Workflow again. If the test is successful, you have now created your first complete workflow. 6.8 End-to-End Navigation: Connecting Technical Level with Business Level This section describes how you link your Technical Workflow with its business-related description in the business process diagram. This linking allows you to give a professional opinion on errors that occur during the workflow s execution by navigating top-down from the business process to its technical implementation. Proceed as follows 1. Display the "Main Order Transaction" business process diagram on the "Local" tab for editing. 2. To the right of the workspace in the sidebar, open the docking window "Links". 3. In the link directory, select the "1_Invoice Supplier A" Technical Workflow. inubit Suite 6: Tutorials

124 124 Integrating Systems and Automating Processes End-to-End Navigation: Connecting Technical Level with Business Level 4. Drag it onto the "Receive invoice" message event. A dialog appears and displays the Technical Workflow. 5. Select the connection line which you want to monitor. 6. Open the context menu and select "Set link point". 7. Click "OK" to close the dialog. 8. Publish the BPD. A colored link point is displayed in the "Receive invoice" activity, indicating a connection to a Technical Workflow: Click the link point to display the linked Technical Workflow. In the Technical Workflow a link for jumping back to the BPD was added. Refer to - End-to-end Navigation between Diagrams (Workbench: User Guide, chap. 2.12, p. 81) - Managing the Connection Parameters of System Connectors Centrally (Workbench: User Guide, chap. 9.1, p. 212) - Partner Management (Workbench: User Guide, chap. 9.2, p. 214) inubit Suite 6: Tutorials

125 7 Developing a Web Application in inubit Workbench 125 This section details the following topics: Workflow Management, p. 125 Developing Your Own Web Application, p. 126 Adding a Web Application to a Portal Page as a Portlet, p. 143 Granting Web Application Permissions, Assigning Them to Portal Roles, p. 147 You require licenses for web applications in the portal and to use the task generator! These components are not covered by the standard license. You can find example programs for all tutorials in the inubit Suite 6, refer to Using Example Diagrams and Users (Tutorials, chap. 1.3, p. 13). Prerequisites You have installed one of the following installation sets of the inubit Suite 6: - Full installation - Process Center You have added a valid license. You find further installation instructions in the Quick Start: - Installing from DVD (Quick Start, chap. 2, p. 4) - Requesting a License Key (Quick Start, chap. 3, p. 5) - Adding the License Key (Quick Start, chap. 4, p. 7) You have logged in to the inubit Workbench with the user miller in order to access to the example diagrams. Refer to Using Example Diagrams and Users (Tutorials, chap. 1.3, p. 13). 7.1 Workflow Management Involving employees is often required and desirable for automated business processes. User interaction as part of the Technical Workflow Interactions with users are completely integrated into the Technical Workflows and are created through running workflows. The assignment of tasks arising from the process flow takes place on the basis of roles and can also be controlled using an organization inubit Suite 6: Tutorials

126 126 Developing a Web Application in inubit Workbench Developing Your Own Web Application diagram. This enables individual tasks to be assigned to a group of responsible parties. The organization diagram can also be used to determine a supervisor with whom a task can be escalated. The processing of tasks takes place via a Web-based, personalized task list. A list of all tasks is displayed for each employee. This list is configured using the task generator module in an integrated WYSIWYG editor. The list structures the tasks of the user and delivers any required additional information such as the priority of the tasks. External applications such as MS Office can also be integrated. The task list is a JSR 168-compliant portlet and an integral part of the inubit Process Cockpit. It can be integrated into all other portals using the portlet standard. Creating portals You can also implement complete portals on the basis of the Technical Workflows and in conjunction with the task generator. The Technical Workflows define the logic required to determine the page sequence and to exchange data with back-end systems. The task generator module defines the individual pages, which also contain the portal navigation elements. The tight connection with the business process diagrams means that a portal can be created in a completely process-oriented manner with the inubit Suite 6. Refer to - Using inubit Enterprise Portal (Workbench: User Guide, chap. 20, p. 461) - Developing a Web Application in inubit Workbench (Tutorials, chap. 7, p. 125) - Task Generator (Data Converter) (Workbench/Process Engine: Modules Guide, chap. 4, p. 55) 7.2 Developing Your Own Web Application This section details the following topics: Creating the Form Mapping, p. 130 Creating Output Mapping, p. 134 Inserting Additional Modules, p. 136 This section describes how to create a form-based Web application for processing orders at the car dealership inubit Suite 6: Tutorials

127 Developing a Web Application in inubit Workbench Developing Your Own Web Application 127 Requirements The portal server is activated. Refer to Activating and Displaying the inubit Enterprise Portal (Workbench: User Guide, chap. 20.3, p. 463). Basic procedure 1. Create a Web application as a Technical Workflow Consisting of: - Web application Input Connector This connector makes the functions of the Technical Workflow available as a portlet on the portal server. All properties that are relevant for the entire Web application, such as application permissions or timeouts, are configured on this connector. As soon as the Web application Connector is deployed on the portal server, a portlet is generated. This portlet serves as a user interface for the Web application. In addition, all relevant information, such as application permissions, is transferred to the portal server. - Two task generators with the task type Form sequence/web application page For generating the order and feedback form. - One joiner and one splitter in each case. - Task generator with the task type Item in task list > Task Each new order should generate an item in the task list of the responsible employee. The task list is displayed in the inubit Process Cockpit area on the Tasks tab. The order is submitted to the employee for approval/rejection. 2. Activate and publish the Technical Workflow. Only portlets based on active Technical Workflows are displayed in the portal. 3. Deploy the portlet. 4. Assign application permissions in the portal to one or more roles. inubit Suite 6: Tutorials

128 128 Developing a Web Application in inubit Workbench Developing Your Own Web Application Proceed as follows 1. Create a diagram of the type Technical Workflow. 2. Insert a Web Application Connector from the System Connector group in the sidebar into the diagram: The module wizard opens. 3. In the first dialog, enter a name for the module. 4. Click Next. 5. Select Input Connector for Connector type. 6. Select Active for the connector. 7. Click Next. Select inubit as the category and define the title of the portlet. By default, the name of the Web application Connector is used: inubit Suite 6: Tutorials

129 Developing a Web Application in inubit Workbench Developing Your Own Web Application 129 All portlets are grouped into categories in the portal. By specifying inubit, you specify that your portlet will be displayed in the inubit category later: Create Task Generator 8. Click Next. 9. Skip all of the subsequent dialogs and close the wizard by clicking Finish in the last dialog. 10. Insert a joiner from the Workflow Controls group in the sidebar, enter a module name and connect it with the Web application Connector. The joiner is required to create the messages in the form of a loop so that an empty form is displayed once each order has been submitted. 11. Insert a task generator from the Data Converter group in the sidebar: a. Enter the module name in the first dialog. b. Click Next. c. In the dialog that now appears, select Form sequence > Web application page. d. Click Next. Skip the Permissions dialog. e. Click Next. inubit Suite 6: Tutorials

130 130 Developing a Web Application in inubit Workbench Developing Your Own Web Application f. In the XSLT Mapper settings dialog, select Ignore input message, since the input data is entered by the user directly into the form rather than coming from a previous module. g. Click Next. h. In the dialog Panel Layout select the layout template Table Layout. All form elements will be arranged in a table because that makes it easier to position them. i. Confirm with Finish. The task generator is displayed in the designer workspace. 12. Connect the task generator with the joiner you just added. 13. Open the context menu of the Task Generator and select Edit (in module editor). The Task Generator > Form Mapping tab opens. In the Designer (bottom right) a small table is displayed which is represented as XML element Panel with an orientation='table' attribute on the Form mapping > XML target area (top): The next sections illustrates how to create the order form with the so called order mapping on this tab Creating the Form Mapping The order form should look like this: inubit Suite 6: Tutorials

131 Developing a Web Application in inubit Workbench Developing Your Own Web Application 131 Proceed as follows Labels for input fields 1. Create labels for input fields: a. Drag a label element from the form designer toolbar and drop it onto the first table cell: The red border indicates where the label is to be inserted. This inserts a Label element on the Form mapping > XML target tab. b. Click the label in the designer. A colored frame appears around the label and the properties of the label element are displayed on the Properties tab. c. To provide text for the label, enter Company in the Specific > Row label line area of the Properties tab. Confirm your entry by pressing Return. The word you entered is now displayed in the designer and in the XML source/target area: d. Repeat the procedure for inserting and naming a label for the other four label elements. Insert each label into an empty table cell. Enter an asterisk (*) after each label name. This informs users who fill in the form later on that all fields are mandatory and must be filled in. inubit Suite 6: Tutorials

132 132 Developing a Web Application in inubit Workbench Developing Your Own Web Application To insert additional table rows, open the context menu for the table and select Insert row. If you select a table row and then insert another row, the selected table row is copied. This make it easier to create elements that are required frequently. 2. Create input fields, name them, and mark them as mandatory fields a. Drag a TextField element from the toolbar and place it in the empty table cell next to the Company label: b. Insert TextField elements next to the other labels in the same way. c. Assign names to the input fields so that they can be identified more easily when being analyzed: To do so, select the first input field and display the Properties tab. In the General area enter the value Company for the name attribute: inubit Suite 6: Tutorials

133 Developing a Web Application in inubit Workbench Developing Your Own Web Application 133 Make sure that the value of the name attribute complies with the naming rules for XML elements. d. Select the mandatory check box. This marks the input field as a mandatory field. e. Repeat the last two steps for all other input fields. 3. Use the context menu to delete the empty table column. Display the preview 4. To display the preview, click in the inubit Workbench toolbar. The form should look like the following: Add buttons 5. You still need buttons for sending the order: a. Insert another two table rows. b. Drag a button element onto the form and place it in this last, empty table row. c. Place a second button next to the first: Pay attention to the red mark. It shows you where the second button is being placed. d. To increase the gap between the two buttons, insert a horizontal filler between them. To define the width of the gap, select the filler and enter a value for the size attribute in the Specific area of the Properties dialog. Example: e. Select a button and display the Properties tab. f. Name the button by entering label=submit in the Specific area. g. Below this, select the submit(value) event, since you want the input data to be submitted when the button is pressed. h. Beneath the event, select the validate checkbox. The system will now check that all fields marked as mandatory are filled in before the Submit button is activated: inubit Suite 6: Tutorials

134 134 Developing a Web Application in inubit Workbench Developing Your Own Web Application i. Assign the values label=cancel and event = cancel() to the second button. The input form is now complete. In the next step, you define how data that users enter into the form is forwarded to the next module in the workflow Creating Output Mapping You use output mapping to define the data structure that is forwarded to the next module in the Technical Workflow. Proceed as follows 1. Click to display a preview. 2. Enter data into the fields so that you can submit the form. 3. Click Submit. The Output mapping tab appears. The XML source file area (bottom left) displays the XML data that is generated when you click Submit and sent to the task generator module: inubit Suite 6: Tutorials

135 Developing a Web Application in inubit Workbench Developing Your Own Web Application Drag the Panel element from the XML source file tab diagonally upwards into the XML target area and drop it onto the template element. The structure is copied to the style sheet along with all child elements (right) and the data (left): 5. Adopt values from elements Naturally, you do not always want to display the static data displayed top left; instead, you want to display the current values entered for the form elements. a. To do so, delete the values displayed in the XML source area (top left): Select the cell and double-click it. Remove the value and confirm the change by pressing Return. b. Drag the Company element from the XML source area (under Form > Response > Panel) to the top left and drop it into the empty row next to the Company element. A context menu opens. c. Select Assign value (value-of) from the context menu. The XPath expression /Form/Response/Panel/Company is displayed in the field. Proceed in the same way for all other elements in the form. The result should look like the following: inubit Suite 6: Tutorials

136 136 Developing a Web Application in inubit Workbench Developing Your Own Web Application You have now completed the output mapping. 6. Click to test the output mapping. The result is displayed on the Mapping results tab (bottom right). The generated XML structure and the data is passed from the task generator to the subsequent module (the splitter) when the Technical Workflow is processed. 7. Publish the module. Publish your module after important configuration steps such as defining form mapping. This allows you to save different work states, because a new version of the module is generated each time you publish it. You can access versions whenever you want Inserting Additional Modules Proceed as follows 1. Display the Technical Workflow again. 2. Insert a splitter ( Workflow Control group): The splitter duplicates incoming orders: - One order is forwarded to the task generator that displays the feedback form inubit Suite 6: Tutorials

137 Developing a Web Application in inubit Workbench Developing Your Own Web Application The other order is passed on to the task generator that generates a task list item. All orders are simply forwarded by the splitter; they are not processed further. 3. Connect the splitter with the task generator. Create order feedback 4. Create the task generator for order feedback. Once the order has been submitted, a short message should tell the ordering party that the order is on its way. a. Create another task generator module. b. Select the Form sequence > Web application page option again. The application permissions do not need to be taken into account in this module, either. c. Select General > Ignore input message in the XSLT Mapper settings dialog. d. Close the module wizard by choosing Finish. e. Open the module for editing. f. Generate the following form using a label and a button in the designer: inubit Suite 6: Tutorials

138 138 Developing a Web Application in inubit Workbench Developing Your Own Web Application g. Define any output mapping, that you can freely select, e. g.: The output message of this task generator is not used any further. Therefore, structure and content of the message are not relevant. 5. Display the Technical Workflow. Connect modules 6. Connect modules: a. Connect the splitter with the task generator you just created. b. Connect the new task generator with the joiner. This connection ensures that an empty order form is displayed to users after they click the OK button in the feedback form. Create a Task Generator for the item in the task list 7. Create a task generator for the item in the task list. Each new order should be displayed in the task list of the responsible employee so that the order can then be approved manually. a. Create another task generator module. b. Fill in the Task generator properties dialog as follows: inubit Suite 6: Tutorials

139 Developing a Web Application in inubit Workbench Developing Your Own Web Application 139 c. Click Next. d. In the Permissions dialog, specify that the Administrator and User portal roles should be used. This causes the task to be displayed to all owners of these roles. The task is deleted from the task list as soon as one of the role owners processes it. Portal roles are only displayed if a portal server is active and a portal is available, refer to Configuring the Portal Server (inubit Process Engine: Administrator and Developer Guide, chap. 2.21, p. 40). e. Click Next twice and while doing so, ignore the dialog XSLT Mapper Settings. inubit Suite 6: Tutorials

140 140 Developing a Web Application in inubit Workbench Developing Your Own Web Application f. In the dialog Panel Layout select the Table layout and then click Finish. g. Open the module for editing and create the following form in the designer: - To ensure that the order cannot be changed, deactivate the enabled attribute for all labels and properties in the Misc area. - Remember to name the display fields using the name attribute. You can facilitate your work routine by copying the form you created in section Creating the Form Mapping (Tutorials, chap , p. 130) in the Task Generator EnterOrder and pasting it here. - Both buttons receive a submit event. In this case, it is important to differentiate between the two buttons. You should therefore enter the following event values: - submit(reject) - submit(release) Confirm your entries by pressing Return. The event values help to identify which button was clicked. They are passed to the subsequent module once either button is clicked. Further processing of the order may depend on the event value. For example, an order with the event value Approve may be passed to the responsible department. This is not part of this tutorial inubit Suite 6: Tutorials

141 Developing a Web Application in inubit Workbench Developing Your Own Web Application 141 Create form mapping 8. The module receives the order data from the form as an input message. You have to map this order data to the form for the task list entry. For this mapping, you need an output message from the first task generator module: a. Display the Technical Workflow. b. Select the first task generator. c. Open the context menu and select Edit (in module editor). The order form is displayed in the designer. d. Click to display a preview. e. Fill in the fields and click Submit. The form preview closes and the Output mapping tab is displayed. f. Test the style sheet: Click the button. The result is displayed on the Mapping results tab. g. Click the button and copy the result to the clipboard. h. Now, display the form for the task list entry in the Designer again. i. Display the Source tab at the bottom left. j. Click the button and select Open > Clipboard. The result you just copied is displayed. k. Expand the structure. l. Select the Company text field in the designer. The corresponding XML structure is displayed in the XML target area. m. Drag the Company element from the Source tab up to the XML source area and drop it into the row to the left of the TextField element that is formatted in bold. A context menu opens. n. Select Assign value (value-of). This specifies that the value of the Company element is to be displayed in the selected display field. The result should look like this: o. Repeat the last two steps for all other elements in the form. p. Click to display the preview: inubit Suite 6: Tutorials

142 142 Developing a Web Application in inubit Workbench Developing Your Own Web Application q. Click Release. The Output mapping tab appears. The XML data created when you clicked the button appears at the bottom left. The current status of the order is identified by the attribute value submitter=release of the Response element. If the order had been rejected, the value would be submitter=reject. r. Create any kind of output mapping. The output mapping is not required in this tutorial because the workflow ends with this module. However, an output mapping must exist or else you cannot publish the module. Drag any element, such as a Panel element, from the XML source file tab diagonally upwards to the XML target area and drop it onto the template element. s. Publish the module. 9. Display the Technical Workflow. 10. Connect the task generator you created most recently with the splitter. 11. Publish the Technical Workflow. 12. Activate the Technical Workflow by selecting it in on the Server tab, opening the context menu, and choosing Activate. The workflow symbol now appears with a colored background: Your Web Application is finished. You can now add it to a portal page as a portlet inubit Suite 6: Tutorials

143 Developing a Web Application in inubit Workbench Adding a Web Application to a Portal Page as a Portlet Adding a Web Application to a Portal Page as a Portlet In this section you learn how to add your Web Application to the inubit Enterprise Portal as a portlet on a new page within a passwordprotected area. Proceed as follows Deploy portlet into the Portal 1. To make the web application initially available as a portlet in the portal you must deploy the portlet in the inubit Workbench: a. In the inubit Workbench, display the Configuration > General settings tab. b. Open the configuration area Portal > Portal Deployment. c. At the option Portlet-Archives (Administration/Deployment) click. A dialog opens. d. Click Deploy archive and confirm the next dialog. The deployment starts. After the deployment has been finished successfully, a corresponding message is displayed. e. Close the dialog. Before you start the deployment consider the notes in the User Guide (Deploying Web Applications as Portlet Archive (Workbench: User Guide, chap , p. 491)). Before you start the re-deployment after having changed your web application particularly consider the notes in section Deploying modified portlets (Workbench: User Guide, chap , p. 493). Add a new page in the private community area 2. The portlet should be displayed on an individual page and be accessible for logged-in guests, only. Thus, you create a new page in the inubit Cockpit. Displaying the inubit Cockpit requires a login. a. In the portal, display the inubit Cockpit of the administrator. This area is automatically displayed when you log in as an administrator. b. Click Add > Page in the toolbar: c. Enter a name for the page. When you have finished making your entry, press ENTER. A new page is created. inubit Suite 6: Tutorials

144 144 Developing a Web Application in inubit Workbench Adding a Web Application to a Portal Page as a Portlet Add a Web application: 3. Display the new page to which you want to add the web application. a. In the toolbar, click Add > More applications. The panel appears containing the available applications: b. Click the category to which you added the portlet. That was inubit. You assigned the portlet to a category when configuring the Web application Connector. All existing portlets in the category are displayed: inubit Suite 6: Tutorials

145 Developing a Web Application in inubit Workbench Adding a Web Application to a Portal Page as a Portlet 145 c. Add your Tutorial_Order portlet and then close the Add Application panel by clicking the red X. The portlet is displayed: Add Page permissions 4. Click on Manage > Page in the toolbar. 5. Click on Permissions. inubit Suite 6: Tutorials

146 146 Developing a Web Application in inubit Workbench Adding a Web Application to a Portal Page as a Portlet 6. Save you changes. 7. Click on Return to Full Page. The newly created page and the portlet are now visible to all users with the role Power User that belong to the inubit Process Cockpit community. Refer to Adding Portlets to a Page (inubit Process Engine: Administrator and Developer Guide, chap , p. 174). Testing Fill in the form. Once you have submitted the form, the following things should occur: 1. The following message should appear: 2. In the Tasks tab in the inubit Cockpit area an order is displayed, for example: inubit Suite 6: Tutorials

147 Developing a Web Application in inubit Workbench Granting Web Application Permissions, Assigning Them to Portal Roles 147 The same task is also shown if you log in using the role Power User and display the Tasks tab again. This is because you have specified in the Task Generator that tasks are to be created for both the portal roles Administrator and Power User. Click a task to display the form: Refer to - Granting Web Application Permissions, Assigning Them to Portal Roles (Tutorials, chap. 7.4, p. 147) - Dialog "Web Application" (Workbench/Process Engine: System Connectors Guide, chap , p. 380) 7.4 Granting Web Application Permissions, Assigning Them to Portal Roles To control the use of your web application, you can grant special application permissions to buttons and input fields. Then, only Portal users with roles to which these application permissions were assigned in the scope of their community, are able to make use of those web application controls. inubit Suite 6: Tutorials

148 148 Developing a Web Application in inubit Workbench Granting Web Application Permissions, Assigning Them to Portal Roles Requirements You are logged in to the portal as an administrator. Proceed as follows 1. In the inubit Workbench, display the Technical Workflow that you created in Developing Your Own Web Application (Tutorials, chap. 7.2, p. 126). 2. Open the Web application Connector for editing. The module wizard opens. Define permissions 3. Click through the dialogs until you reach the Permission management dialog. a. Beneath the display field, enter Release. b. Click the Plus button to copy the permission to the display field: c. Click Finish. 4. Publish the Web application Connector to transfer the permission you just defined to the task generator. 5. Open the last task generator for editing; this is the task generator that creates the task list entry. The task generator is selected in the module tree (left). 6. In the module tree, open the task generator context menu and select Edit properties. The module wizard opens. 7. Click through the dialogs until you reach the Permissions dialog. 8. Adopt the application permissions from the Web Application Connector by selecting the checkbox. The Connector was created in section Developing Your Own Web Application (Tutorials, chap. 7.2, p. 126). 9. Click Next and then click Finish to close the module wizard inubit Suite 6: Tutorials

149 Developing a Web Application in inubit Workbench Granting Web Application Permissions, Assigning Them to Portal Roles 149 Assign permission to form element. 10. Assign the Release permission to the button: a. Select the Release button. b. Click the empty cell next to the enabled attribute in the Conditional area of the Properties dialog. The Select permissions dialog appears: Re-deploy the portlet Add portlet permissions c. Select the Release option. d. Click OK. The dialog closes. The cell now contains {p:haspermission($isportaluser, Release )} and the button has a colored border. From now on, the button is only active in the portal for users to whose role the permission Release is explicitly assigned. e. Publish the module. 11. Re-deploy the portlet to make the changes available. a. In the inubit Workbench, display the Configuration > General settings tab. b. Open the configuration area Portal > Portal Deployment. c. At the option Portlet-Archive click. A dialog opens. d. In the area Archives on portal server in the column Action click Redeploy archive. e. Confirm the next dialog. The deployment starts. After the deployment has been finished successfully, a corresponding message is displayed. f. Close the dialog. 12. In the portal, display the Control Panel of the administrator. 13. To the left in the Portal area, click Roles. A list of all available roles is displayed. 14. Enter power in the search field and click on Search to display the Power User role. inubit Suite 6: Tutorials

150 150 Developing a Web Application in inubit Workbench Granting Web Application Permissions, Assigning Them to Portal Roles 15. Next to the role Power User to which you want to assign application permissions for your portlet, click Actions > Define Permissions. A list of all available portlets for this role is displayed. 16. Click in the field below Add Permissions. A list of all available portlets is displayed. 17. Click on your portlet (e.g. Tutorial_Order ). The Roles window now displays under Action a list of all permissions that are available for your portlet: 18. For each action you want to allow for the role, select the checkbox. This defines the general validity area of the permissions for the Power User role inubit Suite 6: Tutorials

151 Developing a Web Application in inubit Workbench Granting Web Application Permissions, Assigning Them to Portal Roles 151 Select community for permissions 19. To limit the scope of a permission to communities, click on Limit Scope. a. Click Select. A window opens that displays all available communities. b. Click the community to which the page on which the portlet is displayed belongs, e.g. inubit Cockpit. The dialog closes and the changes are accepted c. Repeat this step to assign a specific community to the next permission. Continue in this way until you have assigned all permissions. 20. Once you have configured all permissions, click Save to adopt your assignments. A confirmation message is displayed at the top of the window and an overview with the result of your assignments is displayed. Example: Now, all users with the Power User role in the validity area of the inubit Cockpit community can approve the portlet orders. Users with the role Power User who belong to another community cannot use the Release button. Refer to Displaying Form Elements Dependent upon User Rights (Web Applications only) (Workbench/Process Engine: Modules Guide, chap , p. 67). Make sure that all Technical Workflows and system connectors are active. Testing Proceed as follows 1. Sign in to the portal using the portal role Administrator. 2. In the service menu, click Control Panel. inubit Suite 6: Tutorials