Using INUBIT Enterprise Portal

Unless otherwise indicated, all information in this section is valid for the INUBIT Enterprise Portal based on Liferay 7/DXP.

Usage

With the INUBIT Enterprise Portal, you can create a process-oriented portal that integrates internal and cross-company business processes. This process-oriented portal can serve as a corporate operating system and central user interface.

Portal users are not only restricted to your employees, but can also include customers, suppliers, and other business partners carrying out their tasks in a transaction-oriented way by means of a uniform interface. User interaction easily takes place via a Web browser with no software rollout necessary when processes are added or changed.

Business processes are implemented as Web applications on the basis of the workflow component and, at the push of a button, are straightly deployed to the portal server.

Refer to Developing a Web Application in INUBIT Workbench

The main component of the INUBIT Enterprise Portal is the INUBIT Process Cockpit that offers the most relevant functions as pre-configured BPM portlets.

Portal server versions

By default, the INUBIT software supports the following portal servers

Refer to Software Requirements

Refer to Administering Liferay Version 7/DXP

Calculation of Concurrent Users

The number of users, who may use the INUBIT Enterprise Portal at the same time depends on the number of portal users for whom you have acquired a license.

Display max. number of portal users

The maximum number of users that are permitted to use the portal at the same time can be found in the license file stored at <inubit-installdir>/inubit/server/ibis_root/conf/license.xml.

Calculation base

For each user a license is administered in a license pool. For each active user a license is removed from the pool. When the maximum number of licensed users is reached, the pool is empty and no more users can log in to the portal. As soon as a user is not actively working with the INUBIT Enterprise Portal, her license is put back into the pool and available again for other users.

Users are considered as active, if they perform the following actions:

  • Open a portal page with one or more Web Application portlets. This action finishes, if

    • the portlet’s session expires or

    • the portal’s session expires or

    • the users signed out.

  • Display or take on a task in a task list and thus lock the task for other users. This action is finished, if

    • no tasks are displayed anymore,

    • no tasks are locked,

    • the session of the form or the task expires (depending on what expires later).

If one user performs several actions at the same time, only one license is calculated.

Displaying Number of Active Portal Users

At any time, you can check the number of active portal users using a Web Application Connector by either having them displayed in the INUBIT Workbench monitoring or as report in the portal.

In Connection Manager

In the Connection Manager, you can have all active portal users displayed in real time using a Web Application Connector.

Proceed as follows

In the INUBIT Workbench, select the Monitoring > Connection Manager tab.

For every active portal user an entry with the system type Portal is displayed.

As report in portal

A report indicates the number of active portal users, e.g. during a specific time period.

Proceed as follows

  1. Create a report and use INUBIT Log Database as data source.

  2. In order to include the concurrent portal users, use the column Concurrent user from the System statistic log table.

Refer to Creating Reports with Data from IS Log Database

Opening the INUBIT Enterprise Portal

Prerequisites

  • The Portal Server is installed, configured, and started.

  • The INUBIT Process Engine is started.

  • Liferay is configured for INUBIT.

  • The INUBIT sites and pages are created and the portlets are deployed to the Liferay portal.

Refer to

Proceed as follows

  1. In the INUBIT Workbench, display the Administration > General Settings tab.

  2. Display the configuration category Portal > Portal Server.

  3. Activate your portal by selecting the respective value from the Portal Server option, for example, Liferay.

    In case your portal server is not installed on the same computer as the Process Engine, go to the option Portal Server URL and replace localhost:8080 by the name and the port of the computer on which the portal server is installed.

    Enter the URL of the Process Engine.

  4. Display the configuration category Process User > Server.

  5. Activate your process user server by selecting the respective value from the Process user server option, for example, Liferay.

  6. To save your changes, click workbench user guide 742 0 in the toolbar.

    → The INUBIT Enterprise Portal is now active.

    Activate the INUBIT Process Cockpit

  7. Display the configuration category Portal > Portal Deployment and click workbench user guide 743 1 next to the Portlet archives (Administration/Deployment) option. A dialog opens.

  8. Click Deploy archive and confirm the next dialog. The portlets are being deployed to the INUBIT Enterprise Portal. After successful deployment, a message is displayed. Close the dialog.

  9. To display the INUBIT Enterprise Portal, open a browser and enter the following URL:

    https://<server>:<port>

    → The INUBIT Enterprise Portal is opened.

    workbench user guide 743 2

    By default, minimizing JavaScript files is enabled for faster loading of portlets.

    For debugging purposes though, this can be deactivated by the following options:

    • Setting the parameter javascript.fast.load = false in the portal-ext.properties file.

    • Adding the parameter ?js_fast_load=0&css_fast_load=0&strip=0 at the end of the URL.

    If there is another parameter already added after the URL, the parameter must be appended using &: &js_fast_load=0&css_fast_load=0&strip=0 at the end of the other parameter.

    This applies when debugging JavaScript in a Liferay 7/DXP portal using Web Developer tools.

  10. Log in to the portal.

    The INUBIT Cockpit consists of the following pages:

    • Process Viewer: For displaying the process model (Business Process Diagrams, Organization Diagrams, Business Object Diagrams, and System Diagrams).

    • Task List: Contains personal and role-based tasks that can be used for integrating employees in automated business processes.

    • Report Viewer: For quickly accessing technical and business-related data. By default, the load of your INUBIT installation is displayed.

User Interface of the INUBIT Enterprise Portal

workbench user guide 744 1

Overview

  1. Control Panel

    Provide access to the following functions and areas, for example:

    Adding, configuring, deleting users, sites, apps, and changing the portal configuration

    Only the administrator can see the Control Panel.

    Refer to Managing Portlets in Liferay

  2. User Account menu

    To configure account setting and to display, for example, workflow tasks, notifications, and organizations assigned to the current user.

  3. Site management menu

    To configure the current site, for example, adding, configuring, or deleting subordinated pages.

    Only the administrator can configure sites.

  4. Company logo

    The logo is linked to the portal’s home page.

    Refer to Replacing Portal Logo in Liferay

  5. Navigation menu: Top-level pages of the website All top-level portal pages of a site are displayed as links in the Navigation menu.

Providing and Displaying the INUBIT Cockpit

To make the delivered default portlets of the INUBIT Cockpit visible in the INUBIT Enterprise Portal you have to make them available initially in the INUBIT Enterprise Portal.

Prerequisites

Proceed as follows

  1. Deploy all provided BPM portlets

    Refer to Deploying Web Applications as Portlet Archive

    After deployment, the portlets of the INUBIT Cockpit are visible for al portal users that belong to the INUBIT Cockpit website.

    If you create further users for the INUBIT Cockpit, you must also assign them to the INUBIT Cockpit website. Otherwise, the INUBIT Cockpit is not visible for these users.

  2. Display the INUBIT Enterprise Portal.

  3. Log in as a user having the portal role User.

→ After successful login, the INUBIT Cockpit is displayed.

User Interface of the INUBIT Process Cockpit

The INUBIT Process Cockpit is automatically visible to users with the User portal role.

workbench user guide 745 1

The INUBIT Process Cockpit provides the following default portlets:

Monitoring Portlets in the INUBIT Process Cockpit

Overview

The monitoring portlets can display all information visible in the INUBIT Workbench in the following sub-folders of the Monitoring tab:

  • Queue Manager

  • Scheduler Manager

  • Connection Manager

  • Key Manager

  • System Log

  • Audit Log

  • Process Log

The only exceptions to this are the Server Trace Log and the Workbench Trace Log. These data are exclusively displayed in the INUBIT Workbench.

The System Log monitoring portlet is delivered with the INUBIT software. All other monitoring portlets can very easily be configured on an individual basis.

All monitoring portlets provide multi-client capability: you can use for each portlet the login data of an individual Process Engine user.

Creating Monitoring Portlets

Proceed as follows

  1. In the INUBIT Workbench, display the Administration > General Settings tab.

  2. Display the Portal > Portal Deployment area.

  3. Click the button next to the Monitoring portlets on the portal option. The following dialog opens:

    workbench user guide 747 0

    The displayed XML structure generates a monitoring portlet displaying all data resulting from the System Log.

  4. In order to generate a further monitoring portlet copy the Portlet Element and paste it below the MonitorPortlets element. The resulting structure should look like this:

    workbench user guide 747 1

  5. Change the attributes type, name and id accordingly for the new portlet.

    • Type defines the kind of data displayed in the portlet. The following table lists the type values for the different logs:

      Tab name in the Monitoring tab Value of attribute type

      Queue Manager

      queueLog

      Scheduler Manager

      schedulerLog

      Connection Manager

      connectionLog

      Key Manager

      keyManagerLog

      System Log

      systemLog

      Audit Log

      auditLog

      Process Log

      alltables<Name_of_DatabaseTable>

      e.g.: alltablesORDER

    • Name defines the portlet title.

    • As id you can use a numeric value or a character string. Within the XSLT style sheet you must use a unique value in order, e.g., to distinguish several portlets of the same type.

  6. Use the attributes login and password to add login data of a Process Engine user to each portlet and thus make the portlet multi-client capable.

  7. You can change the portlet layout by using the CSS style sheet elements.

  8. Click OK to close the dialog.

  9. Save your changes and deploy all portlets again.

    Refer to Deploying Web Applications as Portlet Archive

→ The new portlet is provided in the INUBIT Enterprise Portal in the INUBIT category.

Functions Offered by Monitoring Portlet

Paging

All Monitoring Portlets support Paging. Paging means that data is spread over multiple pages.

Use the arrow buttons for navigating through the pages. The number of data sets per page is defined in the first field to the right of the arrow buttons:

workbench user guide 748 0

Filtering

You can filter the tables’ contents by one or more criteria. Enter the filter criterion in the text input field above the respective table column and press the return key.

The filter criteria depend on the data type of the respective column:

  • Text columns

    Upper and lower case are distinguished! Parts of strings are found without wildcard character.

    Example: With the filter criterion ORD for the column Workflow-Name records with workflows titled ORDER are retrieved.

  • Numeric columns

    You can search for ranges, e.g. the filter criterion 0-100 for the column Size input message matches to all records with input messages ranging between 0 and 100 kB.

  • Date columns

    You can also search for ranges here.

    Example:

    16.04.2011 09:19:52.057 - 17.04.2011 09:55:31.069

    Only the rows that match the specified filter criteria are displayed. All other rows are hidden.

To display the full contents of the table again delete the filter criterion and push the return key.

Sorting

  • Sorting

    Click the header of the column by which you want to sort the table.

    An up arrow in the column header indicates that the table was sorted in ascending order by the selected column.

  • Reversing the sort

    Click again on the column header.

    The down arrow in the table header indicates that the sort has been reversed.

  • Cancelling the sort

    Click once again to cancel the sort.

    No arrow is now displayed in the table header.

  • Multiple sorting

    Within a sort you can also sort the rows further by clicking in the headers of additional columns. Numbers are displayed in front of the column headings showing the sort sequence of the columns.

Using INUBIT Monitoring in Business Process Center (BPC)

Usage

The INUBIT Monitoring modules for BPC display all information visible in the INUBIT Workbench in the following sub-folders of the Monitoring tab:

  • Queue Manager

  • Scheduler Manager

  • Connection Manager

  • Key Manager

  • System Log

  • Audit Log

  • Process Log

The Server Trace Log, Workbench Trace Log, Webservice Manager, and Webservice Log are exclusively displayed in the INUBIT Workbench.

Monitoring modules for System Log, Queue Log, Audit Log, and Process Log are delivered with the INUBIT software. All other monitoring modules can be very easily configured on an individual basis.

Prerequisites

  • The BPC Server is installed, configured, and started.

  • The INUBIT Process Engine is started.

  • The Business Process Center is configured as Portal server

  • The Business Process Center is configured as Process Users Server

  • Process Users and Roles from BPC are assigned to the INUBIT administrator.

Proceed as follows

  1. Create, configure, and deploy INUBIT Monitoring module portlets, refer to Configuring Monitor Modules for BPC.

    For the Process Log monitoring module type, the additional tablename attribute has to be configured specifying the database table name.

  2. Open the INUBIT Monitoring Module(s) in the Business Process Center, refer to Opening INUBIT Monitoring Module in BPC.

  3. View the Workbench logs in the BPC portal, refer to Viewing Workbench Logs.

Opening INUBIT Monitoring Module in BPC

Proceed as follows

  1. In the web browser login to the BPC using the following URL:

    https://<server>:<port>

  2. In the BPC Global menu, choose the Settings item.

    → The BPC Administration page is displayed.

  3. Open the Components section in the INUBIT Monitoring tab.

    → The INUBIT Monitoring module(s) deployed to the BPC are displayed in the Components section.

    workbench user guide 750 1

  4. Click the workbench user guide 750 2 icon to open the desired monitoring component.

    → The log tabs configured for the opened monitoring module are displayed.

    workbench user guide 751 0

  5. To open one of the logs, click the corresponding tab.

Viewing Workbench Logs

When having opened a log tab, you can configure the tab as follows:

Sorting

To sort the log entries by up to three columns, click the table heading(s) of the desired column(s) to switch between Sort Ascending, Sort Descending, and no sorting.

Alternatively, you can click the triangle that appears when hovering a table heading of a column and choose the desired sorting. An up arrow or a down arrow in the table heading indicates how the column is currently sorted. If no arrow is displayed, the column is not sorted.

Filtering

When clicking the triangle that appears when hovering a table heading of a column, a menu is displayed. With this menu, you can—besides sorting—hide and display columns as well as filtering the entries by entering a case-sensitive filter text, a value, or by choosing a date.

In numeric columns, you can filter for ranges, for example: Using the filter criterion 0-100 for the Process ID column matches to all records with Process ID ranging between 0 and 100.

In date columns, you can choose a date for one of three criteria: Before, After, and On.

The header of a filtered column is underlined, and it is displayed in bold italic.

To remove a filter condition, deactivate the Filter checkbox.

Paging

To change the number of entries displayed in the table, enter the new value in the With 10 Items field in the navigation bar and click the Refresh icon workbench user guide 751 1.

Displaying the Audit Log, Queue log, System Log etc.

Proceed as follows

Open the desired log tab on the monitoring module containing it.

→ The corresponding log entries are displayed.

workbench user guide 752 0

Configuring and Displaying the Process Log

Prerequisites

  • You have created a custom table in the Database Manager in the INUBIT Workbench.

  • You have configured the custom table column in the monitoring module configuration file.

Proceed as follows

Open the Process Log tab on the monitoring module containing it.

→ The Process Log entries are displayed.

workbench user guide 752 1

Portlet Process Viewer in the INUBIT Process Cockpit

Specifying Visibility of Diagrams in the Process Viewer

By default, all diagrams of the process viewer are visible only for the pre-configured tutorial users.

To make the diagrams visible for other process users, you must assign the diagrams to process user roles in the INUBIT Workbench. You can specify the visibility for a group of diagrams or for individual diagrams.

Prerequisites

Technical workflows cannot be displayed.

Proceed as follows

  1. In the INUBIT Workbench, display the Designer tab.

  2. In the Server tab, select the diagram group or diagram to which you want to assign process user roles.

  3. Open the context menu, then select Assign process user roles. A dialog is displayed listing all available process user roles.

  4. Select the checkbox for the roles that are to have access to the diagram or diagram group.

    For diagram groups, your process user role assignments apply to all diagrams of the group (inheritance relation). You can remove process user roles assigned to a diagram group only from the diagram group and not from the individual diagram. Apart from that, you can however assign and remove process user roles from individual diagrams.

  5. Click OK to save.

    → Once the page is refreshed, the diagram becomes visible and is displayed in the INUBIT Cockpit process viewer.

Using Functions of the Process Viewer

workbench user guide 753 1

  1. Toolbar

    The following functions are available via the process viewer toolbar:

    • Back and Forward button

      By using the Back and Forward button, you can move backwards and forwards to diagrams within the portlet.

    • Zoom functions

      By using the zoom functions Fit page, Fit width, Zoom out, Zoom reset and Zoom in, you can change the size of the displayed diagram.

    • PDF export

      • Print: Generates a process model report for the currently displayed diagram

      • Print all: Generates a report based on all diagrams of the process model.

        The generated PDF document is opened and displayed in a new and separate browser window.

    • Display/hide columns

      By clicking the button Hide columns, you can simultaneously hide and display again the right column (description, legend) and the left column (diagram tree).

    • Search

      The search function searches all names and descriptions for the entered character string.

      • Search results: The results page lists the corresponding diagrams sorted and by way of links. The results are grouped and displayed by the different diagram types (e.g. BPD, BOD, etc.) on individual tabs. On each tab, the search results are sorted alphabetically by their diagram name and within the diagram name they are sorted and displayed by the element name:

        workbench user guide 754 0

        In the desired tab (diagram type), click one of the links to display the respective diagram.

  2. Tree view

    The Tree view button is used to display or hide the tree structure of the diagram directory. If the tree view is not visible, only the diagram types are displayed. By default, the tree view is displayed. By using the configuration panel, you can specify that the tree view is initially not displayed:

    Refer to Display/hide columns

  3. Description In addition to the displayed diagram, a corresponding description is offered (if available). By default, the description is always displayed, but can also be hidden - together with the Tree view column - by clicking the Hide columns button. By using the configuration panel, you can specify that both description and legend are initially not displayed:

    Refer to Display/hide columns

  4. Legend

    The legend specifies all elements used in the diagram. The context-sensitive legend can either be collapsed individually by using the push-button or together with the description window by using the Hide columns button in the toolbar. By using the configuration panel, you can define that the legend - together with the description - is initially hidden.

    Refer to Display/hide columns

    By default, the legend texts cannot be edited. However, they can be customized by users with administrator rights:

    Refer to Customizing Legend Texts of the Process Viewer

  5. Diagram view Displays the diagram selected in the tree view to the left. Via the configuration panel, you can define that initially the diagram view displays a defined process model:

    Refer to

Customizing the Process Viewer Starting Page and Available Options

By default, when opening the process viewer starting page it is empty. You can customize this starting page by individually designing it with text or having displayed a specific process model as starting diagram. Furthermore, you can use the configuration page for defining the visibility and order of the toolbar buttons as well as the visibility of columns for different areas (e.g. tree view, legend).

Proceed as follows

  1. Display the process viewer.

  2. In the process viewer title bar, click workbench user guide 755 0. A menu opens.

  3. In the menu, select Preferences. The configuration editor for the starting page is displayed:

    workbench user guide 756 0

  4. Define the required configuration steps for the initial settings:

    • Defining the start page

      In the area Define the start page, select the required options. Depending on the selected option, the display changes.

      • Display empty page

        Defines an empty page in the diagram area as initial view in the Process Viewer.

      • Display process model

        Opens a diagram explorer in tree view for selecting the desired process model to be displayed on the start page.

      • Display text

        Opens a text editor for entering text to be displayed on the start page.

    • Display/Hide areas

      In the column display of the Process viewer, you can display or hide some certain areas. Select the desired option in the Display/hide areas option. For each option, a small preview is offered in the window to the right.

    • Hide the Description and the Legend areas

      Initially hides the right-hand column containing description and legend.

      • Hide the Tree View area

        Initially hides the left-hand column containing the tree view.

      • Display all areas

        Initially displays all three columns in the portlet.

      • Display the process model only

        Initially hides the right-hand and left-hand column and only displays the column in the middle.

    • Extras

      • Detailed Information

        Define of additional element information, e.g. element name, metadata (if available and either sorted alphabetically or as used in the metadata manager), comments, BPM rules or links, are to be displayed on click in the form of pop-up windows or in the Description area.

      • Links

        If you do not use the default process viewer in the INUBIT Process Cockpit, you must first create the link between the process viewer and the report viewer. You do this by entering the respective URL of your report viewer in the field Report Viewer URL. You retrieve the URL in the same as described in Creating a URL to Link Diagrams in the Process Viewer.

      • Graphical Settings

        Define if the graphics in the Process Viewer are to be displayed with drop shadows by checking an option.

    • Customize toolbar

      You can customize the visibility and order of toolbar buttons:

      1. Select the toolbar buttons to be displayed by checking an option.

      2. Modify the order of the displayed buttons as desired by using Drag’n’Drop to move the tool lines and thus rearranging them.

  5. Click OK to save your changes.

    → The editor closes. The modified starting page of the Process Viewers is displayed, when you reload the page or click the entry Diagrams in the tree view.

Customizing Legend Texts of the Process Viewer

By default, in every diagram, the corresponding legend texts are automatically displayed.

As a user with administrator rights, you can configure the legend texts to modify its textual content.

The modified text content only affects the Process Viewer, not the Workbench.

To do this, you use scripts that unpack the required translation file (extractProcessVieweri18n) and re-wrap it after modification (updateProcessVieweri18n).

You change the desired legend text in the IBISTextResource.properties file and restore it afterwards to the Process Viewer.

Prerequisites

You are a user with administrator right or can contact an administrator.

Proceed as follows

  1. In the directory <inubit-installdir>/inubit/server/ibis_root/conf/portal, execute the extractProcessVieweri18n.bat or the extractProcessVieweri18n.sh file.

  2. Edit the IBISTextResource.properties file by modifying legend texts for the desired diagram type and by saving them. You find the legend texts for the different diagram types labeled in different sections as follows:

    • Edit text for Business Process Diagrams in the section between Business Process Diagram Legend - begin and Business Process Diagram Legend - end.

    • Edit text for Organizational Diagrams in the section between Organigram Legend - begin and Organigram Legend - end.

    • Edit text for System diagrams in the section between System Diagramm Legend - begin and System Diagramm Legend - end.

    • Edit text for Process Maps in the section between Process Map: Legend - begin and Process Map: Legend - end.

    • Edit text for Business Object Diagrams in the section between Constraints Diagram Legend - begin and Constraints Diagram Legend - end.

      Multiline legend texts are wrapped automatically in given display area in the Process Viewer. Manual line breaks require the `<br/> XHTML tag.

  3. In the directory <inubit-installdir>/inubit/server/ibis_root/conf/portal, execute the updateProcessVieweri18n.bat or updateProcessVieweri18n.sh file.

  4. Deploy the portlets again.

Note that the procedure starting from step 3 is required after each new INUBIT patch. It is also recommended to keep a backup of the modified file available.

Creating a URL to Link Diagrams in the Process Viewer

You can create a URL that directly links to a diagram or to an element in a diagram, which is displayed in the Process Viewer.

You can send someone this URL for example by e-mail for directly displaying the diagram or an element in the Portal.

For calling diagrams and elements, the Process Viewer uses the GET parameter diagramName and moduleID, which have to be adjusted in the URL.

You use GET parameters to transmit parameter/value pairs that are to be processed by called applications while processing a search request.

Refer to Linking Reports to External Web Applications

Prerequisites

Proceed as follows

  1. Display the Process Viewer.

  2. Retrieve the URL to be adjusted

    1. In the diagram tree to the left, select any diagram and click it to be displayed.

    2. In the title bar of the portlet, click the Maximize button.

  3. Copy the URL, which is displayed in the browser’s address bar, into an external application in order to adjust it.

  4. Delete the &p_p_state=maximized parameter from the URL.

  5. In order to create a new URL to be used as diagram or element link, carry out one of the following actions:

    • Create URL to link a diagram

      • Attach to the end of the URL the diagramName= parameter with the name of the desired diagram as parameter value. The name must exactly the same as defined for the diagram in the INUBIT Workbench, e.g.: &diagramName=Assembler-AG-Organigramm.

        The diagram name must be URL-encoded, e.g.: %20 = space.

    • Create URL to link an element

      1. Attach to the end of the URL after the parameter value pair for the diagram the moduleID= parameter.

      2. Change to the INUBIT Workbench and retrieve the moduleID for the desired element, which is displayed as number via tooltip at the element.

      3. Insert this number as parameter value to the moduleID into the URL, e.g.: &moduleID=194.

        If you wish to send a URL linking to an element in a diagram, you must always attach the diagram name and the module ID.

    → You have now created a new URL that you can send in order to directly link to a diagram or module. If you enter the URL into the browser’s address bar, the referenced diagram is displayed in the Process Viewer of the portal. The referenced element is highlighted in red.

If you have not been logged in to the Portal beforehand, the login page opens first requesting you to enter your login data.

Portlet Task List in the INUBIT Process Cockpit

Overview

The Task List is part of the INUBIT Process Cockpit. In the Task List all persons involved in a business process can display their individual tasks.

Make sure your browser uses UTF-8 character encoding, e.g. to avoid problems with filtering and sorting tasks.
workbench user guide 759 1

The tasks are represented in a table with the following columns:

  • Task

    Displays the name of the task. The name originates from the correspondent dialog field, which was filled when creating the Task Generator.

    The symbol signalizes the task type:

  • Description

    A short description from the dialog of the same name that was filled in when the module was created.

  • Start

    Date and time of the module activation.

  • Expiration

    The point in time when the task will be removed from the task list. This point in time is calculated from the start time and the timeout entered when the module was created.

Sorting Tasks

Proceed as follows

  • Sorting in ascending order

    Click the header of a table column. The corresponding tasks are sorted. The up arrow in the column header indicates that the table content was sorted in ascending order by the selected column, e.g.:

    workbench user guide 760 2

    Alternatively, you can select the sort order directly from the column menu.

  • Reversing the sorting

    A second click the table header reverses the sorting order.

  • Selecting columns

    To display or hide columns, select the entry Columns from the column menu and activate or deactivate the checkbox next to the column.

For information on how to activate the sorting according to the German standard DIN 5007, refer to Using DIN 5007 sorting.

Using DIN 5007 sorting

When using the sorting according to the German standard (refer to DIN 5007), umlauts and characters with an accent are sorted with the corresponding vowels without umlaut or without accent, e.g.: Ä=A, ä=a, Ö=O, ö=o, Ü=U, ü=u, ß=ss, é=e, á=a etc.

Sorting is applied on task name, description, and user-defined columns of string data type for both portals BPC and Liferay.

Task list on a BPC portal

  1. Prepare the task list.

    • Existing Tasklist instance

      Redeploy the Tasklist, refer to Deploying modified portlets.

      Continue with step 2.

    • New custom Tasklist instance

      1. Create a copy of the Tasklist, refer to Adjusting Task Lists.

      2. In the following line, change the enableDIN5007Sort parameter to: true

        <xsl:param name="enableDIN5007Sort">true</xsl:param>

      3. Save the changes and deploy the new custom Tasklist to the BPC portal.

        → DIN 5007 sorting is activated. No further steps are necessary. In the BPC portal, you can change the setting as described in the following steps.

    • Existing custom Tasklist instance

      1. Add the following line below the line with the caseSensitiveFilter parameter

        <xsl:param name="enableDIN5007Sort">true</xsl:param>

      2. Save the changes and redeploy the task list.

        → DIN 5007 sorting is activated. No further steps are necessary. In the BPC portal, you can change the setting as described in the following steps.

  2. Log in to the BPC portal as an administrator.

  3. Choose the Administration item in the Global menu.

  4. Open the Process Interaction tab.

  5. In the Components section, choose the task list for which you want to configure the sorting.

  6. In the Settings section in the Tasklist_Configurations line, click in the Value cell. A JSON editor opens.

    workbench user guide 761 0

  7. Check the Tasklist_Configurations file:

    Check whether the enableDIN5007Sort parameter is set as follows and change it accordingly if not: "enableDIN5007Sort": true

  8. Click the Apply changes button.

Task list on a Liferay portal

  1. Create a new Tasklist and set the following parameter to true, refer to Adjusting Task Lists:

    <xsl:param name="enableDIN5007Sort">true</xsl:param>

  2. Deploy the new Tasklist.

Filtering Tasks

If you filter the indicated tasks by a specific criterion, you can work with a subset of tasks quickly and easily.

Proceed as follows

  1. From the column menu, select the Filters entry. A text field is displayed.

  2. Click in the text field.

  3. Enter the filter criterion, for example:

    workbench user guide 762 1

    By default, the filtering is case-sensitive. For changing the filtering to case-insensitive, create a new Tasklist using the Task Lists on the portal option in the Administration > General settings > Portal > Portal Deployment menu in the Workbench, set the value of the caseSensitiveFilter parameter to false, and deploy the new Tasklist to the Liferay portal, refer to Adjusting Task Lists.

  4. Press the Return key.

    → The table content is filtered. Only tasks are displayed which match the filter criterion.

    To change the filter criterion, click the text field again and modify the text.

    To remove the filter, deactivate the checkbox next to the Filters entry or delete the content of the text field.

Taking Over, Processing, Delegating and Releasing Tasks

You can take over a task before actually processing it. As long as you have taken over a task, it is locked and cannot be processed by others. You can release tasks, after you have taken them over, without processing them.

As soon as you start processing a task, it is taken over automatically and thus locked for other users.

When you have resolved a task, it is removed from the Task List automatically.

Proceed as follows

  • Taking over tasks

    In the Task List, click the green arrow button next to the task, which you want to take over, e.g.:

    workbench user guide 762 2

    The task is now displayed in bold:

    workbench user guide 762 3

  • Processing tasks

    Click the row containing the task.

    Depending on the type of the task, a form or some information is displayed or an external application is started.

    The task type is signalized by the symbol displayed to the left of the task name. Refer to Integrating Employees into Workflows by Tasks

  • Releasing tasks

    Click the blue arrow button to the right of the task, e.g.:

    workbench user guide 763 1

    The task is released and displayed again in the default font style with a green arrow.

  • Editing task properties, delegating task

    Use the Edit button to open the page Settings where you can re-initialize the task or delegate it.

    workbench user guide 763 2

  • Delegate task to all recipients (available only if the directDelegateToAll option is activated in the task list used)

    Refer to Adjusting Task Lists

    Click the Delegate to all recipients icon in the concerning line to delegate the task to all members in all roles configured.

workbench user guide 763 3

Adjusting Task Lists and Adding Columns

Overview

Task lists are generated with XSLT style sheets.

You can adapt the supplied task list Tasklist to your requirements by simply copying, renaming and adjusting their XSLT style sheets.

In this task list, data can also be sorted and filtered. In addition, the Tasklist provides a paging functionality. The Tasklist uses the Ext JS framework and displays task details in a window above the task list. The task details are loaded via Ajax.

Additionally, you can extend the task lists with customized columns in order to display business content.

Adjusting Task Lists

Proceed as follows

  1. In the INUBIT Workbench, display the Administration > General Settings tab.

  2. Display the configuration area Portal > Portal Deployment.

  3. Next to the option Task Lists on the portal, click the workbench user guide 764 0 button. The following dialog opens:

    workbench user guide 764 1

  4. Select the task list that you want to copy and adapt.

  5. In the Toolbar, click the workbench user guide 764 2 button to copy the XSLT style sheet:

    workbench user guide 765 2

    The XSLT style sheet is copied and a new entry is displayed in the table.

  6. Enter a meaningful name for the new task list in the Name field

    The Id is automatically generated. After generation, you can change the Id once. Please note that the Id must be unique and cannot be changed afterwards.

  7. If the task list should also be listed in another application category in the INUBIT Enterprise Portal, enter this category in the Category field

    Refer to Adding Portlets to a Page in Liferay

  8. In task lists, tasks from several INUBIT Process Engines can be displayed.

    In the field Other servers, enter the list of INUBIT Process Engines from where tasks should be collected. If you do not enter anything, only the tasks of the current INUBIT Process Engine are displayed.

    When entering the addresses in the field Other servers, you are expected to observe the format that is displayed for the option URL of the Process Engine. Several addresses are separated by blanks.

    For all specified INUBIT Process Engines, the Process Engine password must be the same.

  9. In order to deactivate the new task list, clear the checkbox for the option Enabled. Disabled task lists are not available as applications in the INUBIT Enterprise Portal and can therefore not be added to a portal page.

  10. Adapt the task list: You can manipulate the parameters of the task list by changing the values of the xsl:param element. The functions of parameters are documented in the XSLT style sheet.

    If you want to use the Process Viewer portlet on a portal page other than the default portal page, you must adjust the link to this portlet in the processViewerLink parameter. The link must be correctly set, if you want to link tasks from a task list with tasks in Business Process Diagrams.

Using the Process Viewer portlet on another portal page

Proceed as follows

  1. Open the portal page with the Process Viewer portlet.

  2. Click the plus icon in the portlet title to maximize it, the complete address is displayed.

  3. Copy the link part after hostname, port, and language code (https://<server>:<port>/de/) up to (but not including) the link part starting with ?p_p_id=ProcessViewer_WAR_isp to the clip board.

  4. Open the desired task list for editing (refer to step Adapt the task list: You can manipulate the parameters of the task list by changing the values of the xsl:param element. The functions of parameters are documented in the XSLT style sheet).

  5. In the task list, search for the parameter processViewerLink.

  6. Replace the string /group/inubit-cockpit/prozessmodell with the link part you have copied to the clipboard.

  7. Click OK to save the task list.

  8. Click the disk icon in the toolbar to save the changes.

Adding Columns to Task Lists

You can add further columns to the task list to display specific business-related contents. You can translate the column names in any languages and have them displayed.

The additional columns are generated for each Task Generator by using the variables mapping. In the task list, these columns are only displayed, if tasks are available that have been generated by a Task Generator based on a corresponding variables mapping.

You must determine the number of additional columns for each Tasklist when extending the Tasklist. This is due to the fact that each column in the XSLT style sheet of the Tasklist must be defined.

Proceed as follows

  1. Insert an Assign module before the Task Generator that generates the tasks with the additional columns, e.g.:

    workbench user guide 766 1

  2. Configure the variables mapping at the Assign module as you like. In doing this, you can map any source values (e.g. static values, variables, contents from input message) to a target variable, e.g.:

    workbench user guide 766 2

    The target variables must be of the xs:string type and observer the following structure:

    ISTasklistEntry.[<LanguageCode>.]<ColumnName>.[<ColumnPosition>]

    Additional columns are always displayed to the right of the default columns. An additional column with the position 1 is therefore the first column to the right of the last default column.

    You can define variables for different languages by using an optional language code (de, en, etc.) followed by a period.

  3. Only when enlarging the Tasklist:

    1. Display the XSLT style sheet of the Tasklist.

      Refer to Adjusting Task Lists

    2. Set the value of the parameter staticEntries to true:

      <xsl:param name="staticEntries">
  true
</xsl:param>

      In order to create a connection between the variable that provides the contents and the column that displays the contents, insert for each new column an Entry element in the xsl:variable element, e.g.:

      <xsl:variable name="translations">
  <Entry name="Invoice" en="Invoice No."/>
</xsl:variable>

  4. Multilingual column names

    By using the entry element from step 3, you can also translate the column names in any language and have them displayed.

    When declaring variables for multilingual column names within the Task Generator, they must be extended by adding the language code attribute:

    ISTasklistEntry.[<LanguageCode>.]<ColumnName>.<ColumnPosition>

    1. Display the XSLT style sheet of the task list.

      Refer to Adjusting Task Lists.

    2. Insert for each added column an Entry element in the xsl:variable element, e.g.:

      <xsl:variable name="translations">
    <Entry name="Invoice" en="Invoice No."/>
</xsl:variable>

    3. Insert an attribute for each language. The attribute corresponds to the country code of the desired language according to ISO 3166. Enter the translation of the column name as attribute value, e.g.:

      <xsl:variable name="translations">
  <Entry name="Invoice" en="Invoice No" de="Rechnungsnr."/>
</xsl:variable>

After applying changes to the XSLT style sheet, you must re-deploy the task list.

Adjusting Task Lists for a BPC Portal

Usage

To display task list details in a panel in the BPC portal and to configure both the position and the size of the panel

Prerequisites

  • You have configured BPC as portal for you INUBIT installation.

  • You have created a tasklist to be used as portlet on the BPC portal.

Proceed as follows

  1. In the INUBIT Workbench, display the Administration > General Settings tab.

  2. Display the configuration area Portal > Portal Deployment.

  3. Next to the option Task Lists on the portal, click the icon workbench user guide 764 0

  4. In the task list table, click the task list you want to adjust.

  5. Click the text view icon workbench user guide 767 2 to edit the task list settings.

    workbench user guide 768 1

  6. Adjust the following parameters:

    1. taskDetailView

      Set the taskDetailView parameter to true (default: false) in order to enable displaying the task list detail panel.

    2. taskDetailPosition

      Set the taskDetailPosition parameter to one of the following values:

      • north: the panel is displayed on top.

      • west: the panel is displayed on the left.

      • east: the panel is displayed on right (default).

      • south: the panel is displayed on the bottom.

    3. taskDetailSize

      Set the taskDetailSize to the width in pixels of task detail panel, default: 500

  7. Click OK to end editing the task list settings.

    The changes are not yet saved.

  8. Click the disk icon workbench user guide 768 2 in the toolbar to save the changes.

  9. Deploy or re-deploy the tasklist

    Refer to Deploying Web Applications as Portlet Archive

Creating Ad Hoc Processes

Usage

From the Task list of the INUBIT Process Cockpit, you can spontaneously start processes, so-called ad hoc processes. By using it, you can e.g. generate a new task at any time, delegate it to employees and have it displayed in their respective task list.

Functional principle

Technically, an ad hoc process is generally implemented as a Technical Workflow with at least one Task Generator. In the module wizard of this Task Generator the option Entry in Task List > Form is selected.

When starting the ad hoc process from within the task list, the module of the workflow is started that is configured as the so-called ad hoc process starter. This can be the Task Generator itself or any module before the Task Generator. The module you select depends on the fact if the Task Generator should create an already pre-filled or an empty form:

  • The Task Generator is to create a pre-filled form:

    Configure a module in front of the Task Generator as ad hoc process starter and use a sub-workflow between ad hoc process starter and Task Generator to create the form data.

  • The Task Generator is to create an empty form:

    Configure the Task Generator itself as ad hoc process starter.

After submitting the form data by using the Submit button, the form data are handed over to the next module in the workflow and are processed further as defined in the Technical Workflow.

A click on the Cancel button transfers the task for further processing to the task list.

The ad hoc process starter receives as input message an XML structure containing the following information:

  • Name of process user who starts the ad hoc process

  • All available process user roles

You can use this information to create e.g. a further task in the workflow and delegate it to selected process user roles.

Configuring a Module as Ad Hoc Process Starter

Prerequisites

A process user server must already be active!

Proceed as follows

  1. Open the Technical Workflow for editing.

  2. Mark the module that you want to use to start the process.

    You can start the Technical Workflow directly at the Task Generator or at any module in front of it, e.g. to fill the form with suitable data.

  3. Open the context menu of the module and select Ad hoc process starter. The following dialog opens:

    workbench user guide 770 0

  4. Enter a name and select the roles.

  5. Click OK to close the dialog.

→ The ad hoc symbol is displayed on the module and indicates that the module is used as ad hoc process starter.

Starting an Ad Hoc Process

Proceed as follows

  1. In the INUBIT Process Cockpit, display the Tasks tab.

    On the right over the Task List, a list of available ad hoc processes is displayed:

    workbench user guide 770 1

  2. Select the desired ad hoc process from the list.

  3. Click workbench user guide 770 2 to start the ad hoc process.

→ The form that is defined in the Task Generator is displayed. If you fill in and submit the form, the data are handed over to the next module in the workflow.

Removing the Ad Hoc Process Marker from the Module

Proceed as follows

  1. Open the Technical Workflow for editing.

  2. Open the context menu of the module with the marker.

  3. Select Ad hoc process starter. The dialog for selecting the process roles opens.

  4. Cancel the selection of process roles.

  5. Click OK to close the dialog.

→ The symbol on the module is removed. The module can no longer be used as ad hoc process starter.

Workflow Design of Web Applications

In contrast to desktop applications for example, web applications run in loops. Therefore, in the INUBIT Enterprise Portal, the last – not yet submitted – form of the web application is always displayed. Thus, the workflow that implements the web application always displays in the Queue Manager the status Waiting. In this status, the workflow does not consume any resources of the INUBIT Process Engine. In the workflow, the loop is e.g. implemented by a Joiner:

workbench user guide 771 1

The Web Application Input Connector is directly followed by a Joiner. The last form of the web application is connected to this Joiner. Therefore, in the web application, the first form is again displayed after the last.

A web application is stopped as soon as a session or portal timeout occurs or the user logs out from the portal.

For a practical introduction into the development of individual web applications, refer to Developing Your Own Web Application.

Deploying Web Applications as Portlet Archive

Before you can use your own and supplied web applications in the portal, you must deploy them. To do this, you must compile the desired web applications to a portlet archive.

When having configured the Business Process Center (BPC) as portal server, there is a Process Interaction portlet to be used with BPC. To remove the deployed Process Interaction portlet, click the delete icon in the Action column.

Prerequisites

  • You have already configured a process user server (refer to Configuring the Process User Server).

  • Virtimo AG recommends ensuring that no user is logged in to the portal during deployment. This can lead to problems with deployment. In case users are logged in and problems arise when displaying the portlet, remove the portlets from the page and inserts them again.

    Refer to Managing Portlets in Liferay

Compiling the Portlet Archive

Proceed as follows

  1. In the INUBIT Workbench, display the Configuration > General Settings tab.

  2. Display the configuration area Portal > Portal Deployment.

  3. Next to the option Portlet archives (Administration/Deployment), click workbench user guide 771 2. The following dialog opens:

    workbench user guide 772 1

  4. In the section Currently available portlets, select in the Action column all portlets that are to be deployed as a joint archive.

    When clicking the checkbox next to the archive name, all portlets of the archive are selected. When clicking this checkbox again, all portlets are deselected.

    Additionally, you can sort both the Name and the Title column by clicking on the column heading. When clicking on the column header for the first time, the entries are sorted in ascending order. When clicking on the column again, the entries are sorted in descending order.

  5. Click the Deploy archive button. The following dialog opens:

    workbench user guide 773 0

  6. Enter the name of the archive. If an archive of the same name already exists on the portal server, only those portlets are added to the existing archive that do not yet exist in the archive on the portal server.

  7. Click OK to close the dialog.

    The portlet archive is deployed to the portal. As soon as the deployment is completed, all deployed portlets are displayed in the section Archives on portal server.

  8. Close the dialog.

Deploying modified portlets

If you have modified web applications that have already been deployed, you can simply re-deploy the portlet archive. You need not recombine the archive again.

You need to re-deploy portlets after performing the following actions:

  • Task lists: creating, activating, deactivating, changing name or category

  • Monitoring-Portlets: creating, activating, deactivating, changing name or category

  • Web Application Connector: creating, activating, deactivating, changing name, changing category, changing permissions After all other actions, as for example modifications at modules in the portlet workflow, it is sufficient to re-initialize the portlet.

Refer to Re-initializing Web Applications

Proceed as follows

  1. Open the deployment dialog as described in Compiling the Portlet Archive.

  2. In the section Archives on portal server, click Redeploy:

    workbench user guide 773 1

  3. A prompt is displayed.

  4. Confirm the prompt. The portlet archive is re-deployed.

  5. Close the dialog.

Removing the Portlet Archive

You can remove the complete portlet archive from the portal server. This is e.g. useful, if you will no longer offer one or several web applications from the portlet archive.

Proceed as follows

  1. Open the deployment dialog as described in Compiling the Portlet Archive.

  2. In the section Archives on portal server, click Undeploy archive from portal:

    workbench user guide 774 0

    A prompt is displayed.

  3. Confirm the prompt. The portlet archive is removed from the portal. All available portlets are again displayed in the section Currently available portlets.

  4. Close the dialog.

Download Available Portlet as .war File

Proceed as follows

  1. In the INUBIT Workbench, display the Configuration > General Settings tab.

  2. Display the configuration area Portal > Portal Deployment.

  3. In the Portlet archives (Administration/Deployment) line, click workbench user guide 774 1.

    → The following dialog opens:

    workbench user guide 774 2

  4. To download an archive, click workbench user guide 774 1 in the line of the archive name.

    → The following dialog opens.

    workbench user guide 775 0

  5. Choose the desired directory.

  6. Enter the file name.

  7. Click Save.

→ The portlet is saved as a war file in the given directory.

Using INUBIT Web Application in Business Process Center (BPC)

Usage

To display INUBIT web applications in the BPC portal:

Prerequisites

  • The BPC Server is installed, configured, and started.

  • The INUBIT Process Engine is started.

  • The Business Process Center is configured as Portal server.

  • The Business Process Center is configured as Process Users Server.

  • Process Users and Roles from BPC are assigned to the INUBIT administrator.

Proceed as follows

  1. Create, configure, and deploy the web application, refer to:

  2. Open the web application in the BPC, refer to Opening INUBIT Web Application in BPC.

Opening INUBIT Web Application in BPC

Prerequisites

You have logged in to the BPC portal.

Proceed as follows

  1. In the BPC Global menu, choose the Settings item.

    → The BPC Administration page is displayed.

  2. Open the Components section in the INUBIT WebApp tab.

    → The INUBIT WebApp(s) deployed to the BPC are displayed in the Components section.

    workbench user guide 776 0

    When setting the Module_ReinitOnLoad option to true, a new entry is created in the Queue Manager on each WebApp load.

    When setting the Module_ReinitOnLoad option to false, no new entry is created in the Queue Manager if the WebApp is already loaded.

  3. Click the Open icon workbench user guide 776 1 to open the desired INUBIT WebApp.

    → The INUBIT WebApp is displayed.

    workbench user guide 776 2

    Click the Reload WebApp icon workbench user guide 776 3 on the top-right of the portlet to reload the WebApp.

    Click the Re-initialize WebApp icon workbench user guide 776 4 on the top-right of the portlet to re-initialize the WebApp.

→ Now, the INUBIT WebApp can be used, for example, to submit an order as described in the Tutorial, refer to Developing Your Own Web Application

Re-initializing Web Applications

In order to make modifications that have been applied to existing web applications visible in the INUBIT Enterprise Portal, it is usually enough to re-initialize the web applications.

Find a list of actions that require a re-deployment, refer to Deploying Web Applications as Portlet Archive.

Proceed as follows

  1. Display the relevant portlet.

  2. In the title bar of the portlet, click the configuration button:

    workbench user guide 777 0

    A menu opens.

  3. Select Preferences. The preference page is displayed.

  4. Click Reinit.

Identifying the URL of a Web Application

You can provide access to a Web application by means of a link to your employees or customers. To do this, you can send the URL of the web application, for example by e-mail. If the user calling up the URL is not yet logged in at the portal the login window is displayed.

This section explains how to determine the URL of your Web application.

Proceed as follows

  1. Open the page of the INUBIT Enterprise Portal where the web application is displayed.

  2. Submit the form.

    In the address line of the browser appears the URL of the last displayed form, e.g.

    https://<server>:<port>/group/inubit-cockpit/bestellung?p_auth=MsEv3RSe&p_p_id=75cfc19bc0a8005500a937ae1db4816a_WAR_isp&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_count=1

  3. Delete the definition of the parameter p_auth including the next & character and all parameters starting with the parameter p_p_lifecycle.

    → The sample URL now looks like this:

    https://<server>:<port>/group/inubit-cockpit/bestellung?p_p_id=75cfc19bc0a8005500a937ae1db4816a_WAR_isp

Enforcing a Restart of a Web Application

Usually, web applications run in a loop and are not restarted.

Refer to Workflow Design of Web Applications

In order to restart a web application explicitly, call the web application via its URL and attach the parameter precall=true, e.g. https://<server>:<port>/c/portal/layout?p_l_id=PRI.1002.2&p_p_id=8de66c4ec0a8005d00c0dc01861afbef_WAR_isp&precall=true.

This means that the workflow which implements the web application is restarted, beginning with the Web Application Input Connector. Any existing portal session is interrupted and a new portal session is established.

Refer to Identifying the URL of a Web Application

Example scenario

The explicit restart of a web application is useful, if users call the web application e.g. by clicking a link.

After the first click on the link, the web application is opened, a new portal session is established and the first form is displayed.

If users, then, do not use the web application directly and, later on, call the web application by clicking the link again, it is no longer the first form that is displayed, but the last displayed.

The reason for this is that the first instance of the web application, which has been generated by the first click and still runs, is not closed upon the second click. As long as the first instance still runs, no new instance is created. Here, the parameter precall=true is the solution.

Exchanging Data between Portlets: Inter-Portlet Communication

You can configure two web applications which are rendered as portlets by the INUBIT Enterprise Portal in such a way that the content of one portlet changes automatically depending on the content of the other portlet.

Example

There are two portlets on one page of the portal:

  1. In the source portlet users select an IT solution to get more information about it:

    workbench user guide 778 0

  2. In the target portlet the corresponding order form is displayed in which the selected solution is already listed (highlighted in red):

    workbench user guide 778 1

Background

When clicking the Submit button in the form of the source portlet, the selected data is transferred to next form in the same portlet and at the same time it is written into a Data element.

This Data element can be accessed from all portlets which are displayed on the same portal page like the source portlet. In order to make the Data element available for one portlet only, the target portlet’s ID must be defined in the source portlet.

When the next form in the source portlet is displayed, the form in the target portlet is also updated with the contents of the Data element.

Prerequisites

  • The INUBIT Enterprise Portal Liferay is activated.

  • Both portlets are implemented as web applications by Technical Workflows.

  • Both Technical Workflows are activated.

  • Both portlets are deployed.

  • Source and target portlets are added to the same page of the Portal.

Proceed as follows

  1. Configuring the target portlet

    Open the Web Application Connector of your target portlets and copy the interportlet communication ID:

    workbench user guide 779 1

    The ID is created automatically when the Web Application Connector is created. But you can overwrite the ID manually.

  2. Configuring the source portlet

    1. Open the Web Application Connector of the source portlet.

    2. In the Interportlet communication target field enter the ID of the target portlet copied in step 1:

      workbench user guide 780 0

  3. Defining a Data element for data transfer

    1. Display the Technical Workflow which implements the source portlet, for example:

      workbench user guide 781 0

      About the role of the Task Generators:

      • Selection: Creates the form, in which users select an IT solution, and transfers the selected data to the Feedback form.

      • Feedback: Writes the selected data into the Data-element and generates the form containing information about the selected data.

    2. Edit the Task Generator, which receives the data as input message which are to be transferred to the target portlet. In this example is the Task Generator Feedback.

    3. In the form mapping add a Data element with the attribute submit=’true’ directly beneath the Request element:

      workbench user guide 781 1

      The effect of the attribute submit=‘true‘ is that the form in the target portlet is submitted with the data from the Data element; this has exactly the effect as if users had selected the data manually and clicked on Submit.

  4. Creating a form mapping

    1. Load the output message which was created by the preceding Task Generator into the Source tab. In this example this is the preceding Task Generator Selection.

    2. Map the content of the output message which is to be handed over on to the Data element, for example:

      workbench user guide 782 0

  5. Creating an output mapping

    1. Display the form preview in the INUBIT Workbench and submit the form.

      The Output mapping tab is displayed. The XML response is displayed in the XML source file area.

    2. Map the contents of the XML response on to the output message.

    3. Publish the Task Generator.

  6. Creating an example message in the target portlet

    1. In the INUBIT Workbench, display the Technical Workflow of the target portlet. In this example the workflow looks like this:

      workbench user guide 782 1

    2. Switch on the watch mode.

    3. Test the portlets in the portal.

    4. In the INUBIT Workbench, save the input message of the Task Generator Order that displays the content of the Data element to the clipboard.

  7. Displaying data from the source portlet in the target portlet

    1. Open the Task Generator Order for editing.

    2. Load the input message from step 6 into the Source tab.

    3. Map the content of the Data element on to the form, e.g.:

      workbench user guide 783 0

  8. Creating an output mapping based on the XML response

    1. Display the target workflow in the watch mode.

    2. In the Portal display the source portlet and submit the source form.

      The target form is updated and displayed. In the INUBIT Workbench a watch point with a yellow marker is displayed directly before the Task Generator Order. Here, the process waits for the next user interaction.

      workbench user guide 783 1

      This watch point contains the XML response of the browser with the Data element from the source portlet.

    3. Open the watch point. Click Copy to clipboard.

    4. Open the Output mapping tab and load the XML response from the clipboard.

    5. Create the output mapping in such a way that the Data element is emitted as well.

    6. Publish the Task Generator.

Press Esc to exit full screen
Modal image placeholder
Press Esc to exit full screen