Kofax Ascen 7.0 Release Script for Oracle Content Services 10g - Manual (Page 32)

Ascent® 7.0 Release Script for Oracle Content Services 10g Release Notes
28 Kofax, Inc.
Workflow Parameter Values May be Passed to an Unassigned Workflow
If the name of a subfolder defined in release setup is the same name as an existing Oracle Content
Services folder, some workflow parameter values may be passed to the subfolder at release even
when it has a different assigned workflow than the release root location. This is because release
setup uses the parameters of the release root location. (SPR 00024080)
Example
Setup in Oracle Content Services of a parent and child structure:
Library A: Parallel Vote workflow
Folder B: Serial Approval workflow
Release script release setup:
Library A is selected as the release root location
A subfolder definition is added that will select Folder B
On the Workflow Settings tab, parameters for the Parallel Vote workflow will display.
Release will succeed and the workflow parameter values specified for the Parallel Vote
workflow will be passed to Folder B Serial Approval workflow if either of the following is
true:
„
No links are made (i.e., default values will be used).
„
The only values linked are to one or more of the parameters that are common to both
workflow types—for example, Justification and Request Timeout.
Release will fail if values are linked for one or more of the parameters that are not common to
both workflows—for example, “Number of approvals required to approve.”
Workaround: When adding a subfolder definition, make sure that any existing subfolders that
may be selected by the definition have an Upload Document workflow with parameters that
match any parameters linked in release setup.
Restricted Category Attributes Are Passed
If the name of a subfolder defined in release setup is the same name as an existing Oracle Content
Services folder, the release root location’s category and attributes may be passed to the subfolder
at release regardless of its category restrictions. This is because release setup uses the allowed
categories of the release root location. (SPR 00024068)
Example
Setup in Oracle Content Services of a parent and child structure:
Library 1: Allows only the Invoice category
Folder 1: Allows only the Expense category
Release script release setup:
Library 1 is selected as the release root location
Folder 1 is added as a new subfolder definition
On the Document Settings tab, attributes for the Invoice category will display.
Release will succeed and the Invoice category and attributes will be passed to the document in
Folder 1.