We take care of few customer. All of them have Antivirus. Those anti-virus
expire on a yearly basis.

I create a new attribute call : AVExpirationDate.

I want to have a workflow that check that and send an email to me and the
customer 30 days before the expiration.

Few month agon I post here on that, I was testing the crm on a lab, somebody
told me how to figure the workflow. Now we run in a production CRM and I
delete the temps install by mistake and cannot remember the way to do it.

Can someone help me on recreating this.

RE: Work to check for time remaining by Niths

Niths
Thu Jul 24 13:06:03 CDT 2008

Hi David,

You can do this using the Wait condition in Workflows. Create a Workflow to
run when the record is created. Then click 'Add Step' and select 'Wait
condition'. Click to configure and select 'Workflow' under local values.
Select the timeout property and specify the dynamic values in the Form
Assistant (30 days before AVExpirationDate in this case).

HTH,
Niths

"David" wrote:

> We take care of few customer. All of them have Antivirus. Those anti-virus
> expire on a yearly basis.
>
> I create a new attribute call : AVExpirationDate.
>
> I want to have a workflow that check that and send an email to me and the
> customer 30 days before the expiration.
>
> Few month agon I post here on that, I was testing the crm on a lab, somebody
> told me how to figure the workflow. Now we run in a production CRM and I
> delete the temps install by mistake and cannot remember the way to do it.
>
> Can someone help me on recreating this.
>

RE: Work to check for time remaining by David

David
Thu Jul 24 19:11:03 CDT 2008

This is exactly what I did last time

Last time they told me that doing it this way was not very good becaus it
consume system ressource.

They told me that I should do it using windows scheduled task. Can we use
windows to schedule CRM task?

Let me know

"Niths" wrote:

> Hi David,
>
> You can do this using the Wait condition in Workflows. Create a Workflow to
> run when the record is created. Then click 'Add Step' and select 'Wait
> condition'. Click to configure and select 'Workflow' under local values.
> Select the timeout property and specify the dynamic values in the Form
> Assistant (30 days before AVExpirationDate in this case).
>
> HTH,
> Niths
>
> "David" wrote:
>
> > We take care of few customer. All of them have Antivirus. Those anti-virus
> > expire on a yearly basis.
> >
> > I create a new attribute call : AVExpirationDate.
> >
> > I want to have a workflow that check that and send an email to me and the
> > customer 30 days before the expiration.
> >
> > Few month agon I post here on that, I was testing the crm on a lab, somebody
> > told me how to figure the workflow. Now we run in a production CRM and I
> > delete the temps install by mistake and cannot remember the way to do it.
> >
> > Can someone help me on recreating this.
> >

RE: Work to check for time remaining by Niths

Niths
Fri Jul 25 04:08:00 CDT 2008

David,

The wait condition will not consume system resources. It runs only when the
specified condition is satisfied.

HTH,
Niths

"David" wrote:

> This is exactly what I did last time
>
> Last time they told me that doing it this way was not very good becaus it
> consume system ressource.
>
> They told me that I should do it using windows scheduled task. Can we use
> windows to schedule CRM task?
>
> Let me know
>
> "Niths" wrote:
>
> > Hi David,
> >
> > You can do this using the Wait condition in Workflows. Create a Workflow to
> > run when the record is created. Then click 'Add Step' and select 'Wait
> > condition'. Click to configure and select 'Workflow' under local values.
> > Select the timeout property and specify the dynamic values in the Form
> > Assistant (30 days before AVExpirationDate in this case).
> >
> > HTH,
> > Niths
> >
> > "David" wrote:
> >
> > > We take care of few customer. All of them have Antivirus. Those anti-virus
> > > expire on a yearly basis.
> > >
> > > I create a new attribute call : AVExpirationDate.
> > >
> > > I want to have a workflow that check that and send an email to me and the
> > > customer 30 days before the expiration.
> > >
> > > Few month agon I post here on that, I was testing the crm on a lab, somebody
> > > told me how to figure the workflow. Now we run in a production CRM and I
> > > delete the temps install by mistake and cannot remember the way to do it.
> > >
> > > Can someone help me on recreating this.
> > >

RE: Work to check for time remaining by David

David
Fri Jul 25 06:37:01 CDT 2008

So even if I have 50 of those workflow in stand bye it doesnt matter right?

What happen if the system crash?

"Niths" wrote:

> David,
>
> The wait condition will not consume system resources. It runs only when the
> specified condition is satisfied.
>
> HTH,
> Niths
>
> "David" wrote:
>
> > This is exactly what I did last time
> >
> > Last time they told me that doing it this way was not very good becaus it
> > consume system ressource.
> >
> > They told me that I should do it using windows scheduled task. Can we use
> > windows to schedule CRM task?
> >
> > Let me know
> >
> > "Niths" wrote:
> >
> > > Hi David,
> > >
> > > You can do this using the Wait condition in Workflows. Create a Workflow to
> > > run when the record is created. Then click 'Add Step' and select 'Wait
> > > condition'. Click to configure and select 'Workflow' under local values.
> > > Select the timeout property and specify the dynamic values in the Form
> > > Assistant (30 days before AVExpirationDate in this case).
> > >
> > > HTH,
> > > Niths
> > >
> > > "David" wrote:
> > >
> > > > We take care of few customer. All of them have Antivirus. Those anti-virus
> > > > expire on a yearly basis.
> > > >
> > > > I create a new attribute call : AVExpirationDate.
> > > >
> > > > I want to have a workflow that check that and send an email to me and the
> > > > customer 30 days before the expiration.
> > > >
> > > > Few month agon I post here on that, I was testing the crm on a lab, somebody
> > > > told me how to figure the workflow. Now we run in a production CRM and I
> > > > delete the temps install by mistake and cannot remember the way to do it.
> > > >
> > > > Can someone help me on recreating this.
> > > >

RE: Work to check for time remaining by Niths

Niths
Sun Jul 27 05:53:00 CDT 2008

I've checked with another MVP who said this was the case in 3.0 but works
much better in 4.0 thanks to the asynchronous service. Refer to this link for
details: http://technet.microsoft.com/en-us/library/cc151103.aspx

HTH,
Niths

"David" wrote:

> So even if I have 50 of those workflow in stand bye it doesnt matter right?
>
> What happen if the system crash?
>
> "Niths" wrote:
>
> > David,
> >
> > The wait condition will not consume system resources. It runs only when the
> > specified condition is satisfied.
> >
> > HTH,
> > Niths
> >
> > "David" wrote:
> >
> > > This is exactly what I did last time
> > >
> > > Last time they told me that doing it this way was not very good becaus it
> > > consume system ressource.
> > >
> > > They told me that I should do it using windows scheduled task. Can we use
> > > windows to schedule CRM task?
> > >
> > > Let me know
> > >
> > > "Niths" wrote:
> > >
> > > > Hi David,
> > > >
> > > > You can do this using the Wait condition in Workflows. Create a Workflow to
> > > > run when the record is created. Then click 'Add Step' and select 'Wait
> > > > condition'. Click to configure and select 'Workflow' under local values.
> > > > Select the timeout property and specify the dynamic values in the Form
> > > > Assistant (30 days before AVExpirationDate in this case).
> > > >
> > > > HTH,
> > > > Niths
> > > >
> > > > "David" wrote:
> > > >
> > > > > We take care of few customer. All of them have Antivirus. Those anti-virus
> > > > > expire on a yearly basis.
> > > > >
> > > > > I create a new attribute call : AVExpirationDate.
> > > > >
> > > > > I want to have a workflow that check that and send an email to me and the
> > > > > customer 30 days before the expiration.
> > > > >
> > > > > Few month agon I post here on that, I was testing the crm on a lab, somebody
> > > > > told me how to figure the workflow. Now we run in a production CRM and I
> > > > > delete the temps install by mistake and cannot remember the way to do it.
> > > > >
> > > > > Can someone help me on recreating this.
> > > > >