(...) e-mail and phone number (if verification via SMS is required). By going through the “Send to sign” path, the document is sent to the recipients who receive an e-mail about the document pending approval. The signing of the document is done via DocuSign page. Fig. 2. Signing the document by DocuSign After approval, a sender receives an e-mail informing that the (...)
(...) on Delete a user: Fig. 6. Delete a user action Two technical “[Tech]Add” and [Tech]Remove” form fields have been created in the process. Depending on whether in the previous step we add the “Add a user” or “Delete a user” path, one of the form field is set to the “1” value. As you see in Fig. 5 and 6, an acti (...)
(...) ue from the drop-down menu Pop-up search window -> an additional pop-up window appears, where you can select several options Autocomplete -> a text field that dynamically suggests answers depending on the given characters Person or group – allows you to search and select people, domain groups or SharePoint groups. Date and time – allows you to present and edit date and tim (...)
(...) bsp; The configuration of the Serial correspondence process The Outgoing correspondence process consists of four steps. On the “Registration” step you need to enter the data where depending on the selected path, you can move to the “Waiting for scan” step or directly to the “Preparation and shipping” step. In this step the documents are generated which can be sen (...)
(...) b and fill in the data set that will be passed to the Web service. The group name (“displayName” attribute) should be consistent with the organization policy. Depending on the settings, the group naming may require specific prefix or suffix. For more information see -> https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/groups-naming-p (...)
(...) mp;returnurl=%2Fdb%2F1%2Fapp%2F71&AttText1=’ + [$FileLeafRef] + ‘&AttText4=’ + [$ID] + ‘&AttText3=’+[$FileRef]” } } Depending on the “Status” column value, a “Start WEBCON BPS” text is displayed in the SharePoint library view; there is a simple function here: if([$Status]==’’,’St (...)
(...) use the configuration compatible with DEV/TEST/PROD environment i.e. use the constants containing the DEV/TEST/PROD sections in our configuration. By providing the different values in each section depending on the environment in which you work, the appropriate value will be inserted in the generated file. A description of good practices along with examples of the use of individual constants has been des (...)
(...) ps it goes through). When configuring paths that allow you to navigate workflow instances to previous steps, consider the following options: Set additional execution conditions on the action, depending on whether the workflow was moved back. For example: use an action that sets the value of an invisible technical form field to “1” if one of the “move back” paths is (...)
(...) y to enter multilingual names. The default value is set by providing an ID to correctly save the name translations. ID is stored in a process constant which allows you to enter the different values depending on the DEV-TEST-PROD environment, and use them in other places in the process configuration. Fig. 8. The default value of the “Invoice type” form field (...)
(...) The system step compliments the existing steps in the application. In this article, we presented one of the simpler cases of use based on two workflows, but system steps can be used more widely depending on business needs.
(...) hade of color with a proportionally distributed shade. C. Conditions The Conditions mode using conditional instructions and the operators available depending on the data type of the selected column. In this mode you can change the color and fonts, and refer to the content of other columns (from the 2020.3 version). In the example below, there is a colu (...)
(...) next to the application name, a window will appear in which the types of the application form will be listed. The searching structure allows viewing instances without spending time defining a report. Thanks to this, you can quickly search the structure and find the instance you are interested in.
(...) signed in different ways: Based on the logic of the business application (predefined task assignment) By indicating the specific user or group of users Based on a business rule Dynamic, depending on the value of one of the form fields By using the “Create a task” action By using the “Add privileges” action (in some cases it is better to grant permissions to edition (...)
(...) veral ways to modify the AI analysis to better suit our process: A) Changing the rank of the rule For each of the generated rule, we can define how important or relevant it is supposed to be. Depending on the rank, they will have a greater or lesser impact on the norm execution level of the instance. After changing the ranks in order to update information on the Anomalies (...)
(...) wser, the user interface will be presented in the language set in that browser. If the language of the browser is not available in WEBCON BPS Portal, the presentation language is set to English. Depending on the chosen interface language, correct phrases defined in the configuration and texts of fixed interface labels (which are the part of configurated language pack) are displayed. Defau (...)
(...) ID]. Let’s go to the workflow configuration – we want the task in the “Invoice description (FrontOffice”) step to be assigned to one of two groups depending on the selected department. The above configuration will work as intended, but it may provide us with several problems. This mechanism is quite complicated an (...)
(...) ldquo;Expense settlement” workflow. At the “Waiting for completion” step we must prepare two actions: The action responsible for moving ten expenses to the appropriate step (depending on the accounting decision) The action that updates the list of expenses on the settlement stage, indicating which expenses were updated by the first action Fig. 9. Actions on th (...)
(...) or us can be easily created from a simple wizard (available in the WEBCON BPS Designer Studio in the “Tasks” tab). This type of process doesn’t use the process licenses – so depending on the business needs, you can easily create several dictionaries. Fig.1. Creating a new document template process – wizard placement Like in any typical process w (...)
(...) b WEBCON BPS Designer Studio can be launched from a local machine but in order to connect smoothly to both Portal and the database, it requires an environment configuration. Depending on the chosen type of WEBCON BPS installation: with SharePoint, StandAlone and following methods of authentication: integrated login, SQL login, The foll (...)
(...) that color names are saved as HEX code. You can fill them in manually or choose from a picker by clicking a rectangle next to the tooltip. Color picker looks is different depending on the browser. Screenshot above presents color picker on a website displayed in IE. Screenshot below is from Chrome browser. Add a theme and check the “Is active&rdq (...)