**

Is anyone using a start and end date and push field workflow that creates
new tickets between the start and end date entered by the agent ? If so
how did you accomplish this using a date range without a date field for
each specific date ? Thanks in advance.

--------------------------------------------
This e-mail and any files transmitted with it are the property of
Regions Financial and/or its affiliates, are confidential, and are
intended solely for the use of the individual or entity to whom
this e-mail is addressed. If you are not one of the named
recipient(s) or otherwise have reason to believe that you have
received this message in error, please delete this message
immediately from your computer. Any other use, retention,
dissemination, forwarding, printing, or copying of this e-mail
is strictly prohibited.

**

You will need fields for the dates to be in. Make the agent enter a
start and end date through a dialog and it can commit to the current
ticket window, then you will have to dates to go in between. Or it can
push and create from the dialog, on close or a button. If the dates are
in the future, you will need them to be stored on the ticket and have an
escalation to do the push fields. Either way, the dates need to be solid
in a field for qualification if your doing a push fields on an
escalation. If you do the push fields off a dialog form the dates don't
need to be stored. I don't have enough info from you to elaborate
anymore, but hopefully this will give you insight.

>>> Rick.Snow@REGIONS.COM 07/09/02 08:02AM >>>
**

Is anyone using a start and end date and push field workflow that
creates
new tickets between the start and end date entered by the agent ? If
so
how did you accomplish this using a date range without a date field
for
each specific date ? Thanks in advance.

--------------------------------------------
This e-mail and any files transmitted with it are the property of
Regions Financial and/or its affiliates, are confidential, and are
intended solely for the use of the individual or entity to whom
this e-mail is addressed. If you are not one of the named
recipient(s) or otherwise have reason to believe that you have
received this message in error, please delete this message
immediately from your computer. Any other use, retention,
dissemination, forwarding, printing, or copying of this e-mail
is strictly prohibited.


To UNSUBSCRIBE, email the message "unsubscribe arslist" to:
listserv@listserv.vistait.com
You may also control your subscription options, including UNSUBSCRIBE,
at www.ARSLIST.org

**

To explain this more clearly let me give an example. From the users view,
I want to enter a start date of 07/01/02 and the end date of 08/01/02. I
am completing a ticket for a server outage problem. When I click on save,
31 tickets should be created identically with different dates, for 07/01/02
- 08/01/02. From the admin standpoint I would like to accomplish this
with the least amount of workflow, and least amount of date fields on a
form. It would not always be a period of thirty days though, in some cases
it may be more but for the most part less. I understand that if I put 50
date fields on a form and use an active link to say set field ('Date Field
1' = $Start Date$ + 1) and so on for the fifty date fields until Date Field
X > 'End Date' and then have 50 push field actions to create a ticket for
each date field as long as they are not greater than the end date. This
seems excessive and I am hoping to find an easier way to do this.



Ron Pierce
M> cc:
Sent by: "Action Subject: Re: Multiple Dates
Request System
discussion
list(ARSList)"
ISTAIT.COM>


07/09/2002 08:19 AM
Please respond to
"Action Request
System discussion
list(ARSList)"






**

You will need fields for the dates to be in. Make the agent enter a
start and end date through a dialog and it can commit to the current
ticket window, then you will have to dates to go in between. Or it can
push and create from the dialog, on close or a button. If the dates are
in the future, you will need them to be stored on the ticket and have an
escalation to do the push fields. Either way, the dates need to be solid
in a field for qualification if your doing a push fields on an
escalation. If you do the push fields off a dialog form the dates don't
need to be stored. I don't have enough info from you to elaborate
anymore, but hopefully this will give you insight.

>>> Rick.Snow@REGIONS.COM 07/09/02 08:02AM >>>
**

Is anyone using a start and end date and push field workflow that
creates
new tickets between the start and end date entered by the agent ? If
so
how did you accomplish this using a date range without a date field
for
each specific date ? Thanks in advance.

--------------------------------------------
This e-mail and any files transmitted with it are the property of
Regions Financial and/or its affiliates, are confidential, and are
intended solely for the use of the individual or entity to whom
this e-mail is addressed. If you are not one of the named
recipient(s) or otherwise have reason to believe that you have
received this message in error, please delete this message
immediately from your computer. Any other use, retention,
dissemination, forwarding, printing, or copying of this e-mail
is strictly prohibited.



To UNSUBSCRIBE, email the message "unsubscribe arslist" to:
listserv@listserv.vistait.com
You may also control your subscription options, including UNSUBSCRIBE,
at www.ARSLIST.org



To UNSUBSCRIBE, email the message "unsubscribe arslist" to:
listserv@listserv.vistait.com
You may also control your subscription options, including UNSUBSCRIBE, at
www.ARSLIST.org

Hi Rick

If I understand you correctly, that you want to create all the tickets in
the main form, not as child tickets in a separate form, I have put together
a small sample of how this could be achieved, rather than trying to explain
it.

The attached def file contains a simple form with two date fields, one
temporary date field and a flag field, and four filters. It creates a
ticket for each date in the range on submit.

A couple of notes: When working out the temp Next Date field it adds 26
hours and then used the DATE() function to return to midnight to overcome
any problems with daylight savings time changes.

If you're looking at the workflow, don't forget to look at the Else actions
otherwise you'll get into a loop.

If you put in a large date range and a lot of workflow is triggered on your
form when you submit a ticket, you could reach the limit of filter
operations allowed on your server - the config may need changing in the
admin tool.

Hope this helps

David Sanders
Remedy Consultant
=================
tel +44 (0)1494 468989
mobile +44 (0)7710 377761
email sandersd@globalnet.co.uk
web http://www.users.globalnet.co.uk/~sandersd/

View Enterprise Service Suite - CRM Sales automation, Support and Training -
http://www.users.globalnet.co.uk/~sandersd/CRM



-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:ARSLIST@LISTSERV.VISTAIT.COM]On Behalf Of Rick S. Snow
Sent: 15 July 2002 14:52
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Multiple Dates


**

To explain this more clearly let me give an example. From the users view,
I want to enter a start date of 07/01/02 and the end date of 08/01/02. I
am completing a ticket for a server outage problem. When I click on save,
31 tickets should be created identically with different dates, for 07/01/02
- 08/01/02. From the admin standpoint I would like to accomplish this
with the least amount of workflow, and least amount of date fields on a
form. It would not always be a period of thirty days though, in some cases
it may be more but for the most part less. I understand that if I put 50
date fields on a form and use an active link to say set field ('Date Field
1' = $Start Date$ + 1) and so on for the fifty date fields until Date Field
X > 'End Date' and then have 50 push field actions to create a ticket for
each date field as long as they are not greater than the end date. This
seems excessive and I am hoping to find an easier way to do this.



Ron Pierce
ARSLIST@LISTSERV.VISTAIT.COM
M> cc:
Sent by: "Action Subject: Re: Multiple
Dates
Request System
discussion
list(ARSList)"
ISTAIT.COM>


07/09/2002 08:19 AM
Please respond to
"Action Request
System discussion
list(ARSList)"






**

You will need fields for the dates to be in. Make the agent enter a
start and end date through a dialog and it can commit to the current
ticket window, then you will have to dates to go in between. Or it can
push and create from the dialog, on close or a button. If the dates are
in the future, you will need them to be stored on the ticket and have an
escalation to do the push fields. Either way, the dates need to be solid
in a field for qualification if your doing a push fields on an
escalation. If you do the push fields off a dialog form the dates don't
need to be stored. I don't have enough info from you to elaborate
anymore, but hopefully this will give you insight.

>>> Rick.Snow@REGIONS.COM 07/09/02 08:02AM >>>
**

Is anyone using a start and end date and push field workflow that
creates
new tickets between the start and end date entered by the agent ? If
so
how did you accomplish this using a date range without a date field
for
each specific date ? Thanks in advance.

--------------------------------------------
This e-mail and any files transmitted with it are the property of
Regions Financial and/or its affiliates, are confidential, and are
intended solely for the use of the individual or entity to whom
this e-mail is addressed. If you are not one of the named
recipient(s) or otherwise have reason to believe that you have
received this message in error, please delete this message
immediately from your computer. Any other use, retention,
dissemination, forwarding, printing, or copying of this e-mail
is strictly prohibited.




To UNSUBSCRIBE, email the message "unsubscribe arslist" to:
listserv@listserv.vistait.com
You may also control your subscription options, including UNSUBSCRIBE,
at www.ARSLIST.org




To UNSUBSCRIBE, email the message "unsubscribe arslist" to:
listserv@listserv.vistait.com
You may also control your subscription options, including UNSUBSCRIBE, at
www.ARSLIST.org



To UNSUBSCRIBE, email the message "unsubscribe arslist" to:
listserv@listserv.vistait.com
You may also control your subscription options, including UNSUBSCRIBE, at
www.ARSLIST.org

**

On Mon, 15 Jul 2002 08:51:35 -0500, Rick S. Snow wrote:

First it will be date + 86400 not 1 - time is in seconds so 60*60*24
= 86400.

Easy way is one extra display only date field - tmpdate - then set up
a filter loop

1) tmpdate = startdate
2) push new record using tmpdate
3) tmpdate = tmpdate + 86400
4) if tmpdate <= endate goto 2

4 AL's

HTH

>**
>
>To explain this more clearly let me give an example. From the users view,
>I want to enter a start date of 07/01/02 and the end date of 08/01/02. I
>am completing a ticket for a server outage problem. When I click on save,
>31 tickets should be created identically with different dates, for 07/01/02
>- 08/01/02. From the admin standpoint I would like to accomplish this
>with the least amount of workflow, and least amount of date fields on a
>form. It would not always be a period of thirty days though, in some cases
>it may be more but for the most part less. I understand that if I put 50
>date fields on a form and use an active link to say set field ('Date Field
>1' = $Start Date$ + 1) and so on for the fifty date fields until Date Field
>X > 'End Date' and then have 50 push field actions to create a ticket for
>each date field as long as they are not greater than the end date. This
>seems excessive and I am hoping to find an easier way to do this.
>
>
>
> Ron Pierce
> > M> cc:
> Sent by: "Action Subject: Re: Multiple Dates
> Request System
> discussion
> list(ARSList)"
> > ISTAIT.COM>
>
>
> 07/09/2002 08:19 AM
> Please respond to
> "Action Request
> System discussion
> list(ARSList)"
>
>
>
>
>
>
>**
>
>You will need fields for the dates to be in. Make the agent enter a
>start and end date through a dialog and it can commit to the current
>ticket window, then you will have to dates to go in between. Or it can
>push and create from the dialog, on close or a button. If the dates are
>in the future, you will need them to be stored on the ticket and have an
>escalation to do the push fields. Either way, the dates need to be solid
>in a field for qualification if your doing a push fields on an
>escalation. If you do the push fields off a dialog form the dates don't
>need to be stored. I don't have enough info from you to elaborate
>anymore, but hopefully this will give you insight.
>
>>>> Rick.Snow@REGIONS.COM 07/09/02 08:02AM >>>
>**
>
>Is anyone using a start and end date and push field workflow that
>creates
>new tickets between the start and end date entered by the agent ? If
>so
>how did you accomplish this using a date range without a date field
>for
>each specific date ? Thanks in advance.
>
>--------------------------------------------
>This e-mail and any files transmitted with it are the property of
>Regions Financial and/or its affiliates, are confidential, and are
>intended solely for the use of the individual or entity to whom
>this e-mail is addressed. If you are not one of the named
>recipient(s) or otherwise have reason to believe that you have
>received this message in error, please delete this message
>immediately from your computer. Any other use, retention,
>dissemination, forwarding, printing, or copying of this e-mail
>is strictly prohibited.
>
>
>
>To UNSUBSCRIBE, email the message "unsubscribe arslist" to:
>listserv@listserv.vistait.com
>You may also control your subscription options, including UNSUBSCRIBE,
>at www.ARSLIST.org
>
>
>
>To UNSUBSCRIBE, email the message "unsubscribe arslist" to:
>listserv@listserv.vistait.com
>You may also control your subscription options, including UNSUBSCRIBE, at
>www.ARSLIST.org
>
>
>
>


--
Regards

Dave Saville
Please note new email address dave.saville@ntlworld.com