search results

(...) Introduction Task creation is one of the basic functionalities enabling the creation of instance workflows in WEBCON BPS. Tasks in the system can be created in the step configuration on a given path or as an action that can be placed e.g. on the entry to the step. This article describes the “Create a task action” action, as well as the standard method of creating a task on a path (...)

(...) les for creating the file name, but for the example described, the name will remain as in the original attachment.   Fig. 3. The business rule returning the file name   2. The path with actions On the “Active” step, a dedicated “Send the attachment via OneDrive” path was added that contains several actions: Get users drive ID (using the REST Web (...)

(...) le describes the validation mechanism.   The example workflow In the example “Purchase order” workflow, all validation actions were configured on the “Register” path .   Fig. 1. The fragment of the “Purchase order” workflow   Validation actions have been configured in the “Actions” tab on the “Register&rdquo (...)

(...) ld - read and edit restrictions                > Form type - default assignments                > path s - assignments                > Business rules - user lists   The “Change also archived tasks” option allows you to assign pr (...)

(...) ts of 1) form rules that are executed when the form is displayed, 2) visibility settings for the top bar buttons, 3) editing mode, 4) attachment settings, 5) and accessibility settings for transition path s.   Creating a new form configuration The WEBCON BPS platform builds a compact form by default. When you create the main form, a compact form is automatically built. In most cases, this (...)

(...) ellip;) next to it to choose it from a list of available parent sites, Title - site name, Description - site description, URL name – the text that will be displayed in the website address path .   Fig.3 Action configuration for “Create a site”   You can save the address of the newly created site in a workflow's form field. To do so, tick the b (...)

(...) wly created subsite, and consider adding a site description in the “Description” field. In the “URL name” field, enter the name that should be displayed in the website address path .   Below you can see how we have filled in the values. We have used the values from the form to fill in the name, description, and URL name fields. If you want to do the same, click on a (...)

(...) ceeds to further recognition of the file queue in the service   Fig. 5. Missing or unmatched barcode   In the “Workflow StartUp Settings” tab, you can define a path to be followed by the workflow after adding the attachment to the workflow.   Fig. 6. The “path for new element” option   In the “Additional fields settin (...)

(...) om of the article). To do this, create an empty directory on the disk, e.g., with the same name as the theme, and use the command: Export-AdfsWebTheme -Name MyADFSWebTheme -Directorypath  "C:MyADFSWebTheme"   All graphics, styles and scripts of our theme will be exported. Fig. 4 The theme downloaded to the hard drive   Now, you can repla (...)

(...) e user. Once submitted, it is sent for acceptance to the Approver. If the Approver accepts, the action requested in the form (create, delete or edit the user) is performed on the “Accept” path that goes from the “Acceptance” step to the “Actions done” step. Fig. 1 The workflow for creating, removing, and editing BPS users   In our example, we (...)

(...) dynamically on the form, i.e., it can be executed after each change in the value of the Text 1, 2, 3 form fields; it can also work statically, e.g., when the form goes from one step to another (on a path )or  when a button is clicked. For the function to work dynamically, in the “Style and behavior” tab we have added a rule that sets the value of the Concat(Text 1,2,3) field on va (...)

(...) asks must perform an action. WEBCON BPS has a comprehensive tool that allows you to choose who the task should go to in the next step; it is configured in the ‘Task assignment’ tab on the path that links two steps.   However, this is not the only way to assign a task to the user. This article discusses how you can use the “Choose an approver” action to assign a task. (...)

(...) at the final step   Promotion process configuration   The promotion process should be configured adequately to the business needs, which involves creating appropriate steps, path s, and form fields. In our example, we will need to create the Client form field so that the system knows from which instance it should download the tags used in the process. The next thing we should (...)

(...) "Basic features" option. After expanding this menu, go to the “Services” submenu and select your Service. The screenshot below shows the view in Studio after following this path . Check the box next to “Basic features”.   Fig.1. Service configuration.   Data update takes place only at times selected by the user. To define the update hours (...)

(...) ot; form field configuration In the advanced configuration of the item list, uncheck the “Allow delete” option - instead of deleting rows we will mark them as inactive. On the Register path , you should add the form validation action to check the uniqueness of the instance. If the “Role” form field has been added, then in the system should be only one workflow instance with a (...)

(...) ing substitute with standard emails – determines whether to send notifications to Substitutes about newly created tasks. They are sent only if the Send standard email option is selected ion the path , Notify substitute of tasks assigned before substitution started – determines whether email notifications should also be sent for tasks created before the substitution period – such sub (...)

(...) he modified form containing the fields for entering data into the EMSI_JobChange_UK table. Fig. 1. The fragment of the UK Job Change workflow form After following the "Add data" path , the data completed on the form will be saved to the table in the database and will be displayed on the table preview visible on the form. Fig. 2. The fragment of the UK Job Change workf (...)

(...) ations. You can define additional conditions for each action. Fig. 5. Workflow designer Each created project contains two default steps – Start and Final which are connected by one path . You can add any number of intermediate steps, define flow control steps (they are used for directing documents through one of the possible path s based on a condition e.g. can be used to skip a step (...)

(...) Removed Public REST API 4.0 - - - - Supported Deprecated Public REST API 5.0 - - - - Supported Supported Choose path (List/SQL) Actions Yes (deprecated) supported until the end of 2022 N/A replaced with the Flow Control step N/A N/A Sign an attachment with Cosign Action Defun (...)

(...) must take the following into consideration: Volume of workflow instances registered daily Complexity of the form (number of form fields, item lists) Number of steps in given workflow (every path transition is recorded in the instance’s history) Number and type of actions used in the system (e-mails, changing field values, launching subworkflows) Average size and number of attachmen (...)