Leonsoftware Wiki

User Tools

Site Tools

You are here: start » updates » important-recent-changes-explained-by-our-ceo
updates:important-recent-changes-explained-by-our-ceo

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision Both sides next revision
updates:important-recent-changes-explained-by-our-ceo [2014/09/22 11:04]
bartek created 		updates:important-recent-changes-explained-by-our-ceo [2014/09/22 11:20]
bartek
Line 9: Line 9:
 At the moment we are focusing on making sure that there are no more glitches due to these changes. Airport Directory problem has been fixed and there should be no more major problem with it. We will shortly add possibility to add handling agent by you without asking us for this. We just need about 3 weeks for this to be completed. Our new Airport Directory is ready to accept custom handlers, we just didn't manage to make the user input for it yet. For the time being, please send your request about adding handler to [[support@leonsoftware.com]]  At the moment we are focusing on making sure that there are no more glitches due to these changes. Airport Directory problem has been fixed and there should be no more major problem with it. We will shortly add possibility to add handling agent by you without asking us for this. We just need about 3 weeks for this to be completed. Our new Airport Directory is ready to accept custom handlers, we just didn't manage to make the user input for it yet. For the time being, please send your request about adding handler to [[support@leonsoftware.com]] 
  
-3.14 release of Leon has been the major release in all Leon history. This was also the reason why we had to introduce so many changes 'live'. We have introduced complete new Airport Directory, new Handling Request features and much improvements to the OPS side of the new interface plus what is VERY important and cannot be seen - we have prepared database structure for further application growth and speed improvement (this is now our big concern - we want to make Leon faster for users).+3.14 release of Leon has been the biggest release in Leon history. This was also the reason why we had to introduce so many changes 'live'. We have introduced complete new Airport Directory, new Handling Request features and more improvements to the OPS side of the new interface plus what is VERY important and cannot be seen - we have prepared database structure for further application growth and speed improvement (this is now our big concern - we want to make Leon faster for users).
  
 At the very beginning of Leon, we were relying on the data structure which we called 'operation'. Operation is always series of legs but it is clearly visible that it means different things to different departments. For Sales - operation is a trip - series of legs sold to the particular customer (sometimes you call it job, sale etc.). For OPS operation is a series of legs performed on one aircraft in a single day. For maintenance operation counts as all legs between aircraft is released from home base and is back. So far our operation was the 'OPS' version of all those mentioned above. This caused many problems with the interaction between Sales and OPS. I know that many of you got used to split/merge operations and got proficient in omitting this problem but the main problem is that later on, all other departments - Accounting, Cost Control etc. have problem to reference to the same data. This was also the main reason why our Sales module is far from being perfect. We are aware that Sales module is now the key - soon all our hands will be on this module and since we have introduced these changes, it will be possible. At the very beginning of Leon, we were relying on the data structure which we called 'operation'. Operation is always series of legs but it is clearly visible that it means different things to different departments. For Sales - operation is a trip - series of legs sold to the particular customer (sometimes you call it job, sale etc.). For OPS operation is a series of legs performed on one aircraft in a single day. For maintenance operation counts as all legs between aircraft is released from home base and is back. So far our operation was the 'OPS' version of all those mentioned above. This caused many problems with the interaction between Sales and OPS. I know that many of you got used to split/merge operations and got proficient in omitting this problem but the main problem is that later on, all other departments - Accounting, Cost Control etc. have problem to reference to the same data. This was also the main reason why our Sales module is far from being perfect. We are aware that Sales module is now the key - soon all our hands will be on this module and since we have introduced these changes, it will be possible.
Line 41: Line 41:
   * And soon one more change. Many of you have been complaining about color change in planned flights view. Now option is yellow and confirmed flights are green. And still there are many arguments that it is not intuitive. We of course will not revert to the previous version ;) Instead of this color chaos, we have been proposed to create other, more intuitive logic and this logic is as follow:    * And soon one more change. Many of you have been complaining about color change in planned flights view. Now option is yellow and confirmed flights are green. And still there are many arguments that it is not intuitive. We of course will not revert to the previous version ;) Instead of this color chaos, we have been proposed to create other, more intuitive logic and this logic is as follow: 
  
-ALL ACTIVITIES BEING NOT CONFIRMED WILL BE THE SAME COLOR BUT WITH STRIPES.+**ALL ACTIVITIES BEING NOT CONFIRMED WILL BE THE SAME COLOR BUT WITH STRIPES.**
  
 Please see the example below: Please see the example below:
-  
-<tu grafika> 
  
-Before we implement this change, I would like to know your feedback. Please direct it to my email: pczubilinski@leonsoftware.com with the email subject 'colors'. If the idea would be accepted, we would introduce the same rule for reservations.   +{{:updates:ZZZ.png|}}
  
-I am sure all this changes will soon prove its usefulness. Thank you for your patience,  understanding and support.+Before we implement this change, I would like to know your feedback. Please direct it to my email: pczubilinski@leonsoftware.com with the email subject 'colours'. If the idea would be accepted, we would introduce the same rule for reservations.    
 + 
 +I am sure all these changes will soon prove its usefulness. Thank you for your patience,  understanding and support.
  
 Pawel Czubilinski Pawel Czubilinski
 CEO, Leon Software CEO, Leon Software
 pczubilinski@leonsoftwre.com pczubilinski@leonsoftwre.com

Page Tools

© 2021 LEON SOFTWARE ALL RIGHTS RESERVED | Leon Software