Sometimes users need to be assigned a task to do a specific function such as create documents. Currently, a user would need to create a document to request a new task to create a new document. Once the task has been submitted and workflow started the original "request" document is not needed or useful.

Adding the ability to Create a task that includes data fields that are customizable by administrators and for specific users to see would solve many issues. I envision that there would be a button under tasks that would say Create a task and based on the user role for instance in billing a set of fields are available such as "create an invoice" that user would click on create an invoice and would ask a few questions or select from a few drop down menu of items (customizable by admin) and then hit submit. This would trigger a task without any document. the processing user would get the task that shows the form or populated fields such as create invoice, amount, customer, etc. and is now able to create the document.

Our office a lot of times has to assign tasks for creating documents when there is no documents that exist already. Another example is if a manager needs someone to create a report or a power point presentation.

I think it would be very helpful for many offices.

Currently if I have a workflow task and I create a field in the dialog that is set to user of a group and multi-select and I have specified a group for the task assignment to display a list of users. I have found that if the group contains a role that the members of the role do not display in the list of user for the workflow field defined as user of a group. Only the individual users assigned to the group NOT the users assigned to the Role that is listed as a member of the group are displayed. All users including those users that are part of the group via being in the Role that is assigned to the group should be displayed.

In the workflow designer, you can schedule a task to run if a date field is a length of time after or before a date. There is no easy way to schedule it to run for documents that have a date = a date specifically today's date. So the solution is to have it run after the past 1 day and before the next 1 day and for some reason that ran it a day ahead of schedule so I had to put in a condition as the first command in the workflow to see if the date was = today() and if it was continue on if it is not then end the workflow.

At the work flow when there is an activity with an e-mail, I can send the e-mail to differents addressee but if I want to change the sender or select the sender who have to send the e-mail it's impossible, isn't it, because always choose the sender from e-mail service, and as I see always have to be the same, so please how can I change the sender when I program to send an e-mail through activity from the workfrow. I think it will be very interesting to have the oportunity to select the sender because not always the e.-mail comes from the same department.

In a workflow table field entry I would like to set a required field for a specific row. Here is an example. We have therapy evaluations. The referral comes in and is scheduled for the different therapy types with a table field that has the therapy type, date, location, and completion date. Then the therapists do the evaluations and they fill in the completion date. I would like to require that they fill in the completion date but if I require it then the first person to complete the evaluation would have to enter a date for the rest of the evaluations.

I frequently have workflows that require tasks to be due by x number of days after an indexed date.
The problem is I can only set the reminder date by a variable, which requires me to hardcode the due date after a reminder date.

I have a situation where a reminder date is 1 week before a due date, and the due date should be 30 days after a date index field.

If the document is stored the day before the task needs to be due, the reminder date defaults to the following day (since a reminder cannot be set to a past date), which shifts the due date to a week after it's actually due.

The best fix would be to allow due dates set by variables.
This would also benefit workflows that have multiple tasks that all need to be done by the same due date.