search results

(...) dictionary processes. When exporting from an Excel file, the Instance and Type column are visible, as well as all form fields that the dictionary process has (and are also marked as visible on the Field matrix ). The exported file contains all instances of the dictionary – even those marked as inactive.     The “Import from Excel file” function allows you to place a (...)

(...) PS Designer Studio allows you to create documentation for each created process. It consists of two files - DOCX that contains the text description of the process, and XLSX that contains the form Field matrix . Generating documentation There are three options to generate documentation: right-click on a process in Designer Studio use the Ctrl + D go to the Tasks tab     (...)

Applies to version 2019.1; author: Konrad Wojtycza   Introduction Adding a button to the form The “Registration of purchase order” workflow Adding the form rule triggered on a button “MoveToNextStep” form rule invoke “InvokeMenuAction” form rule invoke “InvokeRule” form rule invoke “Startelement/OpenElement”

(...) e is an update of the already existing article, it shows the configuration in version 2020.1.3. For the original see: BPS actions - introduction.   Introduction Global form template Field matrix - basics Filling in Field matrix Visibility tab Visibility - example Editability and requiredness tab Editability and requiredness - example Style and behavior tab Style and behavior - (...)

(...) d a list of the available paths in the form menu.   Configuration To enable the list of available paths at a given workflow step, go to WEBCON BPS Designer Studio -> Workflows -> Field matrix , and select the “Standard areas” tab. Then select the “Path list” option in the step where you want to display the path.   Fig. 2. Enabling the path list o (...)

(...)   Fig.8 Form preview in a web browser   Break / Restore Settings Inheritance - allows you to break or restore inheritance of compact form settings   Tab: Field matrix Open the tab Field matrix of the compact form. Go to the tab Form Fields to change form fields visibility. To define which areas should appear on the form and which should not open the Standard ar (...)

(...) dual instances' visibility and editability. You can see that the "Information" form field is set to be visible on the matrix in the details.   Fig. 10 Visibility on the Field matrix   The rule for changing the "Total value."  The rule for changing the "Total value" was executed. The "Show information when approval is req (...)

(...) sed on from the promotion process. Initially, the tags that are already registered will be locked for editing. However, we cannot make the “Tag’s name” column read-only in the Field matrix because we will still need to add new tags. Therefore, the list in the Modification step should look like in figure 3 below. The first two lines have been added earlier, and because of that, they are (...)

(...) ble in the dictionary. Fig. 12. The configuration of data source An example form of incoming correspondence may look like this: Fig. 13. The incoming correspondence form   Field matrix After defining the form and workflow designer, complete the Field matrix and define the visibility/editability/requiredness for each field in the individual steps. The matrix consists of four sect (...)

(...) ew method For the function MARK REQUIRED I MARK NOT REQUIRED to work properly, the field and item list columns in which requiredness will be modified should be set as ‘required’ in the Field matrix .   Fig. 4. Field matrix - setting the "Justification of need" form field   Fig. 5. Field matrix - setting the "Department Head's Consent" form f (...)

(...) iate 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 . Note: History does not include information on form fields from the Data presentation group and some from the Specialized form fields group. Fig. 3. highlights the individual elements of Histor (...)

(...) ce 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 fields were hidden on the Field matrix , they are not visible in the archive view). Moreover, although the general layout of the instance corresponds to the Field matrix configuration, the aforementioned dynamic content is not included. Al (...)

(...) de of the „Execution of Investment Projects” application   After selecting a workflow, a component with the following three tabs appears: Form designer, Workflow designer, and Field matrix . Designers are similar in appearance to those available in WEBCON BPS Designer Desk. In case the user does not have a personal license to access Designer Desk, all designers will open in read-only (...)

(...) ocess” button or the “Save all” icon.   To test the rule, open the form in the Portal and ensure that the relevant form fields are set as "Visible" in the "Field matrix ". Entering any value in the “Field 1” or “Field 2” form field results in transferring it to the “Total” form field. Entering values in both fields results (...)

(...) y in the process configuration (checking the “Enable instance and task sharing” checkbox in the “Sharing” section). You can manage the availability of the button in the “Field matrix ” (workflow name → “Main form” → “Field matrix ” → “Standard areas”) and by editing the form layout in a selected step (workflow name → the (...)

(...) you to generate QR codes for specific instances can be activated by the BPS application designer in Designer Studio. To do that select the QR code checkbox in the Standard areas tab (Main form → Field matrix ).   Capturing photos within the form By using the mobile application, you can capture and crop photos in the form. Such photos are then added as attachments and can be used in the (...)

(...) the test data for each step and field type on my own.  Therefore, I focused this time on generating the form data using the REST API. After all, we already have the workflow steps, field, and Field matrix , why should we define this again for Playwright? :) What has happened: I focused on PowerShell this time for accessing the REST API. I got interested in PowerShell classes. Since we alread (...)

(...) = document.createAttribute('accept'); attr.value=".pdf"; document.getElementById("fileupload-add").setAttributeNode(attr); </script> Don't forget to set the visible checkbox in the Field matrix . When loading the form, the accept attribute is being added to the input element  The open file dialogue reflects the accept attribute and only shows the file types you configured. (...)

(...) ld is active. This field allows users to decide if and how the selected color appears on the widget. From the four available options, select Fill. After configuring the form field availability in Field matrix and saving the configuration, the added Widget appears as follows:   One widget, two views: on the left, the project cost is within the budget (40,000 EUR); on the right, it exceeds th (...)

(...) tance from the workflow.   The button is visible to the Business administrator, regardless of whether the form is currently displayed in admin mode (you can configure its visibility in the Field matrix within Designer Studio). Please note that once the button is used, an instance is irreversibly removed from the workflow. Therefore, it should only be used in applicable situations, such as when dele (...)