search results

(...) wo tabs: Steps – the stages of the workflow Actions – events executed when documents travel between steps of the workflow e.g. validation of entered data, file generation, sending notification s. 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. (...)

(...) evel or system Event Log.   Fig. 9. Possible errors   In case of events qualified as errors, the information can be sent to a specified e-mail address as administrative notification . To configure such notification for users list synchronization choose “Users list synchronization” in the notification range.   Fig. 10. The "Administrative notificati (...)

(...) r registers 10 workflow instances a day Every user moves 20 instances by one transition path per a day Every workflow instance registration and every path transition triggers a “send e-mail notification ” action. System is used for 12 months * 21 workdays = 252 workdays Every month, 2500 one-paged scans are added to various instances   Space used by instance registration: 25 (...)

(...) The function ignores empty values. In this article, we will copy values from the item list to the “Approvers to notify” form field. In this field, we select people who will receive a notification about an instance to be approved.   Fig. 1. The SELECT VALUES function in the expression editor Business case As you can see below, users copied to the “Approvers to not (...)

(...) help you to add configuration components, such as: Form field Step Transition path Report BPS group Action – general Action – form validation Action – e-mail notification Hardcopy template Privileges  Glossary of basic terms Below you can find a collection of basic terms used for describing WEBCON BPS environment. Tab. 1 Glossary of basic terms (...)

(...) it is possible to give it a Name and Description, each automation will also have two Definitions – one in the General tab and one in Error handling.   An automation named Ticket notification created on an On entry trigger   NOTE: As with action templates, it is possible to create automation templates in the Configuration node of process – such automations can then be fre (...)

(...) ocated Language Profile language Available options: pl-PL en-US es-ES de-DE UsePush Defines if the application should use PUSH notification s. Available options: true – use PUSH notification s false – do not use PUSH notification s   Below you can see an example of BPSX file con (...)

(...) .     Other examples of use The use of the Outlook Classic add-in is an alternative to automatic start of workflows based on messages sent to functional mailboxes (such as notification s@company.com), which is supported in WEBCON BPS through the Hotmailbox feature cooperating with the Exchange server. The feature should be used when the decision to start a workflow is made by the en (...)

(...) e “Add a barcode” action. As in the case of reading a barcode, the operation is executed by a service due to its duration. Associated modules: “Barcode printer”.   notification s – various operations related to delivering messages or notification s. The service sends, among other things, queued e-mail messages, i.e. the ones added to a queue by the “Send a custom (...)

(...) nu buttons. In the given example, the automations will be divided into the following groups: Generating documents Generate Excel Generate Word Convert Word to PDF Sending notification s via e-mail Send notification to superior Send notification to author Send notification to assigned person To create a new group of buttons, select Menu button in the Actions list se (...)

(...) ction This article aims to compile a list of minimum permissions for Microsoft Graph applications that will be used for handling four mailbox-related features available in WEBCON BPS. E-mail notification s Administrative notification s HotMailBoxes MailApproval   Each of these features can be configured to use Server type: Exchange Online - Microsoft Graph which allows them to work ( (...)

(...) Applies to version: 2022.1.4 and above; author: Grzegorz Straś   Introduction In the configuration of actions (e.g. Send a custom e-mail) and in E-mail notification templates, it is possible to define an account that will be used as the sender instead of the default sender address. This can be either an E-mail address or a Distribution group with “Send as” privileges. & (...)

(...) define a list of e-mail addresses). For each specified e-mail address there is a separate sharing with a unique link to the selected instance. It is also necessary to configure an e-mail sent as a notification to a person obtaining the link. To do that, enter the e-mail subject in the “Confirmation email - subject” in the action configuration window and type in its content in the “Confirm (...)

(...) oup is considered executed when completed by any group member. In both cases (assigning tasks to a group and assigning tasks directly to group members) it is possible to enable the sending e-mail notification s functionality to inform a group member about receiving a task. To do that, check the Send standard e-mail checkbox available under the “Task creation” tab (step edition → the &ldquo (...)

(...) this module has its own unconfigurable 30-minute interval. Additionally, for the modules listed below, the system checks if according to the configured schedule it is time to run them: Mass notification s Substitutions update Exchange rates synchronization LogCleaner Updating OLAP analyses SOLR indexer User synchronization Awaiting text layer, Awaiting recognition, and Awaiting learning (...)

(...) horization code will be sent to the user's email address (email message), phone number loaded from Active Directory and defined in the user's profile (SMS), or to the mobile application (PUSH notification ).   Fig. 4. SMS with authorization code   The received authorization code must be entered in the form window: Fig. 5. Form window for entering the authorization code (...)

(...) ed in the language selected in the User profile in Portal. Values selected on the form for a Choice list that are available in other parts of the system (e.g. in Reports, My tasks, Rules, and Mass notification s) are also displayed in the language currently set in Portal. However, this does not apply to previously saved instances – once the translations have been configured, the form must be re-popula (...)

(...) device.  Information about trusted device is also available in the Profile device in Profile. However, here you can only edit the device data or remove it as a trusted device.   PUSH notification s The application supports PUSH notification s that inform about creating new tasks for users. They are displayed within bubbles and, additionally, as a small application icon in the device status b (...)

(...) ies listed based on how they are supported:     Native part: Profiles, logins, and PIN authorization Searching for information stored in barcodes and 2D codes PUSH notification s Scanning barcodes and 2D codes Determining exact device location Biometric authorization WebView WEBCON BPS Portal Scanning barcodes and 2D codes and inputting informations (...)

(...) mprove user engagement, and provide a more personalized experience that aligns with modern expectations. Why Clients Need More Than a Default Template   The default WEBCON email notification template is by design a "one-checkbox" option to inform users about incoming tasks. It offers a sound foundation in terms of functionality, but it significantly lacks in areas crucial for b (...)