where did you put your code (which event) and how is your step where your code is located defined? Note that reject returns a workflow to the most recent step Review/Edit, or Review/New.
I placed this code in entry event, in the first step of the workflow. on rejection, it is taking me to review/edit step. my problem is i am getting standard rejection mail notification even i am stopping it using <$wfSet("wfJumpEntryNotifyOff", "1")$>.
> I placed this code in entry event, in the first step of the workflow. on rejection, it is taking me to review/edit step.
Is the first step the same as the review/edit step? If not, you found the cause - your code is not executed.
I think, however, that your problem is different: the zeroth step cannot be customized so the author will receive the standard notification regardless what you did in the first step.
is there any way i can customize zeroth step ?? will adding one more step in the beginning help solving the issue ??
Setting the target step will take you to the step when document is rejected, but it is not stopping the system generated rejection mail.
will adding <$wfSetIsNotifyingUsers(0)$> solve my problem of stopping the standard/system generated notifications ???
I think not, unless you suppress all the notifications and in other steps you'll handle notifications yourself (I think there is a setting to do that somewhere in config.cfg).
Either way, it should be easy to verify.
My workflow has got 4 steps, where i am using reject code in the entry event of the first step. First step, checks whether document has all the required details or else it sends the document to edit/contribution mode. Users can reject only from 2nd, 3rd, 4th steps. Is the issue coming here ???
changing in config.cfg effects all he other workflows as-well. For approve, this works perfectly, i am using jump script for approve @ each step and suppressing the standard ones. it sends only the custom email notification. this is happening only for reject notification becasue i am using reject jump only in 1st step. will adding reject jump @ each step will the issue ???
I would not use workflows for that at all. If I got you, the control in the first step is machine-based, right? If so, you can perform the checks in a filter and right away display a message that document could not be checked in. I have implemented something similar, what rejected content if a user exceeded given quota.
If you can't verify the check in an automated manner you'll need to study if/what filters are available for sending notifications emails. The one that I could find was SmtpClient, which "processes all sent email messages, which includes workflow notifications and subscriptions." At the end of the day this might be the easiest and cleanest way...
I am checking if the document has got all the criteria or not in the first step and if it meets the criteria,it send to the 2nd step to start the approval process. if any one rejects in the 2nd,3rd,4th steps author is getting both standard and custom notifications in all the preceding steps. will adding rejection jump @ all the steps, solve the problem ???
Feel like we are starting to go in circles.
There is one thing you need to verify yourself: What happens, in a new workflow, if you
a) reject a document on the first step defined as review/edit or review/new
b) reject a document in any following (review!) step, but create an idocscript code in entry event that will take the rejected content and jump immediately to the zeroth step. In this case you can try setting of wfJumpEntryNotifyOff
The first step will be just pass-thru - you can create another which will forward it immediately to the second step, if the content arrives from the zeroth, so you mainly need the use case b). If you can find a combination, go for it, it not, you can't use workflows and need to go with filters.
I'm afraid I can't tell more.
" reject a document in any following (review!) step, but create an idocscript code in entry event that will take the rejected content and jump immediately to the zeroth step. In this case you can try setting of wfJumpEntryNotifyOff"
This works perfectly fine.
I tried the mentioned approach of creating a 2 step workflow which has the following steps :
- Created a criteria workflow .
- Added following steps : -Reject Notification step(Edit/reveiw Step)-- added the condition -if wfAction like reject --notify the author with the custom template else move to next step with following piece of code :
<$if wfAction like "REJECT"$>
-Approval step-(Edit/reveiw Step)-- in this reviewer is notified for the approval.
Now I'm stuck in --when the reviewer rejects the content both custom and OOTB mails are being sent though I have used <$wfSet("wfJumpEntryNotifyOff", "1")$> in each step.
Now I'm not able to figure out what exactly needs to be done to suppress the OOTB notification.