For those interested, these are the logs demonstrating the error:
*** Subtract (Does not work): <ACTL> /* Thu Jan 11 2007 12:47:40 */ <ACTL> Start active link processing -- Operation - On Control <ACTL> For Schema - zBug_BusinessTime2 <ACTL> Linked to field - Subtract (536870909) <ACTL> On screen type - CREATE <ACTL> Checking zBug_BT2-cmdSubtract010 (10) <ACTL> -> Passed qualification -- perform if actions <ACTL> 0: Set Fields <ACTL> Process: Application-Bus-Time2-Subtract 1168537660 2 4 BusinessHours Holidays <ACTL> Returns (536870916) = Tuesday, January 09, 2007 6:00:00 PM <ACTL> /* Thu Jan 11 2007 12:47:40 */ <ACTL> Stop active link processing - On Control *** Add (Works): <ACTL> /* Thu Jan 11 2007 12:47:07 */ <ACTL> Start active link processing -- Operation - On Control <ACTL> For Schema - zBug_BusinessTime2 <ACTL> Linked to field - Add (536870910) <ACTL> On screen type - CREATE <ACTL> Checking zBug_BT2-cmdAdd010 (10) <ACTL> -> Passed qualification -- perform if actions <ACTL> 0: Set Fields <ACTL> Process: Application-Bus-Time2-Add 1168537627 2 4 BusinessHours _Holidays <ACTL> Returns (536870916) = Monday, January 15, 2007 12:47:07 PM <ACTL> /* Thu Jan 11 2007 12:47:07 */ <ACTL> Stop active link processing - On Control Axton Grams On 1/11/07, Axton <[EMAIL PROTECTED]> wrote:
I am not using the status history times. I've verified this is a bug and am preparing to report it with demonstration code. The scenario is like this: Start Time: $TIMESTAMP$ Amount: 2 Units: Days Segment1: Business Hours Schedule Segment2: Holiday Schedule RP for subtract: $PROCESS$ @@:Application-Bus-Time2-Subtract $Start Date$ $Amount$ $Units$ $Segment1$ $Segment2$ Returns: 1/9/2007 6:00:00 PM RP for Add: $PROCESS$ @@:Application-Bus-Time2-Add $Start Date$ $Amount$ $Units$ $Segment1$ $Segment2$ Returns: 1/15/2007 12:25:49 PM The problem is that the Application-Bus-Time2-Subtract always defaults the 'time' to the latest 'time of day' defined for the expected date. The subtraction works fine for all other units (seconds, minutes, hours); just not for days. Axton Grams On 1/11/07, Sullivan, Neil G CTR USAF AFRL/SNOX < [EMAIL PROTECTED]> wrote: > > ** Axton, > > Are you having any trouble with your filter not recognizing the ' > Status-History.Closed.TIME' field or do you not use that in your > process? > > Neil "Sully" Sullivan > Remedy Developer/Administrator > AFRL/SNOX > Wright Patterson AFB, OH 45433 > 937-904-9788 > > ------------------------------ > *From:* Action Request System discussion list(ARSList) [mailto:[email protected] > ] *On Behalf Of *Axton > *Sent:* Thursday, January 11, 2007 11:10 AM > *To:* [email protected] > *Subject:* Business Time 2 > > > ** Sanity check needed. For those using business time 2, have you > noticed any oddities using the business time subtract with days as the > units? It seems that date/time returned defaults to the end of the day. If > I convert the days value to seconds, using 10 hours per day, the timestamp > returned is accurate. > > Axton Grams > __20060125_______________________This posting was submitted with HTML in > it___ > __20060125_______________________This posting was submitted with HTML in > it___
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
