Time based workflow

There is a field "Delivery date" in oppty & we want to send a reminder mail 10 days before delivery date once that oppty is closed/won.
So, how can i write that expression?

Thanks but i know that i'll have to write time based workflow,however there is provision of wait for +10 days after some event happens & not -10 days.
Ketki

Similar Messages

  • Time Based Workflow - how to make it work?

    Hello,
    Has anyone successfully built a Time Based Workflow? Could you share your examples?
    For me it does not work properly.
    I have tried to set up 2 workflows: on Opportunity Close Date and Account Contract Expiration Date.
    - Account Contract Expiration Date: I want an Account Owner to get an email notification exactly 6 months before the contract with his client expires. However - the email is triggered each time the record is modified - so I have seen in the workflow monitor that users on the date of contract expiration - 180 days will receive as many emails as many times they modified the record! Is there a way to avoid this situation?
    - Opportunity Close Date - I want to send an email to Opportunity Owner's Manager - 10 days after the opportunity was closed. However - there will be the same issue as above + the wait action is not working with a PRE function.
    Please let me know what you think and if you have already built a Time Based Workflow that works correctly.
    Edited by: MagdaR on May 18, 2010 1:57 AM

    Let's start with the workflow for Opty Close Date.
    There are a lot of ways to do this, so you'll need to evaluate which way is best for your case, but the basics are to check to ensure that the opty is closed for the first time, then set the flag. In order to accomodate for the opty being closed when it is created, you will have to consider a post default for the flag in addition to the workflow.
    In this case, you could create a workflow on Opty using the before modified record saved trigger event. In the Rule Condition, have the workflow check for a closed opty and if the status changed to closed during this modification. There are a number of options to validate this, including sales stage = Closed/Won or Lost, Closed Date is populated for the first time, Status is closed. In any case, just validate that the opty was closed for the first time using the PRE Function (i.e., PRE(Closed Date) is null and PRE(Closed Date)<>Closed Date). When your condition is met, set a flag that will trigger the event. You could also add a date that the wf conditions were met the first time, to ensure that you track when the rule was originally triggered.
    The next step is to have a workflow that unsets the flag if the conditions are not met. Set the order on this one to follow the rule above.
    The last rule is the wait/email rule and it uses the when modified record saved event. This rule triggers on the flag being checked, then waits to send the email.
    Test this and validate that it will work for your purposes. Based on this workflow, you should be able to create the other one, and I can help if you have any issues.
    Good Luck,
    Thom

  • Time Based workflow not working

    Hi,
    I am facing issue in time based workflow. I designed a worflow with two actions. Wait action is the first action and second action is send email. For send email the from address is current user and TO is owner of the record. One thing I noticed is that its working fine when "I" triggered the workflow and assign owner as "me". Its not trigerring the mail when owner is somebody else. I can see the instance with the following error message in the workflow monitor. "The buscomp Service Request is no longer valid for workflow name ********. The workflow instance ******* has terminated."
    Edited by: user11100286 on Oct 1, 2010 4:33 PM

    Hi,
    I am facing issue in time based workflow. I designed a worflow with two actions. Wait action is the first action and second action is send email. For send email the from address is current user and TO is owner of the record. One thing I noticed is that its working fine when "I" triggered the workflow and assign owner as "me". Its not trigerring the mail when owner is somebody else. I can see the instance with the following error message in the workflow monitor. "The buscomp Service Request is no longer valid for workflow name ********. The workflow instance ******* has terminated."
    Edited by: user11100286 on Oct 1, 2010 4:33 PM

  • Time based workflow over long Period

    Hello,
    I'm looking for experiences on Time based workflow over long Period.(Over 1 or 2 years).
    Does any limitation exist ?
    Thanks for your help.

    I dont think there will be anyone who can really verify this information over two years im not sure that they have been in use this long

  • Time Based Workflow - update existing activities?

    Hi, I've added a checkbox field to my activities template, and wondered if it is possible to update this field on existing >124K activity records using a time based workflow. <br><br> Has anyone come across this requirement, or have any thoughts on how to solve the issue? <br><br> Thanking you in advance for assistance.
    Edited by: Sherry10602332 on Oct 11, 2010 12:07 PM

    Hello SKJ
    Your requirement is to send an email notification to an owner if the Opportunity remains with sales Stage = "Inquiry" for more than 90 days.
    New Record Saved.
    This means even the opportunity can be modified but the sales stage should not change. For e.g. when i create a new record, I can have the sales stage as "Inquiry" and save. At a later date I can modify the description of the opportunity (this would change the modified date), but the sales stage remains at Inquiry. Thus the notification should go 90 days after the sales stage has been set and not since last modified date. Keeping this in mind the condition the rule condition "Rule Condition : Sales stage = "Inquiry" and modified date = Created date" needs to be modified as Sales stage = "Inquiry".
    Coming to Modified Condition:
    Trigger Event - When Modified Record Saved
    Rule Condition : (PRE('<SalesStage>')<>[<SalesStage>] AND [<SalesStage>]="Inquiry") OR ([<SalesStage>]="Inquiry")
    Wait 90 Days
    Revaluate Conditon = 'Y'
    Action Send Email Notification
    Explanation
    When you set the sales Stage as "Inquiry", the condition (PRE('<SalesStage>')<>[<SalesStage>] AND [<SalesStage>]="Inquiry") would be satissfied and then the workflow would trigger. After 90 days if the sales stage is still in "Inquiry", the second part of the condition "[<SalesStage>]="Inquiry" would be satisfied and the email notification would be sent. If the sales stage has been changed to other sales stage, then the condition would fail and the notification would not be sent.
    Regards,
    Paul Swarnapandian

  • Time Based Workflow in R16

    Can someone confirm that Time Based Workflows will be in R16? I have heard talk of this but not able to find confirmed documentation that it will be included.
    Thanks

    Time based workflows aren't in R16, we'll check again when R17 come out.
    cheers
    Alex

  • Time-Based Workflow Using Together Workflow Editor

    hello experts,
    Is there any script or functionality in Together Workflow Editor to create Time-Based workflow.In case the approval status is pending fo a particular duration of time  it should go for approval to another user(approver).
    Thanks and Regard,
    Piyush S

    I don't think there is a standard functionality for that. Isn't it maybe possible to work with a Timer object?

  • Time based workflow:wait action not working

    I need to build a workflow for sending mail to manager if for an opportunity sales stage "requirement" remains for more than 30 days,I have given the workflow condition as:
    ([<SalesStage>] = "01 - Requirements")
    & then 2 actions 1st "Wait" & then "Send mail" somehow its not working.Please guide where i am getting wrong..

    Let me understand your business case: You need to send ONE email to the manager of the opportunity owner, if the Sales Stage = '01 - Requirements' for more that 30 days.
    You need two workflows and a unused/custom field (a boolean field is preferred). Both workflows are similar. The first workflow is based on the event - When new record saved. This workflow will be invoked as soon as a new opportunity is created. The second workflow is invoked whenever the opportunity is modified using the event - When modified record saved. Any user who has edit rights to the opportunity could modify the opportunity but not change the sales stage. This results in an unpleasant situation where the manager could be flooded with emails. That's where we use the boolean field to protect against multiple updates and ensure a single email is sent after 30 days if the sales stage is still '01 - Requirements'
    Workflow 1
    Record Type: Opportunity
    Event: When new record saved
    Condition:[<SalesStageId>] = "12ASA-XCD34" AND ([<IndexedBoolean0>] IS NULL OR [<IndexedBoolean0>] = "N")
    Note:
    1. IndexedBoolean0 is the field named Indexed Checkbox in the list of fields
    2. I have used the sales stage id. You have to find out the sales stage id for '01 - Requirements' and use it here.
    Workflow 1 - Actions (remember to activate all actions and workflows)
    1. Action = Wait
    Period= 30 days
    Reevaluate Rule Conditions After Wait = Y
    2. Action = Field Update After Wait
    Field Name = Indexed Checkbox
    Value = "Y"
    Overwrite Existing Values = Y
    3. Action = Email
    From > Specific Email Address> "[email protected]"
    To > Relative User On Record > Opportunity Owner's Manager
    Repeat this workflow configuration for Workflow 2, where the only difference is the event which should be When modified record saved
    Exposing the Indexed Checkbox on the opportunity detail page layout for all users is optional (not recommended). It might be a good idea to expose this checkbox on the opportunity detail page for the administrator role only... so that he/she can take corrective action if an email is not sent after 30 days.

  • Problem in Time based workflow

    I have written a workflow for mail triggering if a Sustomer complaint remain open for more than a week
    Workflow Condition:
    Workflow Rule Condition LookupValue("SR_STATUS", "Open" )
    Record Type Complaint
    Active Trigger Event When new record saved
    But mail is triggering even when Complaint status is "In progress","Open-Escalated"
    Please suggest the modification needs to be done in Workflow

    Hi there,
    Please check the workflow condition syntax or if you can share the same here, that would help to understand the issue better.
    Rgds,
    Mayank

  • How to exclude weekends in Time-based workflows?

    The escalation process need to exlude the weekends in computing the age of a lead record.
    Can anyone has a solution/expression to use to exclude the weekends?
    Appreciate anyone's feedback. Thansk!
    Mark

    Hi Harrie:
    Not sure I understand what you did. Suppose, for example, that I am setting the Wait duration to P5D. But I want to wait 5 business days instead of 5 calendar days. Do you first calculate what the end-time would be and then set the Wait expiration instead of the duration? In other words, waiting UNTIL a particular time, instead of waiting FOR a specified duration? Is this how you are doing it?
    Tks.

  • Send Email Notification - Time Based Workflow

    Hi,
    I have a requirement similar to the ones posted on this thread Re: Send notification on pre-defined date
    but have couple of questions on the logic. Can anyone please suggest a solution for this requirement
    The requirement is to send an email notification to an owner if the Opportunity remains with sales Stage = "Inquiry" for more than 90 days.
    Here's what I tried
    Work Flow Name - Opp Closure - New
    Trigger Event - When New Record Saved
    Rule Condition : Sales stage = "Inquiry" and modified date = Created date
    Action
    Wait -
    Period - 90 days
    Send Email
    Wait 7 days
    Updates Slaes Stage from " Inquiry" to "Closed/Lost"
    The above workflow will take care of New opportunties that are created and never modified
    I am having issues figuring out the logic for modified record
    Work flow Name - Opp Closure - Mod1
    Trigger Event - When Modified Record Saved
    Rule condition : sales Stage = "Inquiry" and <IndexedBoolean> IS NULL or <IndexedBoolean> = "N"
    Action
    Wait - 90 days
    Workflow Name - Opp Closure - Mod2
    Trigger Event - When Modified Record Saved
    Rule Condition : Sales stage = "Inquiry" and <IndexedBoolean> IS NULL or <IndexedBoolean> = "N" and (today()-<LastUpdate>) > 89
    Action
    Wait - 0 days
    Send Email
    Wait 7 days
    Updates Slaes Stage from " Inquiry" to "Closed/Lost"
    Update IndexedBoolean = 'Y'
    But here I am confused about a scenario where after waiting for 90 days when it exceutes Opp Closure - Mod2 and if its been 20 days since the record was last modified, the condition fails and actions do not get executed which is fine but what if the record is never modified after that period and remains in Inquiry status , how will I capture that scenario and execute the workflow actions. Please advise
    Regards,
    SKJ

    Hello SKJ
    Your requirement is to send an email notification to an owner if the Opportunity remains with sales Stage = "Inquiry" for more than 90 days.
    New Record Saved.
    This means even the opportunity can be modified but the sales stage should not change. For e.g. when i create a new record, I can have the sales stage as "Inquiry" and save. At a later date I can modify the description of the opportunity (this would change the modified date), but the sales stage remains at Inquiry. Thus the notification should go 90 days after the sales stage has been set and not since last modified date. Keeping this in mind the condition the rule condition "Rule Condition : Sales stage = "Inquiry" and modified date = Created date" needs to be modified as Sales stage = "Inquiry".
    Coming to Modified Condition:
    Trigger Event - When Modified Record Saved
    Rule Condition : (PRE('<SalesStage>')<>[<SalesStage>] AND [<SalesStage>]="Inquiry") OR ([<SalesStage>]="Inquiry")
    Wait 90 Days
    Revaluate Conditon = 'Y'
    Action Send Email Notification
    Explanation
    When you set the sales Stage as "Inquiry", the condition (PRE('<SalesStage>')<>[<SalesStage>] AND [<SalesStage>]="Inquiry") would be satissfied and then the workflow would trigger. After 90 days if the sales stage is still in "Inquiry", the second part of the condition "[<SalesStage>]="Inquiry" would be satisfied and the email notification would be sent. If the sales stage has been changed to other sales stage, then the condition would fail and the notification would not be sent.
    Regards,
    Paul Swarnapandian

  • What is the minimum delay on Time based workflows?

    Hi,
    I would like to know if there is a way to define a Wait action between 0 and 1 minute. My need is to define a wait of 10secondes. Is it possible using function or other ways?
    Thanks a lot
    Regards

    Thanks for you very quick reply. Here is my full problem. I want to get a £10 Everything Pack including new SIM card (although another page seems to say £12.99 or something similar) . I am in Australia about to walk for three weeks in the UK. I arrive in Bristol on Saturday afternoon and go straight to our B&B in Chepstow. With a quick internet search I can find no EE dealer in Chepstow. Through your website I was hoping to order an EE SIM and have it delivered to the B&B for me to collect by 7th August. However my identification is needed. Can I email my photocopied ID (passport or driver’s licence) to EE and have someone sign for the SIM at the B&B? Also, can I start an account by phone as I only have an Australian credit card? I do not anticipate needing to top up the account.
    I can find no email contact on your website for such direct enquiries.
    Alternatively, can I get an EE card somewhere in Bristol on a Saturday afternoon? If so, where?

  • Sales orders in TDMS company/time based reduction  are outside the scope

    Guys,
    I have had some issues with TDMS wheras it didn't handle company codes without plants very well. That was fixed by SAP. But I have another problem now. If I do a company code and time based reduction, It doesn't seem to affect my sales orders in VBAK/VBUK as I would have expected. I was hoping it would only copy sales orders across that have a plant which is assigned to a company code that was specified in the company code based reduction scenario. That doesn't seem to be the case.
    VBAK is now about one third of the size of the original table (number of records). But I see no logic behind the reduction. I can clearly see plenty of sales documents that have a time stamp way back from what I specified in my copy procedure and I can see others that have plant entries that should have been excluded from the copy as they do belong to different company codes than the ones I specified.
    I was under the impression that TDMS would sort out the correct sales orders for me but somehow that doesn't seem to be happening. I have to investigate further as to what exactly it did bring across but just by looking at what's in the target system I can see plenty of "wrong" entries in there either with a date outside the scope or with a plant outside the scope.
    I can also see that at least the first 10'000 entries in VBAK in the target system have a valid from and to date of 00.00.0000 which could explain why the time based reduction didn't work?
    Did you have similar experiences with your copies? Do I have to do a more detailed reduction such as specifying tables/fields and values?
    Thanks for any suggestions
    Stefan
    Edited by: Stefan Sinzig on Oct 3, 2011 4:57 AM

    The reduction itself is not based on the date when the order was created but the logic enhances it to invoices and offers, basically the complete update process.
    If you see data that definitely shouldn't be there I'd open an OSS call and let the support check what's wrong.
    Markus

  • Calculation of SLA times based on Service Organization

    Is it possible to calculate the SLA times based only on Service org?
    a) Using Service contracts i.e create SC with only org and assign the Service & Response profiles.
    Else as mentioned below.
    Please give your more thoughts.
    I maintain the Service & response profiles at "Maintain Availability and Response Times" .
    Can I access these values directly in the BADI ?
    My scenario is
    a) An agent belongs to a service org.
    b) I define these Profiles seperately for each Org (Org1 Org2 etc) at the above tcode.This manual entry.I know we dont have org to profiles mapping in the above tcode.I just painly maintain.
    c) In the BADI i check the org entered in the complaint.
    d) for Ex if the Org1 is entered I want to access the profiles for Org1.If else ladder.
    e) then use these profiles to calculate the SLA times.
    f) then save the document.
    g) Also trigger an e-mail saying the above time lines.
    Is the above flow possible??
    Let me know if you want me to post this onto another thread.
    Thanks
    amol

    Shalini,
    I will be just maintaining the service and response profiles in the "Maintain Availa..." tcode.
    There wont be exact mapping stored in any table.
    My logic would be ,i dunno whether this right or wrong..
    1) Once i get the Org ,I would compare like ths
    if( orgdata = org1)
    then service profile 1 etc.
    2) then apply the profiles to the cal of SLA times.
    I think we can achieve what you said using CRM_ORDERADM_I_BADI
    Or we need to use the BADI's specifically mentioned for serv contract det and calculation of SLA.
    As you know in SAP for SLA times we need to have the service contract for a) customer b) org  and many other parameters.then to this SC we need to associate the service and response profiles.When the SC is determined in a complaint ,the serv and resp profiles will be used to get the SLA times.
    But my requirement is to have determine the SLA times based on the service organisations.Not based on the customer and any other parameters.
    For ex : If my serv org is in India the times would be diff ..if my serv org is in US the times would be diff.
    So let me know what approach would be best ?
    Use BADI's as above or does this approach of having define different Service contracts (without having Partner functions customer etc) for diff orgs?
    Thanks
    Amol

  • Problem in Time Based Publishing Content

    Hi every1,
      Im working with Time based publishing.
    Using xml form builder i created 3 contents means 3 xmls.
    Then i created one iView for reading the contents (KM Navigation iView) and i setup the properties like
    layout set, layout set mode, root folder of contents.
    After creation of iView i checked in the preview all 3 contents visible in my iView.
      Now i want to show time based content in that iView.
    Contents displayed as per time based
    for that i enabled time based publishing and life time of particular content(xml)by using the given way
    Time dependant publishing in Km. I clicked on the right hand side of the name of my folder-> go to details -> Settings -> Lifetime. there you have to enable the time dependant publishing. Then i opened the folder and click on the rt hand side of the document-> properties -> lifetime, here give the time span of the document.
    After life time setup , again i seen in the iView for reading the contents (previous created) in the preview
    again all 3 contents displayed including life time expired content also.
       Please give me solution for this, or any more configurations required.
    Note :
    I required to display the contents in between time applicable only ( from time and until time).
    Thanks in advaince
    Vasu

    I have waited more than 3 hours for settings to apply.
    But i couldn't find any changes.
    any other solution?
    Thanks
    Vasu

Maybe you are looking for