留言板
DL Documents Workflow
Hey,
in current LR revision, DLFileEntryWorkflowHandler isVisible(); returns false, so that it is not displayed in Workflow configuration (Control panel); Is it because it is in development ? If so, when is it ready ?
Also it is a little bit different from other assets, for instance after I just add a file in Document Library (DLAppLocalService), there is no pending Task for document reviewer...
Could please anybody bring some light into DL Document workflow in current LR revision ?
in current LR revision, DLFileEntryWorkflowHandler isVisible(); returns false, so that it is not displayed in Workflow configuration (Control panel); Is it because it is in development ? If so, when is it ready ?
Also it is a little bit different from other assets, for instance after I just add a file in Document Library (DLAppLocalService), there is no pending Task for document reviewer...
Could please anybody bring some light into DL Document workflow in current LR revision ?
If anybody was looking for the same, it moved right to the Document Library: Documents Home - Edit or Folder - Edit
Though there is one thing I don't really get :
A DL folder may contain files of basic or custom types.
WorkflowDefinitionLink makes association between [ Folder - WorkflowDefinition - Type ] where Type is either 0 or fileTypeId.
Now, when Type is fileTypeId - it means that within the folder, workflow is executed for files having particular fileTypeId only.
When Type is 0, then it means that no FileTypes were specified (when editing folder) and workflow should be executed for all files in that directory.
The association is clear in the later case, but I believe that in the former case, workflow can be executed only for ONE fileType in a folder. That's why there is a radio button for selecting default File Type in the FileType - Workflow matrix when editing folder. Only files their file type is selected are to be workflowed.
If anything from what I just said is not correct, please let me know.
A DL folder may contain files of basic or custom types.
WorkflowDefinitionLink makes association between [ Folder - WorkflowDefinition - Type ] where Type is either 0 or fileTypeId.
Now, when Type is fileTypeId - it means that within the folder, workflow is executed for files having particular fileTypeId only.
When Type is 0, then it means that no FileTypes were specified (when editing folder) and workflow should be executed for all files in that directory.
The association is clear in the later case, but I believe that in the former case, workflow can be executed only for ONE fileType in a folder. That's why there is a radio button for selecting default File Type in the FileType - Workflow matrix when editing folder. Only files their file type is selected are to be workflowed.
If anything from what I just said is not correct, please let me know.