search results

(...) s after creating them because there may be delays due to data replication. Otherwise, you may receive a 404 error. We can easily account for the required delay in WEBCON BPS by using the “On time out” trigger for our action.     The time out will execute the action creating the team three time s. Each execution will be preceded by a 5-minute interval. The recommended (...)

(...) nd size of attachments for the selected processes (e.g. invoice cost, contracts), the size of the database may reach even several Terabytes. The backup/recovery procedures for such databases are very time consuming. Division into a dedicated database allows you to simplify the procedures and save time . Unlike the main database containing metadata and entire instance history (lots of operations I/O), (...)

(...) Elements table stores information about the instance and form fields value and the WFHistoryElementDetails table – information about values from the “Item list” form field. Every time when the instance goes to the next step in the workflow, in the WFHistoryElements table a new entry will be created. If the form has the “Item list” form fields, the same will happen in t (...)

(...) Configure” button.     There are three operating modes in the action configuration:     Create new file – it will create one new file each time when the action is triggered Create new file for item list rows – creates a separate file for each row in the item list Update existing file – updates a selected file based on the cat (...)

(...)   Tooltips on paths and steps The workflow steps in the MODERN form are listed on the right:   Fig. 4. The MODERN form   The step description is visible at all time s in the Task details section (if it is present on the form). To check the tooltip on the current step and other steps, hover over them.   Fig. 5. The tooltip on the workflow step &n (...)

(...) Configuration of the “Send a custom e-mail” action The e-mail notifications can be defined on the step as actions of the following types: On path On entry On exit On time out Upon instance deleting Upon instance saving On browser opening Menu button   The “Send a custom e-mail” action can be assigned as a workflow global action: U (...)

(...) bsp;you can limit the presented requests according to the absence type. For example you can present only vacation requests on demand in the schedule. Period – the ability of defining the time range on the chart. Levels of auto-expand – the schedule presents data taking into account the company structure, defining this property gives us the opportunity to automatically expand (...)

(...) cting the “Back to department registration” option will open the “Department registration” form. With this solution there is the ability to return to the basic workflow at any time .   Fig. 14. The Register department form   Conclusion Hyperlink actions triggered by menu buttons allow us to seamlessly connect and pass info between two separate workfl (...)

(...) A description of WFMails table columns: MAIL_Status – information about the status of the message MAIL_AttemptsNumber – a number of attempts to send a message MAIL_LastAttempttime – a last attempt to send a message MAIL_WFDID – an instance ID from which the action was initiated MAIL_STPID – a step ID at which the message was queued MAIL_DEFID – (...)

(...)   Fig. 3. The result of the query regarding the privileges on the process   The table contains information about the granted privileges, in addition you can check the date and time of granting the privileges and refresh information about them.   Form privileges in the workflow To grant the privileges for the individual forms in the workflows, select the specific w (...)

(...) informational function (e.g. displaying the data from other workflows), they should be replaced by data row or data table form fields. These form fields do not have the limitations and can reduce the time of loading the form. If the main system workflow is complicated and is supported by several dependent sub-workflows, they can be separated into two individual but still related processes. Make su (...)

(...) . Such a query should be implemented with an action ID. You can also add the additional filter in the “Additional filter” section e.g. to show the actions triggered in a certain period of time (e.g. of the condition: „LOG_TSInsert > ‘2020-04-20’” – the action performed after 20th of April 2020). The action ID can be entered in the configuration window: (...)

(...) ns in the process   An example The simple workflow of registration a vacation request has been created. When registering the request, the user may indicate the substitute person for the time of absence.   Fig. 4. The workflow of registration the vacation request   Steps in the workflow: Registration – entering the basic data Acceptance – supe (...)

(...) actions you configured, and keep in mind what ramifications repeating these actions would have. For some actions, executing them again once the workflow instances passes through the trigger one more time will make perfect sense – for others, it will not (e.g. an action that is meant to be triggered once per workflow, regardless of what steps it goes through). When configuring paths that allow y (...)

(...) ame and externalID columns   This approach, unlike to the previous one, will always search the data source. The more column will be searched, the greater will be the impact on form loading time . Using only the identifier allows to enter the value other than the choice field ID – e.g. NIP or vendor ID from an external system. It is also insensitive to display name changes or name forma (...)

(...) s of currently logged in user are checked to edit the parent instance. If the user does not have appropriate privileges, the action returns an error. Overwrite user editing element – sometime s an undesirable situation is setting the currently logged in user as a person who recently modified the workflow instance, because such a person has the privilege to read the instance value throughou (...)

(...) 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.

(...) e “Assign a task” path will allow you to move an instance to the next step and assign a task to the group. This means that the task will be assigned to all users in the given group at the time when the task is assigned. The users will receive information about the necessary changes to be made and then, they will receive the ability of confirming their realization by completed the &ldquo (...)

(...) given path – this function allows you to check which paths in the workflow are most often chosen. They should be particularly closely monitored in terms of query optimization and execution time of procedures. How many instances have ever been found in a specified step – seeing how many instances and how often have gone through a specified step, we can react quickly e.g. when in (...)

(...)   After selecting the category, the task is assigned to this person.   Task vs Privileges There are situations where the workflow stops at some step for a longer period of time (e.g. the employee wants to receive new equipment). In this situation, the “Equipment” step will be active for a long time and with it the active tasks assigned to the employee. The so (...)