Warning for different date/times regarding installation sites Hot

by Peter Østerkryger Larsen on October 28, 2016

We sometimes have an issue with developers forgetting to update the date/time for installation on all selected sites.
A solution for these mistakes would be if there where a check when a developer "Freeze" a package.
If there are a difference for one or more installation date/times in the selectes sites the panel for "DP Site Information Page" could show up with a warning for this and here you can correct it or just press "Finish" to accept. Maybe some cutomers always have these differences so there shoul be a preference setting for "Warning if installation date/time are different".

This warning could be shown for Freeze and Approve.

Regards Peter

  • Ideas

  • Please login to view any attachments.

  • Hi Peter,

    With the HLLX you can do this all yourself. This is the purpose of the exits. Introduce your own validation where needed.
    In the shops were I introduced HLLX, exit PCRE0007 was customised to :
    a) Determine all productions sites
    b) Set the date/time with +1 year (MANUAL installation is used, so install date is not really relevant)
    c) Block the screen for input (dataLocked='YES')

    Wit the HLLX you could even, set a warning message in PCRE0107 or overrule the given values by the developer and overrule them.

    As your request is rather shop dependent I would go for the HLLX, it is actually really where it is designed for :-)

    Cheers

    Johan
    Johan Jacob Commented by Johan Jacob December 22, 2016
    Top 10 Reviewer  -  

    Hi Peter,

    With the HLLX you can do this all yourself. This is the purpose of the exits. Introduce your own validation where needed.
    In the shops were I introduced HLLX, exit PCRE0007 was customised to :
    a) Determine all productions sites
    b) Set the date/time with +1 year (MANUAL installation is used, so install date is not really relevant)
    c) Block the screen for input (dataLocked='YES')

    Wit the HLLX you could even, set a warning message in PCRE0107 or overrule the given values by the developer and overrule them.

    As your request is rather shop dependent I would go for the HLLX, it is actually really where it is designed for :-)

    Cheers

    Johan

    Have you considered the remote site grouping exit? If the makeup of target sites varies greatly by change packages within an application, then this may not be a viable solution, otherwise it may be.
    Robert (Bob) Davis Commented by Robert (Bob) Davis November 20, 2016
    Top 500 Reviewer  -  

    Have you considered the remote site grouping exit? If the makeup of target sites varies greatly by change packages within an application, then this may not be a viable solution, otherwise it may be.

     

PrintEmail