search results

(...) to define the connection only once, and after that you can use WEBCON BPS out-of-the-box actions to quickly achieve your goals.   For example, you can set up new sites or create, edit and delete SharePoint lists and its elements. You can also download attachments from the list or manage user privileges using one of the predefined actions in the "SharePoint user  & privileges&qu (...)

(...) Applies to version 2020.1.3 ; author: Dawid Golonka    Introduction   This article describes how you can create, delete , and edit individual users in WEBCON BPS, using a standalone installation (one that operates without SharePoint). These features have been introduced with version 2020.1.3 of the program. You can also use BPS groups to manage users. To read more about i (...)

(...) de the previously prepared fixed list of values as a source. Fig. 3 - The "Role" 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&rdq (...)

(...) the Default content database is the parent Global administrator. This gives them almost unlimited power to manage Substitutions – they can add substitutions for themselves and others, edit and delete them, and freely change their settings. Fig. 10. Example of the Default content database definition   Summary When configuring Task delegation substitutions, one should keep in m (...)

(...) After adding an action on the selected path, an additional icon will appear next to it. You can define the order in which actions will be executed (if there is more than one action), and edit or delete the action.   Fig. 6. Available actions on the transition path When you click on any diagram element, a window with its properties will appear on the right side. Steps &ndas (...)

(...) ctionary instances. Import – it allows you to update the existing dictionary instances in a given environment and add new ones. Instances that are not in the package will not be changed (delete d or modified). Replace all instances – it allows you to delete all existing instances of the dictionary and add those from the package.   Fig.4 . Importing the contents of th (...)

(...)   Configuration of the "Add privileges" action The user may be granted one of four possible privileges levels: Administration - the highest privileges to read, edit and delete instances Modification (can’t delete ) - standard privileges to read and edit instances Read - only – privileges to read without editing the instance Read - only (can’t view at (...)

(...) ort-Export mechanism will have a different GUID identifier. This will result in overwriting any changes at the next import of this process from the TEST environment (the newly created element will be delete d, because in the TEST environment the object with this GUID does not exist). During an emergency in which any modification of the process had to be made manually, apart from the Import-Export mec (...)

(...) authentication policy in version SAML 2.0 by default. SharePoint server requires authentication token in version SAML 1.1.   SAML 1.1 configuration in SharePoint In order to do that delete authentication policy SAML 2.0 and add SAML 1.1 policy. This modification requires using a handful of scripts which delete default SAML 2.0 policy and add a new policy of authentication tokens: SA (...)

(...) y element in the queue. You can use this option if for example, 5 unsuccessful indexing attempts were made due to Solr unavailable. After resetting the counters, they will be reprocessed.  5. delete delete error elements - Deleting elements from the queue that have reached the limit of 5 invalid indexing attempts. Deleting pending elements - Deleting elements from the queue tha (...)

(...) emplate – it differs from the one exported for the “Change translations” function and contains only the ID column and name columns to be edited. When the value in the name field was delete d and it is empty during export, the system will remain the previous name of the configuration element. In the example below you see that the name of the “3839” element has been changed fr (...)

(...) alue is selected. By activating “Allow selecting values no longer available in the data source” checkbox one can decide whether the data selected in the choice field, which later will be delete d from the data source, should remain as the values selected in the choice field. By activating “Support multi language names” checkbox one can display in the choice list the translated i (...)

(...) d to that automation. Attachments menu actions are the exception, these will remain unchanged and actions on this trigger will not be migrated into automations. The WFTimeoutActions table will be delete d from the database. It is no longer 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 additi (...)

(...) ment sent for signature. In the respective case restrict searching to searching with the current instance ID, check if the file belongs to “To be signed” category, and make sure it is not delete d.   Figure 8. Authentication configuration In the authentication section select the previously created connection, set “grant_type” parameter to password aut (...)

(...) n when the field selection is active, i.e. it is in a black border (or use the right mouse button) (Fig. 3). Then select the appropriate value format using the arrow keys and Enter. It is possible to delete a fragment of the rule using the Backspace or delete system key. Fig. 3. Context menu of the Weather form field   When creating a rule, it is possible to use the Tab key and th (...)

(...) present case, it will be added to the "Accept" path:     After following the path, the action will download data from OneDrive, save it to the BPS database, and then delete the files from the indicated location in the service. Additionally, the successful action will be evidenced by the restoration of the original appearance of the attachment icons in the workflow insta (...)

(...) ield displayed as a table with definable columns that contain user’s data. This form field can be edited to the extent provided by the system: users can change the column values as well as add, delete , and clone individual rows. It is also possible to independently configure the Item List columns and their parameters, including width. This article is devoted to this very parameter and lists the (...)

(...) dquo;Insert condition”. At the transition from one step to the other the “On timeout” automation “Insert conditions” are recalculated. As a result, old conditions are delete d and new ones are created in their place. The moment of recalculation of “On timeout” insert conditions is shown on the diagram below.  Recalculation of “On timeout&rdqu (...)

(...) History may vary depending on the form field. For example, when changes are made to the Item list, the icon for that form field turns green (regardless of whether its data has been added, changed or delete d) and a small plus appears next to it. After clicking on the icon, a preview of the changes made is displayed.   Fig. 7. The Item list icon in History after making changes along with t (...)

(...) and “Remove from content database”.   Retention modes The archiving process can be executed in three modes. Irrespective of the selected mode the data are irreversibly delete d from the process database. It only retains information on the removed instances numbers in order to ensure uniqueness – the instance number can never repeat. The retention modes are described (...)