Version 3.3 of ArcGIS API for Flex and ArcGIS Viewer for Flex Released

Version 3.3 of both the ArcGIS API for Flex and ArcGIS Viewer for Flex was released on Monday, April 29th.

This is a minor release focusing on enhancements of existing functionality, improving workflows, updated localization, and bug fixes.  As a reminder, the ArcGIS Viewer for Flex source code and ArcGIS API for Flex samples are on GitHub, but you can still download the ArcGIS API for Flex from the ArcGIS Resource center.  For more information visit the respective Resource Centers: ArcGIS Viewer for Flex , and ArcGIS API for Flex.  Please refer to the comprehensive list of What’s new in the ArcGIS API 3.3 for Flex and What’s new in the ArcGIS Viewer 3.3 for Flex for complete details.

The following highlight a few of the updates in the 3.3 release.

Enhanced DirectionsWidget

The updated DirectionsSkin in the API is showcased in the DirectionsWidget allowing users advanced options for optimizing routes and specifying return to starting location.

Improved support in Application Builder for modifying operational web layers

The following layer types (KML, CSV, GeoRSS, WMS, WMTS, and Web Tiled Layers) now support modifying the URL property in the edit dialog.

Improved support for URL parameters in the Viewer

The Viewer now supports centering the map using coordinates of a point location or an extent as well as specifying the spatial reference of the location/extent [well-known id (wkid)].

Enhancements related to Portal for ArcGIS, ArcGIS Online, and ArcGIS for Organizations

When specifying the Portal for ArcGIS URL, Application Builder will also populate the helper URLs for Geometry Service URL, Route URL, and Search URL used in the Directions Widget.

This entry was posted in Developer, Web and tagged , , , . Bookmark the permalink.

Leave a Reply

7 Comments

  1. rafaelncruz says:

    Did you remove or forget the useful Clear option on the Enhanced DirectionsWidget, or is there any setting to make it appear?

    • Lloyd Heberlie says:

      Hi Rafael,

      If you only have two stops, then you don’t see the option to delete a destination.
      Once you add a destination and you have 3 or more locations for a route (directions) you will then see the delete button. At which point the route will be cleared automatically and then you can keep adding destinations or just click the “Get Directions”.

      The workflow has been updated, hopefully removing the need for a “Clear” button.

      Lloyd

      • rafaelncruz says:

        Hi Lloyd,

        Thanks for the reply, its not as straightforward as before but i guess our users can get used to it.
        Another question regarding the directions widget, is there any option that would make the “Show option” disappear? I lost it and couldnt make it appear.
        Great work on the viewer.

        Regards,
        Rafael

      • Lloyd Heberlie says:

        Hi Rafael,

        Another option for the clear button, would be to use your own custom skin. This would require re-compiling the app and/or widget. In your skin, you could add a User Interface component that would call “hostComponent.clear()”. The hostComponent in the skin is a reference to the Directions Component. This would allow you to put the “Clear Directions” button back into your application.

  2. jmcclure@spepa.com says:

    Do you still have to use the up and down arrows to move layers on a list? It would be much more convenient to implement the ability to drag and drop them where they need to go. This is a big problem considering every time you hit up or down the view moves to where you have to scroll up or down to find the layer you just clicked.

  3. carrierkh says:

    I would like to see the ability to toggle operational layer’s visibility depending on which basemap is visible. For example,
    Basemap1 visible=”true”
    operational1 visible = “true”
    operational2 visible = “true”
    operational3 visible = “true”
    Basemap2 visible=”true”
    operational1 visible = “false”
    operational2 visible = “true”
    operational3 visible = “true”

  4. carrierkh says:

    I also like the idea of being able to drag and drop layers versus using the up and down arrows.