Re: FW: Am I making this more difficult than it is?

2009-04-04 Thread John



Lisa, (or anyone)

We have Kinetic Calendar hooked up to drive ITSM 7 - on call. This  
type of problem could be eliminated as you would graphically see what  
is covered what is not in a calendar -- and schedule people accordingly.


Would you be interested in seeing a demo on how to use Kinetic  
Calendar to drive on-call schedules in a graphical way?



-John



--
John David Sundberg
235 East 6th Street, Suite 400B
St. Paul, MN 55101
(651) 556-0930-work
(651) 247-6766-cell
(651) 695-8577-fax
john.sundb...@kineticdata.com

On Apr 3, 2009, at 1:11 PM, Kemes, Lisa wrote:

**

I have a record with a Start Date field of: 4/12/2009 12:00:00 AM and  
an End Date field of: 4/30/2009 12:00:00 AM.


If someone were to create another record with a Start Date of:  
4/1/2009 12:00:00 AM and an End Date field of 4/15/2009 12:00:00 AM, I  
want it to error because this would "overwrite" (not really) the other  
record.


This is for my On Call system.  Therefore, if these 2 records are  
allowed to exist, you would have more than one person on call (as a  
primary) for the same dates (4/12, 4/13, 4/14 and 4/15).


Hope this makes sense!

I actually have these records on a table and I would like to walk  
through the table to make sure the records with the Start Date field:  
4/1 and End Date field: 4/15 does not get created.


AR System 7.0
Oracle 10g
Windows 2003 Server


Lisa Kemes
AR System Developer
Tyco Electronics
717-810-2408 tel
717-810-2124 fax
lisa.ke...@tycoelectronics.com



__Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"  
html___



___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"


Re: Am I making this more difficult than it is?

2009-04-04 Thread Brian Bishop
Hi Lisa,

 

I would suggest you want to check if either the start date or end date falls
within the date range used. Thus to do this you would need the following.

 

(“Start date of record being submitted” => “Start date of record submitted”
AND “Start date of record being submitted” =< “End date of record
submitted”) OR (“End date of record being submitted” => “Start date of
record submitted” AND “End date of record being submitted” =< “End date of
record submitted”)

 

This would tell you if either the start date or end date fall within the
range already allocated.

 

Brian Bishop

Goldstag Consultants Ltd

tel: 07973 746832

 

 <http://www.linkedin.com/in/brianpbishop> Linkedin

 

From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Kemes, Lisa
Sent: 03 April 2009 19:12
To: arslist@ARSLIST.ORG
Subject: FW: Am I making this more difficult than it is?

 

** 

 

I have a record with a Start Date field of: 4/12/2009 12:00:00 AM and an End
Date field of: 4/30/2009 12:00:00 AM.

 

If someone were to create another record with a Start Date of: 4/1/2009
12:00:00 AM and an End Date field of 4/15/2009 12:00:00 AM, I want it to
error because this would "overwrite" (not really) the other record.  


This is for my On Call system.  Therefore, if these 2 records are allowed to
exist, you would have more than one person on call (as a primary) for the
same dates (4/12, 4/13, 4/14 and 4/15).

 

Hope this makes sense!

 

I actually have these records on a table and I would like to walk through
the table to make sure the records with the Start Date field: 4/1 and End
Date field: 4/15 does not get created.

 

AR System 7.0

Oracle 10g

Windows 2003 Server

 

 

Lisa Kemes 

AR System Developer

Tyco Electronics

717-810-2408 tel

717-810-2124 fax

lisa.ke...@tycoelectronics.com

 

 

 

__Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ 

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.283 / Virus Database: 270.11.40/2039 - Release Date: 04/03/09
06:19:00


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
<>

Re: Am I making this more difficult than it is?

2009-04-03 Thread Kemes, Lisa
This works!

Thanks so much Lyle!!


Lisa




From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor
Sent: Friday, April 03, 2009 2:45 PM
To: arslist@ARSLIST.ORG
Subject: Re: Am I making this more difficult than it is?

**
It's simpler than it seems at first.  If you're trying to find if there is a 
conflicting record, you're looking for something like this:

Existing_start_date < new_end_date and existing_end_date > new_start_date

That is, in order for the new time period to overlap the old one, the new time 
period has to end after the old one starts, and it has to begin before the old 
one ends.

Your query might look like this:

'Start Date' < $End Date$ AND 'End Date' > $Start Date$

Does that make sense?

Lyle

From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Kemes, Lisa
Sent: Friday, April 03, 2009 12:12 PM
To: arslist@ARSLIST.ORG
Subject: FW: Am I making this more difficult than it is?

**

I have a record with a Start Date field of: 4/12/2009 12:00:00 AM and an End 
Date field of: 4/30/2009 12:00:00 AM.

If someone were to create another record with a Start Date of: 4/1/2009 
12:00:00 AM and an End Date field of 4/15/2009 12:00:00 AM, I want it to error 
because this would "overwrite" (not really) the other record.

This is for my On Call system.  Therefore, if these 2 records are allowed to 
exist, you would have more than one person on call (as a primary) for the same 
dates (4/12, 4/13, 4/14 and 4/15).

Hope this makes sense!

I actually have these records on a table and I would like to walk through the 
table to make sure the records with the Start Date field: 4/1 and End Date 
field: 4/15 does not get created.

AR System 7.0
Oracle 10g
Windows 2003 Server


Lisa Kemes
AR System Developer
Tyco Electronics
717-810-2408 tel
717-810-2124 fax
lisa.ke...@tycoelectronics.com



__Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___


NOTICE: This email message is for the sole use of the intended recipient(s) and 
may contain confidential and privileged information. Any unauthorized review, 
use, disclosure or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply email and destroy all copies of 
the original message.
__Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"


Re: Am I making this more difficult than it is?

2009-04-03 Thread ARSmarts Support

Hi Lisa,

I think you need to create a filter with a Set Field action that will  
check the condtion hereafter, and a second one that will raise an  
error if the first filter found a matching record.


Let's assume that your form is called Sample
You create a display-only field on that form called zTmpEntryID
You create a first filter on submit and on modify. The Run If is  
empty. It contains one Set Field action

From: Sample
Set If: ('Start Date' <= $Start Date$ AND 'End Date' > $Start Date$)  
OR ('Start Date' < $End Date$ AND 'End Date' >= $End Date$)

If No Match => Set Field To Null
If Multiple Match => Use First Matching
zTmpEntryID <- $1$

The second filter just displays an error message in case of  
zTmpEntryID is not null.


Hope this helps,
Jean-Louis Halleux
Remedy Expert & Developer
ARSmarts sa
www.arsmarts.com

On 03 Apr 2009, at 20:11, Kemes, Lisa wrote:


**

I have a record with a Start Date field of: 4/12/2009 12:00:00 AM  
and an End Date field of: 4/30/2009 12:00:00 AM.


If someone were to create another record with a Start Date of:  
4/1/2009 12:00:00 AM and an End Date field of 4/15/2009 12:00:00 AM,  
I want it to error because this would "overwrite" (not really) the  
other record.


This is for my On Call system.  Therefore, if these 2 records are  
allowed to exist, you would have more than one person on call (as a  
primary) for the same dates (4/12, 4/13, 4/14 and 4/15).


Hope this makes sense!

I actually have these records on a table and I would like to walk  
through the table to make sure the records with the Start Date  
field: 4/1 and End Date field: 4/15 does not get created.


AR System 7.0
Oracle 10g
Windows 2003 Server


Lisa Kemes
AR System Developer
Tyco Electronics
717-810-2408 tel
717-810-2124 fax
lisa.ke...@tycoelectronics.com



__Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"  
html___



___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"


Re: Am I making this more difficult than it is?

2009-04-03 Thread Givens, Gregory CONT
Simple answer.. Yes

Think a Push fields action.
Query
'Start Date' = $Start Date$ and 'End Date' = $End Date$
For a match Display an error message
No Match take no action since you are submitting the ticket anyway

Greg Givens 

-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Kemes, Lisa
Sent: Friday, April 03, 2009 1:12 PM
To: arslist@ARSLIST.ORG
Subject: FW: Am I making this more difficult than it is?

** 
 
I have a record with a Start Date field of: 4/12/2009 12:00:00 AM and an End
Date field of: 4/30/2009 12:00:00 AM.
 
If someone were to create another record with a Start Date of: 4/1/2009
12:00:00 AM and an End Date field of 4/15/2009 12:00:00 AM, I want it to
error because this would "overwrite" (not really) the other record.  

This is for my On Call system.  Therefore, if these 2 records are allowed to
exist, you would have more than one person on call (as a primary) for the
same dates (4/12, 4/13, 4/14 and 4/15).
 
Hope this makes sense!
 
I actually have these records on a table and I would like to walk through
the table to make sure the records with the Start Date field: 4/1 and End
Date field: 4/15 does not get created.
 
AR System 7.0
Oracle 10g
Windows 2003 Server
 
 
Lisa Kemes 
AR System Developer
Tyco Electronics
717-810-2408 tel
717-810-2124 fax
lisa.ke...@tycoelectronics.com
 
 
 
__Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ 

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"


smime.p7s
Description: S/MIME cryptographic signature


Re: Am I making this more difficult than it is?

2009-04-03 Thread Lyle Taylor
It's simpler than it seems at first.  If you're trying to find if there is a 
conflicting record, you're looking for something like this:

Existing_start_date < new_end_date and existing_end_date > new_start_date

That is, in order for the new time period to overlap the old one, the new time 
period has to end after the old one starts, and it has to begin before the old 
one ends.

Your query might look like this:

'Start Date' < $End Date$ AND 'End Date' > $Start Date$

Does that make sense?

Lyle

From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Kemes, Lisa
Sent: Friday, April 03, 2009 12:12 PM
To: arslist@ARSLIST.ORG
Subject: FW: Am I making this more difficult than it is?

**

I have a record with a Start Date field of: 4/12/2009 12:00:00 AM and an End 
Date field of: 4/30/2009 12:00:00 AM.

If someone were to create another record with a Start Date of: 4/1/2009 
12:00:00 AM and an End Date field of 4/15/2009 12:00:00 AM, I want it to error 
because this would "overwrite" (not really) the other record.

This is for my On Call system.  Therefore, if these 2 records are allowed to 
exist, you would have more than one person on call (as a primary) for the same 
dates (4/12, 4/13, 4/14 and 4/15).

Hope this makes sense!

I actually have these records on a table and I would like to walk through the 
table to make sure the records with the Start Date field: 4/1 and End Date 
field: 4/15 does not get created.

AR System 7.0
Oracle 10g
Windows 2003 Server


Lisa Kemes
AR System Developer
Tyco Electronics
717-810-2408 tel
717-810-2124 fax
lisa.ke...@tycoelectronics.com



__Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___


 NOTICE: This email message is for the sole use of the intended recipient(s) 
and may contain confidential and privileged information. Any unauthorized 
review, use, disclosure or distribution is prohibited. If you are not the 
intended recipient, please contact the sender by reply email and destroy all 
copies of the original message.



___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"


FW: Am I making this more difficult than it is?

2009-04-03 Thread Kemes, Lisa

I have a record with a Start Date field of: 4/12/2009 12:00:00 AM and an End 
Date field of: 4/30/2009 12:00:00 AM.

If someone were to create another record with a Start Date of: 4/1/2009 
12:00:00 AM and an End Date field of 4/15/2009 12:00:00 AM, I want it to error 
because this would "overwrite" (not really) the other record.

This is for my On Call system.  Therefore, if these 2 records are allowed to 
exist, you would have more than one person on call (as a primary) for the same 
dates (4/12, 4/13, 4/14 and 4/15).

Hope this makes sense!

I actually have these records on a table and I would like to walk through the 
table to make sure the records with the Start Date field: 4/1 and End Date 
field: 4/15 does not get created.

AR System 7.0
Oracle 10g
Windows 2003 Server


Lisa Kemes
AR System Developer
Tyco Electronics
717-810-2408 tel
717-810-2124 fax
lisa.ke...@tycoelectronics.com




___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"