Loading...
 
(Cached)
Page actions
PDF Refresh Print

bRobots Handbook

1. Part I. Preface

bRobots® enables you to rapidly implement complex business processes in SAP systems using a low-code approach. It is highly extensible and deeply integrated in the SAP ERP eco-system.

1.1. Intended audience


This handbook is mainly intended for the following user roles:

  1. Developers
    The following sections are the most important ones:
    1. Introduction
    2. BRO Basics
    3. Installing template processes
    4. Creating a new process based on a template process
    5. Part III. Common development tasks
    6. Part IV. Administration
  2. Business rules maintainers
    The following sections are the most important ones:
    1. Introduction
    2. BRO Basics
  3. Key users that are managing workflows
    The following sections are the most important ones:
    1. Introduction
    2. Part IV. Administration


Additionally, there are sections important for users of the SAP Basis team. These are:

  1. Introduction
  2. Installing bRobots®

1.2. Conventions used in this book


To provide a consistent and easy to read text, several conventions are followed throughout the book.

1.2.1. Keyboard shortcuts


Keyboard shortcuts are not described as they are listed next to the function button or as entry in the menu system anyway.

1.2.2. Functions in the application toolbar


If a function within the application toolbar of a SAP transaction has a corresponding entry in its menu system then the menu system entry is always used instead. If no corresponding menu system entry is available, then a screenshot of the icon used for the function button is used with no further descriptions. Entering a menu is indicated by the character >.

Example for a menu entry: Edit > Selections > Select All

Example for a function in the application toolbar:

1.2.3. Typographic Conventions

  1. Italics
    An italic font is used for emphasized text and the first usage of technical terms.
  2. Monospace in all caps
    A Monospace in all caps font is used for SAP-Transactions, ABAP objects, data dictionary entries and values within applications.
  3. Monospace in bold
    A monospace in bold font is used for fields and values within applications.
  4. Monospace in italics
    A monospace in italics font is used for paths in the menu system of an application.
  5. Monospace
    A monospace font is used for filenames and URLs
  6. Hoverable black font
    A hoverable black font is used for cross references

1.2.4. Definitions

The following definitions are used within this handbook:

  1. “Developer” refers to anyone who interacts with a bRobots® installation by modifying ABAP code.
  2. “Rule maintainer” refers to anyone who interacts with a bRobots® installation by modifying rules.
  3. “User” refers to anyone using functionality supplied by a bRobots® installation by executing rules and/or processes.
  4. “Request” refers to a workflow consisting of steps triggered and managed by bRobots®.
  5. “SAP Workflow” refers to a workflow triggered and managed by the SAP system itself.

1.2.5. SAP Theme

There are several different design options in SAP. To ensure that every reader has the same starting point for a good understanding of the manual, all graphic illustrations of SAP in this manual are based on the SAP Signature theme.
To check which theme is set in SAP, proceed as follows:

  1. Click to maintain the SAP Logon Options (refer to Figure 1)
  2. Select SAP Signature Theme as Theme Setting.

2. Part II. Getting started

2.1. Synopsis


After performing all sections within this chapter, you will:

  1. Have a basic understanding of the components of bRobots®.
  2. Have installed everything needed to build new processes with bRobots®.
  3. Have a basic understanding on how to create and maintain BRO rules.
  4. Know how to install processes.
  5. Have a basic understanding on how to create a new process.

2.2. Introduction

2.2.1. Synopsis

After this section you will know on a high level:

  1. The technical and business capabilities of bRobots®.
  2. The technical components of bRobots®.
  3. How bRobots® integrates into SAP.

2.2.2. What is bRobots®

bRobots® is a Framework consisting of the following pillars:

  1. The easy creation of input screens – named Fiori App+.
  2. The rule-based calculation/derivation of values of SAP objects and the easy creation/update/deletion of SAP objects – named Decision+.
    1. In foreground after the user filled in the input screens.
    2. In background automatically at specific stations within a workflow.
    3. In background only to allow other transactions to re-use the knowledge of the creation/update/deletion.
  3. The easy creation of workflows – named Workflow+.
    1. In foreground after the user filled in the input screens.
    2. In background only to allow other transactions trigger workflows.


The framework consists of hard-wired code which does not need any customization by developers. Additionally, it supplies many customer exits to allow re-using the time proven code of the framework for the specific challenges a developer faces.

The following core functions are available for companies using the bRobots® Framework:

  1. Default processes based on best practices for the following SAP objects:
    1. Material master
    2. Business partner
      1. General
      2. Customer
      3. Vendor
  2. The possibility to easily customize the default processes to suit the specific needs.
  3. The possibility to easily digitize processes that need direct interaction with the SAP system by eliminating the need for forms made in text processing software (like MS Word®).
  4. A tool to start connecting requesters for changes in the system with the corresponding decision makers.
    1. Reduces the overhead for the requesters to follow their request.
    2. Reduces the overhead for the decision makers to understand the request.
    3. Eliminates the overhead of manually copying and pasting request data into the actual SAP transactions.

2.2.3. bRobotS® technology Stack

In this section we discuss the technical structure of each pillar of bRobots®. bRobots® is the result of years of development of the product BRO – Business Rules Organizer. BRO itself is a rule engine built upon the SAP ABAP stack. It is thus highly integrated in SAP S/4 HANA.

BRO is the fundamental technology which drives bRobots®. All configurations, developments and customizings in bRobots® are done with BRO rules or in conjunction with BRO rules. During its history BRO has received the following addons which can either interact with BRO or can be used by BRO rules:

  1. Additional Action Types (For more information on action types please see Available action types)
    1. For sending e-mails – named Action Type E-Mail.
    2. For creating screens in SAP GUI and in Fiori – named Action Type Screen Definition and Webscreen.
    3. For creating SAP workflows – named Action Type Workflow Dispatch.
  2. A collection of function modules that can be used by BRO rules to create/update/delete SAP objects – named BRO MDM+.
  3. Utility applications to track and manage workflows created by the Action Type Workflow Dispatch – main applications are the Process & Service Cockpit and the Process & Service Monitor.


Depending on the pillar, the following components are built on top of BRO:

  1. Fiori App+
    Is a framework using the Action Type Screen Definition. Additionally, it integrates everything necessary to provide a fully functional Webscreen component. Thus, any application made with Fiori App+ will be executable in SAP GUI as well as in a web browser.
  2. Decision+
    Consists of the following parts:
    1. A framework to use BRO rules to calculate/derive values for SAP objects.
    2. Extensible pool of function modules that will take care to save the results of the BRO rules.
      1. BRO MDM+ ships function modules allowing saving different SAP objects (among other things material master, business partner, customer, vendor)
      2. BRO MDM+ defines a framework on how to add SAP objects that are not already covered by the function modules shipped with BRO MDM+.
  3. Workflow+
    Is a framework to create and manage dynamic workflows based on BRO rules. It further consists of exits to add functionality within the stations of the dynamic workflow based on the station itself.


Each pillar of bRobots® can be used on its own without any interaction to the other pillars. This is a core feature to allow starting projects where currently the greatest pain point within a company resides. Besides being able to use them on their own they are also implemented to have a very low barrier to start interacting with each other. This interaction is also done by the means of BRO rules.

The best-practice template processes that are part of bRobots® (see What is a template process for more information) are always using all pillars.

2.2.4. bRobots® Version scheme


All pillars of bRobots® and their respective components are using the same version number. The installed version is documented in the SAP system as installed component.
If you are already running bRobots® on your system, then you can log in to your SAP system using the SAP GUI and execute System > Status… and then click on next to Product Version. Filter for the value HKS in the column Component.


The column Release shows the Major Release installed on the system. The column SP Level shows the Service-Pack installed on the system.

  1. Major Release
    A major release is created once a year in Q3/Q4. It is a collection of all service packs since the last major release.

    Example Major Release: 5.4 (listed as Release 5_4 in the installed components of the SAP system)
  2. Service-Pack
    Service-Packs are created between two Major Releases. Its number is not limited but typically there are 4 to 6 for each Major Release. Each new Service-Pack comes with a Changelog which includes instructions on how to re-engineer a bRobots® installation before or after upgrading to this Service-Pack. Additionally, re-engineering reports might be included if necessary to automize re-engineerings.

    Example Service-Pack: 3 (listed as SP Level 0003 in the installed components of the SAP system)


A Service-Pack internally consists of:

  1. Bugfixes
    Bugfixes are only supplied for functions that are part of bRobots® itself not for solutions using bRobots®.
  2. Features
    New features that are either enhancing already existing functions of bRobots® or adding completely new functions.


Solutions using bRobots® are not supplied with new functions automatically. Depending on the feature it might be enabled by customer running the solution.
The Major Release concatenated with the Service-Pack results in the actual bRobots® version. Examples:

  1. Major Release 5.4 with Service-Pack 3 results in the bRobots® version 5.4.3.
  2. Major Release 5.5 results in the bRobots® version 5.5.0

Important: Re-engineering instructions if necessary are only supplied for changes in ABAP in the namespace /HKS/. Changes in the template decision areas are documented but re-engineering instructions are not supplied as those are never needed for the template decision areas anyway as they must be copied by the customer first. If the customer copies a template decision area to use it for his own processes, then changes to the template by akquinet HKS business technologies GmbH must be done manually by the customer in his individual copy of the template decision area if necessary.

2.2.5. Information for bRobots® maintenance contracts

akquinet HKS business technologies GmbH is selling maintenance contracts for bRobots® installations. The base contract includes:

  1. The possibility to report bugs to the bRobots® development team.
  2. The entitlement to receive bugfixes for the installed bRobots® version.
  3. Access to the bRobots® Wiki

The actual contract might diverge from the statements listed in this section and its subsections.

2.2.5.1. Entitlement to receive bugfixes


If a customer encounters a bug in a solution using bRobots® then the bug can be reported to the development team at akquinet HKS business technologies GmbH. The development team will get in touch with the customer if necessary to get more technical details. If the bug resides within bRobots®, then akquinet HKS business technologies GmbH will:

  1. Create a fix for that bug.
  2. Create necessary written instructions to perform re-engineerings to apply the bug fix.
  3. Depending on the bug one of the following options is available:
    1. The necessary changes in the code base of bRobots® on the customer are applied manually by an employee of akquinet HKS business technologies GmbH. This is only possible if the necessary change is very minimal.
    2. akquinet HKS business technologies GmbH supplies a transport request including the fix to the bug. Further features or bug fixes might be included in that transport request.

The customer must allow specific actions in his SAP system to be able to receive the bugfixes. If the customer fails to supply the possibility of performing the stated actions, then the customer must wait until the next Service-Pack which will include the bug fix. The necessary possible actions are:

  1. Allow source code modifications in the namespace /HKS/ by either an employee of akquinet HKS business technologies GmbH or by an employee of the customer.
  2. Allow local transport requests to create modifications in the namespace /HKS/ by either an employee of akquinet HKS business technologies GmbH or by an employee of the customer.
  3. Allow the transport of copies of local transport requests including modifications in the namespace /HKS/ by either an employee of akquinet HKS business technologies GmbH or by an employee of the customer.

Important: This entitlement is only available if the installed bRobots® version is not older than two Service-Packs. If the installed bRobots® version is Service-Pack 1 of a Major Release, then the last Service-Pack of the previous Major Release is still entitled to receive bugfixes.

2.2.5.2. Objects covered by the maintenance contract


Not every object supplied by akquinet HKS business technologies GmbH is covered by the maintenance contract.
Supplied bugfixes are available for the following objects and are handled differently for each object:

  1. ABAP code in the namespace /HKS/
    Any bug will be fixed and supplied.
  2. Rules in the decision areas KEN_HKS, BUP_HKS, MAT_HKS
    Any bug will be fixed and supplied.

    Decision areas that have been copied from the decision areas KEN_HKS, BUP_HKS and MAT_HKS will not receive any bugfixes by akquinet HKS business technologies GmbH.

2.3. Installing bRobots®

2.3.1. Synopsis

After performing all actions in this section, you will:

  1. Have bRobots® installed.
  2. Be able to develop create and maintain new rules and processes using bRobots®.

To perform the installation the following pre-requisites are required:

  1. Your SAP system meets the minimal system requirements.
  2. You have SAP GUI installed.
  3. Your account on your SAP system has sufficient authorizations to perform actions in the following transactions:
    1. STMS
    2. PFTC
    3. PFCG
    4. SWU3

2.3.2. Minimal system requirements

The backend components require a SAP ERP system with the following component versions:

ComponentReleaseSP-Level
SAP_ABA>=740>=0009
SAP_BASIS>=740>=0009

Using bRobots® on a SAP ERP system running lower component versions is not officially supported. Doing so is allowed but on the customer’s own risk. It might result in errors during the installation or to undefined behavior when executing components of bRobots®.

The frontend web components of bRobots® are created using SAPUI5 in Version 1.108. All browsers officially supported by that version of SAPUI5 are supported by bRobots® too. The list of supported browsers is available here.

2.3.3. Import transport requests

The transport requests needed contain everything necessary to run bRobots® on a backend system and on a frontend system. If you want a separate transport request with only the components necessary for a frontend system, then please send an e-mail to office at akquinet.at.

2.3.3.1. Fetching transport requests

The transport requests for an installation are always included in a Downloads section of a bRobots® changelog document on the bRobots® Wiki. The newest changelog document can be found on the Homepage of the bRobots® Wiki.
You will need to log in with a Wiki user having sufficient authorizations to access the transport requests. If you cannot access the transport requests then please send an e-mail to office at akquinet.at.


You must download all ZIP-files in the section First time installation of a changelog document. Place all extracted files in the transports directory of your physical SAP system. Each transport request comes as a pair of files with a different prefix:

  1. The file starting with K must be placed in the directory cofiles.
  2. The file starting with R must be placed in the directory data.

Important: if your SAP ERP system is not running the industry solution for Retail, then you must not import the "Release Retail ZIP".

2.3.3.2. Preparing the system

Before an import can be performed the system parameter for the allowed maximum size of a compiled version of a screen must be checked. If this parameter is too small, then an error might occur during the import of bRobots® or during the maintenance of BRO rules. The system parameter responsible for this is ztta/dynpro_area. More information on this system parameter can be found in the SAP note 167229. It can be checked and changed performing the following steps:

  1. Open transaction RZ11
  2. For the field Parameter name use the value ztta/dynpro_area.
  3. Execute Edit > Display.
  4. If the current value is less than 1,000,000 then it is highly recommended to increase it. A value of 1,500,000 is recommended. To change the value, perform the following steps:
    1. Execute Edit > Change.
    2. Place the desired value in the field New Value.
    3. Tick the option Switch on all servers.
    4. Click on Image .

2.3.3.3. Import transport requests

With the transport requests files available to the SAP system, it is now time to add them to the import queue in the Transport Management System and import them. This is done in the following way:

  1. Open transaction STMS.
  2. Execute function Overview > Imports.
  3. Perform a double click with the mouse on the system in which you want to perform the import.
  4. For each transport request downloaded from the Wiki perform the following actions:
    1. Execute Extras > Other Requests > Add.
    2. As the value for the field Transport request use the filename starting with K without the file extension. Use the file extension as a prefix before K. Example: the file K900622.H4D results into the transport request H4DK900622.
    3. Click on Image
  5. The transport requests must be imported in a specific order. The order is already listed in the Downloads section on the Changelog page where you have downloaded the transport requests. As some transport requests might take up to an hour to import it is recommended to import each transport request manually and only after the previous transport request has been imported successfully. For each transport request in the transport queue perform the following action:
    1. Select the transport request in the import queue still open from the previous steps.
    2. Execute Request > Import.
    3. Use the client number you on which bRobots® should be installed for the field Target Client.
    4. Depending on your needs you might want to schedule the import for a specific date in the tab Date.
    5. It is recommended to perform the import asynchronously. This is set in the tab Execution.
    6. In the tab Options use at least the following flags:
    7. Click on Image
    8. You now must wait until the transport request shows up as imported. Please check the return code of the import:
      1. 0 or 4: Import was successful.
      2. 8: Please check if your system is an ECC or a S4 installation. Depending on that different actions might be taken.
        1. Your system is an ECC installation: Please check the import logs.
          1. If the only error message in the import log is Table TOBJ_ATTR is not in nametab. then the import can be considered as successful.
          2. If other error messages are alongside the error message Table TOBJ_ATTR is not in nametab. then please get in touch with your contact at akquinet HKS business technologies GmbH or send an e-mail to office at akquinet.at. Either way please include the import logs.
        2. Your system is a S4 installation: Please get in touch with your contact at akquinet HKS business technologies GmbH or send an e-mail to office at akquinet.at. Either way please include the import logs.
      3. 12: Local settings on your system hinder the import. Please check the import logs.

2.3.4. Setup the SAP system

2.3.4.1. Setup the SAP workflow engine

In a system that is not already using SAP Workflows the SAP Workflow Engine must be enabled first. This is done in the following way:

  1. Open transaction SWU3.
  2. For each of the following entries perform first Auto-Customizing > Execute and then Edit > Execute:

2.3.4.2. Setup the SAP workflow

The task of the SAP Workflow Workitems of bRobots® must be updated after an installation. This can be done the following way:

  1. Open transaction PFTC. Use the value TS as Task type and the value 00391804 as Task.
  2. Execute function Task > Display.
  3. Execute function Additional data > Agent assignment > Maintain
  4. Execute function Edit > Attributes….
  5. Use the radio button value General Task and set the value NO_CLASS for Classification. Afterwards click on the function Transfer.

2.3.4.3. Setup the classification system


Requests created using bRobots® can have attachments. Attachments are stored in regular document info records. The link between a request and a document info record is created by classifying the document info record with the characteristic HKS_WFLOWNMB in the class /HKS/BRO_WF in the class type 017.

The characteristic and the class must be created directly on the system.

Create the characteristic by performing the following steps:

  1. Open transaction CT04.
  2. For the field Characteristic use the value HKS_WFLOWNMB and use the function Characteristic > Create.
  3. Use the following values:
    1. Tab Basic data
      1. Use BRO: Request number as Description.
      2. Use 1 as Status.
      3. Use CHAR as Data Type.
      4. Use 12 for the Number of Chars.
      5. Use the option Multiple Values.
    2. Tab Descriptions
      1. Use BRO: Antragsnummer for Language DE.
      2. Use BRO: Número da solicitação for Language PT.
      3. Save the characteristic using the function Characteristic > Save.


Create the class by performing the following steps:

  1. Open transaction CL01.
  2. For the field Class type use the value 017 and for the field Class use the value /HKS/BRO_WF.
  3. Use the function Class > Create.
  4. Use the following values:
    1. Tab Basic data:
      1. Use BRO: Link to WF as Description.
      2. Use 1 as Status.
    2. Tab Char.
      1. Insert a new line with the value HKS_WFLOWNMB in the column Char..
  5. Save the class by clicking .

2.3.4.4. Setup BRO

2.3.4.4.1. General setup

Next up the initial setup of the BRO global customizing must be performed. This is done by the following steps:

  1. Open transaction /HKS/BRO_GCUST
  2. Fill in the values according to the following screenshot:

2.3.4.4.2. Report for where-used lists

For the rule maintenance a report must be scheduled. This report ensures that certain where-used lists are kept consistent. Perform the following steps:

  1. Open transaction SA38.
  2. Use /HKS/W_UREBUILD_INACT_RULE_CR for the field Program.
  3. Use the function Program > Execute.
  4. Leave the parameters and the select options empty.
  5. Use the function Program > Execute in background.
  6. Use an output device that suits your needs the best. We recommend to not physically print the spool for this job.
  7. Setup the job:
    1. Click on the button Immediate.
    2. Tick the box Periodic Job.
    3. Click on the button Period Values. We recommend using the button Hourly. Afterwards click on to confirm the period values.
    4. Click on to schedule the job.

2.3.4.4.3. Function module /HKS/BRO_MDM_MAINT_OBJCL


Please login to see more.

2.3.4.5. Setup template decision areas

2.3.4.5.1. Retrieving template decision areas


Each bRobots® version ships with decision areas that can be used for customer-specific solutions. The available decision areas are:

  1. KEN_HKS
    This decision area contains the basic functionality to create request implementations using bRobots®. It includes a very minimalistic example process type (see What is a process for more information on what a process type is) which is intended to be used as a template for actual customer specific process types. It is included in every bRobots® product and is therefore generally available in the Changelog alongside the workbench and customizing transport requests.
  2. BUP_HKS
    This decision area contains advanced functionalities to create requests specifically in the context of the SAP objects business partners, customer master data and vendor master data. It includes full example process types to create, extend and modify those SAP objects. It is only included in the product bRobots® Business Partner. If you have purchased bRobots® Business Partner, then please request the file containing this decision area by sending an e-mail to office at akquinet.at.
  3. MAT_HKS
    This decision area contains advanced functionalities to create requests specifically in the context of the SAP object material master data. It is only included in the product bRobots® Logistics. If you have purchased bRobots® Logistics, then please request the file containing this decision area by sending an e-mail to office at akquinet.at.


If you have purchased a training from akquinet HKS, then you will receive a copy of the decision area BUP_HKS and MAT_HKS for a period of 60 days. The allowed usage within those 60 days is limited to trainings. Therefore, an import into a production client is not allowed. After the 60 days have passed the decision areas BUP_HKS and MAT_HKS and all copies thereof must be deleted from the system.

2.3.4.5.2. Importing template decision areas


2.3.4.6. Setup Frontend Components

The frontend components of bRobots® must be explicitly enabled after an installation. This is done by performing the following actions:

  1. Open transaction SICF.
  2. Perform Program > Execute.
  3. Now use the tree view on the bottom of the transaction. The service of each of the following paths must be enabled by performing a context menu click and then clicking Activate Service. Choose in the appearing popup to activate all sub services.
    1. default_host > sap > bc > bsp > hks
    2. default_host > sap > hks > bro_screen
    3. default_host > sap > bc > ui5_ui5 > hks
    4. default_host > sap > bc > ui5_ui5 > sap > hks

2.4. BRO Basics

2.4.1. Synopsis

In this section you will learn:

  1. The basic terms of BRO.
  2. The transaction involved to maintain BRO rules.
  3. A basic handling of BRO in the perspective of a
    1. Business rule maintainer
    2. Developer



2.4.2. bRobots® decision area


Please login to see more.

2.4.2.1. Create a decision area


Please login to see more.

2.4.2.1.1. Create a decision area from scratch


Please login to see more.

2.4.2.1.2. Create a decision area from a template


Please login to see more.

2.4.2.1.3. Default settings for a decision area


Please login to see more.

2.4.2.2. Maintain and Display a decision area


Please login to see more.

2.4.2.2.1. BRO fields


Please login to see more.

2.4.2.2.1.1. Variables


Please login to see more.

2.4.2.2.1.2. Table fields


Please login to see more.

2.4.2.2.1.3. Characteristics


Please login to see more.

2.4.2.2.1.4. Constants


Please login to see more.

2.4.2.2.2. Aliases


Please login to see more.

2.4.3. Create a simple rule

2.4.3.1. Synopsis




Please login to see more.

2.4.3.2. Example 1: create a simple rule


Please login to see more.

2.4.3.3. Deletion of a rule


Please login to see more.

2.4.3.4. Conditions


Please login to see more.

2.4.3.5. Actions


Please login to see more.

2.4.4. Categorize a rule

2.4.4.1. Synopsis


Please login to see more.

2.4.4.2. Create a rule category


Please login to see more.

2.4.4.3. Maintain a rule category


Please login to see more.

2.4.5. Running a rule


Please login to see more.

2.4.6. Creation and maintenance of Conditions


Please login to see more.

2.4.7. Creation and maintenance of Actions


Please login to see more.

2.4.8. Create complex rules to create a material

2.4.8.1. Synopsis


Please login to see more.

2.4.8.2. Example 2: Create complex rules to create materials - direct data definition


Please login to see more.

2.4.8.3. Rule-Chains connected by action types GOTO and CALL


Please login to see more.

2.4.8.4. Example 3: Create complex rules to create materials - generic way


Please login to see more.

2.4.9. Debugging a rule


Please login to see more.

2.4.9.1. Setting a breakpoint in bRobots® rules


Please login to see more.

2.4.9.2. With the Rule Report


Please login to see more.

2.4.9.3. With the BRO Testtool


Please login to see more.

2.4.9.3.1. Example 4: Global field F receives the value V1 althought it should receive V2


Please login to see more.

2.4.9.3.2. Example 5: The rule R is not executed at all


Please login to see more.

2.4.9.3.3. Example 6: The non-global field F occurs more than once


Please login to see more.

2.4.9.4. With the /HKS/BRO_VPROT


Please login to see more.

2.4.9.4.1. Setting up the protocol


Please login to see more.

2.4.9.4.2. Runtime value protocol management


Please login to see more.

2.4.10. (Mass) Deletion of flagged rules


Please login to see more.

2.4.11. Run a rule within ABAP


Please login to see more.



2.5. Installing template processes

2.5.1. Synopsis


Please login to see more.

2.5.2. What is a process


Please login to see more.

2.5.3. What is a template process


Please login to see more.

2.5.4. Installing a template process

2.5.4.1. Synopsis


Please login to see more.

2.5.4.2. Copy decision area


Please login to see more.

2.5.4.3. Copy runtime constants


Please login to see more.

2.5.4.4. Copy authority groups


Please login to see more.

2.5.4.5. Copy general workflow setup


Please login to see more.

2.5.4.6. Maintenance of the copied workflow setup


Please login to see more.



2.5.4.7. Create process aliases


Please login to see more.

2.5.4.8. Create process-specific workflow setup


Please login to see more.

2.5.4.9. Maintain user groups for steps


Please login to see more.

2.5.4.10. Start working


Please login to see more.

2.5.5. Creating a new process based on a template process

2.5.5.1. Synopsis


Please login to see more.

2.5.5.2. Copy process


Please login to see more.



3. Part III. Common development tasks

3.1. Synopsis


Please login to see more.



3.2. Rule transport


Please login to see more.

3.3. Mass activation of rules


Please login to see more.

3.4. Mass Generation of rules


Please login to see more.

3.5. Adding a new field on an existing screen


Please login to see more.

3.6. Setting a default value for an existing field


Please login to see more.

3.7. Adding new restrictions to an existing field


Please login to see more.

3.8. Adding a new button to an existing screen


Please login to see more.

3.9. Adding a new screen


Please login to see more.

3.10. Adding a new process step


Not yet released.

3.11. Adding a new process


Not yet released.

3.12. Calling a BRO function module


Please login to see more.

3.13. Creating a BRO function module


Please login to see more.

3.14. Calling a BRO MDM+ action function module


Please login to see more.

3.15. Creating a BRO MDM+ action function module


Please login to see more.

3.16. Adding a new field in the hierarchy


Please login to see more.



4. Part IV. Administration

4.1. Process & Service Monitor

4.1.1. Synopsis


Please login to see more.

4.1.2. Viewing a workflow


Please login to see more.

4.1.2.1. On header level


Please login to see more.

4.1.2.1.1. Example 7: Viewing completed requests on header level


Please login to see more.

4.1.2.2. On step level


Please login to see more.

4.1.2.2.1. Example 8: Viewing completed requests on step level


Please login to see more.

4.1.3. Admin use cases


Please login to see more.

4.1.3.1. Example 9: Admin use case - Replace a workitem


Please login to see more.

4.1.3.2. Example 10: Admin use case - Reserve a workitem


Please login to see more.

4.1.3.3. Example 11: Admin use case - Change the user group of a step


Please login to see more.

4.1.3.4. Example 12: Admin use case - Change the initiator of a request


Please login to see more.

4.1.3.5. Example 13: Admin use case - Re-activate a rejected request


Please login to see more.

4.2. Maintain user group assignments

4.2.1. Synopsis


Please login to see more.

4.2.2. Maintain user group assignments


Please login to see more.



4.3. Getting the version of the local bRobots® installation


Please login to see more.

4.4. Upgrading bRobots®


Please login to see more.

5. Part V. Appendix

5.1. Available operators for conditions


Please login to see more.

5.2. Available action types


Please login to see more.

5.3. Available process prefixes


Please login to see more.

5.4. Available process objects


Please login to see more.

5.5. Available template processes


Please login to see more.

5.6. Decision area setup


Please login to see more.

5.6.1. System Landscape - 3 systems


Please login to see more.

5.6.2. System Landscape - 2 systems


Please login to see more.

5.6.3. System Landscape - 1 system


Please login to see more.

5.7. Rules for input tree nodes


Please login to see more.

5.7.1. Database key


Please login to see more.

5.7.2. Logical key


Please login to see more.

5.7.3. Value


Please login to see more.