web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Workflow wait condition scenario

(0) ShareShare
ReportReport
Posted on by

Hi, we have a custom entity which is linked through subgrid in Account entity. There are two date fields X and Y in my custom entity.

  1. So when the user enters date in X now that my workflow should trigger after 5 minutes and should check for date in Y.If there is a date in Y field then workflow should stop.
  2. If there is no date, then it should send an email and after 10 min it should check for date, if not it shouls send an email. In the similar way it should check for 15 min and 20 min. (If there is date workflow should stop, This is some what like generating a remainder until we have a date in Y field)

Any help with screen shots and steps is highly appreciated.

Thanks

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Nadeeja Bomiriya Profile Picture
    6,804 on at

    Hi Sam,

    Here are the steps and some screenshots.

    1. Create a workflow that triggers when Field X is updated.

    2. First step, add a Timeout step to wait for 5 minutes.  (Timeout is a substep in Wait Condition. Therefore, add a wait condition and then configure the steps as below. Below example was for the second wait condition. Hence 10 minutes.  Make sure, in the Form Assistant, you select the Minutes > After > Look for (Process) > Execution Time in order.)  This step will wait for 5 minutes from the from the current time.

    Process-Timeout-Workflow.png

    3. Next add a condition to check the Field Y (in my example Anniversary) and Stop Workflow if condition is met.

    Process-Timeout-Workflow.png

    Ideally, you should create a new DateTime field in your custom entity and update the value after every Timeout and use that field to configure the timeout from second Timeout step.  That way, you can perform this more accurately. I haven't tested this so may have errors, but you should get the idea.

  • Suggested answer
    Nithya Gopinath Profile Picture
    17,078 on at
  • Suggested answer
    Vipin J Profile Picture
    1,603 on at

    Hi,

    Just be careful when using a wait condition

    I went into a situation where I was required to make changes to business logic after it went Live in Production.

    There could be Old waiting workflow instances that needs to be well taken care off by first cancelling and manually running new workflow logic.  

    I have written a .Net piece of code for doing this - refer here

    [View:https://vjcity.blogspot.com/2019/09/cautiously-changing-logic-of-existing.html:750:50]

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans