Re: Replacing artime with Business Time 2.0

[Fawver, Dustin]

Hi, Rod.


No, I haven't looked into those.  The documentation that I found on BMC's site 
seems to describe how to create them, but doesn't give "real world" examples of 
how they can be used.  Can you point me in that direction?


Thanks!


--Dustin



From: Action Request System discussion list(ARSList) <arslist@ARSLIST.ORG> on 
behalf of Rod Harris <r...@smapps.com.au>
Sent: Monday, January 9, 2017 7:45 PM
To: arslist@ARSLIST.ORG
Subject: Re: Replacing artime with Business Time 2.0

**
Hi Dustin,
Have you looked into using the assoc versions of the business time commands? I 
find these to be much easier to work with as they abstract away all the 
individual names of the time segments from the set fields commands. You just 
create a business time entity and link all the time segments you need to that. 
That way you can adjust the calendars of available and unavailable times with a 
lot of flexibility without ever needing to change the code.

Rod

On 10 January 2017 at 08:00, Fawver, Dustin 
<faw...@mail.etsu.edu<mailto:faw...@mail.etsu.edu>> wrote:
**

Greetings!


So I've ran into some old filters that are using artime to calculate time 
differences.  I read up on the BMC ARS 9.1 documentation to try to wrap my head 
around Business Time 2.0.  Here's what I've done.


- Created a Level 1 Business Time Segment titled "Work_Day" that runs from 
8:00am - 8:30pm, recurring weekly on Monday - Friday.

- Created a Level 2 segment titled "Pre_Shift" that runs from 12:00:00am to 
7:59:59am with the aforementioned recurrence.

- Created a Level 2 segment titled "Post_Shift" that runs from 8:30:01pm to end 
of day with the aforementioned recurrence.

- Created a Level 10 segment called "Holidays_2017" that lists specific dates 
and is set as unavailable.


The command used in Set Fields is:


$PROCESS$ Application-Bus-Time2-Diff "$Arrival Time$" "$Resolved Time$" 
"Work_Day" "Pre_Shift" "Post_Shift" "Holidays_2017"


It seems to work.  However, it looks like I forgot to include a time segment 
for the weekends.  Here are my questions.


1)  Aside from the recurring weekend time segment that I forgot, does it appear 
that I have things set up correctly?


2)  In order to take into consideration all of the unavailable times, do I need 
to include the name of each time segment in the Set Fields command?  I fully 
expect to have to create another segment with new holidays around the beginning 
of next year.  There are also times when offices are closed due to things like 
inclement weather.  I was hoping to have some level 3 or 4 segments that I 
would like to have considered as well, but not have to update the filter each 
time one is added.


I hope this all makes sense.


Thanks!

--Dustin Fawver

HelpDesk Technician
East Tennessee State University
(423) 439-4648

_ARSlist: "Where the Answers Are" and have been for 20 years_

_ARSlist: "Where the Answers Are" and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Replacing artime with Business Time 2.0

[Rod Harris]

Hi Dustin,
Have you looked into using the assoc versions of the business time
commands? I find these to be much easier to work with as they abstract away
all the individual names of the time segments from the set fields commands.
You just create a business time entity and link all the time segments you
need to that. That way you can adjust the calendars of available and
unavailable times with a lot of flexibility without ever needing to change
the code.

Rod

On 10 January 2017 at 08:00, Fawver, Dustin  wrote:

> **
>
> Greetings!
>
>
> So I've ran into some old filters that are using artime to calculate time
> differences.  I read up on the BMC ARS 9.1 documentation to try to wrap my
> head around Business Time 2.0.  Here's what I've done.
>
>
> - Created a Level 1 Business Time Segment titled "Work_Day" that runs from
> 8:00am - 8:30pm, recurring weekly on Monday - Friday.
>
> - Created a Level 2 segment titled "Pre_Shift" that runs from 12:00:00am
> to 7:59:59am with the aforementioned recurrence.
>
> - Created a Level 2 segment titled "Post_Shift" that runs from 8:30:01pm
> to end of day with the aforementioned recurrence.
>
> - Created a Level 10 segment called "Holidays_2017" that lists specific
> dates and is set as unavailable.
>
>
> The command used in Set Fields is:
>
>
> $PROCESS$ Application-Bus-Time2-Diff "$Arrival Time$" "$Resolved Time$"
> "Work_Day" "Pre_Shift" "Post_Shift" "Holidays_2017"
>
>
> It seems to work.  However, it looks like I forgot to include a time
> segment for the weekends.  Here are my questions.
>
>
> 1)  Aside from the recurring weekend time segment that I forgot, does it
> appear that I have things set up correctly?
>
>
> 2)  In order to take into consideration all of the unavailable times, do I
> need to include the name of each time segment in the Set Fields command?  I
> fully expect to have to create another segment with new holidays around the
> beginning of next year.  There are also times when offices are closed due
> to things like inclement weather.  I was hoping to have some level 3 or 4
> segments that I would like to have considered as well, but not have to
> update the filter each time one is added.
>
>
> I hope this all makes sense.
>
>
> Thanks!
>
> --Dustin Fawver
>
> HelpDesk Technician
> East Tennessee State University
> (423) 439-4648
> _ARSlist: "Where the Answers Are" and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"