Features

In our workflow, triggered by action stamps, emails are sent to user groups for which there are new tasks. Some colleagues sometimes need a reminder to edit the documents now so that they can continue with the workflow. In order to automate these reminders, I would like the “Send email” action to be configurable in such a way that it sends a new email to the user group after a certain period of time when the task for the corresponding document has not yet been completed.

We work in accordance with our authorization structure via the task menu. Unfortunately, ALL stamps that can be used for the corresponding document are displayed during editing, regardless of which step of the workflow I am in. This more often results in “wrong” stamps being used in the task, which, in case of doubt, should be used elsewhere in the workflow. This can lead to misdirected documents, which unnecessarily interrupt or slow down the process. In this case, it would be desirable that only the stamps associated with the magnetic structure are actually available.

If the stamp action “EmailDispatch” was not carried out successfully, I would like useful error handling, similar to the “HTTP Request” stamp action. If the email delivery fails, there is currently an entry in the server's event log. Of course, no one looks through this. As a result, important documents (e.g. invoices) are not sent. The reason for the failure could be a moved email server or an email address that does not comply with naming conventions. A “stamp is only applied when email is delivered to the server” could bring significant improvement here. Other measures, such as “setting a property in case of an error,” would also be possible.

We have not yet switched to magnetization in some folders and would also like to be able to switch to the metadata view in the stamp actions and use it.

In our opinion, the stamping of multi-feature sets could be better designed. Instead of always carrying out the stamp process several times (e.g. allocation of invoice items/partial amounts to cost centers), this should be carried out within a stamp process. For this purpose, during the stamping process, a multi-characteristic could be provided with a (+) symbol, which, when confirmed, makes the corresponding multi-characteristic set available again. In our opinion, this has optimized the stamping process and also offers good combination options with other wishes expressed here, such as calculation features. Example: Distribution of an invoice amount until the entire value has been distributed.

We only want to make stamps visible if the documents to be stamped meet a specific characteristic (e.g. document type). At the moment, this is only possible by using additional sub-magnets in the workflow, which check the conditions and to which we determine stamp visibility. This requires a certain amount of additional effort and the workflow overview suffers.

We want to be able to specify/narrow down the email action using characteristics. For example, an email should only be sent to our marketing department if the department feature on the document matches.

If you select the stamp action “Send email”, you can send an email to “all stamp holders” as a group of recipients. It would be perfect if the “All stamp holders” option would also take into account who is actually allowed to read the document. As an example: There is a “factual examination” magnet. All employees are “editors” for this folder and can stamp the magnet's receipts. Each document has a “Reviewer” characteristic. Only the employee who has been selected as an inspector is allowed to read the corresponding document. If I select “Email delivery” --> “all stamp authorized” during the stamp campaign, all employees will receive a message. Regardless of whether they can see the document or not. It would have to be based on whether the employee receives an AMAGNO task or not.

This is a customer request. SQL autocomplete can be used for simple stamping. When mass stamping, autocompletion does not seem to work and the features can only be filled by hand. It should also be possible to use autocompletion here.