Associates workflow definitions with entry definitions.
public void binder_setDefinitions( String accessToken, long binderId, String entryDefinitionIds, String  workflowDefinitionIds );
The binder_setDefinitions operation associates entries within the specified binder with workflow processes. Vibe associates identifiers in the first element of both arrays, the second element of both arrays, the third, and so on. The second element should contain pairs of entry and workflow, separated with a comma. For example, ""entry_def,wflow_def""""entry_def,wflow_def"] and so forth.
When an entry is associated with a workflow process, creation of an entry of that type automatically places the entry into the initial state of the workflow process. By default, workspaces do not contain entries that can be associated with workflow processes. However, users can alter definitions by using the designers in the UI so that a custom workspace can include one or more files.
NOTE:This operation is an overwrite operation, setting all workflow associations for the folder; you cannot use repeated calls to this operation to set associations incrementally. Set all of the workflow associations for the folder with one call.
Either the security token passed to your application by Vibe as part of implementing a remote application, or the null value.
The binder identifier for the folder or custom workspace within which you want entries associated with workflow processes.
An array of definition identfiers for each type of entry to which you want to associate a workflow process.
An array of workflow identifiers in the order in which you want them applied to the entry-definition identifiers in entryDefinitionIds.
Java objects in the Vibe sources (see Section 5.6.1, Working with Java Objects)