|
shortki
|
 |
« Reply #1 on: July 08, 2017, 12:37:34 AM » |
|
workflow.link enables collaboration for multiple users, therefore, individual service functions have a significant difference in implementation compared to the inShort application.
In particular, the Queues functionality becomes much richer, and I need some time to work through the concept of multi-user queues. This will not only be a mechanism for ranking current tasks, but also a means of allocating and assigning work to participants in the working group. Also, Queues will become a mechanism for sending notifications about current tasks. Therefore, Queues is an important stage in the subsequent development of the service, which needs to be thought over carefully.
The Task Calendar function also needs to be worked out.
The search in workflow.link is similar to inShort and is available in reports, you only need to preconfigure any report.
In workflow.link, there is no tactical coloring and various graphical styles of the diagrams, as drawing the graphics in a browser is not fast enough for these features. Also there are no proxy objects, as they can become a source of problems when working together. Illustrations in PDF format are not supported, as not all browsers support it, by the way, and vice versa, inShort does not work with SVG, since macOS does not have appropriate support.
In other respects, the systems are as much as possible identical.
|
