Hi David,
here are some ideas:
1. Provide an opputunity to configure the webclient default inbox (http://servername/workflowwebaccess/tasklist.aspx).
So you can set the default view for each user centralized as admin but also individualize as user (displayed columns, colors, any other filters, ...)
2. Provide an oppurtunity to extend the number of displayed tasks in a tasklist of the WebClient.
By default the number of tasks is 20 or something around it and if you have f.e. 50 Tasks within a list (because of high very high task processing times) you need to click through 3 pages instead of scrolling down. I know that such amount of displayed items in the list would cause a bigger load and it would be slower loading the list, but scrolling through all items is much more convinient than clicking through several pages page.
3. Provide an oppurtunity to identify easily bottlenecks within a model. (something like a global trigger for a model, not a single process)
f.e. Set a property at design time in a model that fires a notification (with PIDs, ProcessNames, TaskName, ResponsibleName of each, ...) to a specific user that TaskName got overdue in more than (n) processes.
4. Integrate Captaris Simulator to Captaris Workflow.
Provide oppurtunity to select a deployed model (not import *.mod file) that has already completed processes within Captaris Workflow then there should be all available details (from the TEAMPLATE DB) automatically set in the configuration of that simulation:
- set the average execution time of each task
- set the number ob processes created per hour (generator)
- set the average weight of the links (between tasks)
- and so on...
5. Provide an oppurtunity to create multiple groupings in a task list.
f.e. group firstly by Task (f.e. "Manager approval")n then secondly by Status and thirdly by Responsible.
So you would have something like grouped lists in SharePoint.
6. Grouped lists should be saved so you do not need to group them each time again.
7. AD Synchronization
Groups in Groups containing users should be synchronized
8. Provide an oppurtunity to reset an already completed webtask via WebAccess
If I find some more, I will post them here aswell.
Best regards,
Igor