Here are some frequently asked questions (and our answers) about workflow.
| Question: | Why does renaming an item in the hierarchy not rename the workflow it represents? |
| Answer: | The name in the hierarchy represents the name of the workflow as the user of the workflow sees it. Whereas the name of the workflow is the title of the workflow as seen in the workflow editor and printouts of workflows. |
| |
| Question: | What happens if I update a workflow definition when there are instances running? |
| Answer: | All workflow definitions are versions, a running instance of a workflow is based on a particular version of the definition. Therefore generating a new definiton will have no effect on running workflows. |
| |
| Question: | What happens when an activity fails, for example if a web service for an activity can't be contacted? |
| Answer: | The workflow engine retries the activity 3 times and, if it still fails, it marks the activity as failed. The administrator of the system is e-mailed details of the failure. Once the problem is corrected, eg the web service is made available for connections, the workflow can be restarted from the workflow status screens. |
| |
| Question: | When executing a web service in a workflow I get a 401: access denied error, even though IE can view the web service correctly |
| Answer: | IE can pass Windows logon credentials to the web server, whereas the workflow engine does not. Check that another web browser (Netscape etc) can talk to the web service, and check the security settings on the directory within IIS. |
| |
