![]() ![]() |
|
Help for Process Engine Administration | |
Search | Index | |
![]() |
|
![]() |
![]() |
![]() |
Content Services library integration issues (FileNet Web Services Client or Open Client)Each time you change a workflow definition and check it into a Content Services (CS) library (FileNet Web Services Client and Open Client only), the workflow definition version is incremented. By default, the CS library keeps five document versions available online. Offline documents are not accessible to the Process Engine. If you attempt to launch a workflow that is offline, it will fail. There are two ways to work around this problem. Save workflows locally During workflow development, the workflow author can save the workflow to the local file system instead of to the CS library. This will eliminate workflow definitions that are not being used for current workflows from being stored unnecessarily in the CS library. Increase the CS library default setting You can increase the default value in the CS library to a number more consistent with your site's usage requirements. Increasing the number of versions kept online decreases the likelihood that a workflow definition will not be available when needed. The default value for the number of document versions available on-line is per library, not per document, so consider the ramifications for your entire CS library before changing the default. For further information about the document versions available setting, see the Content Services documentation.
|
![]() |
|
![]() |
|