July 2009
15 posts
RESOLVE deployment date moved one day
RPM 5.5 will be deployed to RESOLVE on Aug 5th instead of the 4th. The AGENT dates remains unchanged, Aug 11th.
5.5 entered testing today, API is cool
Just doing some testing on the upcomming API functionality. I made a simple PHP function as an example. Here’s what using it to get account information looks like:
rpm_req("GetAccount", array("Supplier"=>"XOFake","Account"=>"0004440000010442"))
And the result is an object with all the information on the account. We’re going to have API calls for lots of things. I’ll...
RPM 5.5 column select UI also has drag and drop
So you’ll be able to arrange the columns from the select column page as well. And just like the other improvements to that page, changing the column order is pure JavaScript meaning it’s instant and you don’t have a page load delay after moving a column.
RPM 5.5 Deployment Dates
You heard it here first
RESOLVE: Tuesday Aug 4
AGENT: Tuesday Aug 11
Fixes uploaded last night
Our fix from last week introduced two problems with multi-selects. They started having problems when set to be required and when used in flows. Everything is working now.
Google Operating System →
Google has no doubt the future is SaaS. That suits RPM just fine.
iPhone supported →
Now that I’ve spent more time testing RPM from my iPhone, I’m going to declare it officialy supported. There are a couple minor Javascript quirks, but they’re not in common places. Mostly it works great, although a dedicated iPhone app would be nicer…
JSON Intro →
We’re going to go with JSON for the API for both input and output. At least for now.
rpmsoftware.com is back up
rpmsoftware.com website is down
I was right in the middle of updating the wiki page on the upcoming API when the website went down. Our opps guru is looking into it. The app pool is crashing and we don’t know why yet. The actual RPM application is unaffected.
Dev team is using iPhones now
Most of our development team is now using the iPhone 3GS. Using RPM from an iPhone is much nicer than from any other phone I’ve tried.
Fix uploaded
There was a problem with list fields when they were repeating. If a value was selected when adding the repeating field it would not be saved. In the case of multi-select fields the selections could get added to the field in the master form (the first set of repeating fields). It was a complex problem and the bottom line is that it’s fixed.
RPM API ideas →
We’re going with REST over SOAP, if only to be fashionable.