1. Home
  2. Release Notes
  3. Release Notes – Jun 6th, 2016

Release Notes – Jun 6th, 2016

New Features & Improvements

  • The Dropsource product was moved to a subdomain for easier product and website maintenance. You can still access the log in page from dropsource.com but you will be brought to app.dropsource.com. All of your previous bookmarks and links will work but they will now redirect to the new url.
  • The Intercom customer support messenger has been added to Dropsource. Now you will be able to contact the Dropsource team directly from the workbench without needing to go off site. This won’t replace other ways of contacting us. We are still available via email and our help forum.
  • Dropsource now has a help center drawer that allows you to quickly access documentation, tutorials, and support videos directly from the workbench. It is accessed by clicking the help button in the bottom left of the workbench.
  • Links have been added so you can access our docs and forum right from workbench.
  • Several placeholders in the workbench have been replaced with support videos, giving users access to helpful on-boarding material in context of new features.
  • Dropsource now has an expanded set of documentation, tutorials, and support videos to help you better learn Dropsource and become a power user!
  • Dropsource has been migrated to a new API graph that lays the foundation for us to support a lot more functionality with imported APIs. Keep a look out for cool features to come!
  • When an array is returned in an API response, you will now bind the data source instead of a prototype. Data sources are bound to tables (lists, page controllers, view pagers, etc) and not to table cells (list tiles, views, etc).
  • When editing a request, the parameter group dropdown now has a count beside each row to tell you how many parameters are in each group.
  • Response headers will now display and be usable in Dropsource.
  • Arrays and primitives in a response will now display and be usable in Dropsource.
  • The following validators have been added,updated, or removed to support the new API graph. You can find more information on each validator here.
    • Added “Dynamic Element Validation”
    • Updated “Multiple Child Elements in Dynamic Parent Validation”
    • Updated “Dynamic Parent Validation” and changed name to “No Child Element in Dynamic Parent Validation”
    • Updated “Multiple Prototypes Binding to Same Element” and changed name to “Multiple Data Source Assignments to Same Element Validation”.
    • Updated “Parent Prototype Mismatch Validation” and changed name to “Parent Data Source Mismatch Validation”.
    • Updated “Parent Prototype Missing Validation” and changed name to “Missing Data Source Validation”.
    • Removed “Prototype Validation”.
    • Updated “Static Parent Validation”.
    • Updated “Unexpected Parent Prototype” and changed name to “Unexpected Data Source”.
  • Warning validators have been added to the to do list. Warnings are suggestions from Dropsource telling you about potential mistakes in your app that won’t break anything but should probably be fixed (or at least considered).
  • The warning “Request Isn’t Run Validation” has been added to the to do list. This warning will alert you to any request on a page that is not being run.
  • Dynamic actions have been added to the workbench. Now you can pass dynamic information from a response into actions such as making phone calls, visiting websites, etc.
  • An image to url action has been added allowing you to convert image urls returned in an API response and display them as images in your App.
  • A color picker has been added to the element properties.
  • api keys are now provided by default for demo APIs when added to your project so you don’t have to get your own key. This is not intended for production use.
  • The terminal action icon has been changed from a red flag to a black and white checkered flag.
  • The first page you create in a project will now be automatically set as the landing page of your app.

Bug Fixes

  • Request Parameters can now be cast between different input types.
  • Parent context can now be selected as a value in the evaluate logic expression action.
  • The View Pager’s inactive tab text color now matches the active tab text color.
  • TextView Set Text Invalid Argument. The TextView’s setText() method will no longer try to cast its input as a String resource rather than an actual string.
  • Nesting “Evaluate Logic Expression” actions no longer results in duplicate variable declarations or compilation failure.
Was this article helpful to you? Yes No

How can we help?