Skip to Content
avatar image
Former Member

Workflow Approval mail reminders

Hi All ,

I would like to send follow up mails for the document approvals if they are not approved by specified duration or workflow end date. Is there any standard configuration which would be helpful to me , I have checked good in system and i did not find any information on same.

I am thinking to go via custom way , can any one suggest the way i can go  or tell me how to proceed if they have worked on a similar requirement .

Right now i am thinking to write a mail script in workflow itself but then i would be needing to get details if workflow is pending or not etc.. so I shall be doing it in Pre script?...



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    May 29, 2013 at 12:46 PM

    Hi Uday,

    There isn't any standard in the tool send reminder notifications for workflow pending approvals.

    I had a similar requirement with a customer and we implemented a custom solution. The customer required notification to the approvers if the approval has been pending for X # of days.

    The solution we implemented is to develop a custom jar file that contained code check the status of all the workflows pending approvals and generate email notification. The custom jar file needs to be deployed on Sourcing application server. For the custom jar to be executed, we had Set up a Schedule Tasks which would check in the background for the pending approval workflow and send out email notifications.

    I hope this helps. Let me know, if you need any additional information.



    Add comment
    10|10000 characters needed characters exceeded

    • Hi Uday,

      Once you have the custom jar file ready, the deployment of the file is a Basis activity. You need to provide the file to your Basis contact and they will have to run the setup steps on the application server for deploying the file which gets created in the custom jar folder.

      And yes, the sourcing services have to re-started after the custom jar deployment.