You can save a workflow definition in either your local file system or in an object store or library.
NOTE To
make a workflow definition available for production use by others, you must check in the workflow
definition to an object store or library
that has the Workflow definition document class. If you use the Launch command to run the workflow
from Process Designer, the program will prompt you to save. You can disable the automatic Add/Check
in feature in the workflow preferences. See Preferences
- Workflow for additional information.
To save a workflow definition in an object store or library
for the first time
Workplace
FileNet Web Services Client
Open Client
Save in an object store
From the File menu, select FileNet
Add New.
Click Browse, then open the appropriate object store
and the desired folder.
Enter a title for the document. The document title subsequently displays in the list
of workflow definitions.
NOTE If
you leave the document title blank, the document title will display as a very long number.
Specify security access for other users. (Optional.) See Participant
selection for information about selecting users.
Click Finish.
Save in a library
From the File menu, select FileNet
Add New.
Enter a document name.The system automatically appends the extension PEP.
Click Browse, then open the appropriate library and
the desired folder.
Click Save, then click Next.
Enter a document title. The document title subsequently displays in the list of workflow
definitions.
Click Next to specify security access for other users.
(Optional.)
Click Finish.
To save changes to an existing workflow definition that you have checked out
From the File menu, select one of the following:
Use FileNet Check In to check in your changes and unlock
the file. This increments the version of the workflow definition. Process Designer
closes the workflow definition after the checkin.
Use FileNet Save to save your changes and leave the workflow
definition open (and checked out) in Process Designer
after the save.
Workplace
FileNet Web Services Client
Open Client
FileNet Save does not increment the version in the
object storeonly the checked in version is visible. If you close the workflow definition
or close Process Designer
after saving a workflow definition using FileNet Save, that workflow definition will remain
checked out to you. When you re-open that workflow definition, it will contain all changes
up to the save. However, if you cancel the checkout or another user assumes the checkout,
all changes since the last checkin will be lost.
FileNet Save increments the version number
in the library. Therefore, if you subsequently cancel a checkout, only changes made in
the current session will be discarded.
To save an open workflow definition to your local file system
From the File menu, choose Save
As.
Browse to the location where you will store the file.
Enter a filename.
TIP
If you use File > Exit to close a Process
application (Process Administrator, Configuration Console, Designer, or Tracker),
the application will prompt you to save any unsaved changes before it closes.
However, if you click the Close button [X] in the upper right corner of the
window, one of the following will occur:
If the program is running as an application, it will prompt you to save
any changes.
If the program is running as an applet inside a browser window (the name
of the browser displays in the title bar), the program will close immediately
and any unsaved changes will be lost.