Enable/disable transition buttons?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2009 10:18 AM
I have a wf review task where if the document is accepted a further document has to be added to the bundle in order to proceed whereas if the document is rejected no further document exists. I can achieve this by including a further node for the reveiwer but that would involve the job being shut down and then opened again from the reviewer's work queue. It would be much cleaner if the accept button was not available unless the new document was added but the reject option was enabled from the start.
Does anyone have any ideas how this may be achieved or is it possible at all?
Thanks.
Does anyone have any ideas how this may be achieved or is it possible at all?
Thanks.
Labels:
- Labels:
-
Archive
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2009 02:40 PM
Hi, I wrote your question and tinking about the same issue. Did you solve the problem ? If you coud help me I would be happy, because I haven't found any answer yet!!
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2009 02:14 PM
Hi maas,
I was working on something along these lines not too long ago. It seems that if you do not name a transition in your task-node 'accept' then the accept button will not appear. This was useful to me as I could script ahead of time to check if the condition needed was fulfilled. If it was then the workflow would fork off to a task-node that included both 'accept' and 'reject'; if the condition was not fulfilled, then the fork would bring the user to a task-node that did not include the 'accept' transition.
Hope this helps.
I was working on something along these lines not too long ago. It seems that if you do not name a transition in your task-node 'accept' then the accept button will not appear. This was useful to me as I could script ahead of time to check if the condition needed was fulfilled. If it was then the workflow would fork off to a task-node that included both 'accept' and 'reject'; if the condition was not fulfilled, then the fork would bring the user to a task-node that did not include the 'accept' transition.
Hope this helps.