WorkflowGen.com | Knowledge Base | Documentation | Downloads | Support | RSS

Entries from February 1, 2007 - March 1, 2007

How to Improve WorkflowGen performance?

Posted on Friday, February 16, 2007 at 10:21 by Registered CommenterWFG Team in | CommentsPost a Comment

- Install the database server (SQL or Oracle) on a different machine than the Web server
- Use the local IIS SMTP server to notification emails
- Limit the number of process data: keep only data used in conditions , important to be displayed and used as search criteria
- Limit the number of results returned in the end user module lists to 50 (Config/Number of records displayed in pages lists)
- Limit the number of results returned in the portal home page to 50 (Config/Maximum number of records into home page list)
- When the end-user completes an action, do not return automatically to the portal home page (Config/Once an action is completed)
- If you are using the portlet module, put into place a caching system when integrating your portal
- If you have a large number of requests and users, it would be a good idea to replicate your WorkflowGen database on another server for your  statistics and reports, so that you don't strain your production server
- Synchronize with WorkflowGen only potentially active users and groups. Use the text connector to synchronize a filtered list of users and groups
- Check that all your uploaded PDF forms have been optimized (Save As in Adobe Acrobat Professional)
- Check the performances of your FDFToolkit and SDK scripts (SQL queries, function calls and proceeding)