The development roadmap is only visible to admins and planners. You can still submit an idea above.
The known-issues list is only visible to admins and planners. You can still report a bug above.
Change Log
v0.20.23
FixPush to eResource no longer risks creating duplicate records if a run is interrupted, and asks you to choose when a person or project has more than one possible match.
v0.20.22
FeatureYou can now push a project, the people booked on it and their bookings into eResource Scheduler. Running it again updates the same records rather than making copies.
v0.20.21
FeatureConnected apps can now refresh ship positions, with a shared ten-minute limit to avoid repeat requests.
v0.20.20
FixBehind-the-scenes tidy-up of how personal details are stored.
v0.20.19
FeaturePersonal details, pay rates and costs are now kept separately and only shown to the people at the right company base.
FeatureAdmins can set which company base each user belongs to.
v0.20.18
FeatureGroundwork for multiple company bases. Admins can see the company's bases in Settings, and everything you already have belongs to EWP UK.
FeatureThe Region choice has been removed from a person's contract details — the company base replaces it.
v0.20.17
FeatureApps that read customers from ewpResource now also receive each customer's Zigaflow link, so ewpSupport can match customers to Zigaflow.
v0.20.16
FixShip tracking no longer saves the tracking service's "not known" wording (such as "ETA: -" or "Destination not available") as if it were a real port or arrival time. Unknown values are now left blank, and the map and project list simply leave them out.
FixApps that read ship positions from ewpResource now always receive a proper date for the arrival time, or nothing, never text. This was stopping ewpProject from updating.
v0.20.15
FixImporting a project from eResource now finds its bookings and the people on them. It previously reported no bookings even when the project had them.
FixIf eResource can't be read while opening a project to import, the import now shows what went wrong with a Try again button, instead of loading forever.
FixThe eResource import now stops with a clear message if eResource answers in a way the app doesn't understand, or has more records than it can read in one go, rather than carrying on with an empty or incomplete list.
v0.20.14
FeatureThe Access Fonn settings now show which Fonn user the access token belongs to, since everything this app does in Fonn appears under that person's name.
FixWhen Fonn refuses a request, the message now names the two credentials Fonn actually needs and where to get each one: the subscription key from the Fonn API Developer Portal, and the access token from inside the Fonn app. It no longer asks for an 'Api-Key', which Fonn doesn't use.
v0.20.13
FeatureTest connection in the Access Fonn settings now checks both that Fonn can be reached and that the projects path works for a real project, and tells you which part failed. If Fonn has no projects yet, it says the path couldn't be tested rather than reporting success.
FixThe Access Fonn web address and projects path are now tidied when saved, so a stray slash can no longer break document downloads and uploads. A full web address pasted into the projects path is refused with an explanation.
FixTest connection is paused while you have unsaved Fonn settings, so it can't report on settings you've just changed.
v0.20.12
FixThe Access Fonn settings could save a wrong projects path if you pressed Save while the page was still loading. The settings now stay locked until your saved values have loaded.
FixWhen Fonn can't find something, the message now says whether the projects path in settings is to blame, or whether the web address simply doesn't have that page, and shows the address it tried.
v0.20.11
FeatureThe ewpResource logo now matches ewpProject: the R mark followed by the app name, in the menu, the page header and the site footer.
FixIn light mode the logo showed an old calendar-and-clock picture instead of the R mark. It now shows the R mark in both light and dark mode.
v0.20.10
FixConnected applications such as ewpProject can no longer read Fonn data through ewpResource, and the project details they receive no longer include a Fonn field. They now connect to Fonn directly with their own key. Nothing changes inside ewpResource: projects stay linked to Fonn and the Fonn panels work as before. Projects, ships, customers and people read exactly as before for connected applications.
v0.20.9
FeatureConnected applications such as ewpProject can now read Fonn projects, issues, checklists and documents through ewpResource, using ewpResource's own Fonn connection — no second Fonn key needed. It needs the new Fonn permission on the API key, is read-only, and stops working whenever Fonn is switched off here.
FeatureKeys with the Fonn permission also see which ewpResource projects are linked to a Fonn project. Keys without it see no change.
v0.20.8
FeatureA person with inspection records, equipment history or pay submittals can no longer be deleted by any route — not just from the screens, but also through connected systems and imports. Outside the app the message is shorter than the one you see on screen, but the rule can't be got round.
v0.20.7
FeatureThe crew board on the dashboard now lists only people with something in the dates you're looking at, the same as on a phone. A line underneath says how many others have nothing in that range, and Show all brings them back. Anyone with work in range still appears, even if they're marked unavailable — greyed and labelled.
FixUtilisation and the Deployed figure now measure against crew you can actually book. People marked unavailable are no longer counted, so the percentage may move.
v0.20.6
FeatureYou can now sort the resource list. Choose name, base, availability or recently added on any tab; people also sort by role or by passport expiry, soonest first, and vehicles by registration or year, and equipment by category or asset tag. Your choice is remembered.
v0.20.4
FixThe confirmation before deleting a person now tells the whole truth. It says the bookings being removed are past bookings — the record of jobs they worked — counts the equipment status entries and form requirements that go with them, and warns you when a project will lose its named project manager or kit will lose its holder.
FixDeleting several people at once now applies exactly the same protections as deleting one: anyone who signed off an equipment inspection is skipped, not deleted, and those checks no longer weaken as the records build up.
FixA delete that removes nothing now says so instead of reporting success.
FixArchived is one state again: making an archived person available again also brings them out of the archive, so nobody can be hidden from every list while marked available. The list filter now says "Show archived", matching the badge.
v0.20.3
FixThe check that lists what will be removed before deleting a person now completes. It was stalling on "Checking what's attached…", so travel and equipment allocations were never counted and the delete could not be confirmed at all.
v0.20.2
FeatureSome people can no longer be deleted at all. If there are equipment inspection records, equipment history or pay submittals against them, those are kept as evidence, so the app says so and offers to archive the person instead. Archiving is now the right choice for a leaver: the record and its history stay, they come out of every picker and count as unavailable, and an admin can restore them.
FixDeleting a person now really removes them. Until now "delete" only hid the record while their bookings stayed on the job, which is how a nameless row appeared on a project timeline. Deleting now takes the bookings, cabin allocations, travel, leave and reminders with it, and the confirmation lists exactly what will go, and how many of each, before anything happens.
FixAnyone still holding a booking today or later still cannot be deleted — that guard is unchanged.
v0.20.1
FixSomeone who still has work booked can no longer be deleted. The app now says who they are booked on and between which dates, and points you at the two things that actually help: mark them unavailable, or move their bookings to somebody else first. Bookings that have already finished are history and do not stand in the way.
FixPassport expiry warnings now follow the booking rather than whether a person is marked available. Anyone with a trip still to come gets the warning, even if they have been set to unavailable — nobody should sail on an expired passport because a tick box was cleared.
FixA booking on a timeline, list or report can no longer appear without a name. If the person behind it has been deleted, the row says so by name instead of showing a blank.
FixPeople marked unavailable now appear on the dashboard crew board greyed out, with their bookings, instead of disappearing from it — so the headline crew figures and the board below them agree about who counts.
v0.20.0
FeaturePeople now have a first name and a last name rather than one name field, so a surname that has to match a passport can be recorded properly — including names with two given names and two surnames, which a computer cannot split safely on its own. Where a stored name could not be split with confidence it has been left exactly as it was and marked "needs checking" on the person's record, for someone to confirm rather than guess. Only an admin or planner can change a person's first or last name, and every change is kept in the change history.
FeatureYou can now set what you are called, in your own settings, next to the theme and language. It shows around the app with your surname, so a planner scanning a timeline still knows which Byrne they are looking at. Travel bookings, crew rosters, invoices, pay and every PDF always use your formal first and last name — never your preferred one.
FixThe Resources list now sorts people by surname, the way a crew list reads, instead of by first name. Searching matches a first name, a surname or what somebody is called, so typing "Mike" finds Micheal Byrne.
FixImporting people now recognises someone you already have when their email address is written with different capitals, instead of creating a second copy of the same person.