Il giorno 10/gen/2013, alle ore 17.42, Denis Signoretto ha scritto:

> Hi Syncopers,
> 
> After using Syncope console for a while, IMHO, I would like to propose a 
> little refactor.
> 
> Under the "Task" tab there are 4 sub tabs. 
> "Propagation Task" and "Notification task" are similar and show related 
> executed jobs occured. 
> "Synchronization Task" and "Scheduled Task" have a different usability 
> approach. Their main function
> it's for new Synchronization and Scheduled Task creation while jobs execution 
> it's "hidden" under edit icon.
> 
> I would like to propose a refactor where all (Propagation | Notification | 
> Synchronization | Scheduled)
> task show the executed jobs moving Synchronization and Scheduled Task 
> creation under Configuration
> (like notification). 
> 
> If under Configuration ther's no space left for all tabs, a common main 
> "Policies" tab could be created
> to group (password | account | synchronization) policies.

Hi Denis,
I don't like so much this refactoring. I'd prefer to maintain tasks all 
together.
But this is just my personal opinion.

Regards,
F.

>  <http://www.intesys.it/firme/logo_intesys.jpg> 
> 
> Denis Signoretto | Senior Project Manager
> 
> Intesys - Via Roveggia 122 A - 37136 Verona 
> Tel. 045 503663 | Fax 045 503604
> denis.signore...@intesys.it
> www.intesys.it <http://www.intesys.it/>  
> 
> Le informazioni contenute nella presente e-mail e nei suoi allegati 
> potrebbero essere confidenziali/riservate e sono dirette unicamente ai 
> destinatari sopra indicati. In caso di ricezione da parte di persona diversa 
> è vietato qualunque tipo di divulgazione o copia anche parziale. Chi riceva 
> questo messaggio per errore è pregato di inoltrarlo al mittente e di 
> cancellare questa e-mail. 
> 
> This e-mail and its attachments may contain confidential/reserved information 
> and is intended only for the use of the address(es) named above. If the 
> reader of this message is not the intended recipient of this message, please 
> note that distribution or copying of this communication is forbidden. Anyone 
> who receives this communication in error should return it immediately to the 
> sender and delete the message. 
> 
> 

Reply via email to