With a new plugin called “Button,” the integration capabilities of the Dew-X system have been greatly expanded.

What happens when a member of our organization ceases to be a member of our organization? How will the system behave? What about the history? What about tasks in progress? Itp., etc. You will find answers to these questions in this article.

If you are convinced that your organization needs a worklfow system, it is time to act. There are at least a few ways. Here we will address two of them.

The primary purpose of Namespaces is to represent sets of data that do not require flow. However, most business areas can be presented either in a static form or in a flow form. There are also areas that can be presented in both forms. Finally, there are also those where the flow is limited to one activity of the process – in this case, a static presentation is also a much better solution.

It is commonly believed that if something is for everything, it is for nothing. On one hand, there is a lot of truth in this, but on the other hand, this wisdom is often overused.

The advanced search engine allowed searching for process instances using many parameters. However, there was a need to searching also by user.

When we want to utilize the Dew-X system, for example, to handle error reports, even if the individuals we invited to use it are external to the Organization, they can see the complete list of its members internally when sending a task. This behavior of the system is correct, although not always desired.

Can all users delete tasks (process instances)? No. Only administrators (Admin role) and the owner (Owner) of a given Organization can delete any tasks (process instances).

Several clients reported to us the need to enable selected users to search among all process instances, not just those in which the searcher participated. We decided to remedy this by introducing a new role: searcher (Search)

What to do when many different activities should be performed at the same time by several different departments/people? For example, payment and accounting at an external accounting office should be done in parallel. There are at least two ways to achieve this goal.

When, for various reasons, we want to limit the visibility of certain processes for some users, e.g. related to strategy, HR, complaints, investments, marketing, etc., reflecting the structure would be very useful. In such a situation, the best solution will be to use “organizations” as company departments or task areas.

During our implementation of a purchasing process in a restaurant chain, the question arose as to why Global Tables are not used in the available process templates? We agree that both Global Tables and Dictionaries would be very useful in them. Especially in the definitions of the invoice workflow process or purchase requests. So why were neither Global Tables nor Dictionaries used there? The reason is very simple.

Virtual offices, external mailing offices and coworking are great solutions. They allow to outsource correspondence handling.

During one of our consultations, where we created ad hoc processes together with users, the idea arose to build a process based on a shared document, edited during the process by each party.

It turns out that Dew-X is also suitable for handling support requests. The interactive agency decided to use it for this purpose.

We were contacted by a law firm that handles many of its clients’ cases at the same time.The goal was to optimize the flow of cases and control them.