Configuration (English)
Please post all ideas that concern the configuration of DocuWare in this forum (i.e. DocuWare Administration, Workflow Designer, Desktop Apps).
94 results found
-
Email Notification Link via Workflow
Currently Workflow Designer does not allow you to generate the link name from variables with in DW only so the only option is to hardcode it.
It would be nice to be able to use the filename and a date as the link in the email being received by end users. It gives more meaning that hard coding the word document and then followed by variables
2 votes -
Workflow Designer: Assign a task to a role expect specific users
We would like the possibility to assign a task to any member of a role, except some specific users. The use case would be in a 4-eyes principle workflow, where in a same role one user must perform an action and another user (not especially an n+1) from the same role must review the action.
12 votes -
Allow the creation of Data Records from Workflow Manager/Designer.
I have a need to create two 'Numbers' from based on a condition. If IndexField A is not empty create the 'Number'. If Indexfield B is not empty create the 'Number'. It would be good enough for the customer that one or two Data Records are created using the data
6 votes -
allow us to use different fonts or text colours
This is a fairly simple idea: allow us to use different fonts or text colours in the decision forms.
Use case: an invoice that's part of an AP approval workflow fails validation and we'd like the reason for the validation-failure to be in red text to draw the user's attention to it.
3 votes -
Allow to configure automatic stamps with blackground colour in Workflow Manager
As you can not set an specific location for the automatic stamps in Workflow Manager, sometimes it can be stamped over the text of the document....if you can select a colour for the background of the stamp, at least you can see better the text included in the stamp
8 votes -
Improve connector lines
Connector lines are impossible to work with and make look logical. They move on their own to mess up the WF when any step is moved or removed. A great model for the designer would be the connector lines in Visio. Please improve the designer with useable, logical and clear connector line composition logic.
3 votesThank you for your idea. With the next generation of our Workflow Designer we will make sure this works far better. We currently cannot say exactly when this idea will be implemented. As soon as we have more information we will update its status.
-
allow list-type Role variables to be used as select lists in tasks
When creating a decision as part of a task and adding the various fields to the form, we can tie a select list to a field (for all the usual reasons). However, we can only use the select lists we've configured in the Admin Tool (or configurations). It would be great if we could use lists that we dynamically create as part of the workflow using the new Role variable. This would enable more customization of the workflow decisions, and since we already have the list-type Role global variable it might not be that hard to just allow the usage…
7 votes -
WF Steps as templates
Once I've created a WF step, ex., Task or Assign to, etc., I'd like to copy it and use it as a template for use in later steps in the overall WF. Please add this feature.
2 votes -
Fixed location option for workflow stamps
We have need to have approval stamps located in a particular location on the documents in the workflow. Being able to set a static location for a particular workflow task stamp would be nice.
5 votes -
Allow the opening of file URIs in the workflow manager
We can create links on a form to open a web capable application (http://...) but not a file link (file:///.....)
4 votes -
Allow nested operators in workflow designer
For the trigger conditions, it should have the same functionality as the file cabinet profile index filters. We should be able to set if Field1 is equal to Value1 AND Field2 is empty OR if Field3 is empty OR if Field4 is empty.
15 votes -
Development mode for Workflows
It would be nice to have a switch that would enable/disable notifications of non-controllers for workflows. This would allow the notifications to be put in place during testing and then enabled en masse when rolling the workflow out.
It would be even better if there was a way to redirect all notifications to the Controllers/Admins on a development workflow. That way the workflows can be confirmed as working, without spamming the end users before the workflow is ready.
8 votes -
Add formatting options to workflow information.
In workflows you can add a description to assist users, however there is no way to format any text in that information window.
6 votes -
Catch All Error Block
It would be incredibly useful to have a workflow wide error handling option. With the addition of the error variables in 6.11, this would allow a single action to be taken regardless of error location, and greatly simplify workflow design.
As it is, connecting all of the error outputs becomes hideously complex very quickly.
6 votes -
Allow additive Assignment of Tasks (Roles + Users + Variables)
Allow additive assignment of Tasks (Roles + Users + Variables)
It would be really super helpful if Tasks could use additive assignment throughout. This especially is true for escalation / rerouting. For example to add the a manager when escalating, so that the original person still can act on the task as well.
As it is now, this won't work. Consider the scenario:
- An incoming document triggers a workflow.
- The document has an index field "Assignment" and it's value is "Joe"
- A User-type global variable is populated with the value from "Assignment"
- The workflow assigns the…6 votes -
Allow error links to be hidden in Workflow Designer
It would be wonderful if we can toggle off the display of the red error links, maybe also providing some indication on the item that it is connected (for example change the color on the handle of the error output.) For complex workflows with many automatic steps, the error links can become overwhelming.
6 votes -
Allow to use stamp at decision level and not task level
It would be great if we could have the possibility to select an option : if one of the decision of the task should have a stamp and not another
For example : If i validate an invoice, stamp is placed
If i use the decision : request info is used, there is no need to place any stamp on the invoice.Options are currently very limited regarding task stamps
Thank you.
7 votesThank you for your idea. Right now we are focusing on other topics, so we are not considering this idea for future releases. If the demand for this topic increases, we might add it to future plans.
-
Enable horizontal scrolling in Workflow Designer
Scrolling mechanics natively supported in windows have evolved from vertical-only to include the horizontal dimension. Putting horizontal scrolling to use here would greatly help when working with large workflows -- just as much as vertical scrolling does. Whether using a touchpad with 2-finger drag, or a mouse with a tilt-wheel, navigation becomes much simpler, allowing the user to focus on the workflow itself rather than dragging the scrollbar back and forth.
3 votes -
Make Workflow Designer variables available in text area of stamp
WFD has a lot of ability to massage index field data that can be re-written to indices. It would be nice to get those values into text fields in WFD stamps. Currently the "Stamps include:" options are a limited number of unalterable data items. It would be great to include WF variables in additional text field(s).
3 votes -
In WorkFlow, conditional field show
For example:
If DocType ="invoice" then SHOW field "Total Invoice".
Show fields depending value of others fields
29 votesThank you for your idea. Right now we are focusing on other topics, so we are not considering this idea for future releases. If the demand for this topic increases, we might add it to future plans.
You can use a condition before the task and then use two different tasks. This seems to be a little more complicated, but structures the workflow easier readable and makes the single tasks less difficult to configure.
- Don't see your idea?