This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
updates:important-recent-changes-explained-by-our-ceo [2014/09/22 11:20] bartek |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | Recently we have been changing a lot of user interface in Leon, but the good news is that **almost all major changes which affect daily usage of the application have been implemented**. We are aware that some of you may have negative impression that we have done all of this without announcing much in advance, which caused a lot of troubles on your side. We would like to apologize for all inconveniences produced by these changes. | ||
- | In this article we would like to let you know why we did all of this and why we strongly believe it will improve Leon's user experience in short future. | ||
- | |||
- | These changes were necessary to ensure compatibility with the new Leon which is coming with big steps now and to allow much improvement in Sales module which going to be developed shortly. | ||
- | |||
- | After analyzing how Leon is used by you, we have decided to make it in "**one shot**" | ||
- | |||
- | 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 biggest release in Leon history. This was also the reason why we had to introduce so many changes ' | ||
- | |||
- | At the very beginning of Leon, we were relying on the data structure which we called ' | ||
- | |||
- | We have made this ' | ||
- | |||
- | All starts in Sales. Sales is the department which creates quotes and then adds trips to the scheduling software. For this reason, trip must be always related to the sales unit, so we have | ||
- | |||
- | SWITCHED OPERATION TO TRIP WHICH IS NOW FROM SALES PERSPECTIVE, | ||
- | |||
- | This of course created many problems we had to address and we have addressed all of them in recent month. Many areas in the application were based on the concept that operation is the structure from OPS point of view. | ||
- | |||
- | * Adding flights from Planned Flights view. We know it works too slow and we wanted to simplify the code. It was very confusing that you have one series of legs in the first tab and could have completely other one in ' | ||
- | |||
- | * Printing documents from Flights List view. OPS was printing those documents by clicking on the operation number. But this produced documents for entire operation (which for the time being was the ' | ||
- | |||
- | * Marking legs as changed. So far it was the flight order number which was red after any change. However, after introducing trips, this number was red on all legs in the trip, which made it very difficult to track particular changes. For this reason we have introduced the ' | ||
- | |||
- | * Handling requests - this function was always not ideal in Leon. Handler agents blamed us for the fact they didn't receive inbound and outbound times. For this reason we had to completely rewrite the entire module to make it work better and be integrated with new Leon. | ||
- | |||
- | * Saving journey logs. So far it was only possible to save entire series of legs after an operation was completed. When it was during one day, it was OK but since now trips can be in multiple days, it was not possible to save journey log progressively. We had to change it. | ||
- | |||
- | * Split/merge - this was introduced mainly to allow OPS and Sales to workaround the problem, which was the fact that operation was not for individual customer. Operators handled it in two ways - one group was creating operations as they would be trips (across multiple days) and then OPS had to chunk those operations into smaller pieces to be able to work on them. This way, the original grouping was destroyed and we couldn' | ||
- | |||
- | * Moving empty leg between trips - If we treat trips as sales units then often there is a triangle route, i.e. 1 - empty leg (a/c positioning to pick up pax), 2 - pax leg, 3 - empty leg (return to base). Empty legs are constantly being send to broker platforms and when such empty leg has been sold, it needs to be moved to new trip. The function of moving legs between trips has been added for this purpose and acts instead of previous split/ | ||
- | |||
- | * We had to address the requirement of assigning different aircraft registrations in one trip. Sometimes a/c is AOG **and this should not be the reason to split trips** (this is still the same trip, just a/c needs to be replaced). For such cases now you modify aircraft both in Planned Flights view and in Flights List view. | ||
- | |||
- | * Together with color change (green <-> yellow) you have complained about empty legs visibility. This had been changed to blue. Also we will make options (yellow) less visible because we heard complaints that this color is to distracting. | ||
- | |||
- | * 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.** | ||
- | |||
- | Please see the example below: | ||
- | |||
- | {{: | ||
- | |||
- | 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 ' | ||
- | |||
- | I am sure all these changes will soon prove its usefulness. Thank you for your patience, | ||
- | |||
- | Pawel Czubilinski | ||
- | CEO, Leon Software | ||
- | pczubilinski@leonsoftwre.com |