The Declare workflow action declares a file or repository asset placeholder in a workflow. You can declare an asset placeholder anywhere within a workflow; its placement affects the project workflow in two ways:
After the project advances beyond the declaration, its Assets tab displays a link to unsupplied assets with this text:
Required assets not yet supplied:nwhere
nis the number of outstanding assets to be included in this project. If an asset placeholder is not required, that number is always 0.The declaration makes the asset placeholder available to later tasks, such as Author, for inclusion as a subject.
You define a Declare element with the following settings:
Asset placeholder name
Nucleus path of the asset’s repository or VFS component
Item type or file type
Required (optional)
Note: If you omit the Required setting, the project can be completed without inclusion of that asset.
For example, this Declare element declares Press Release as a required placeholder for a repository asset:
Declare repository asset Press Release from repository
/my/app/PressReleaseRepository and item type pressRelease as required
The following Declare element defines Target Users as a placeholder for a file asset:
Declare file asset Target Users from VFS
/atg/epub/file/ConfigFileSystem and file type profileGroup as required
Note: The atg.vfs package contains a VirtualFileDescriptor class that supports the notion of a file type within a virtual file system. The class has one method that returns the type name. For the RepositoryVirtualFileSystem, the name returned is the virtual file’s underlying item descriptor, such as profileGroup or scenario. For any other type of VFS, an empty string is returned.
