Re: UI Proposal for XCF-1098

<div>
Damian Krzeminski wrote:
<blockquote cite="mid:fjc76e$539$1 <at> ger.gmane.org" type="cite">
  Andrei Cristian Niculae wrote:

  <blockquote type="cite">
    Hi guys,

I've attached to the JIRA issue XCF-1098 ( 
<a class="moz-txt-link-freetext" href="http://track.sipfoundry.org/browse/XCF-1098">http://track.sipfoundry.org/browse/XCF-1098</a> ) the UI proposal for this 
feature.

I've chosen this look because I'm thinking a scheduled restart happens 
asynchronously. It's not something that happens every day or every week.

  </blockquote>

I like UI for dalayed restart. I do not like UI for cancelling delayed 
restart. I do not think we should even offer that option (please note 
that original issue did not ask for it). But if we do offer cancelling 
delayed jobs I would propose that it's being handled on the Jobs 
screens: admin sees the jobs in Scheduled phase and can click on them 
and cancel them. I think poluting Manage Phones with nontrivial and 
probably not very useful operation is not needed.

If people disagree with that I would like to ask that patch with 
cancelling delayed restarts is separate from the patch for delaying 
restart (which is non controversial and desired)

  
</blockquote>
Honestly, I don't like the UI for canceling delayed restart either :)
It's too big.<br>
I just thought that if we offer the possibility to schedule a restart,
we should offer <br>
a possibility to cancel that restart. But we could just explain in the
quick help&nbsp; how this works<br>
and how the admin can reschedule a restart by sending the profiles
again.<br>
One more method would be to make the Schedule Restart clickable, and
this would take us to<br>
a different page where the admin has the possibility to cancel or to
reschedule the restart.<br>
Anyway, for the moment I'll just focus on the delayed restart, as you
suggested, and after I'm done,<br>
we could furthermore discuss the canceling procedure, if we want to
have one.<br><blockquote cite="mid:fjc76e$539$1 <at> ger.gmane.org" type="cite">

  <blockquote type="cite">
    This is how I'm thinking it will work: the administrator modifies the 
phone profile, checks the phone and clicks "Send Profile". The page 
illustrated in Scheduled-restart-device2.jpg appears 
(<a class="moz-txt-link-freetext" href="http://track.sipfoundry.org/secure/attachment/13205/Scheduled-restart-device2.jpg">http://track.sipfoundry.org/secure/attachment/13205/Scheduled-restart-device2.jpg</a>). 
Here he has the option to restart the phone immediately or to plan a 
scheduled restart. He has to choose the day of the week and the hour for 
a scheduled restart.

  </blockquote>

Implementation question: so what we are really delaying is restarting of 
the device that needs a new profile and not generating this profile. Right?

  
</blockquote>
Yes. The profile is generated immediately and if the phone is restarted
manually, it will download the new configuration.<br><blockquote cite="mid:fjc76e$539$1 <at> ger.gmane.org" type="cite">

  <blockquote type="cite">
    After he clicks OK, the page illustrated in 
Scheduled-restart-device1.jpg 
(<a class="moz-txt-link-freetext" href="http://track.sipfoundry.org/secure/attachment/13204/Scheduled-restart-device1.jpg">http://track.sipfoundry.org/secure/attachment/13204/Scheduled-restart-device1.jpg</a>) 
appears.
Also, I'm thinking that "Send Profile " and "Send All Profiles" buttons 
should be renamed "Generate Profile" and "Generate All Profiles".

  </blockquote>

Well: "Send" is shorter than "Generate"... do you think people get 
confused by "Send"?

</blockquote>
You're right, "Send" is shorter :) I was just thinking that we actually
just generate the profiles and the phones pick them up, so we're not
exactly sending them.<br>
But I don't think people will get confused by this, and since the panel
is already big, I guess "Send" is the best choice.<br><br>
I'll update the pictures so they reflect what we've discussed here.<br><br>
Regards,<br>
Andrei<br>
</div>