search results

(...) ment or add a list of points) you can use the HTML language.   Fig. 2. The configuration of the step description   The position of the tasks displayed on the form and their visibility at individual steps can be configured on the global form template.   Fig. 3. The “Task details” section on the global form template   Task description Task d (...)

(...) p; Breaking inheritance – overwriting configuration At the current step on the form (Fig. 5) you can also: Overwrite the configuration of form fields, item list columns Define the visibility of the system areas Change settings such as visibility , editability or requirements form fields   Below there is an example – the “Analitical breakdown” item list: (...)

(...) entering a new value in the “Change amount” field will appear:   Fig. 11. The action of changing the “Change amount” field value   Finally, hide the visibility of technical field on the form.   Fig. 12. Availability restrictions

(...) g. 8. Searching instances on the report   To get the effect as shown in the screenshot above, in the "Search" section, select "Show results immediately" and turn on the visibility of the search panel (Fig. 9).   Fig. 9. Search panel configuration   Good practices: The instance number should be carefully considered before starting the production (...)

(...) orm fields displayed on it, and their settings. The form fields are organized in order and position (top, left, right, bottom) that is set on the graphical representation of the form. They have their visibility and editability settings, as well as other configuration options.    The configuration of the form consists of 1) form rules that are executed when the form is displayed, 2) visibility (...)

(...) ons directly in the browser. The configuration options are the same as when editing a button in Designer Studio.  Fig. 1. Enabling button edit mode.    Under the "visibility " field in the button configuration screen, you can check "Hide in the navigation menu." If you do so, the start button will be hidden on the main page of the application. It (...)

(...) tions that impact the visual layer.  This functionality toggles a diagnostic mode in WEBCON BPS Portal, which registers all invocations on the form, i.e., form rules, JavaScript, editability, visibility restrictions, etc. (see full list below). Diagnostic mode is activated in the user menu by selecting the "Show diagnostics" option. All WEBCON BPS Portal users have access to it. Fig (...)

(...) nt form field (ID and name) in the Value column. Fig.15 -Instance hyperlink configuration (create tags)   The last thing that needs to be done is setting the instance hyperlink visibility to hidden if there is already an existing instance, as shown in figure 16.   To do this, in the Promotion process, create a business rule that will check this (in Returned value type, selec (...)

(...) rdered into the form. They will be loaded from the URL parameters into the form fields you have specified. You can also limit who can see the button by choosing “Custom” in the “visibility ” field and selecting the right user(s). Only Active Directory users can be selected here. Figure 5 URL parameters and visibility configuration Configured start buttons on Portal (...)

(...) u click on any diagram element, a window with its properties will appear on the right side. Steps – you can only change the name and description Paths – you can define additional visibility restrictions and assign a task to the specified user Actions – you can change the action type and define additional execution conditions Fig. 7. Step/path/action edition You can z (...)

(...) described in detail in the following paragraph. The last part of the configuration is giving privileges for the reports. They give users options to create private views and choose non-standard report visibility (breaking inheritance of privileges from the application). Those privileges can be given to AD users. Fig. 10 User privileges configuration Views Report views allow users to create i (...)

(...) stant Another, more complex example, is the use of the SQL function that checks whether a user with a given login belongs to a given SharePoint group. This condition can be used to define the visibility of the form field (Invalid).   Fig.16. SharePoint group ID assigned manually. Incorrect configuration   In the example above, the number 45 was incorrectly used as the Share (...)

(...) ined target form fields.     The “Search” section allows you to select which source columns will be searched for matching characters with the autocomplete field. visibility of individual source columns in the autocomplete suggestions menu is defined in the “Show in dialogue (PopUp)” section. Marking source columns will cause their information to appear in th (...)

(...) that should be displayed in the form of links. To save space on the form, you can divide the table into pages by specifying how many rows are to be displayed on one page (10 by default). visibility requirement Define if the visibility of form fields depends on other conditions (e.g. form field value, currently logged in user). Editability requirement Define if the visibili (...)

(...) ble as quick path” checkbox.     A quick path will be displayed only for the user who holds the privilege for editing the given instance. To a path can be ascribed a visibility requirement but when at one path there are several instances at the same time then the visibility requirements must be met for each element. For administrators It happens that in case of err (...)

(...) o the selected process and then to Settings → Substitutions. Fig. 2. Configuration of work on behalf of another user in WEBCON BPS Designer Studio   Configuration in Portal and visibility of applications/processes when creating a substitution To add a substitution from Portal, go to the user settings and select Substitutions from the drop down menu. Fig. 3. User menu – (...)

(...) er needed since each timeout will now be associated with an automation. Menu buttons that have a Printout a barcode label action defined on them will have an additional business rule added to their visibility condition: one that states that the button will only be visible if the Document entry point ID is different than EMPTY. This is so that such buttons are only visible on machines that are document ent (...)

(...) rt type selected for the data series, it is possible to customize parameters relating to the appearance of the chart, such as: fill color (including lightening/darkening), border style, width, color, visibility , radius, etc.       In each chart view, it is possible to configure the sorting of data by the selected series or the X axis value. The exceptions are series containing (...)

(...) ation.   Fig. 2. Example of Instance history   History contains information about the instance, its workflow, and operations performed on it by users. Unless an appropriate visibility restriction rule has been defined, History also displays the names of all form fields along with the values entered for them, even if the user has set these fields as invisible in the Field matrix. (...)

(...) ldquo;Data row”, “Chart”, or “HTML” form fields. Additionally, archiving does not include custom controls, as well as form and business rules.     The visibility of an archived instance is another important matter. In such case all the fields visible just before the instance is moved from the content database will be visible after archiving (if some form fiel (...)