| Category |
Issue |
| Process Manager does not support
user names containing white space, '\', or '\t' |
If your user accounts have Domain specification (for example, using Microsoft Windows Active
Directory service for user management), and your Process Manager server is running
on a Linux server, you will encounter problems with the server rejecting an invalid user name if the
user names contain white space, '\', or '\t'.
For example, do not use "DOMAIN\john smith".
Also, if LSF is used as the job scheduler, the LSF configurations should comply with the above
rule as well, since Process Manager will retrieve some user name information from LSF.
|
| Flow Editor, user variables. |
In Flow Editor, if a user variable is used for the work item name (for
example, #{MYJOBNAME}):
- Submitting a test flow with a variable value for the work item name (for example,
MYJOBNAME=J1) succeeds, but the work item name is updated to the variable
value (that is, J1).
- Rerunning a test flow with a variable value for the work item name (for example,
MYJOBNAME=J1) does not work.
To prevent this issue, do not use user variables for any work item names.
If you must
use user variables, you can work around this issue by first designing and testing your flows without
using user variables for any work item names. After the flow definition is working correctly, change
the appropriate work item names to use user variables just before committing the flow.
|
| Flow Editor, test flow, submission forms. |
In Flow Editor, if you submit a test flow to debug a draft flow step
by step, submission forms might fail on the first run. Subsequent test flows work after the first
run and committed flows are not affected. To work around this issue, if a submission form fails in
a test flow, rerun the test flow to see if it succeeds. If the test flow still fails, the problem is
with the draft flow itself and you need to debug the test flow further.
|
| Flow Editor, subflow arrays, completion criteria. |
In Flow Editor, the Ignore work items in the waiting state
that will never run, or that depend on... completion criteria for subflow arrays does
not work as expected.To work around this issue before you run the flow, edit the flow in one of
the following ways:
- Clear the Ignore work items in the waiting state that will never run, or that depend
on... checkbox in the list of completion criteria. That is, do not use this particular
completion criteria.
- Have a separate job that can make sure that the flow is in a running state before the subflow
array execution is complete.
To work around this issue for a flow that is in progress, perform one of the following actions:
- Change the flow state immediately and continue running the flow.
- Continue running the flow and when the flow is complete, change the flow state to ensure that
the job item that occurs after the subflow array can run.
If you are running a single branched flow with this criteria, the work around is to
clear the Ignore work items in the waiting state that will never run, or that depend
on... checkbox in the list of completion criteria (that is, do not use this particular
completion criteria).
|
| Calendar Editor update |
When using an old Process Manager Calendar Editor
application with the newer Process Manager Fix Pack 7 server,
the text still reads "Save" when the action will implicitly automatically save and apply the
calendar. The user should update their Process Manager Calendar Editor and
client package. |
|