If we have scheduled restarts of components, we will also need a table where we can see what actions are queued and at what time. What if several changes are made that trigger such action? Should the operator be able to roll back or cancel a change before it is activated? Should the operator be informed after the action was taken about its status?
--martin -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Douglas Hubler Sent: Saturday, February 04, 2012 3:14 PM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] Confirming config roll out changes to 4.6? On Sat, Feb 4, 2012 at 8:29 AM, Tony Graziano <[email protected]> wrote: > In the mockup does it auto fill in the current date/time? y, i didn't add that to mock up, but real ui would auto fill in just like phone profiles. > On Sat, Feb 4, 2012 at 8:20 AM, Michael Picher <[email protected]> wrote: >> That looks good, maybe a warning above the OK button that states the >> restart will default to current time unless a different date and time are entered. given my above answer, you'll probably agree this would be nec. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
