CA Service Management

Expand all | Collapse all

Blackout period Change Order

  • 1.  Blackout period Change Order

    Posted 10-10-2016 06:33 AM

    Hi All,

     

    We have created the  change window is blackout period , then we are creating the CO during the change window blackout period its created the successfully.

     

    But we are looking when blackout period defined the sdm should not allow user to create the CO.

     

    regards,

    napa



  • 2.  Re: Blackout period Change Order

    Posted 10-10-2016 06:55 AM

    Hi,

    solution with spel:

    mod file:

    MODIFY chg POST_VALIDATE z_blackout() 1337 FILTER (EVENT("INSERT"));

     

    spl file:

    chg::z_blackout() {
        string wrkshft_schedule;
        duration is_blackout;
        date blackout_end;

        wrkshft_schedule = (string)expand("&{'blackout' = wrkshft.sym->sched}");
        if (is_empty(wrkshft_schedule)) {
            logf(ERROR, "Unable to fetch workshitf");
            return;
        }
        is_blackout = workshift_abs2work(wrkshft_schedule, (date)now(), (date)((int)now()+60));
        if ((int)is_blackout < 30) {
            blackout_end = workshift_work2abs(wrkshft_schedule, (date)now(), (duration)5);
            logf(ERROR, "Unable to create COs within blackout window. Blackout will end at [%s]", (date)blackout_end);
            set_error(1);
            set_return_data(format("Unable to create COs within blackout window. Blackout will end at [%s]", (date)blackout_end));
        }
    }

     

    You shoud create "blackout" workshift with blackout schedule, script will fetch it using Workshift name.

     

    This code is not tested but should work

     

    This method could be more flexible if you publish new attribute in Change Category table to maintain individual schedules for specified categories.

     

    Regards,

    cdtj



  • 3.  Re: Blackout period Change Order

    Posted 10-10-2016 07:11 AM

    Hi cdtj,

     

    Thank you for quick reply 

     

    Sorry i forgot mention we have tenant box. 

     

    Its possible to spell coding the based on the CI mapped Change Order , then we need to check the CI service status something 'blackout'. If CI service status = blackout it will not allow to create or update the CO until CI service status moved different status.

     

    Regards,

    napa



  • 4.  Re: Blackout period Change Order

    Posted 10-10-2016 07:41 AM

    Could you share which attribute or interface tab is used to link CI and CO?

    But here could be "leak" situation, when employee will create CO and only then will attach CI.



  • 5.  Re: Blackout period Change Order

    Posted 10-10-2016 09:42 AM

    Hi cdtj,

     

    while creating the CO page we are using added the CI its configuration tab , its default.

     

    Regards,

    napa