Tag Archives: paraplan

Update to ParaPlan iOS 1.4.5

23 March

We just updated our iOS version of ParaPlan to version 1.4.5. 

View trips for future dates:

Manifestdate

This allows drivers to view their scheduled trips for tomorrow (or any day for that matter). On the iPhone, touch settings, then touch on Manifest date change the manifest date. Drivers can also long-press on the date to toggle between Today and Tomorrow. On the iPad, there is a Change Date on the front screen. Touch that to select from a drop down calendar.

When viewing a date other than today, drivers cannot perform actions on any trips. The date is also displayed is the navigation bar. Drivers can leave the app and it will remember which date was selected for up to three hours. After three hours of not using the app, the date will reset to today.

See City and State of a stop by long pressing the stop:

Citystate

To quickly see the city and state of a stop, long press the stop and the popup action menu will display the city and state.

Support for Dynamic Type:

Dynamic Type is a new accessibility feature released with iOS 7 that allows text to be displayed in a larger font to make for easier reading. Go to Settings.app to select the desired font size. Switch back to ParaPlan and all text will be displayed in the new font.

Visual indication of wheelchair clients:

Wc

Clients that have a wheelchair or clients that require a wheelchair equipped van now have their names displayed in red. This makes it simple for drivers to take a quick glance at their eManifest to know what to expect when pulling up to a pick up location.

Route confirmation screen:

Summary

After logging in, the driver is greeted with a summary of their work date. It tells them the route (or routes) they are assigned to, the vehicle (or vehicles) that they will be driving, the first pick up time and the last drop off time and the number of stops they need to perform. The summary will countdown and automatically dismiss after 10 seconds. The driver can also click “View eManifest” to dismiss the summary. To stop the countdown, the driver can touch anywhere on the summary to stop the countdown timer. This is handy if the driver sees something in the summary that doesn’t look right.

Other Improvements:

When scrolling down on the stop list, the status bar and navigation bar are hidden to show more stops at a single time. Scroll all the way to the top to see the status and navigation bar.

The login screen has been improved. It is cleaner and faster.

Long client comments show up better and do not shrink so small that a magnifying glass is required.

When looking at routes, the vehicle number is displayed in parentheses – Blue AM (54)

We fixed a bug that caused permissions to not to take immediate impact. No more killing the app so the correct buttons are displayed. We are still not sure why people found that to be so annoying.

Improvements to create Invoice workflow

22 January

ParaPlan has a fully functional billing system. We can create invoices either for a client or for a single funding source with multiple clients. We also handle payments, pre-payments, over-payments and under-payments. Today our interface for creating invoices got a little bit easier to use.

InvoiceScreen

 

#1 – Window starts at the top

This window grows vertically as invoices get populated. We watched our users move the window to the top of the screen time and time again to see all the information on the screen. Now, the window starts at the top of the user’s display.

#2 – Smarter billable trips finder

The panel now displays the client name or program name for this invoice. The expander is also auto-expanded after the client or program is selected.

#3 – Sortable headers

The labels are now clickable and will sort the list accordingly. Click once to sort ascending. Click again to sort in descending order. The label turns bold when it is being sorted. Green means sorting ascending. Red means the list is being sorted in descending order.

These changes are currently going through internal testing. It will be released in the next update.

ParaPlan Desktop update v4.1.621.11131

21 June

78c0004e91d753a658fa8190626c3be9

 

It is bug fix Friday here at EnGraph Software. We pushed out an update earlier in the week that had some blazing fast improvements to how Scheduling Canvas worked. There were a few oversights on our end and this release will help address those.

Building a new date would cause certain trips to become flagged for sending to MDTs. Drivers were getting wrong trips and too many trips. This has been resolved.

If somebody else cancelled or no-showed a trip, it was showing up in the Unscheduled bin on your computer instead of in the Cancellation bin. This is now going to the correct bin.

If you added a fill-in trip, not all the information that was just entered was being displayed in the Scheduling Canvas. The data was actually there and now it shows up as expected.

If you accidentally clicked “add fill-in”, but closed it before making any changes, you’d expect that trip to go away as it had always done in the past. Well, it wasn’t. It was hanging around and cluttering up your screen and making a few people thinking they had gone crazy. It will now go away and you can have your clean Scheduling Canvas and your sanity back.

As always, the update will install automatically.

 

Update for ParaPlan REST

17 June

ParaPlan REST is our web interface to the database for ParaPlan Mobile for iOS. We made quite a few internal improvements that makes the code much easier to maintain and much easier to add features.

We’ve changed how the devices talk to the server. Now when a device logs on, it will be handed a url that it will before its calls against. This will allow us to quickly change endpoints if need be and will also allow us to remove a database call that each request incurred when the request was searching for the correct database. This will speed up each call and gets rid of the cross-pollination issue we were seeing when the server was overloaded.

We are also pushing out updates to other products today:

ParaPlan Mobile is getting signature capture.

ParaPlan Desktop got a faster Scheduling Canvas and support for viewing signatures captured by our iOS app.

ParaPlan Server allows trips to be changed when in progress on Mentor Rangers and smarter Zonar connections.

Version 1.1 of ParaPlan now available in the App Store

22 May

Download on the App Store Badge US UK 135x40

 

 

 

ParaPlan Mobile for iOS is the best complimentary driver paratransit or NEMT (Non-Emergency Medical Transportation) app for iPhone or iPad. It seamlessly connects to the ParaPlan database to allow drivers to see their digital manifest. Changes made in the field are reflected on the dispatchers screen in a matter of seconds. 

We recently updated the version to 1.1. Here are the new features available.

Demo mode – Test the app and see exactly how well it will fit in your operation.

iPad love – All screens take advantage of bigger iPad screen. Also many smaller screens are displayed as popovers or form sheets.

Reminders – Get notified 30 minutes before a stop to make sure you leave on time. Or schedule a notification to make sure you remember to mark the stop as performed. Or both. Schedule multiple notifications up to 24 hours in advance of a stop. Any stop that has a reminder gets a neat little badge on the manifest screen.

Navigation – Click Get Directions on any place to launch Maps to get turn-by-turn directions. Choose in settings which mapping provider to use.

Badge icons – Your front screen will show how many stops are left on your manifest.

Swipe to perform – Swiping left or right on a stop will reveal the most likely action for that stop. Either Arrive, Perform or Undo (we all make mistakes).

Geofencing – This saves your battery life if you haven’t moved in a while.

Sounds – Click sounds, confirmation sounds, notification sounds. All the audio feedback you desire. Unless that’s not your sort of thing, then you can turn them all off.

Confirmation alerts – Those can now be turned off as well.

Pull to refresh – All screens have the standard Apple pull to refresh tear drop.

Lots of other polishing, tinkering and bug fixing. Our developers and testers worked really hard on this update. We really hope you enjoy it as much as we do!

2013 05 05 20 13 41

2013 05 06 16 28 37

2013 05 07 07 12 34

2013 05 05 20 05 40

2013 05 05 20 04 21

How updates work in ParaPlan

09 May

Launching application with ClickOnce

 

We use a technology called ClickOnce to keep all of our clients up-to-date on the latest version of ParaPlan Desktop. ClickOnce enables our software to install over the internet and perform background updates over the internet. ParaPlan automatically checks for updates and install them in the background while the user continues to perform their tasks in ParaPlan. The next time the user starts using ParaPlan, they will be using the newer version. We have the ability to let the user know they need to update in the case of a major update that impacts the database. Most cases, the user doesn’t even know the update has been applied. We find this provides a level of continuity with the software experience that users appreciate.

We also don’t check for updates until AFTER they have started working. We feel that people open our software to get stuff done and the last thing they want to concern themselves with is downloading and installing a new update when they have work to do!

Manually initiate an update

Sidebar about

 

A user can always check the About screen to see the current version of the software and the date the software was released. Launching this screen will also perform a manual check for updates. If an update was found, it will display that to the user and let them know when they need to restart.

Lifecycle of an update

We develop our Windows software using Microsoft Visual Studio. We use a product called Team Foundation Server (TFS) to manage all of our builds. Here is the entire lifecycle of an update.

  1. A new feature is added to ParaPlan in Visual Studio.
  2. The feature is checked into our internal testing queue.
  3. Manual and automatic tests (unit tests) are performed.
  4. If all the tests pass, the feature is checked into the release branch of TFS.
  5. TFS compiles the new feature into ParaPlan and runs another set of automatic tests.
  6. If those tests pass, TFS builds a .application with the new feature and places it on software.engraph.com.
  7. On each client’s computer, ParaPlan will check software.engraph.com for a new version of the .application file every four hours.
  8. If a new version is found, ParaPlan will download the new feature and install it while the user is still working in ParaPlan.
  9. If the new feature is very important, ParaPlan will alert the user and instruct them to restart ParaPlan.
  10. If it was not a crucial update, the user will continue to work in the old version. The next time they restart, they will have the new version.

From a development standpoint, the process is completely automated outside of the manual testing process. This allows us to push out frequent updates and support a large number of clients.

From a user’s standpoint, their experience is contiguous as they receive new updates. We can push out frequent updates without the user having their workflow interrupted.