I believe that is something you set on the CI. The Change then recognizes that when the two are related.
Rick -----Original Message----- From: Joe D'Souza <jdso...@shyle.net> Date: Fri, 19 Feb 2010 16:53:33 To: <arslist@ARSLIST.ORG> Subject: Re: Change Management Blackout Periods I don't think there is one OTB unfortunately. I do agree this is a very interesting requirement, that may be relevant in many business scenarios.. In your quest to find an OTB solution if you do stumble on one, please do let us know... Cheers Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org]on Behalf Of Frank Caruso Sent: Friday, February 19, 2010 2:28 PM To: arslist@ARSLIST.ORG Subject: Re: Change Management Blackout Periods ** I cannot believe with the mountains of code in ITSM that deals with Busines Time, Time Segments and holidays that there isn't a built in way of accomplishing this simple task. On Fri, Feb 19, 2010 at 9:13 PM, Joe D'Souza <jdso...@shyle.net> wrote: ** Frank, Interesting requirement.. This is how I might have handled it.. I would build a configuration form (custom) called Configure Change Blackout Dates or something.. Three fields that I would see as mandatory on this form is: Start Date End Date Reason for Blackout I would sort the results of this form on the Start Date so if any search is performed on this form using workflow, the start date for all configured blackouts would be correctly sorted.. Build temporary display only fields lets say $ztmpBlackOutStart$, $ztmpBlackOutEnd$ and $ztmpBlackOutReason$ on the Change Request form for the above three fields, or wherever else that you might be initiating that change and scheduling it from to query results of the black out form, and if the Scheduled Start date is found anywhere in between all the configured blackouts, bring the first result it finds, and dump into those fields.. Have both active link as well as filter workflow check for the contents of these display fields that you have built, and if not null, display an error that says something like "Blackout Period : " $ztmpBlackOutStart$ " to " $ztmpBlackOutEnd$ ". Reason for Blackout : " $ztmpBlackOutReason$ That should prevent the scheduled date from being saved if selected anywhere in any configured blackout periods.... A similar check can also be done for the end date if it intrudes onto a blackout period.. Cheers Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org]on Behalf Of Frank Caruso Sent: Friday, February 19, 2010 9:30 AM To: arslist@ARSLIST.ORG Subject: Change Management Blackout Periods ** ITSM 7.0.3 ARS 7.1 Is there a way to block users from scheduling changes during certain time periods? I have been reading through the docs on using Business Events and Time Segments but am having no luck. We do not use holiday or work day schedules of any kind. TIA Frank _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
