I understand the inheritance of the LazyApproval terms at site collection and site level that the terms come from the phrases in the farm (as outlined in this post ). In my farm phrases I have "approved" and at my site collection level I have "approved". If I respond to a lazy approval email with the term "approved" I get automated response saying "Your response was not able to be interpreted. Please try again with a clear indication of your chosen outcome."
If I "break" the inheritance by adding phrases at site collection level, these phrases should be taken into account when I reply to an email from a workflow. I have added "cassy" as a term but when I reply to lazy approval for a workflow on that site I get the same error as above. However, if I reply with "approve" it works fine.
This makes absolutely no sense to me - has anyone seen this before?
Solved! Go to Solution.
Yes I did rhia and we are still going through troubleshooting! They've sent me the document to check everything is set up ok but I am at the mercy of our farm administrators and this is not getting moved along as quickly as I would like - still as soon as I have some answers I will pop them on here x
Update to this - had a call with Nintex Support today and we have confirmed that "approve" and "reject" are working but any other lazy approval terms are not. Incredibly frustrating. They are investigating further.
Please keep me updated, as I have also just experienced this issue and need to resolve it. I have the same list of terms, and had the same issue - submitted "Approved", got the email telling me it was invalid.
Here was reply from support Rhia Wieclawek:
I have received a response from the Dev team and they have asked that I raise a defect request for this case. The reason is when the replied email contains more rows with 'Line break' before and after the LazyApproval phrase the LA fails. I'm afraid though we can't explain why 'approve' and 'reject' work.
Moving forward, when the defect is raised it will be discussed in a triage meeting later this week and it will be given a rating. Then according to this rating that is when it will be fixed and released, when it is released I will contact you and supply the release with the fix.
Unfortunately I will not be able to give a time limit of when the fix will be released.