TO DO: Translate missing excerpts to English!
Note for authors: Please do not attach any pictures to this excerpt page! Upload all images you want to use in an excerpt to the page _BPaaS_images.
Chapter | Name | Excerpt | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Authorization Concept using Roles | old_authorization_concept | The following usage description of roles is deprecated. Starting with version PAS 18.1 we urgently recommend to create Apps mit zentraler Rollenverwaltung. Starting with version PAS 18.1 please only use the element Role. | |||||||||||||||||||||||||||||||||||||||||
Developer Guide | execute_export | Das Coding muss für jedes Template individuell angepasst werden. Bei der Ausführung des Codes werden die Instanzdaten den entsprechenden Platzhaltern im Template zugewiesen und der Download der Datei veranlasst. Gerne helfen wir Ihnen bei der Umsetzung Ihrer Datenexporte. Wenn Sie die Exportfunktion von Scheer PAS BPaaS einsetzen möchten, wenden Sie sich an Ihren Scheer PAS Consultant. | |||||||||||||||||||||||||||||||||||||||||
Developer Guide | provide_export_template | Die Vorlage kann in einem Formular hochgeladen oder von einem Administrator direkt im System bereit gestellt werden. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | applink_parent_child | Child Instance = instance in opening app | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | button_close_form | Attention: All following process steps will no longer be executed, the process will stop at this position. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | column_type_config | Configurate Column Type This option allows you to define your own column types. You could replace actual values with other output values, for example with a picture in a column instead of a value from the container. in order to define when a set value is replaced by a defined value, conditions have to be defined. How to configurate a column type is described on page Spaltentyp definieren. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | column_wizard_disabled | The column wizard can only be used if the model was assigned to a process app. Otherwise the button remains inactive: | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | column_wizard_info | The column wizard is only available for instance tables. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | default_buttons_config |
| |||||||||||||||||||||||||||||||||||||||||
Executing Processes | delete_responsive_element | Important information regarding the deletion behavior of grouping elements: If you delete a grouping element it is erased from your work space including all content . While the grouping element will also be erased from your database, its content can still be found and used via the search function. If the grouping element was linked prior to deleting, then only the current grouping element is erased. The linked element remains intact and can be found via the search function. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | example_table_config_upload | Example: Overview configuration to display uploaded data
| |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_combinations | Forms always have to be attached to a function. When modeling an EPC you may use the following form combinations:
| |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_additional_css_classes | Additional CSS Classes Possibility for a field acurate Layoutanpassung. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_app_project | Process App Project Insert the name of the App Project you wish to link here. This field uses auto-complete and shows matching App Projects in a recommendation list. If an App Project was entered, the corresponding model can be opend via the eye icon. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_column_config | Configurate Columns Click on the gear wheel to open an editor, which enables editing the columns of the table. An overview of available options can be found on page Tabellen manuell konfigurieren. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_create_new_tab | Create in a New Tab If this option is activated, a click on opens a new browser tab for the creation of a new element. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_current_value | Current Value This field can be used to insert default settings for the form element. The field Current Value contains a default value, which appears during form completion. If not overwritten by the user, this value will be transfered to the container while saving. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_description | Description The user sees the content of this commentary field in the form as a quick info: | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_edit_mode | To choose an option as default setting, click to activate the form field's edit mode. After successful editing finish by clicking . | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_edit_mode_text | To insert a text as default click After successful editing finish by clicking . to activate the form field's edit mode. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_execute_model | Execute Model Option to insert a different EPC model from a current BPaaS project. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_fieldname_for_possible_values | Container Name for Possible Values Possible values can not only be entered manually, one can also reference data objects from a container. In this case please enter the reference to the in container defined object into the field Container Name for Possible Values. The configuration field Possible Values remains empty. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_fieldname_in_container | Field Name in Container Defines the name under which the form field will be saved in the data container. If the Field Name in Container remains empty, then the field identifier (name) will be used to save in container. If two form fields share the same field name in container, then both will access the same value. The Field Name in Container is a technical identifier. It is often used for extended coding. Therefore the Field Name in Container should not contain any spaces, special characters or umlaut. For further information please visit Das Container-Prinzip. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_focus | Focus Element This field is ready for input and will be visually enhanced during form completion. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_hashtags | Hashtags Possibility to highlight your own key terms (Hashtags). The leading hashtag sign # (hash) will be inserted automatically. Use the space bar to separate multiple hashtags: One hashtag may be used for multiple form fields: | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_hide_input | Hide Input Instead of the entered content only dots are visible. This functionality finds its primary use in password entry. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_instance_new_tab | Open Instance in a New Tab If this option is activated, a chosen instance is opened in a new browser tab. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_mandatory | Mandatory The marked element must be filled or used. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_name | Name Field name shown in the form. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_overview_new_tab | Open Overview in a New Tab If this option is activated, a click on opens a new browser tab for the overview. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_possible_values | If in the field Possible Values a pair of values with same values was entered, i.e. 2;2 or ja;ja then one of these values will be deleted from the field display during saving. This value will be saved to the database as both value and label. For more information please see Mögliche Werte: value und label. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_read_only | Read Only This field is read-only. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_save_in_instance | Save Value in Instance If this checkbox is marked, the value entered in this field will be saved to the database during form execution. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_show_name | Show Name If this option is activated, the name of the element will appear in the top row. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_show_name_in_field | Show Name in Field The field identifier is shown within the field and can be overwritten. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | form_elements_table_standard | Standard Size for Table Elements Choose the number of rows the standard instance table shall display here. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | forms_edit_sidebar | The form field may be edited via the Edit Sidebar. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | forms_table_config | Tables have to be configured by the modeler. Please see Tabellenspalten konfigurieren to learn more about the available configuration possibilities. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | gear_color | The color of the gear wheel shows, whether an element is empty (light grey) or if content has already been saved (dark grey). | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | note_execution_model | Execution Model If you previously created your own EPC model, which shall be the basis for executing the Process App, please overwrite the entry in the field Execution Model. This field uses auto-complete. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | note_init_model | Initialization Model The same holds true for the Initialization Model. An Initialisierungsmodell is created when a process shall be executed prior to starting the process app. An example would be data retrieval from a separate system prior to starting the Process App to enable data access. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | note_signature_scaling | The input is centered. The more accurate the aspect ratio of the signature field corresponds to the drawing field, the larger the input will fill the field. The scaling of the aspect ratio of the field will vary depending on the terminal device. Use the preview option to adapt the size of the signature field to your device. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | start_column_wizard | The button start column wizard opens the Spaltenwizard. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | tip_block_elements | It is recommended to only keep standard formatting in block elements. Define all individual changes such as font or font color for all headers in CSS instead. | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | upload_allowed_types | Allowed File Types PAS 18.1.1 If you want to allow certain file types only, specify the allowed file types in this field. Separate multiple file types by comma. Example: Word and JPG files are allowed | |||||||||||||||||||||||||||||||||||||||||
Executing Processes | upload_element_instance_table | The element upload file enables upload of multiple files. This field's content is saved as array. Only one value per table field can be displayed in the search overview. If you wish to display the content of the form element upload file in the search overview, then it needs to be established during the search overview configuration which value out of the array shall be used. The array's first value is addressed with the number 0. Since it can be uncertain how many files were uploaded during multiple file upload, it is recommendable to always reference the first file. There are two options to view the content of the field:
Example: Display of the first uploaded file in the search overview
| |||||||||||||||||||||||||||||||||||||||||
Executing Processes | uuid_note | Purpose of column "uuid" Each instance is assigned an UUID in the database to enable explicit identification. Instance tables contain a by default hidden column uuid. Unhide the column in order to show instance identification numbers. This information is needed for example when contacting BPaaS Support with a support request regarding faulty instances. | |||||||||||||||||||||||||||||||||||||||||
FAQ | note_error_handling | Eine Übersicht über die BPaaS-Fehlermeldungen sowie Hinweise zu möglichen Ursachen und Lösungsansätzen finden Sie im Bereich BPaaS Support auf der Seite Fehlerbehandlung BPaaS. | |||||||||||||||||||||||||||||||||||||||||
FAQ | safari_developer_options | Öffnen Sie dafür im Menü Safari > Einstellungen und wechseln Sie hier zur Registerkarte Erweitert: Aktivieren Sie die Checkbox Menü "Entwickler" in der Menüleiste anzeigen: Die Option Entwickler wird in der Safari-Menüleiste hinzugefügt: Jetzt können Sie über das Entwicklermenü den Cache-Speicher leeren. | |||||||||||||||||||||||||||||||||||||||||
General Information | authorization_check_during_saving | An authorization check will always be performed while saving. | |||||||||||||||||||||||||||||||||||||||||
General Information | cancel_does_not_save | Attention: Unsaved data will be lost when clicking Cancel! | |||||||||||||||||||||||||||||||||||||||||
General Information | close_does_not_save | Attention: Unsaved data will be lost when clicking Close. | |||||||||||||||||||||||||||||||||||||||||
General Information | date_formats | The following place holders may be used to specify the date format:
The place holders may be combined with a fill character, i.e. blank space, dot, comma, hyphen, horizontal line. Fill words are accepted as well.
| |||||||||||||||||||||||||||||||||||||||||
General Information | editing_focus | Tip for working in BPaaS Editors
| |||||||||||||||||||||||||||||||||||||||||
General Information | fileupload | Alternatively you may upload a file via the BPaaS 17.3 ). icon ( | |||||||||||||||||||||||||||||||||||||||||
General Information | fileupload_image_format | Supported formats for image files are *.bpm, *.gif, *.jpeg, *.jpg, *.png and *.tiff. | |||||||||||||||||||||||||||||||||||||||||
General Information | form_test_mode | The testing possibilities of a form are limited within play mode. To test the interaction between multiple apps with the corresponding window management start the apps via tiles in cockpit or via the Process App entry link in Project Editor. | |||||||||||||||||||||||||||||||||||||||||
General Information | metainfos_unchangeable | Meta information are not changeable. If you would like to display meta information in a form field you always need to activate read-only characteristic for the relevant fields. If the field remains editable and changes are made to the meta information, those entries will not be safed! | |||||||||||||||||||||||||||||||||||||||||
General Information | note_authorization_concept | Additional information regarding creating role based apps can be found in the BPaaS Dokumentation on page Berechtigungskonzept mit Rollen. | |||||||||||||||||||||||||||||||||||||||||
General Information | note_element_name | Make sure to always name your elements. This name may not contain any of the following special characters: $ * + ? . ( ) [ ] { } / \ | ^ | |||||||||||||||||||||||||||||||||||||||||
General Information | overview_one_value_per_field | Each field in the table in the search overview may only contain one value each. | |||||||||||||||||||||||||||||||||||||||||
General Information | synchronization | Please be aware that no synchronization will occur between simultaneously opened browser tabs and windows while working on models and forms. Changes made in one window/tab will not automatically appear in a second window/tab. In order to display changes made in a separate window/tab you need to reload your current page. | |||||||||||||||||||||||||||||||||||||||||
General Information | timestamp | The date is saved in amounts of milliseconds (long) since 01.01.1970. Dates that are further in the past are therefore marked with a negative sign. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | bpaas_collection_name | Collection Name All app data is saved in its own name space. In this field you can define sub-name spaces for the instances of this precise entry link in the database. As soon as a collection's name is saved for an entry link, its instances will no longer be saved in the same place as the data of the remaining entry links of the project. We highly recommend to use this option for trial only. Preferably define the name of the collection in the App Project. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | close_pop-up | Leave the pop-up window via the Close button. Caution: Changes will not be saved! | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | css_template_blue | As a standard both the reference model and the overview model of newly created App Projects are assigned the CSS template CSS blue. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | css_templates | Template CSS blue Template CSS red Template CSS grey | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | developer_options |
| |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | doubleclick_editor | Double click on the element to open the editor. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_activate_roles | Activate this option to verify during app execution if the user was assigned the necessary roles. For further information visit Berechtigungskonzept mit Rollen. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_admin_model | Administration Model The Administration Model verifies that all users were assigned the necessary roles. The Administration Model is defined globally in the App Projekt element. If you configurated an Administration Model to be used with only this precise entry link, please save its name here. DEPRECATED with PAS 18.1 Deprecated with PAS 18.1Do not use the Administration Model for role based apps but manage roles centrally via Scheer PAS Administration. For further information visit Berechtigungskonzept mit Rollen. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_app_start | Start Use the Start button or double click on the element to execute the process app. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_cockpit_hide | Hide Element in Cockpit If this checkbox is marked, then this element will not be shown in the cockpit sidebar and no tile creation is possible for this element in cockpit. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_connector_constraints | In order to prevent an EPC from being ineffective always verify event and counterevent when designating constraints. Example: A form offers the answers YES and NO. In the process yes-answers shall follow a different path than no-answers. Therefore after sending the form, it has to be verified which of both paths needs to be followed. Instead of checking if YES or NO was specified, check if YES or NOT YES was entered. This enables you to also pick up cases where neither answer was specified. The counterevent to YES is not NO, but NOT YES! | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_css | CSS Model If layout specifications were defined in your own CSS model, please insert its name in this field. Your predefined design will then be in effect for this model. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_defining_app_project | If you define a model directly in the app element, then the model assigned to the app project will be ignored. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_description | Description A commentary field for the modeler. Its content is invisible to users and its sole purpose is internal documentation. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_edit | Edit the element via the Edit Sidebar. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_execute | Execute Use this button to start your model. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_execution_model | Execution Model The Execution Model is defined globally in the App Projekt element. If you configurated an EPC model, that shall be used with only this precise entry link, please save its name here. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_eye | This field uses auto-complete. Use the | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_fieldname_rest | Field Name in Container Assign a name under which the server answer is saved in the container. If the Field Name in Container remains empty, integration.result will be used. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_first_level | Elements, that are saved to the Project Editor work area cannot be linked via connections. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_hashtags | Hashtags Possibility to highlight with your own Hashtags. The leading hashtag sign # (hash) will be inserted automatically. Use the spacebar to insert multiple hashtags: One hashtag may be issued for multiple elements: | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_hide_mobile | Hide Element in Mobile App If this checkbox is marked, then this element will not be shown in the Scheer PAS Mobile app. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_init_model | Initialization Model The Initialization Model defines process steps that shall be completed prior to executing the app. The to be executed initialization model will be defined globally in the element App Projekt. If you have already configured an Initialization Model that shall be used for this precise entry link, please save its name here. This model will then be used prior to executing the elements. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_mandatory | Mandatory Marks the corresponding element as a requiered entry field. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_name | Name Name of the element within modeling. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_query | Search Query Define here which information of an instance shall be searched for. Click on the gear wheel to open the editor to save the search query as JSON object. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_role_for_link | Role for Link Insert the name of the role to receive app authorization here. The field Role for Link is supported by auto-complete and will list matching suggestions. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_save_instance | Save Instance Use this option to save instances to database. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | epc_elements_show_favorites | Show Favorites PAS 18.1 Activate this checkbox to show this element as favorite in the Scheer PAS Mobile App. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | link_function | Avoid linking functions (to reuse functions via the search or content menu, see EPK-Elemente kopieren und einfügen). Linked functions within an EPC or sub-EPC will lead to errors during process execution. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | logical_operators | Find an overview of commonly used logical operators below:
Generally always use the strict (in-)equality operator. This is to ensure that two operands match not only in value but also by type. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | note_mobile_elements | Mobile elements can only be executed in Scheer PAS Mobile. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | note_process_apps_until_17.2 | ||||||||||||||||||||||||||||||||||||||||||
Modeling Processes | note_roles_in_apps | Keep in mind to always issue two roles! Each role must have a Create and an Overview element. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | pop-up_save | Use the Save button in a pop-up window to save changes . | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | process_step_deleted | Caution when deleting process steps out of a (productive) EPC: Instances, which are situated in this process step can not be opened again afterwards. When trying to open an affected instance the following message will appear in the overview. This message contains name and ID of the deleted process step. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | restifier_url_internal | If your SAP-Restifier is situated in a customer environment, do not forget to fill out the field URL (internal) in the System element. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | sidebar_categories | The drop-down menu in the Sidebar New Elements will only show elements that can actually be created on this current editor level. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | volatile_data | Without further modeling the data is volatile, meaning they have been deposited in the container, but not saved! For further information see Instanzen speichern und löschen and Flüchtige Werte in die Datenbank speichern. | |||||||||||||||||||||||||||||||||||||||||
Modeling Processes | worker_declaration | Do not start worker coding with a declaration. | |||||||||||||||||||||||||||||||||||||||||
Starting BPaaS | bpaas_supported_browser |
* Usage of Internet Explorer Verwenden Sie für die Nutzung von BPaaS 16.04 oder höher den Internet Explorer 11 oder seinen Nachfolger Edge, da der Support für den Internet Explorer 10 seitens Microsoft eingestellt wurde und BPaaS den IE10 nicht mehr unterstützt. Wenn Sie den Internet Explorer 11 verwenden, achten Sie bitte darauf, dass er im Modus Edge läuft. Es gibt eine Reihe weiterer Webbrowser, mit denen BPaaS aufgerufen werden kann, aber der Support der Scheer GmbH beschränkt sich auf die in der Tabelle gelisteten Browser. | |||||||||||||||||||||||||||||||||||||||||
Starting BPaaS | cockpit_import | Exported apps or entire projects can be imported into the cockpit.
Step 1: Define Import
Step 2: Review Import
Step 3: Create Tiles
| |||||||||||||||||||||||||||||||||||||||||
Starting BPaaS | create_tile | To create a new tile use the Sidebar Neue Elemente link. | |||||||||||||||||||||||||||||||||||||||||
Starting BPaaS | create_tile_note | Modelers can create project, app and link tiles. App users are only authorized to create tiles and app tiles for external links. | |||||||||||||||||||||||||||||||||||||||||
Starting BPaaS | delete_tile | To delete a tile from cockpit, please click on the Recycle Bin icon. Confirm Delete in the pop-up window. | |||||||||||||||||||||||||||||||||||||||||
Working with BPaaS Editor | bpaas_search | Hilfreiche Tipps zur Verwendung der globalen Suche finden Sie auf der Seite Suchen im BPaaS-Editor. | |||||||||||||||||||||||||||||||||||||||||
Working with BPaaS Editor | search_maximum | Die Trefferliste zeigt maximal 15 Ergebnisse an. Ist das gesuchte Objekt nicht darunter, verfeinern Sie die Such-Eingabe. Gesucht wird nach mehreren Kriterien: Name, Übersetzung für die aktuelle Sprache, Objekttyp und Hashtag. |