I'm learning on the fly, so thanks for fielding this second of likely many how-to questions about the SDK. I'm honestly not sure that what I'm about to ask is supported today.
Here's the use case I'm considering: Custom Atomic Security on Document Lifecycle User Actions
- To display, a user action must meet at least one of the following criteria
- Only allow members of a document's role(s) to execute the action
- Only allow members of a group to execute the action (Note: the user/group doesn't need to be explicitly named in a role. For example: we may have a group called "Legal" who has a security profile that allows them to see all documents independent of the Sharing Settings.)
- Only allow members of a security profile to execute the action (Similar scenario to #2 but using a different way to identify an authorized user)
- If authorized, ask for the normal WF start step inputs and initiate a document workflow
Ideally, I'd simply be able to use the isExecutable method to run my validation logic, but the menu click (the execute method) would just fire up the workflow start dialog of an existing document workflow. That avoids me having to replicate a workflow start step. Is that possible? I don't think so.
If I can't initiate the existing workflow start step, I see that Document Actions support the following:
- user_input_object_type: If your action takes user input, you may want to identify the user input object type. If omitted, this action does not require a type for user input. Actions which require user input may not require a type.
- user_input_object: If your action takes user input, identify the user input object. If omitted, this action does not require user input.
Does this imply that I can create a user action on a document lifecycle state that pops up an object data entry dialog? And does the action fire upon the save event of that dialog? Or am I making up a scenario that's not supported.
Thanks again for the insight.