public interface Workflow extends Remote, Serializable
WorkflowManager
. Calling a method that is defined
by an interface extending the Workflow
interface causes such a workflow step (procedure) to be executed.
Which workflow is active on a document depends amongst others on the type of document. Therefor the Workflow
interface itself defines no workflow actions, but any Workflow
instance should be cast to a document-specific
interface. The implementation of these document-specific workflows can be provided at run-time to the repository.
Therefor there is no standard set of workflows available. There are a number of commonly available workflows, but
these are not mandatory. See all known sub-interfaces of the Workflow
interface, or
org.hippoecm.repository.standardworkflow.FolderWorkflow for an example.
Implementors of this interface should never return subclasses of the Document
class in their interface. It
is allowed to return an instance of a subclass of a Document
, but the repository will force recreating the
object returned as a direct instance of an Document
.Modifier and Type | Method and Description |
---|---|
Map<String,Serializable> |
hints()
The hints method is not an actual workflow call, but a method by which information can be retrieved from the
workflow.
|
@WorkflowAction(loggable=false, mutates=false) Map<String,Serializable> hints() throws WorkflowException, RemoteException, javax.jcr.RepositoryException
Boolean
to indicate the enabled status of the method. Non-standard keys in this
map should be prefixed with the implementation package name using dot seperations.WorkflowException
- thrown in case the implementing workflow encounters an
error, this exception should normally never be thrown by
implementations for the hints method.RemoteException
- a connection error with the repositoryjavax.jcr.RepositoryException
- a generic error communicating with the repositoryCopyright © 2007–2017 Hippo B.V. (http://www.onehippo.com). All rights reserved.