Announcement Announcement Module
Collapse
No announcement yet.
_flowExecutionKey in 2.0.0.RC1 Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • _flowExecutionKey in 2.0.0.RC1

    I'm using 2.0.0.RC1 and I recently switched over from the SWF 1.0 style URLs to the 2.0 style URLs.

    When I was using 1.0 and I wanted to have the user progress in the flow, I sent the _flowExecutionKey parameter along with the request (either in the URL or as a hidden form field).

    In 2.0 I noticed that the HTTP param is called "execution" instead of "_flowExecutionKey", so I changed my URLs and forms to include the "execution" param instead of _flowExecutionKey and everything seems to work fine. I still include the _eventId param that I used in SWF 1.0.

    Only concern is that I was looking at the changelog and I saw the following entry under 2.0 M2:

    * The recommended URL scheme for working with flows is now REST-based:
    http://host/<flowId>[/requestPath][?requestParameters][#fragment] - to launch a new flow execution; for example http://host/booking
    http://host/executions/<flowId>/<flowExecutionKey> - to resume a paused flow execution; for example http://host/executions/booking

    That makes me think I'm not doing this according to the best practice. I'm a little confused, though, regarding the recommendation for resuming paused flow executions. If the user clicks that link, how would SWF know what event occurred?

    I looked at the sample app and it seems that it still uses _eventId_proceed, _eventId_cancel etc. (See for example enterBookingDetails.jsp.)
Working...
X