inubit 6.1 inubit Solution Center 3.0 User Guide

Transcription

1 inubit 6.1 inubit Solution Center 3.0 User Guide

2 Copyright Bosch Software Innovations GmbH Schöneberger Ufer Berlin Germany Phone: Fax: URL: Bosch Software Innovations GmbH 2013 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. The liability of Bosch Software Innovations GmbH 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 Bosch Software Innovations GmbH. Bosch Software Innovations GmbH 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 Bosch Software Innovations GmbH in a written license agreement. Software provided by Bosch Software Innovations GmbH may include software components of other producers. inubit is a registered trademark of Bosch Software Innovations GmbH. 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 User Guide...7 Scope of the Documentation...7 Tips, Notes and Links in the Documentation...8 Further Information and Support Overview User Interface of the inubit Solution Center Icons in the Solution Center and View Designer Creating and Editing Domain Models Introduction Creating a Domain Model in WebModeler Creating a Root Instance Creating Classes Creating, Adjusting and Deleting Associations Creating an Association Properties of an Association Changing the Properties of the Association Deleting an Association Creating Attributes Data Types for Attributes Multiplicity of an Attribute Saving a Domain Model Editing a Domain Model Opening a Domain Model for Editing Model Changes after Deployment Deploying a Domain Model Activating a Business Domain Creating a Domain Model as a Business Domain in the Solution Center Creating a New Domain Creating Classes Creating a Root Instance Creating Additional Classes Creating an Attribute...34 inubit 6.1: Solution Center: User Guide

4 4 Table of Contents Creating Selection Lists Uploading Image Data Creating Associations Defining Validation Rules Filtering and Sorting Configurable Filters Configuring the REST Filter Filtering the Display Showing/Hiding Table Columns Sorting a Table Column Activating a Domain Model Creating a Domain Model in the inubit Workbench Creating and Deploying a Business Object Diagram Creating and Deploying a Business Process Diagram Deactivating a Business Domain Deleting a Business/Process Solution Using the Solution Center Start and Setup of the inubit Solution Cockpit Header Area Toolbar Object Path Object Browser Domain Library Business Foundation Model Solutions History Clipboard Toolbox Assigning Access Rights Deleting Objects, Libraries or Folders Creating Menus and Menu Items Data Area Creating and Editing Domain Models Using Business Solutions Creating New Business Objects Assigning Business Objects inubit 6.1: Solution Center: User Guide

5 Table of Contents Creating Views Working with Process Solutions Starting a New Process Processing Tasks Using Views Generic View Defining Views in View Designer Defining a New View Defining the Header Section Defining the Body Section Links to Actions, Filters and Sorting Structure of View Designer Defining Views in the Solution Center Adding a Header Section Adding a Data Section to the Body Section Adding Attributes of the User-Defined Class Adding Attributes to an Association Defining List Views Defining a Sort Criterion Integrating Processes Defining Actions on Views Defining Actions on List Views Default Models and Interfaces Technical Core Model Object Types Views Business Foundation Model Application Class Process Class Partner Class REST Interface General Information Authentication Input and Output Formats...87 inubit 6.1: Solution Center: User Guide

6 6 Table of Contents UUID or Node Path Reading Nodes Determining the Menus of the Current User Querying Type Information Querying Views for a Type Exporting a Node Structure Importing a Node Structure Writing Nodes Creating Nodes Changing Nodes Deleting Nodes Linking Objects Removing an Object Link Determining the Parent Node Copying Nodes Moving Nodes Result Elements Reading Associations Page-by-Page Activating, Deactivating and Querying Models Activating Models Deactivating Models Querying Properties and Associations for a Type Name Querying Properties and Associations for a Type Name and Derived Types Querying Models and Their Types Querying, Setting and Removing Node Locks Querying Node Locks Locking Nodes Removing Node Locks Administration Interface Activating/Deactivating Maintenance Mode Determining the Maintenance Status and Maintenance Key Querying the License Querying the Version Backing up the Solution Center Repository Restoring the Solution Center Repository Closing the Solution Center inubit 6.1: Solution Center: User Guide

7 Notes on the User Guide 7 Target audience This document contains detailed information for business users who model and use business solutions. Scope of the Documentation inubit 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 - 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. 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 6.1: Solution Center: User Guide

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. Read this file thoroughly before installing or updating inubit! Quick Start System requirements and installation instruction as booklet delivered with the inubit-dvd. API documentation for plug-in software development kit Found under <is-installdir>/documentation/apidoc/ index.html. JavaScript-Framework of the inubit Found under <is-installdir>/documentation/jsdoc/ index.html Tips, Notes and Links in the Documentation Tips offering useful information for working with inubit. 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 6.1: Solution Center: User Guide

9 9 Further Information and Support Press releases and white papers are available from our website For further inquiries, please contact our support by: Telephone: SupportSystem: We wish you every success in working with inubit. Your team from Bosch Software Innovations GmbH! inubit 6.1: Solution Center: User Guide

10 inubit 6.1: Solution Center: User Guide

11 1 Overview 11 This section details the following topics: User Interface of the inubit Solution Center, p. 12 Icons in the Solution Center and View Designer, p. 13 Usage The inubit Solution Center 3.0 is a web application for quickly creating web-based business solutions. Business solutions are applications for managing business objects. Business objects represent real life business objects, such as customers, products, purchase orders and invoices of an ordering system. Installation variants The inubit Solution Center 3.0 is available in the following variants: Stand-alone installation (installation set Solution Center ) For the stand-alone installation of the inubit Solution Center 3.0, an application server (Tomcat or JBoss) and the Liferay portal server are installed. The graphical user interface of the inubit Solution Center 3.0 runs as a portlet (inubit Solution Cockpit) in a web browser. You model your business domain in the WebModeler directly in the inubit Solution Center 3.0. A connection to inubit Process Engine is possible for executing processes using workflows. For testing purposes and for the tutorial you should use the standalone installation. Integrated installation ( inubit complete installation installation set) The prerequisite for this installation variant is that inubit software is installed. The inubit Solution Center 3.0 uses the Tomcat application server and the Liferay portal server of this inubit installation. In this installation variant, the inubit Solution Cockpit runs on the inubit Enterprise Portal. Unlike with the stand-alone installation, you can model your business domains both in the WebModeler of the inubit Solution Center 3.0 and the inubit Workbench, and you can call workflows in the inubit Solution Center 3.0 from the inubit Process Engine. Components The Solution Center consists of the following components: inubit Solution Cockpit For creating and editing business solutions and business domains. WebModeler inubit 6.1: Solution Center: User Guide

12 12 Overview User Interface of the inubit Solution Center For creating and editing domain models as the basis for business domains and business solutions. View Designer For creating and editing views for the convenient entry, editing and analysis of business objects in your business solution. Alfresco For administrating the business objects in a database. 1.1 User Interface of the inubit Solution Center 1. Menus of the Liferay portal with functions, e. g. for configuring the portal and administrating the portal users inubit 6.1: Solution Center: User Guide

13 Overview Icons in the Solution Center and View Designer Switching between the portlets Solution Center and WebModeler Refer to - Start and Setup of the inubit Solution Cockpit (Solution Center: User Guide, chap. 3, p. 49) - Creating a Domain Model in WebModeler (Solution Center: User Guide, chap. 2, p. 18) 3. Toolbar with the following buttons: - Start page - customized menus and entries - Search field 4. Navigation path to the current object 5. Buttons to activate/deactivate models, for saving or canceling editing (only in edit mode) as well as for changing or creating a view and switching between view mode and edit mode 6. Accordion menu with object browser, history, clipboard and toolbox. The object browser consists of the following areas: - Domain library Contains the supplied domain models as well as user-created domain models, which can then be deployed and activated so that they are available as business solutions or process solution. - Solutions Contains the own system as well federated systems and usercreated business solutions with created business objects. The Business Foundation area contains the Process BO Homepages as well as the objects of the business foundation such as organization and users. 7. Data area with business and technical perspective. Refer to Data Area (Solution Center: User Guide, chap , p. 56). 1.2 Icons in the Solution Center and View Designer Icon Meaning Change to the user-specific start page Switch to edit mode inubit 6.1: Solution Center: User Guide

14 14 Overview Icons in the Solution Center and View Designer Icon Meaning View menu for selecting and creating or editing a view Save changes and switch to view mode Save changes and stay in edit mode Exit edit mode without saving Start search with the term entered on the left Update Object Browser In the object tree, navigate to the object that is currently displayed in the data area User Domain model Application Association between classes Access rights View List view Atomic value Attribute Section or element of a view or task definition, filter of atomic values Setting atomic values On the clipboard: Add current object to the Solution Center clipboard In edit mode: Create new object In View Designer: Duplicate element Open a context menu, e.g. to select the class of a new object inubit 6.1: Solution Center: User Guide

15 Overview Icons in the Solution Center and View Designer 15 Icon Meaning On the clipboard: Remove current object from the clipboard of the Solution Center In edit mode: Delete one or more objects (active only if the user logged in has the right to delete and if at least one object is selected) In View Designer: Delete element Upload file to the Solution Center repository Switch to the detailed view of an object Object properties were changed Save domain model or business object and switch to view mode In View Designer: Open element in new window Cancel editing the domain model or business object Save domain model or business object without leaving edit mode Activate domain model Deactivate domain model View Designer: Switch to full-screen mode View Designer: Close full-screen mode View Designer: Restore the last saved editing status, unsaved changes are lost View Designer: Insert element above another element (during drag & drop, if the mouse is above a permissible element) View Designer: Insert element between two elements View Designer: Insert element underneath an element inubit 6.1: Solution Center: User Guide

16 16 Overview Icons in the Solution Center and View Designer inubit 6.1: Solution Center: User Guide

17 2 Creating and Editing Domain Models 17 This section details the following topics: Introduction, p. 17 Creating a Domain Model in WebModeler, p. 18 Editing a Domain Model, p. 27 Creating a Domain Model as a Business Domain in the Solution Center, p. 31 Creating a Domain Model in the inubit Workbench, p. 44 Deactivating a Business Domain, p. 47 Deleting a Business/Process Solution, p. 48 Usage With the WebModeler, you can create domain models and deploy them as business domains in the Solution Center. There, you activate the business domains to generate business solutions from them in order to manage your business objects. For detailed information concerning WebModeler handling, refer to the WebModeler documentation, starting from chapter User Interface of the WebModeler (WebModeler: Administrator and User Guide, chap. 1, p. 9). 2.1 Introduction You can create domain models in three different ways: In the inubit WebModeler Create the complex domain models in the WebModeler if you want to create a web-based model and the application generated from it is to be exclusively or mainly data-centric. In the inubit Solution Center 3.0 You can also create simple models or make minor adjustments in the domain model itself. In the inubit Workbench You can make complex domain models that include both datacentric and process-centric components in the inubit Workbench and link them to workflows. To do this, you can use the optional process package Build+, for example. After you create the domain model, you have to deploy it in inubit Solution Center 3.0 so that it can be activated and used to create a business solution. inubit 6.1: Solution Center: User Guide

18 18 Creating and Editing Domain Models Creating a Domain Model in WebModeler 2.2 Creating a Domain Model in WebModeler This section details the following topics: Creating a Root Instance, p. 19 Creating Classes, p. 20 Creating, Adjusting and Deleting Associations, p. 21 Creating Attributes, p. 25 Saving a Domain Model, p. 26 Usage The domain model is the starting point for your business solution. The classes, attributes and associations defined in the model describe the structure of your future business objects. Careful modeling makes it easier to work with the solution later. Prerequisites You have a precise idea of the business objects to be modeled and their associations. You have installed, configured and started the Solution Center as described in the installation instructions. You have opened the inubit Cockpit in a web browser and logged on with an administrator ID. You have switched to the WebModeler portlet. The default address is: domain-modeler 1. Click the New button and select menu item Domain Model. 2. In the Properties accordion menu, open the Basic Properties panel. 3. Enter the author, the name of the model and an optional comment and confirm your entries with ENTER. 4. Drag a class icon for the root instance onto the work area and configure it. 5. For each additional object class in your model starting from the root instance add the other classes using the graphical context menu. The new class is automatically linked to the initial class via an aggregation. Refer to - Creating, Adjusting and Deleting Associations (Solution Center: User Guide, chap. 2, p. 21) inubit 6.1: Solution Center: User Guide

19 Creating and Editing Domain Models Creating a Domain Model in WebModeler 19 Alternatively, you can add a new class by dragging a class icon onto the work area. This new class starts off with no association. For information about linking classes, refer to section Creating Associations (Solution Center: User Guide, chap. 2, p. 36). 6. Adjust the associations between the classes. Refer to Creating, Adjusting and Deleting Associations (Solution Center: User Guide, chap , p. 21). There must be precisely one root instance in each diagram. Each class must be linked directly (or indirectly via another class) to the root instance, via an aggregation or composition. 7. Create the attributes for the individual classes. You can copy attributes from the classes in the scope of delivery or create new ones. Refer to Creating Attributes (Solution Center: User Guide, chap , p. 25). 8. Save the domain model. Refer to Saving a Domain Model (Solution Center: User Guide, chap , p. 26) Creating a Root Instance Prerequisites You have opened the WebModeler. You have created a new domain model via menu item New > Domain Model. 1. Drag the class icon onto the work area from the left-hand area with the icons for possible elements. 2. In the Properties accordion menu, open the Basic Properties panel. 3. In the Text field, enter the name of the root instance. 4. In the Stereotype selection list, choose the entry root_instance. The background color is set automatically. 5. In the Properties accordion menu, open the Extended Properties panel. 6. Enter the desired values for the following attributes: - Height: height of the diagram element - Shadow: shading below and to right inubit 6.1: Solution Center: User Guide

20 20 Creating and Editing Domain Models Creating a Domain Model in WebModeler - Width: width of the diagram element - Y (Center): vertical position of the center of the diagram element - X (Center): horizontal position of the center of the diagram element You can also change these properties graphically on the work area at any time. Next, add the other classes for your model. Refer to Creating Classes (Solution Center: User Guide, chap , p. 20) Creating Classes Prerequisites You have opened the WebModeler. You have created a new domain model via menu item New > Domain Model. You have created a root instance. Refer to Creating a Root Instance (Solution Center: User Guide, chap , p. 19). 1. Click the root instance and move the mouse cursor over the icon. 2. Click on the icon that appears to the right and drag the new class element to the desired position. Guide lines help you horizontally and vertically align the new element with existing elements. Alternatively, drag the class icon onto the work area from the lefthand area with the icons for possible elements. 3. In the Properties accordion menu for the new class, open the Basic Properties panel. 4. In the Text field, enter the name of the class and confirm your entry with ENTER inubit 6.1: Solution Center: User Guide

21 Creating and Editing Domain Models Creating a Domain Model in WebModeler In the color table for the Background field, select a background color for the frame with the class name or enter the color's six-digit hexadecimal code in the field in the format #RRGGBB. Refer to 6. In the Properties accordion menu for the new class, open the Extended Properties panel. 7. Enter the desired values for the following attributes: height, width, shadow, horizontal and vertical position. Refer to Creating a Root Instance (Solution Center: User Guide, chap , p. 19). 8. To define the class as an abstract class, activate the abstract field. Abstract classes cannot have any business objects as specimens of the class. They are used to define the shared attributes and associations of subclasses Creating, Adjusting and Deleting Associations This section details the following topics: Creating an Association, p. 21 Properties of an Association, p. 22 Changing the Properties of the Association, p. 24 Deleting an Association, p. 24 Usage You use associations to specify how classes are linked to one another Creating an Association Prerequisites You have opened the WebModeler. You have created a new domain model via menu item New > Domain Model. You have created at least two classes. The class from which you create an association to another class is generally seen as the top class in a composition. So select the top inubit 6.1: Solution Center: User Guide

22 22 Creating and Editing Domain Models Creating a Domain Model in WebModeler class first and then drag the connection to the subclass. You can delete associations or change them later. 1. Select a (top) class. 2. Drag a connection an other (sub) class. - To do this, click on the icon and drag and drop it onto the class you want to connect. - Alternatively, press and hold the SHIFT key and drag and drop the top class onto the desired subclass. The top class is normally linked to the subclass via a composition. 3. If necessary, adjust the association's properties. Refer to - Properties of an Association (Solution Center: User Guide, chap. 2, p. 22) - Changing the Properties of the Association (Solution Center: User Guide, chap. 2, p. 24) - Deleting an Association (Solution Center: User Guide, chap. 2, p. 24) Properties of an Association You can adjust the following properties of an association: Connection type Direction of association Label Line color Connection types The following connection types are available: Association An object in a class can be linked to one or more objects in another class, e.g. the link between a teacher and students. Aggregation Description of a class by means of its subordinate classes, e.g. the link between the classes Lecture and Student. Composition inubit 6.1: Solution Center: User Guide

23 Creating and Editing Domain Models Creating a Domain Model in WebModeler 23 Relationship between a whole and its parts, e.g. the link between a building and the individual floors and rooms, or a folder in a file system and its subfolders and the files within them. If an object in a top class is deleted, the linked objects in the subclasses are also deleted. The composition is default when a new class or association is created. You can select the composition checkbox to convert a composition into an association or inheritance. Inheritance Inheritance of a class to one or more other classes, e.g. the link between the top class Contract and the two subclasses Sales contract and Leasing contract. The business objects in an aggregation and a composition are directly linked to one another. If an object in the top class is deleted, all the objects within the subclasses that are linked to the object are also deleted. Direction of association In the Basic Properties panel in the right-hand window, you can select the direction of an association. The following entries are available: NONE: No direction SOURCE: Directed towards the source of the association TARGET: Directed towards the target of the association BOTH: Both directions Label and line color In the Basic Properties panel in the right-hand window, you have the option of entering a descriptive label for the association. The label appears on the line and can be moved with the mouse. The name of the association in the inubit Solution Center 3.0 is not identical to the label. You can change the line color using the color table for the Color field. Changing the direction of the line In the Points field, you define the coordinates of one or more points at which the line is to change direction: <X value>,<y value>[+<x value>,<y value>] Horizontal and vertical connections do not have any values. The zero point is the top left-hand corner. inubit 6.1: Solution Center: User Guide

24 24 Creating and Editing Domain Models Creating a Domain Model in WebModeler Changing the Properties of the Association Prerequisites You have opened the WebModeler. You have created a new domain model via menu item New > Domain Model. You have created at least one association between two classes. 1. Click on the connection line between two classes. 2. Click on the Edit association icon. 3. To change the connection type, choose one of the following menu items: - Association - Aggregation - Inheritance 4. Depending on the connection type, the following attributes are available: - Association Direction of the association in the direction field. - Aggregation - Activate the composition checkbox to convert an aggregation into a composition. - Deactivate the composition checkbox to convert a composition into an aggregation. 5. In the color table for the Color field, select a line color or enter the color's six-digit hexadecimal code in the field in the format #RRGGBB. The set color only applies to the connection line Deleting an Association To delete an association, click on the delete icon. Classes with no direct or indirect connection to the root instance are ignored during deployment to the Solution Center. You should only delete an association if there is at least one other association from the affected classes to another class. Associations of a class are automatically deleted if you delete the class inubit 6.1: Solution Center: User Guide

25 Creating and Editing Domain Models Creating a Domain Model in WebModeler Creating Attributes Attributes describe the class in question and determine what information the later business object should contain. Prerequisites You have opened the WebModeler. You have created a new domain model via menu item New > Domain Model. You have created at least one class. 1. Click on the class to which you want to add attributes and choose the icon for editing attributes in the graphical context menu. A dialog opens. 2. Click on the icon to add a new attribute. 3. Open the individual fields for editing by double-clicking on them and then enter the relevant values or choose a value from the selection list. Refer to - Data Types for Attributes (Solution Center: User Guide, chap. 2, p. 25) - Multiplicity of an Attribute (Solution Center: User Guide, chap. 2, p. 26) Data Types for Attributes The following data types are supported: Type text int long float Permissible data Any alphanumeric or special character Integers (32 bit) Integers (64 bit) Floating point numbers (single precision) inubit 6.1: Solution Center: User Guide

26 26 Creating and Editing Domain Models Creating a Domain Model in WebModeler Type double date datetime boolean mltext Permissible data Floating point numbers (double precision) Date: stored in the format YYYY-MM-DD, can be edited with a date picker Date and time: stored in the format YYYY-MM-DD HH:mm:ss, can be edited with a date-time picker Boolean values (yes, no) Multi Language Text. The text is displayed in the language set for the user who is logged on, if this language is already available. When an mltext property is edited, the value is only written for the language with which the user is logged on Multiplicity of an Attribute The following multiplicities are supported: Multiplicity Meaning 1..* Mandatory attribute that can occur any number of times 0..1 Optional attribute that can only occur once * Optional attribute that can occur any number of times 1 Mandatory attribute that must occur exactly once Saving a Domain Model Save the domain model so that it can be deployed and activated. Prerequisites You have correctly modeled all the classes, associations and attributes for your domain model. 1. Click on the Save icon. A dialog opens. 2. In the Model name field, the name of the root instance appears by default. However, you can change the name inubit 6.1: Solution Center: User Guide

27 Creating and Editing Domain Models Editing a Domain Model The default setting in the folder structure is /home/root. You can choose another folder or click on the New Folder button to create a new folder. All models are saved in the directory <is/sc-installdir>/ server/wm_root/models. To save your models, create a backup copy of this folder. The folders created in the WebModeler are not created in the file system. 4. In the Comment field, you can enter a detailed description of the model. 5. You can only save a newly created domain model as a new model, not as a new version. If you have edited a domain model that has already been saved, you can decide in the Save as area whether to save the domain model as a new model or a new version. After you have saved the domain mode, you can switch to the model overview and edit it later. Refer to Editing a Domain Model (Solution Center: User Guide, chap. 2.3, p. 27). Once you have finished editing the model, you can deploy it. Refer to Deploying a Domain Model (Solution Center: User Guide, chap , p. 29). 2.3 Editing a Domain Model This section details the following topics: Opening a Domain Model for Editing, p. 27 Model Changes after Deployment, p. 29 Deploying a Domain Model, p. 29 Activating a Business Domain, p Opening a Domain Model for Editing After you have saved a domain model, you can open it again for editing or set access rights for other inubit Solution Center 3.0 users. inubit 6.1: Solution Center: User Guide

28 28 Creating and Editing Domain Models Editing a Domain Model You have to set access rights if you want to invite other users to view, comment or work on a model. 1. Open the WebModeler portlet. 2. Navigate to the saved domain model. 3. In the right-hand overview window, click on the desired domain model. 4. Select an editing step: - Click on one of the plus icons in the Viewers, Annotators or Editors areas to allocate specific access rights for this model to additional colleagues. Click OK to save the changes access rights. - Click on the edit icon to edit the model. Changes to the access rights are automatically saved when they are allocated and are effective immediately. After deployment, only limited changes can currently be made to the model. Click on the Validate diagram icon to use the validation function to check whether the model was modeled without errors and only permitted changes were made. Refer to inubit 6.1: Solution Center: User Guide

29 Creating and Editing Domain Models Editing a Domain Model 29 - Deploying a Domain Model (Solution Center: User Guide, chap , p. 29) - Model Changes after Deployment (Solution Center: User Guide, chap , p. 29) Model Changes after Deployment After a domain model deployment, and if data is available, certain (incompatible) model changes (renamed or deleted classes, associations, or attributes) require a data migration. This process runs automatically but it may take considerable time. If you no longer need the data of the model classes (e.g. test data), you can skip the migration. First of all, you have to delete all instances of your business solution and then you have to deactivate your business domain in the domain library. Refer to - Deleting a Business/Process Solution (Solution Center: User Guide, chap. 2, p. 48) - Deactivating a Business Domain (Solution Center: User Guide, chap. 2, p. 47) Afterwards, you can redeploy the changed model without data migration. Refer to Redeploying Changed Models (Workbench: User Guide, chap , p. 270) Deploying a Domain Model Deploy the domain model to Solution Center to activate it and generate a business solution from it. Prerequisites You have correctly modeled all the classes, associations and attributes for your domain model. You have saved the domain model. You have open the domain model in the WebModeler. Optionally, you can validate the domain model to make sure that it can be deployed. To do so, click on the Validate diagram icon. inubit 6.1: Solution Center: User Guide

30 30 Creating and Editing Domain Models Editing a Domain Model 1. Click on the Deploy to Solution Center icon. A dialog opens. 2. Check the information in the window that opens and adjust it, as necessary. - Server URL This URL is for internal communication and should only be changed if the inubit Solution Center 3.0 runs on a different server or uses a different port. - User User name of a Liferay portal administrator - Password Password of the Liferay portal administrator 3. Click Submit to start deployment. 4. Once the domain model has been successfully deployed, save it again to save the deployment settings. 5. To reach the start page of the WebModeler with the model overview, click on the Models icon. Next, activate the business domain so you can use it to manage business objects. Refer to Activating a Business Domain (Solution Center: User Guide, chap , p. 30) Activating a Business Domain Activate the business domain to generate a business solution from it. Only once the business domain has been activated can you create business objects and link them to each other. Prerequisites You have correctly modeled all the classes, associations and attributes for your domain model. You have deployed the domain model from the WebModeler to the Solution Center inubit 6.1: Solution Center: User Guide

31 Creating and Editing Domain Models Creating a Domain Model as a Business Domain in the Solution Center Switch to the inubit Solution Cockpit. 2. In the object browser, navigate in the Domain Library to your new business domain. 3. Click on Activate Model at the bottom right to activate the business domain. 4. If the business domain does not appear in the object browser under the Solutions folder, click on the Refresh content icon in the object browser's header. The new business solution now appears under the name of the domain model in the WebModeler, under the folder Solution Center Home > Content > Solutions. You can now work with your business solution: create the new business objects and link them to each other. Refer to Using Business Solutions (Solution Center: User Guide, chap. 3.2, p. 57). 2.4 Creating a Domain Model as a Business Domain in the Solution Center This section details the following topics: Creating a New Domain, p. 32 Creating Classes, p. 33 Creating an Attribute, p. 34 Creating Selection Lists, p. 35 Uploading Image Data, p. 36 Creating Associations, p. 36 Defining Validation Rules, p. 38 Filtering and Sorting, p. 40 Activating a Domain Model, p. 44 As an alternative to the WebModeler, you can also create your domain model in the inubit Workbench or in the Solution Center. For the list of icons and their meanings, refer to section Icons in the Solution Center and View Designer (Solution Center: User Guide, chap. 1, p. 13). inubit 6.1: Solution Center: User Guide

32 32 Creating and Editing Domain Models Creating a Domain Model as a Business Domain in the Solution Center Creating a New Domain 1. In the menu tree, click on the Domain Library folder. 2. Go to Edit mode. 3. In the Domain(s) area for the data area, click on the plus icon or the triangle next to it. 4. If applicable, choose the entry scc:domain from the context menu that opens. 5. Change the name of the new domain, e.g. to Fleet model. 6. Open the new domain by clicking on the Edit object properties icon. 7. Set the properties Namespace URI and Namespace Prefix as follows: - Namespace URI: - Namespace Prefix: fp 8. Save your entries. Your new domain should now look like this: Once you have created the domain, you can create the classes. Refer to Creating Classes (Solution Center: User Guide, chap , p. 33) inubit 6.1: Solution Center: User Guide

33 Creating and Editing Domain Models Creating a Domain Model as a Business Domain in the Solution Center Creating Classes You use the object classes to specify what type of objects you want to manage. There must be at least one root instance in each domain. The number and structure of other classes depends on the type of future application Creating a Root Instance 1. In the menu tree, open the new domain. If the domain does not appear immediately, refresh the content of the menu tree. 2. In the Types section, click the plus icon next to the Classes entry or the triangle next to the icon. 3. If applicable, choose the entry scc:class from the context menu that appears. 4. Enter the name of the root instance, e.g. Fleet. 5. Open the new classes by clicking on the Edit object properties icon. 6. In the Stereotypes field, enter root_instance. 7. Optionally, you can enter a description of the root instance in the Description field. 8. Save the change. In the Stereotypes field, the following entry now appears: [root_ instance]. The root instance has now been created. You can then create more classes. Refer to Creating Additional Classes (Solution Center: User Guide, chap , p. 33) Creating Additional Classes 1. Open your domain. 2. In the Types section, click the plus icon next to the Classes entry or the triangle next to the icon. 3. If applicable, choose the entry scc:class from the context menu that appears. 4. Enter the name of the class. inubit 6.1: Solution Center: User Guide

34 34 Creating and Editing Domain Models Creating a Domain Model as a Business Domain in the Solution Center 5. Repeat the steps for all other classes. 6. Save the changes. After you have created the classes, you can change the properties of the classes and assign attributes to the classes. Refer to - Defining abstract classes (Solution Center: User Guide, chap. 2, p. 34) - Creating an Attribute (Solution Center: User Guide, chap. 2, p. 34) Defining abstract classes 1. Open for editing the class that you want to configure as an abstract class. 2. Activate the Abstract checkbox. 3. Save the changes. After you have created the classes, you can assign attributes to the classes. Refer to Creating an Attribute (Solution Center: User Guide, chap , p. 34) Creating an Attribute You use attributes to specify which properties you want to record and manage for the individual object classes. For a Vehicle class, for example, you define the attributes Manufacturer, Model, Registration date and License plate. 1. Open the desired class for editing. 2. In the Attributes section, click the plus icon. 3. From the context menu, choose the entry scc:attribute. 4. Rename the attribute, e.g. to Manufacturer. 5. Open the attribute for editing. 6. Enter the desired values in the relevant fields. Refer to Attribute properties (Solution Center: User Guide, chap. 2, p. 35). 7. Save the changes inubit 6.1: Solution Center: User Guide

35 Creating and Editing Domain Models Creating a Domain Model as a Business Domain in the Solution Center 35 Attribute properties Attribute property Description Properties Range From Range To Range Message Mandatory Is Multiple Default Value Constraint Message Constraint Start of the value range End of the value range Message if range is exceeded Mandatory attribute Attribute may occur multiple times Default value Message if the value of the attribute does not comply with the regular expression defined in the Constraint field Regular expression that the value of the attribute has to correspond to Outgoing Associations Simple Type(s) Validation(s) Target type for the association Refer to Creating Attributes (Solution Center: User Guide, chap , p. 25). Check for the association Incoming Associations Atomic Filter Expression(s) Order Criteria(s) Attribute Filter(s) Atomic Value(s) These fields show all the places where the attribute is used. You can add a new reference to the attribute by clicking on the plus icon. You can delete a reference by clicking on the minus icon Creating Selection Lists Use In a selection list (data type: Enum) you define a list of character strings that you can assign to an attribute to ensure that only these values are used. 1. Select the domain for which you want to create a selection list. inubit 6.1: Solution Center: User Guide

36 36 Creating and Editing Domain Models Creating a Domain Model as a Business Domain in the Solution Center 2. Go to Edit mode. 3. Click on the plus icon next to the entry Enums, choose the context menu item scc:enum (if applicable) and name the selection list, e.g. List of manufacturers. 4. Open the selection list for editing. 5. In the Literals section, click the plus icon in the table header. 6. Choose the context menu item scc:literal and name the new selection list entry, e.g. Audi. 7. Double-click on this entry's other column and enter the following values: - Key: unique designation as a key for identifying this entry. - Position: position of the entry in the selection list. - Image URI: URI for an image file that is displayed in the field that this selection list fills. You can enter any URL. Refer to Uploading Image Data (Solution Center: User Guide, chap , p. 36) Uploading Image Data 1. Select the domain for which you want to create a selection list. 2. Go to Edit mode. 3. Switch to the View for Attachments As Grid view. 4. Click on the Add attachment icon. A dialog opens. a. Click on the folder icon, navigate in the explorer window that opens to the desired file and click Open. b. In the file explorer, navigate to the desired file and drag it to the Add Attachm button. The link to the image in the database appears in the table together with other information Creating Associations Use Associations are used to link classes to each other. Refer to Creating, Adjusting and Deleting Associations (Solution Center: User Guide, chap , p. 21) inubit 6.1: Solution Center: User Guide

37 Creating and Editing Domain Models Creating a Domain Model as a Business Domain in the Solution Center 37 Repeat the following steps for all the classes that need to linked, according to your model. 1. In the object browser, navigate to the class in your domain that you want to link, e.g. Vehicle. 2. If necessary, switch to Default View for class class, navigate to the Source of section under the section Relationship and click on the plus icon or the triangle next to it. 3. If applicable, choose the context menu entry scc:relationship and name the new association (e.g. Vehicle <--> Fleet ) and open it for editing. The designation of the association is optional. In the examples in this documentation and in the Business Foundation Model, the following notation is used to describe an association: <parent class (source)> <--> <child class (target)> 4. Choose the type of link you want ( Composition, Association, Aggregation ) from the selection list in the Type field in the Properties section. 5. Set the multiplicity for the source and target classes : The object can be linked to a maximum of one object from the other class. - 1: The object must be linked to exactly one object from the other class. - *: The object can be linked to any number of objects from the other class *: The object must be linked to at least one object from the other class. 6. Set the role name for the source and target classes. - Optional: in the TargetRoleName field, set a designation for the target of the association, in order to specify the direction of the association. - Optional: in the SourceRoleName field, set a designation for the source of an association, in order to specify the direction of the association. You can use the attributes TargetRoleName and SourceRoleName to assign a person the role Tenant or inubit 6.1: Solution Center: User Guide

38 38 Creating and Editing Domain Models Creating a Domain Model as a Business Domain in the Solution Center Landlord, for example. When creating a link later, you can select which role the objects are displayed for. 7. In the Outgoing Associations section, click on the plus icon next to the entry Class(s) with the Target-of tooltip. 8. Choose the class you want (e.g. Contract ) from the window that opens. Use the selection window's search function to find the target class. 9. Save the changes. In addition to the associations between the individual classes, there has to be at least one class that has an association to the root instance. Creating root instance associations A root instance association is used to link the root class to another class. The root instance must have an association to at least one class in the model. Each class in your model must be linked directly or indirectly (via one or more classes) to the root instance, via an aggregation or composition. A root instant association is created in the same way as associations between the other classes Defining Validation Rules Usage Validations are special objects that you can use to define validation regulations. In the domain, you create universal validation objects that can be reused in all classes and link them as an association to the object to be validated. You can define alternative or additional individual validation rules for each class. However, these only apply to the class for which they are defined. Universal validation rule 1. Select the domain for which you want to create a validation rule. 2. Choose the Generic view. 3. Go to Edit mode inubit 6.1: Solution Center: User Guide

39 Creating and Editing Domain Models Creating a Domain Model as a Business Domain in the Solution Center Click on the plus icon next to the entry Validation(s), choose the context menu item scc:regex_validation (if applicable) and name the validation rule. 5. Open the validation rule for editing. 6. In the Properties section, click the Message field. 7. Enter a message text to appear if the validation rule is not complied with. 8. In the Properties section, click the Constraint field. 9. Enter validation rule as the regular expression. 10. Save your entries. Validation rule for a class 1. Select the class for which you want to create a validation rule. 2. Choose the Generic view. 3. Go to Edit mode. 4. In the Properties section, click the Constraint Message field. 5. Enter a message text to appear if the validation rule is not complied with. 6. In the Properties section, click the Constraint field. 7. Enter validation rule as the regular expression. 8. Save your entries. 1. Select the domain for which you want to create a validation rule. 2. Choose the Generic view. 3. Go to Edit mode. 4. Click on the plus icon next to the entry Validation(s), choose the context menu item scc:regex_validation (if applicable) and name the validation rule. 5. Open the validation rule for editing. 6. In the Properties section, click the Message field. 7. Enter a message text to appear if the validation rule is not complied with. 8. In the Properties section, click the Constraint field. 9. Enter validation rule as the regular expression. 10. Save your entries. Assigning a validation rule 1. In your domain, open the attribute to which you want to add a validation rule. 2. Go to Edit mode. inubit 6.1: Solution Center: User Guide

40 40 Creating and Editing Domain Models Creating a Domain Model as a Business Domain in the Solution Center 3. Click on the plus icon in the Outgoing Associations area. 4. Select the validation rule defined for your domain. 5. Save the changes Filtering and Sorting This section details the following topics: Configurable Filters, p. 40 Configuring the REST Filter, p. 41 Filtering the Display, p. 43 Showing/Hiding Table Columns, p. 44 Sorting a Table Column, p Configurable Filters Usage In a view, you can define static filters for an object group (object set) in order to restrict the set of objects displayed. 1. Choose the object set for which you want to define a filter. 2. Go to the Filters tab. 3. Click the plus icon next to the Existing Filters field. 4. Choose one of the following filter types: - Class filter (classfilter) - Attribute filter - Character string filter: stringfilter - Selection list filter: enumerationfilter - Date filter: datefilter - Filter for integers: integerfilter - Filter for Boolean values: booleanfilter - Combined filters These filters can contain multiple logically linked filters. - REST filters Configuring a filter based on a REST request Refer to Configuring the REST Filter (Solution Center: User Guide, chap , p. 41) inubit 6.1: Solution Center: User Guide

41 Creating and Editing Domain Models Creating a Domain Model as a Business Domain in the Solution Center Open the filter for editing. 6. Choose the class or attribute to be filtered. 7. From the selection list, choose the filter type and enter a filter value. Depending on the attribute type, various filter types are available: - Equals: value is the same as the filter value - Starts with: value starts with the specified character - Before: date is before the specified date - After: date is after the specified date - Smaller: value is smaller than the filter value - Greater: value is larger than the filter value 8. Enter the filter value. Depending on the filter type, there is an input field, a selection list or a checkbox. 9. Save your entries Configuring the REST Filter Use Filtering the contents of a view depending on internal or external data. Examples Displaying contents depending on the age of the user (film rental) Displaying further options depending on already selected options (rate configurator) Prerequisites You have created a view for the data to be filtered. You have access to your Process Engine and external data sources if necessary. Creating a workflow to generate the filter configuration In the workbench, create a new workflow that dynamically generates a filter configuration for the Solution Center. The Solution Center calls this workflow when opening the page of a business solution and transfers the currently displayed object in the data flow as well as the current user to the variables. The workflow can use this data to make a decision for corresponding filter settings. If necessary, it can also query additional data from the Solution Center or another system, for instance the birth date of the current user, to calculate the user s age. The workflow returns a filter configuration in XML format that evaluates the Solution Center and filters the data accordingly. inubit 6.1: Solution Center: User Guide

42 42 Creating and Editing Domain Models Creating a Domain Model as a Business Domain in the Solution Center Create a REST Input Connector 1. Create a new REST Input Connector with which the workflow should start. 2. Name and activate the connector. 3. Open the Resource Configuration tab. 4. Deactivate the GET (call resource data) checkbox and select the POST (create new resource) checkbox. Note that there can be only one filter. If there is already another filter you have to configure both filters as a sub-filter of a composite filter. 5. At the end of the URL line, click the icon and select the Copy URL menu item. You need this URL to configure the REST filter in the Solution Center. 6. Create a REST-Filter in Solution Center (Solution Center: User Guide, chap. 2, p. 43). 7. Open the Reply Configuration tab. 8. Set the reply status code to 200 for OK. 9. Click Finish. Creating an XSLT Converter 1. Create a new XSLT Connector and give it a name. 2. Go to the Module Editor tab. 3. Add the following structure below the xsl:template entry and adjust it: <filter:filter xmlns:filter="inubit.com/solutioncenter/query/filter/rest" xmlns:xsi=" xsi:type="filter:attributefilter"> <filter:type>[operator]</filter:type> <filter:attribute>[namespace-prefix]:[internal name]</filter:attribute> <filter:value>[value]</filter:value> </filter:filter> - Possible operators Attribute type Character string attribute including multi-language texts Numeric attribute Date and time attribute Boolean attribute Operators Equals, StartsWith, Contains, NotEquals Smaller, Equals, Greater Before, Equals, After Equals, NotEquals inubit 6.1: Solution Center: User Guide

43 Creating and Editing Domain Models Creating a Domain Model as a Business Domain in the Solution Center 43 Attribute type Enumeration attribute Operators Equals, NotEquals 4. Click Finish. 5. Connect the REST Input Connector with the XSLT Converter. 6. Publish the workflow. Create a REST-Filter in Solution Center 1. Navigate to the object set of the view for which you want to define a filter. 2. Open the Filter tab. 3. Go to Edit mode. 4. Click the icon and select the entry scc:restfilter. 5. Name the new filter. 6. Insert the URL of the REST Input Connector copied above into the URL field. Create a REST Input Connector (Solution Center: User Guide, chap. 2, p. 42) 7. Save the filter Filtering the Display Usage For filtering the display by means of the values in a column 1. Click on the triangle in the header of the column whose values you want to filter. The triangle appears if you move the mouse cursor over the column header. 2. Choose the menu item Filter, a comparison operation (if applicable) and enter the corresponding filter value. 3. Activate the checkbox next to the menu item Filters. The column header of a filtered column is displayed in bold italics. To deactivate a filter, deactivate the checkbox next to the menu item Filters and refresh the page, if necessary. inubit 6.1: Solution Center: User Guide

44 44 Creating and Editing Domain Models Creating a Domain Model in the inubit Workbench Showing/Hiding Table Columns Usage Selecting the table columns to be displayed 1. Click on the triangle in the header of the column whose columns you want to show or hide. The triangle appears if you move the mouse cursor over the column header. 2. Choose the Columns menu item and activate all the columns that you want to display. Deactivate all the columns that you do not want to display Sorting a Table Column 1. Click on the triangle in the header of the column that you want to sort by. The triangle appears if you move the mouse cursor over the column header. 2. Choose either the menu item Sort Ascending or the menu item Sort Descending Activating a Domain Model After you have completely created the domain model with all classes, attributes and associations, you need to activate it. Refer to Activating a Business Domain (Solution Center: User Guide, chap , p. 30). 2.5 Creating a Domain Model in the inubit Workbench This section details the following topics: inubit 6.1: Solution Center: User Guide

45 Creating and Editing Domain Models Creating a Domain Model in the inubit Workbench 45 Creating and Deploying a Business Object Diagram, p. 45 Creating and Deploying a Business Process Diagram, p Creating and Deploying a Business Object Diagram Usage As a basis for your work with the Solution Center, you can use business object diagrams (BODs) that you create with the inubit Workbench and publish on the Solution Center. Prerequisites The inubit Solution Center Server has been started. The connection between inubit Process Engine and inubit Solution Center 3.0 is configured correctly. How it works Create your BOD in the inubit Workbench. To deploy it to Solution Center, click on the Solution Center deployment button. A domain model is created from the BOD in the inubit Solution Center 3.0. In the inubit Solution Center 3.0, a generic view is automatically created for each class. You can enter master and transaction data in this view. In addition, you can create your own views. You can use the View Designer and the Solution Center's standard functions to do so. This way, you can easily create a data model for a business solution and make it available as a specialized application via a web-based interface. Refer to Using Views (Solution Center: User Guide, chap. 4, p. 63). When you create a BOD for the Solution Center, note that your diagram has to include as a root instance a class that represents your business solution. This is not necessary if your model contains classes that are derived from classes in another model that contains a root instance. Refer to Creating a Root Instance (Solution Center: User Guide, chap , p. 33). This root instance must have associations (generally aggregations) to one or more other classes. inubit 6.1: Solution Center: User Guide

46 46 Creating and Editing Domain Models Creating a Domain Model in the inubit Workbench Depending on the data model, the remaining classes are linked to other classes via associations, aggregations or compositions. Additional information Working with BODs is described in detail in the inubit user guide. Refer to Business Object Diagrams (Workbench: User Guide, chap. 10, p. 247) Creating and Deploying a Business Process Diagram In the inubit Workbench, you can also create a business solution from a business process diagram (BPD). Prerequisites You have correctly configured Solution Center integration in the inubit Workbench on the Configuration > Solution Center > Server configuration page. Refer to Configuring the Solution Center Server (inubit Process Engine: Administrator and Developer Guide, chap. 2.5, p. 49). You have correctly configured your Process Engine as a federated system in the Solution Center. Refer to Configuring inubit Process Engine as a Federated System (Solution Center: Administrator Guide, chap , p. 23). 1. Open the inubit Workbench. 2. Create a new BPD. 3. On the Business Process Diagram page, choose the option Solution Center process model. The names for the process, the business object and the process homepage are created the model name, as is the optional name of a new BOD, as well as the namespace prefix and the namespace URI. Refer to Business Process Diagram Tab (BPD only) (Workbench: User Guide, chap , p. 103). 4. If necessary, define metadata. 5. Click Finish. A BPD and a BOD with preconfigured elements are generated. 6. If necessary, modify the BPD. Refer to Modeling Business Process Diagrams (Workbench: User Guide, chap. 6, p. 141) inubit 6.1: Solution Center: User Guide

47 Creating and Editing Domain Models Deactivating a Business Domain If necessary, adjust the BOD or add its own classes to it. Refer to Business Object Diagrams (Workbench: User Guide, chap. 10, p. 247). 8. Display the associated BPD. 9. Click the Solution Center deployment button of the BPD to start automatic deployment of the BPD and BOD to the Solution Center. Refer to Deploy Solution Center process model to Solution Center (Workbench: User Guide, chap , p. 176). The Solution Center deployment button the BOD only. for the BOD deploys 2.6 Deactivating a Business Domain Use Necessary for redeploying the related domain model without data migration (i.e. faster) from the BOD into the Solution Center. Refer to Deploy Solution Center domain model to the Solution Center (Workbench: User Guide, chap , p. 269). Prerequisites You have deleted all instances of the business solution. Deleting a Business/Process Solution (Solution Center: User Guide, chap. 2, p. 48) 1. Navigate to your business domain below the Solution Center Home > Domain Library > [name of the business domain] node. 2. Click the Activate Model button. 3. Confirm the messages that the model is deactivated successfully. Once the model is deactivated, you can redeploy and reactivate it after model changes. After the Business Object Diagram is deployed from the Workbench, the business domain is activated automatically. inubit 6.1: Solution Center: User Guide

48 48 Creating and Editing Domain Models Deleting a Business/Process Solution 2.7 Deleting a Business/Process Solution Use You must delete all instances of a solution before you can deactivate the business domain. Deactivating a Business Domain (Solution Center: User Guide, chap. 2, p. 47) Prerequisites 1. Navigate to your business/process solution below Solution Center Home > Solutions > Business Foundation > [name of the solution] node. 2. From the context menu of the solution in the object browser, select the Delete item. 3. Confirm the message by clicking Yes, thus indicating that you really want to delete the selected entry. The solution and all of its instances (data) will be deleted inubit 6.1: Solution Center: User Guide

49 3 Using the Solution Center 49 This section details the following topics: Start and Setup of the inubit Solution Cockpit, p. 49 Using Business Solutions, p. 57 Working with Process Solutions, p. 59 Processing Tasks, p. 60 Use You use the Solution Center to create web-based business solutions. You create the domain models for these in the WebModeler, directly in the Solution Center or you can use Business Object Diagrams created using the inubit Workbench. This document describes how you activate and use a domain model created in WebModeler as a deployed domain model in the Solution Center. 3.1 Start and Setup of the inubit Solution Cockpit This section details the following topics: Header Area, p. 49 Object Browser, p. 50 Data Area, p Header Area This section details the following topics: Toolbar, p. 50 Object Path, p. 50 inubit 6.1: Solution Center: User Guide

50 50 Using the Solution Center Start and Setup of the inubit Solution Cockpit Toolbar Start page The Start page icon takes you to the user-specific start page ( Solution Center > Content > Business Foundation > Solution Center > [current user] ). View and edit mode The Edit lets you switch between edit and view modes. When you first start the program, view mode is active. View Menu You use the View icon to open the view menu with a list of views that have been defined for the object or the object class as well as the menu items for editing the current view and for creating a new view. By default, there is at least the Generic view, which lists all properties of an object or an object class. You can define as many own views as you wish. Refer to Using Views (Solution Center: User Guide, chap. 4, p. 63). Search The search finds all objects with the specified character string. By entering a data type in the Type field you further limit the number of objects that will be found. Click the line with the object you were looking for to navigate directly to the object Object Path The object path shows the position of the currently selected object in the tree structure. Use the individual links to navigate directly to the parent object. In case of longer paths, only the last entries are displayed. To display the entries preceding them, click the triangle at the start of the path Object Browser This section details the following topics: Domain Library, p. 51 Business Foundation Model 3, p. 51 Solutions, p inubit 6.1: Solution Center: User Guide

51 Using the Solution Center Start and Setup of the inubit Solution Cockpit 51 History, p. 52 Clipboard, p. 52 Toolbox, p. 53 Assigning Access Rights, p. 54 Deleting Objects, Libraries or Folders, p. 55 Creating Menus and Menu Items, p. 55 Use The object browser displays the supplied objects as well the objects that you have created and the menus in a tree structure. By default, the object tree contains the elements Domain Library and Solutions. Refer to - Domain Library (Solution Center: User Guide, chap. 3, p. 51) - Solutions (Solution Center: User Guide, chap. 3, p. 52) As soon as you have created, deployed and activated a structure of your own, the new domain also appears in this tree. In it you then create new instances of this domain, e.g. a new employee or a new customer. If you have defined classes yourself, new instances appear in the domain of the solution. If you have used the supplied classes for modelling, they appear in the business foundation. If a new object that you have created is subsequently not displayed in the menu tree, reload the page by clicking the Reload content button Domain Library The Domain Library contains all supplied domains of the default classes and the domains of the solutions that you have created. All default classes are started automatically when starting the Solution Center, if they are not already available. The domains of the solutions you have created yourself also appear as separate domains in the Domain Library after deployment Business Foundation Model 3 The Business Foundation Model contains all instances of the supplied classes as well as the user accounts of the Solution Center. You create user accounts in the inubit Enterprise Portal (Liferay) by choosing the Control Panel in the main menu. inubit 6.1: Solution Center: User Guide

52 52 Using the Solution Center Start and Setup of the inubit Solution Cockpit The complete Liferay documentation is available at docs.liferay.com/portal/5.2/official/liferay-administration-guide.pdf Solutions All solutions that you have created in the Solution Center or in the inubit Workbench or which you have imported appear under the Node Solution Center Home > Solutions. In addition, the objects of the Business Foundation Monitor Model 3 appear here, including previously created portal users. Refer to Business Foundation Model 3 (Solution Center: User Guide, chap. 3, p. 51) History The history shows all elements selected during the current session so that you can easily go to a previously viewed or edited document without having to navigate there. You can add an object from the history directly to another object. 1. In the object browser, navigate to the object to which you want to add another object. 2. In the object browser, navigate to the target object which you want add to the previously selected object. 3. Click the History menu item. 4. Choose the Edit view. 5. Select the object to be copied in the history and hold down the mouse button to drag and drop it from the history to next to the desired object in the right window. If the object can be added, the icon changes from to Clipboard You can copy the currently selected object to the clipboard to add it to another object. The advantage compared to the history is that this provides a better overview because you can remove objects you no longer need from the clipboard inubit 6.1: Solution Center: User Guide

53 Using the Solution Center Start and Setup of the inubit Solution Cockpit Select the object to be copied in the tree structure. 2. Click the Clipboard menu item. 3. Click the plus icon to add the object to the clipboard. 4. Navigate to the target object to which you want to add the object from the clipboard. 5. Click the Clipboard menu item and hold down the mouse button to drag and drop the object from the clipboard to the object in the right window. If the object can be added, the icon changes from to. To remove an object from the clipboard, select the object and click the minus icon Toolbox Use The Toolbox offers functions for importing and exporting all or individual objects of your domain models and business solutions. All associations to all other classes - including classes that are not exported - are exported. The actual associated classes/objects, however, are not exported. Before you import you must make sure that all associated classes/ objects already exist. Before you can import objects of a business solution, you must have imported and successfully activated the domain model. Exporting data 1. In the object browser, choose the object to be exported. 2. Click the Export button. 3. Choose the folder and the file name for the archive. 4. Save the file. Importing data 1. In the object browser, choose the object into which you want to import objects. 2. Choose the archive to be imported. 3. Click the Import button. 4. Confirm the success or error message. inubit 6.1: Solution Center: User Guide

54 54 Using the Solution Center Start and Setup of the inubit Solution Cockpit The structure of the object to be imported must be identical to the structure of the class to which you want to add the object Assigning Access Rights Use Assigning/removing authorizations for individual objects, libraries and folders to user roles 1. In the object browser, open the context menu of the object for which you want to grant access rights. 2. Select the entry Permissions. A dialog opens. 3. Select the desired role. 4. Activate the checkboxes Allow or Deny in the columns for the desired rights. Activate the checkbox Deny to remove an access right from a user role, even if it inherited it from a parent object. - ChangePermissions - Create - Delete - Read inubit 6.1: Solution Center: User Guide

55 Using the Solution Center Start and Setup of the inubit Solution Cockpit 55 - Write 5. To add a new user role, click the Add button. 6. In the dialog that now opens, click one or more roles and click OK. 7. Set the access rights for each user role as described in step 3 and step Click OK to close the dialog Deleting Objects, Libraries or Folders 1. In the object browser, open the context menu of the object to be deleted. 2. Select the entry Delete. A dialog opens. 3. Click Yes to remove the object. Click No if you do not want to remove the object Creating Menus and Menu Items For your business solution, you can add individual objects and one of your own views in a separate menu in order to be able to access them directly. 1. Log on to the Enterprise Portal (standard address: localhost:8000). 2. Go to the page with the Solution Center portlet. 3. In the object browser, navigate to the desired object. 4. Open the context menu for the object and select the menu item Add to menu. inubit 6.1: Solution Center: User Guide

56 56 Using the Solution Center Start and Setup of the inubit Solution Cockpit 5. In the Menu name field, select an existing menu or enter a new name to create this menu. 6. In the View name field, you can select an existing view for the object. 7. In the Name field, enter the name of the new menu entry. The new menu appears in the menu bar of the Solution Center Data Area Use In the data area, you see the data of the domain model and the business solutions, and you can also edit these here when you are in Edit mode Creating and Editing Domain Models In Edit mode you create and edit business domains and views for classes and associations. In the Generic view, the following two tabs are available. Business Perspective Contains an overview of classes, attributes, associations, views and list views as well as the attributes of a class that have usually been created by the user or were included in the scope of delivery. Technical Perspective Contains all properties that the selected attribute has by default, e.g. node ID, creation date and creator. Refer to - Creating a Domain Model as a Business Domain in the Solution Center (Solution Center: User Guide, chap. 2, p. 31) - Defining Views in the Solution Center (Solution Center: User Guide, chap. 4, p. 72) inubit 6.1: Solution Center: User Guide

57 Using the Solution Center Using Business Solutions Using Business Solutions This section details the following topics: Creating New Business Objects, p. 57 Assigning Business Objects, p. 58 Creating Views, p. 58 Usage In Edit mode, you create new business objects and interlink them. In the Generic view, the following two tabs are available. Business Perspective Contains an overview of the technical attributes and associations of a business object that were usually created by the user or were included in the scope of delivery. Technical Perspective Contains all attributes that the selected object has by default, e.g. node ID, creation date and creator Creating New Business Objects The classes defined in the domain model are the basis for the business objects of these classes that are to be created the individual vehicles and contracts as well as their assignments. Prerequisites You have created and deployed a domain model. You have activated the domain model. 1. In the object browser, click the business solution you want to edit. 2. Go to Edit mode. 3. In the Outgoing Associations area, click the plus icon next to the name of the class for which you want to create a new object. 4. If appropriate, choose the context menu entry that represents the desired class. The prefix corresponds to the entry in the Namespace-Prefix attribute that you specified when you deployed the domain model. 5. Click the new name and rename the new object. Choose a meaningful name - ideally according to a uniform pattern, e.g. ContractNo.L This will later appear as the title of the business object. inubit 6.1: Solution Center: User Guide

58 58 Using the Solution Center Using Business Solutions 6. Open the business object for editing. 7. Save the changes. Since you have not defined any own views yet, the classes, objects and attributes appear in the generic view in which all included child objects, attributes and associations are displayed with all their values in one row each. Once you have created several business objects you can assign them to each other. Refer to Assigning Business Objects (Solution Center: User Guide, chap , p. 58) Assigning Business Objects You can assign business objects of a class to one or more business objects of another class according to the associations of the classes of your business domain. In our example, you can assign each contract a vehicle and vice versa. 1. Click on your business solution in the Solution Center > Content > Solutions folder to display the root instance. 2. Switch to Edit mode. 3. Open the business object to be linked for editing. 4. In the Outgoing Associations area, click the plus icon next to the name of the class whose business object you want to link. A dialog appears. 5. Select the desired business object Creating Views Having your own views for your business solution and the individual classes makes it easier for the users of your business solution to enter and edit data. Refer to Using Views (Solution Center: User Guide, chap. 4, p. 63) inubit 6.1: Solution Center: User Guide

59 Using the Solution Center Working with Process Solutions Working with Process Solutions You generate a process solution from a Solution Center Business Process Diagram (BPD) created for your process. A Business Object Diagram (BOD) is then automatically generated from that. You can add additional classes and associations if the respective classes are not included in the Business Foundation Model that comes with the product. Once you have finished creating and publishing the BOD, open the corresponding BPD and start the deployment to the Solution Center. The following actions, among others, are executed: Creation, linking, publication of a BOD Deployment and activation of the BOD (in the Solution Center) Creation of a process homepage through which you access your process solution Creation of a standard view for your process solution that you can modify later in the Solution Center Creation of task views for the task lists of the portal users Generation, publication and activation of technical workflows from the BPD Creation of a start button with which a new process is started Assignment of portal roles for the BPD Refer to Creating a Process Solution (Tutorials, chap. 5, p. 83) Starting a New Process Prerequisites You have created a process solution and successfully deployed it in the Solution Center. Refer to Creating a Process Solution (Tutorials, chap. 5, p. 83). 1. In the object browser, navigate to the homepage of your process solution in the folder Solution Center Home > Solutions > Business Foundation. 2. Click the start button of your process solution. inubit 6.1: Solution Center: User Guide

60 60 Using the Solution Center Processing Tasks A window with attributes of the new process appears. When you start the process for the first time, it may be that no attributes appear in the window with the process details. Open the view for editing and add the desired attributes; refer to Adapt view (Tutorials, chap. 5, p. 95). 3. Enter the appropriate information and save it. 4. Click the respective button to send the information. To cancel the process, click the button clearing the entries. Once you have sent the data, it appears in the task list of the process initiator, e.g. the applicant, and in the task list of the next processor, e.g. the HR manager who can approve or reject the leave application. Refer to - Submitting Leave Applications (Tutorials, chap. 5, p. 97) - Approving an Application for Leave (Tutorials, chap. 5, p. 99) - Processing Tasks (Solution Center: User Guide, chap. 3, p. 60) 3.4 Processing Tasks In the Solution Center portlet you can view and process the tasks not only of your process solution but also your tasks in inubit Workbench. 1. Click the Start page button to go to your personal folder in the object browser inubit 6.1: Solution Center: User Guide

61 Using the Solution Center Processing Tasks Click the icon at the beginning of the row with the task that you want to process. Two menu items appear with which you can choose whether you only want to view the task or lock it for processing. If you lock the task for processing, other users cannot edit it. In both cases the task details are displayed. 3. Click the respective button to reject or approve the task. 4. The task is removed from the task list and sent to the next processor, if any. inubit 6.1: Solution Center: User Guide

62 62 Using the Solution Center Processing Tasks inubit 6.1: Solution Center: User Guide

63 4 Using Views 63 This section details the following topics: Generic View, p. 63 Defining Views in View Designer, p. 65 Defining Views in the Solution Center, p. 72 Usage Views are designed to display data in formatted form. For each class, you can create any number of views and use these at various points in your business solution. In Edit mode, you can edit the displayed data, create and link new object as well as delete objects. You use the view menu in the toolbar to choose a view, open a previously created view for editing or create a new view. 4.1 Generic View For each class there is a generic view with the two tabs Business Perspective and Technical Perspective. Business Perspective This view shows all attributes, associations and business objects that you have created. Technical Perspective This view shows all attributes created automatically when the object was created and the values of these attributes, e.g. Created by and Created on. inubit 6.1: Solution Center: User Guide

64 64 Using Views Generic View Structure of a view Views in the Solution Center consist of two areas (sections), the header section and the body section. Unlike the header section, the body section can include an almost unlimited number of different - even hierarchically structured - data sections with different styles. In the header section you should only use the two attributes Title and Description to name and describe the business object. In the body section you choose the styles for the data section that best represent your business objects. In the editstyle field you specify the style for the edit mode and in the viewstyle field you define the style for the view mode. Style elements for data sections You can choose the following predefined styles for a data section: Header This style is designed for the header section. The following styles are designed for the data section in the body section: - Factsheet - List - Overview - Newspaper - Tab Style elements for list views You can choose the following predefined stiles for a list view: Grid, Gridwithprevieweast, Gridwithpreviewsouth Tables that use ExtJS grids for displaying business objects without (grid) or with a preview of the business object in the generic view. The generic view is used by default. You can define your own views and set them as the default. Table HTML table without ExtJS grid Csv Comma-separated display of attribute values Action (only for elements of the action type) Action is to be rendered as a button. Style elements for attribute values (atomic value) You can choose the following predefined stiles, among others, for an attribute value: Simple: Single line text Date: Date selection using a calendar inubit 6.1: Solution Center: User Guide

65 Using Views Defining Views in View Designer 65 Time: Date selection using a calendar and time selection using a selection list HTML: Multi-line text that can contain HTML formatting Checkbox: For activating/deactivating Boolean values Textarea: Multi-line text Int: Whole numbers, other characters are not allowed Float: Floating point numbers (real numbers) Enum_dropdown: Selection list as a drop-down list Attachment_img (only for the Content attribute of attachments): Shows the content of the GUI as an image if the name of the attachment has a corresponding file extension, e.g.: image.png Attachment_download: Attachment is displayed as a link and made available for downloading when clicked. Enum_list: Selection list as a list Enum_checkbuttons: Selection list is displayed as checkboxes Elements in a data section The two main elements of a data section are: Atomic values To display an individual attribute value of the class for which you want to define the view Object sets, e.g. for associations For selecting associations, i.e. attribute values of a class that is linked to the class for which you want to define the view. To be able to display and edit an object group of a linked class in a view of another class, you need a list view of this class. List views For displaying an association and its values. When adding an object group you can select an already created list view or create a new list view. 4.2 Defining Views in View Designer This section details the following topics: Defining a New View, p. 66 Defining the Header Section, p. 67 Defining the Body Section, p. 67 inubit 6.1: Solution Center: User Guide

66 66 Using Views Defining Views in View Designer Links to Actions, Filters and Sorting, p. 69 Structure of View Designer, p. 70 You can conveniently create views in View Designer. Refer to Structure of View Designer (Solution Center: User Guide, chap , p. 70). Alternatively, you can also create and edit views directly in the Solution Center. Refer to Defining Views in the Solution Center (Solution Center: User Guide, chap. 4.3, p. 72) Defining a New View 1. In the object browser, navigate to the business solution for which you want to create a view. 2. Open the View menu in the toolbar and choose the menu item Create New View... A dialog opens. 3. Enter a name for the new view. 4. Activate the Visible checkbox so that the view appears in the view menu. 5. Deactivate the Default checkbox at first. 6. Add a header section with corresponding attributes to the view. Refer to Defining the Header Section (Solution Center: User Guide, chap , p. 67). 7. Add a body section with the corresponding data sections, list views and attributes to the view. You can sort the data section in the body section hierarchically. Refer to Defining the Body Section (Solution Center: User Guide, chap , p. 67). 8. Save the view. 9. Once you have completed the view, activate the Is Default checkbox in the domain library underneath the root instance of your business domain. To do so, open the context menu for the view and choose the menu item Open Element in New Window inubit 6.1: Solution Center: User Guide

67 Using Views Defining Views in View Designer Defining the Header Section Prerequisites You have created a new view for the business solution. You have opened the view for editing. 1. Drag a header section from the Predefined Styles area to the work area. Refer to Predefined styles (Solution Center: User Guide, chap. 4, p. 71). 2. Drag the Title attribute from the Properties tab in the Properties and Associations area into the header section in the work area or the header element in the tree structure. Refer to Properties and associations (Solution Center: User Guide, chap. 2., p. 71). 3. If appropriate, adjust the properties in the Details of Title area. To do so, select the element in the tree structure. Refer to Element details (Solution Center: User Guide, chap. 5., p. 72). 4. Save the changes. Next, add one or more data sections to the body section. Refer to Defining the Body Section (Solution Center: User Guide, chap , p. 67) Defining the Body Section Prerequisites You have created a new view for the business solution. You have added a header section to the view. You have opened the view for editing. 1. Drag a style element, e.g. tab from the Predefined Styles area to the work area or the root element (view) in the tree structure. A new data section ( Section element) is inserted underneath the header section. Refer to Predefined styles (Solution Center: User Guide, chap. 1., p. 71). inubit 6.1: Solution Center: User Guide

68 68 Using Views Defining Views in View Designer 2. Drag an object class (the aggregation of the class with the root instance) from the Associations tab in the Properties and Associations area to the new data section in the tree structure. Refer to Properties and associations (Solution Center: User Guide, chap. 2., p. 71). 3. Choose the previously created list view or choose Add New to create a new list view. The association appears, for example, as a new tab (in case of style element Tab ) in the work area and is added to the data section in the tree view as an Object Set. A new List View element is added underneath. Refer to - Adding Attributes to an Association (Solution Center: User Guide, chap. 4, p. 76) - Defining List Views (Solution Center: User Guide, chap. 4, p. 76) 4. Select the new List View element in the tree view. 5. In the Details of (list view) for the Type field, choose the Grid entry to display the data as a table, if appropriate. 6. Drag one or more attributes from Properties tab to the List View element in the tree view. By holding down the CTRL button, you can select several attributes. 7. To add the associations of two classes, drag them onto the list view. Underneath the list view, a new Objectset element is inserted with a Listview element and a Title element. 8. Drag one or more attributes from Properties tab to the List View element in the tree view. 9. Save your entries. The view is now available to the business solution. You can now test the view and set it as the standard view for the business solution in the domain library. Following that, your business solution is automatically opened with this view. Next, you can define the actions, filter and sorting of the view. Defining a view as the default view When opened, an object is displayed with the default view. If there is no default view for the class of the object, the default view of the parent class is used. If there is no default view for the parent class either, the generic view is used for the class of the object. 1. In the View Designer, open the context menu of the root element of the view (view). 2. Choose the context menu entry Open in new window inubit 6.1: Solution Center: User Guide

69 Using Views Defining Views in View Designer 69 Depending on your browser settings, the object is opened in a new browser window or a new tab page. 3. Switch to Edit mode. 4. Activate the Is Default checkbox. 5. Save the changes Links to Actions, Filters and Sorting You can use the links in the object properties to open an action, filter or sorting for editing or create a new one directly from View Designer. Prerequisites You have created a view for your business solution. You have opened the view for editing in View Designer. Actions 1. Navigate to the list view for which you want to define an action. 2. Click the link in one of the lines aggregated actions or element actions. 3. Create the action. Refer to - Defining Actions on Views (Solution Center: User Guide, chap. 5, p. 79) - Defining Actions on List Views (Solution Center: User Guide, chap. 5, p. 81) Filtering 1. Switch to the object set of the association for which you want to define a filter. 2. Click the link in the Filter row. 3. Create the filter. Refer to Filtering and Sorting (Solution Center: User Guide, chap , p. 40). Sorting 1. Switch to the object set of the association for which you want to define a sorting. 2. Click the link in the Order row. inubit 6.1: Solution Center: User Guide

70 70 Using Views Defining Views in View Designer 3. Create the sorting. Refer to Defining a Sort Criterion (Solution Center: User Guide, chap , p. 77) Structure of View Designer Usage In View Designer you create and edit complete form pages for a business solution. The business solution is displayed with the view that you have defined as the default view in the Is Default field when you created the view. Call You open View Designer via the view menu. Edit current view Opens the currently active view in View Designer for editing. You cannot edit the Generic View. Create new view Opens View Designer for creating a new view inubit 6.1: Solution Center: User Guide

71 Using Views Defining Views in View Designer 71 The View Designer consists of the following areas: 1. Predefined styles Predefined styles that you can use for the individual sections in your view. The icons next to the description show what they look like. 2. Properties and associations The Properties tab contains a table with the titles and types of all attributes available for the selected class. You can choose the attributes that you have defined for the respective class as well as the inubit Solution Center 3.0 automatically set attributes, such as Creator, Modifier, Created Date and Modified Date. The Associations tab contains a table with the titles and types of all associations available for the selected class. 3. Work area Preview of the sections, fields and data of your view as well as of the subsequently displayed website. 4. Tree structure of the view inubit 6.1: Solution Center: User Guide

72 72 Using Views Defining Views in the Solution Center Tree structure of the elements of the view (View Structure) 5. Element details Properties of the respective selected element To create the individual sections and to assign the page elements to be displayed therein (tables, lists, tabs) and attributes, drag the respective element and drop it at the desired position in the work area or in the tree structure. The latter allows for more precise placing of the new element. Change mode to switch to full-screen mode to exit full-screen mode. When you click the icon View Designer restores the last saved processing status. Changes that have not been saved are lost. Context menu for the elements in the view In the tree structure of the view and in the work area, a context menu is available with the following functions: Delete element The element and all lower-level elements assigned to it are deleted from the view (structure and work area). Duplicate element The duplicated element is inserted underneath the position of the element to be duplicated. The element can be moved to another valid position. Open element in new window Opens the selected element in the domain library of the Solution Center. Use this function for changing attributes that cannot be edited in View Designer yet, e.g. to activate the Is Default checkbox for defining the view as the default view. 4.3 Defining Views in the Solution Center This section details the following topics: Adding a Header Section, p. 74 Adding a Data Section to the Body Section, p. 74 Adding Attributes of the User-Defined Class, p. 75 Adding Attributes to an Association, p inubit 6.1: Solution Center: User Guide

73 Using Views Defining Views in the Solution Center 73 Defining List Views, p. 76 Defining a Sort Criterion, p. 77 View Designer offers a more convenient way of creating views. Refer to Defining Views in View Designer (Solution Center: User Guide, chap. 4.2, p. 65). 1. In the object browser, navigate to the Domain Library and choose the class of your domain model for which you want to create a view. To define a view for the business solution, create the view underneath the root instance. 2. Open the Views tab in edit mode. 3. In the table title, click the plus icon or the triangle next to it and then choose the menu entry scc:view. 4. Give the new view a name and open it for editing. 5. Activate the Is Default checkbox if you want to use this view as the default view for the objects of this class in the business solution. However, you should only activate this checkbox if you have defined the header section and body section with at least one data section because otherwise the view is blank and not very meaningful. 6. Activate the Is Visible checkbox if this view is supposed to appear in the view menu for the class in the business solution. 7. In the Page Style field, choose one of the three predefined page styles. 8. Save your entries. Next, add a header and one or more body sections to your view. Refer to - Adding a Header Section (Solution Center: User Guide, chap. 4, p. 74) - Adding a Data Section to the Body Section (Solution Center: User Guide, chap. 4, p. 74) inubit 6.1: Solution Center: User Guide

74 74 Using Views Defining Views in the Solution Center Adding a Header Section There must be exactly one header section in each view. 1. Choose the view to which you want to add a header section. 2. In the Header section, click the plus icon or the triangle next to it and then choose the menu entry scc:view. 3. Give the new section a name and open it for editing. 4. In the Atomic Values section, click the plus icon or the triangle next to it. 5. If appropriate, choose the menu entry scc:atomic_value. 6. Give the new value a name and open it for editing. 7. Define the following attributes: - Title: Title of the view - Position of the section - Hide Title: Activate this checkbox to hide the title - View Style: Choose a style from the selection list to display this section. - Edit Style: Choose a style from the selection list to edit this section. - Tooltip: The text entered here appears as a tooltip when you move the mouse over the section. 8. Save your entries. Next, add a header and one or more data sections in the body section to your view. Refer to Adding a Data Section to the Body Section (Solution Center: User Guide, chap , p. 74) Adding a Data Section to the Body Section 1. Choose the view to which you want to add a data section. 2. In the Body section, click the plus icon or the triangle next to it. 3. If appropriate, choose the menu entry scc:section. 4. Give the new data section a name and open it for editing. 5. In the Basics section, enter the value for the following attributes. - Title: Title of the data section inubit 6.1: Solution Center: User Guide

75 Using Views Defining Views in the Solution Center 75 - Position: Position of this data section in the body section - Hide Title: Activate this checkbox to hide the title. - View Style: Choose a style from the selection list to display this data section. - Edit Style: Choose a style from the selection list to edit this data section. 6. Save your entries. In the next step you add the values and associations of the view. Refer to - Adding Attributes of the User-Defined Class (Solution Center: User Guide, chap. 4, p. 75) - Adding Attributes to an Association (Solution Center: User Guide, chap. 4, p. 76) Adding Attributes of the User-Defined Class 1. Display the data section of the view to which you want to add attributes. 2. In the Atomic Values section, click the plus icon or the triangle next to it and then choose the menu entry scc:atomic_value. 3. Give the new value a name and open it for editing. 4. In the Basics section, define the following attributes: - Title: Title of the view - Position of the value in the view - Hide Title: Activate this checkbox to hide the title - View Style: Choose a style from the selection list to display this value. - Edit Style: Choose a style from the selection list to edit this value. 5. In the Visualized Attributes section, click the plus icon. 6. Choose the desired attribute from the list of attributes. You may only select one attribute. 7. Save your entries. inubit 6.1: Solution Center: User Guide

76 76 Using Views Defining Views in the Solution Center Adding Attributes to an Association 1. Display the data section of the view to which you want to add attributes. 2. In the Object Sets section, click the plus icon or the triangle next to it and then choose the menu entry scc:object_set. 3. Give the new value a name and open it for editing. 4. Define the following attributes: - title: Title of the association - position: Position in the view - hide Title: Activate this checkbox to hide the title - height: Height of data section in pixels - readonly: - true: Relationships cannot be edited in this view. - disablecreate: - true: Relationships cannot be created in this view. - disabledelete: - true: Relationships cannot be deleted in this view. 5. In the Visualized Relationship section, click the plus icon and choose the desired association. 6. In the Visualized (List) View section, click the plus icon and choose the desired (list) view. 7. Save your entries Defining List Views Usage You need list views to be able to reference an object set (attributes of another class) in a view, e.g. if you want to display and edit attributes of the Contract class in the Vehicle class as well. Execute the following steps for all classes for which you want to create list views and/or that you want to reference in views. You can create several differently configured list views for each class. 1. Navigate to the class for which you want to define a list view. 2. Open the List Views tab. 3. In the table title, click the plus icon or the triangle next to it and then choose the menu entry scc:listview inubit 6.1: Solution Center: User Guide

77 Using Views Defining Views in the Solution Center Give the new list view a name. 5. In the Type column, choose the entry CSV. 6. Open the list view for editing. 7. Add the desired list view elements. In the table title, click the plus icon or the triangle next to it. a. Choose the menu entry scc:atomic_value to add a single attribute value. b. Choose the menu entry scc:object_set to add an object set. 8. Define values as described above. Refer to - Adding Attributes of the User-Defined Class (Solution Center: User Guide, chap. 4, p. 75) - Adding Attributes to an Association (Solution Center: User Guide, chap. 4, p. 76) Defining a Sort Criterion 1. Navigate to the object set of the association for which you want to define a sort criterion. 2. Open the Order Criteria tab. 3. In the table title, click the plus icon or the triangle next to it and then choose the menu entry scc:order_criteria. 4. Give the new sort criterion a name. 5. Open the sort criterion for editing. 6. Set the sort order - Sort Ascending=Yes: sort in ascending order - Sort Ascending=No: sort in descending order 7. Set the priority. 8. Chose the attribute(s) according to which you want to sort. 9. Save your entries. If you have defined a sorting criterion, you cannot sort the used columns in the columns. inubit 6.1: Solution Center: User Guide

78 78 Using Views Defining Views in the Solution Center inubit 6.1: Solution Center: User Guide

79 5 Integrating Processes 79 This section details the following topics: Defining Actions on Views, p. 79 Defining Actions on List Views, p. 81 Usage You define actions in lists or list views in order to start user-defined workflows in the inubit Workbench from the inubit Solution Center 3.0 workflows. Prerequisites For each action, there is a suitable workflow in the inubit Workbench. For each action, there is a button with which the respective action can be started. For each action, the workflow generated for it is configured. How it works Once the action has been triggered in the inubit Solution Center 3.0, the configured workflow starts in the inubit Process Engine. After executing the workflow, the inubit Process Engine returns the results to the inubit Solution Center 3.0. Prerequisites You have imported the file SolutionCenter.diagrams.zip in directory <is/sc-installdir>/sc_root/workflows and activated the workflows. You have configured the connection to the inubit Process Engine in the solutioncenter.properties file Refer to Configuration File solutioncenter.properties (Solution Center: Administrator Guide, chap. 1.4, p. 12). You have already created views and list views. Refer to Using Views (Solution Center: User Guide, chap. 4, p. 63). 5.1 Defining Actions on Views Use Add actions to a view to start a technical workflow in inubit Process Engine, e.g. a workflow that processes data and creates a task for an employee or a role. inubit 6.1: Solution Center: User Guide

80 80 Integrating Processes Defining Actions on Views This way you can, for example, start a workflow that starts a workflow after a new vehicle has been created. This workflow generates a task for another employee for entering the contract details for the new vehicle and assigning them to the vehicle. The following step describes which steps are required in the inubit Solution Center 3.0 for linking a workflow to a view and starting it from the view. Prerequisites In the inubit Workbench, you have created or imported one or more workflows. You have created views for the respective classes. Refer to Using Views (Solution Center: User Guide, chap. 4, p. 63). 1. Navigate to the class for which you want to define an action. 2. Open a view for a class. 3. Go to the Actions tab. 4. Click the plus icon in the table header, choose the context menu entry scc:workflow_action and name the new action, e.g. Assign Contract. 5. Open the new action to configure the properties. a. Activate the Confirm checkbox if you want to display a prompt. Following that, enter the corresponding message text in the Confirm Msg field. b. Activate the Acknowledge checkbox if you want to display a confirmation window and then enter the corresponding message text in the Acknowledge Msg field. c. In the Workflow field, enter the name of the technical workflow to be started, e.g. Assign_SC_ContractDetails. d. In the User Group field, enter the name of the group of the workflow. The workflow name and the group are required attributes; all other attributes are optional. e. Choose the type of the workflow, e.g. Start Process inubit 6.1: Solution Center: User Guide

81 Integrating Processes Defining Actions on List Views 81 f. In the Redirect Type field, choose the object that is supposed to be displayed at the end of the workflow, e.g. Object. 6. Save the changes: Now open, for example, the Vehicle Details view for the Vehicle class. At the bottom right, the following button appears with which you start the specified workflow: 5.2 Defining Actions on List Views Usage Actions on list views are designed for executing an action for an individual element or a selected set of elements. Prerequisites In the inubit Workbench, you have created or imported one or more workflows. inubit 6.1: Solution Center: User Guide

82 82 Integrating Processes Defining Actions on List Views You have created list views for the respective classes. Refer to Using Views (Solution Center: User Guide, chap. 4, p. 63). 1. Navigate to the class for which you want to define an action. 2. Open a list view for a class. 3. Choose the Generic view. 4. Create a new action. a. In the Outgoing Associations area, click the plus icon next to the Action(s) entry with the List View Element Action tooltip to create a new action for an individual element. b. In the Outgoing Associations area, click the plus icon next to the Action(s) entry with the List View Element Action tooltip to create a new action for an individual element. 5. Choose the context menu entry scc:workflow_action. 6. Open the new action for editing and configure it. Refer to Defining Actions on Views (Solution Center: User Guide, chap. 5.1, p. 79). 7. Save the changes. The buttons for the actions appear in the view in which you are using the respective list view. Actions for individual elements appear in the respective row of the element. The triggering of this action applies only to the element in whose row you click the button. Actions for a group of elements appear in the header of the table with the elements for which they can be used. Triggering this action applies to all elements that you previously selected in the table. To select, click into the rows you want to select while holding down the CTRL key. By holding down the Shift key you select all elements between two selected elements inubit 6.1: Solution Center: User Guide

83 6 Default Models and Interfaces 83 This section details the following topics: Technical Core Model, p. 83 Business Foundation Model, p. 84 REST Interface, p Technical Core Model This section details the following topics: Object Types, p. 83 Views, p. 84 Usage The Technical Core Model (TCM) contains a model of the technical classes supplied by the Solution Center, which you can use for modeling your solution. This Technical Core Model is the basis of the Business Foundation Model, which is already a basic solution whose classes you can use for business process modeling. Refer to Business Foundation Model (Solution Center: User Guide, chap. 6.2, p. 84). The Technical Core Model is divided into two large groups: object types and views. There are simple and complex object types as well as various predefined views Object Types You can use many predefined object types to develop your solution and create complex links and nesting in almost unlimited ways. The simple object types form the basis for complex object types. Complex object types can contain simple and complex object types in almost unlimited levels of nesting. inubit 6.1: Solution Center: User Guide

84 84 Default Models and Interfaces Business Foundation Model Views For all classes, there is default view with the most important objects and attributes as well as a generic view that shows all objects and attributes of this class. You can structure views as tables, journals, fact sheets or forms and either release them for editing or use them only for viewing data. The elements of a view can then be nested in an almost unlimited number of levels. The nesting levels are limited only by what can be displayed on the monitor or printout. 6.2 Business Foundation Model This section details the following topics: Application Class, p. 84 Process Class, p. 85 Partner Class, p. 85 Usage The Business Foundation Model (BFM) provides three important business domains, their classes and links as the basis for modeling your solutions: Application, Process, Partner. The Business Foundation Model is based on the Technical Core Model and uses the basic classes provided therein for simple and complex object types. Refer to Technical Core Model (Solution Center: User Guide, chap. 6.1, p. 83) Application Class The Application class provides subclasses that allow you to display your solution as a new menu with its own menu entries, and link it to certain user accounts and roles inubit 6.1: Solution Center: User Guide

85 Default Models and Interfaces REST Interface Process Class The Process class makes available subclasses that enable you to add tasks and events to your solution. You can link the tasks and events to user accounts, while the tasks can also be linked to roles Partner Class The Partner class provides subclasses that allow you to add persons and organizational units as well as links to user accounts and business functions to your solution. 6.3 REST Interface This section details the following topics: General Information, p. 86 Reading Nodes, p. 88 Determining the Menus of the Current User, p. 89 Querying Type Information, p. 90 Querying Views for a Type, p. 91 Exporting a Node Structure, p. 91 Importing a Node Structure, p. 92 Writing Nodes, p. 93 Reading Associations Page-by-Page, p. 104 Activating, Deactivating and Querying Models, p. 107 Querying, Setting and Removing Node Locks, p. 111 Administration Interface, p. 113 Usage The REST interface (REST = Representational State Transfer) is designed for accessing the repository of the Solution Center to add, edit, delete or read data. inubit 6.1: Solution Center: User Guide

86 86 Default Models and Interfaces REST Interface Functional principle You use an XML or JSON structure to transfer the objects to be read, created or edited. You can thus execute numerous operations with a single call: Read several objects Create and link several objects Change several objects Delete several links and objects The href mechanism lets you edit any number of complex structures with one call. In the same call, you can also reference newly created nodes as parent nodes in order to create new objects underneath. The database is accessed using an HTTP message via a REST client. In the sent message, parameters are used to specify which actions are supposed to be executed. If you have configured your application server for HTTPS you can also use HTTPS to access the database. Refer to HTTPS Configuration (Solution Center: Administrator Guide, chap. 1.8, p. 15). Prerequisites You have programmed a solution that can generate an HTTP message with defined content and send it to a specified address. You have created a business solution that can be reached from your application. The Solution Center has been started. You have access to a REST client (e.g. the inubit REST Connector or the Firefox add-on) General Information This section details the following topics: Authentication, p. 87 Input and Output Formats, p. 87 UUID or Node Path, p. 87 You need the following general information in order to be able to use the REST interface correctly inubit 6.1: Solution Center: User Guide

87 Default Models and Interfaces REST Interface Authentication Authentication takes place using the HTTP Basic Authentication procedure, where an authorized user enters a user name and password Input and Output Formats The different functions of the REST interface expect certain input as POST parameters and/or return the output or results requested via the GET parameters. You use the following settings to control the input and output formats. Input format Evaluation using the Content Type header parameter Output format Evaluation using the accept header parameter If not specified explicitly, XML takes precedence over JSON (JavaScript Object Notation). If a header parameter includes XML and JSON as acceptable formats, XML is used. Since browsers often use their own settings, always specify the expected format explicitly. - XML: application/xml - JSON: application/json If XML output is expected, the optional Boolean parameter skipns is supported for some functions. If this parameter is set, namespaces and prefixes are not written into the XML output. By default, this parameter is set to false. To see whether a function evaluates this parameter, refer to the individual function descriptions UUID or Node Path REST functions often require an output node to which an operation is to be applied. As an alternative to the UUID (Universally Unique Identifier), which can change when the Solution Center or the created business objects are ported, the REST interface also supports the specification of a node path. The UUID is then internally determined from this path. The starting point for a node path is the Solution Center root node, which appear as the root node in the object browser (house icon and name Solution Center Home ). A node path resembles an XPath, for example: inubit 6.1: Solution Center: User Guide

88 88 Default Models and Interfaces REST Interface /cm:content/cm:solutions/fpm:vehicle The individual localization steps (the character strings between the / ) consist of the prefix of the domain model, a colon and the respective technical node name: <domain prefix>:<technical name of the object> This is case sensitive. Do not confuse the node name with the title that you can see in the inubit Solution Cockpit. You'll find the prefix of the domain model on the Technical Perspective tab of the Generic view in the Name field. For the Solutions node under the Solution Center Home node, the node name is composed as follows: Name of the node: solutions Prefix (derived from scc:solutions type): scc Localization step: scc:solutions If there are several nodes with the same name, you must use the familiar XPath notation, for example: /scc:solutions[2] This selects the second node with the name solutions Reading Nodes Usage The selected node element and optionally the view used are read and returned inubit 6.1: Solution Center: User Guide