Ideas

Bonjour, Je voudrais voir avec vous s'il est possible de modifier les coches de cases par défauts lors de la prise en compte d'un document de couverture SB->AD. Sur l'étape 3/4 (voir PJ) je voudrai que les 3 cases “Copy” soit par défaut toutes ...

Dear Vellox team, current Receipt control activation is only for information. Logistics staff can receive goods, even though there is a Receipt Control requirement, since this is not constraining (neither poping-up during Receipt). I think this wo...

Dear Vellox team, Transportation fees are currently considered apart from the calculation's base of the VAT. They should be embeded to properly match with Suppliers' invoices. Illustration attached.

Bill of Material (BOM) have not been designed to manage Decimal , but only Integer. We need DECIMAL capability to manage multi-dimension items (those who are purchased in roll (like cable) and consumed in meters for example). Consequence: items li...

At present, track data is displayed until FDM data loads (if available), then it switches over. If the FDM data is incomplete (due to no cell at end of track), it would be useful to be able to force display back to Track data. Add a toggle to enab...

Bonjour, Pourriez vous remplacer dans le dispatch l'intituler “HAWB” par “STATUS” et insérer dans l'onglet les mentions suivantes: - DELIVERED - IN PROGRESS - SHIPPING AREA - CUSTOMS CLEARANCE Au quotidien, cette information permet à tous les serv...

Bonjour, Je me permets de vous contacter afin de vous soumettre une suggestion d’amélioration concernant le processus de création des PR. Serait-il envisageable de rendre les champs ORIGIN et SN obligatoires avant la validation d’une PR ? Cette am...

Current Tracks Download only has a capability of 2500 lines or tracks. For large aircraft fleet like ours, this only gets us 5-6 months worth of data/Flight History. This should be increased to 10,000 Tracks/Lines of Data or at the very least 5000...

Would be very useful to us, and I would think other large fleets accounts, to be able to have a column in reporting that identifies Fixed Wing vs Rotary Wing, specifically when we are looking at things like flight hours.

In concept, it would add the following as a 'location' reference when Airport or Custom codes were not found: If geo.locality within threshold → use “<d> <bearing> of <locality>” Else if geo.route within 2 km → “near <route>...