requestParameters getting lost during local storage interactions in custom logout flow

Liam Hoekenga liamr at
Thu Apr 11 10:18:50 EDT 2019

> You should definitely *not* alter the flow, that will turn every patch
> into a major ordeal. Altering templates is fine.

I'd rather not alter the flow itself, but it seems that by the time it gets
to the template, requestParameters is lost and all that's available is the
conversation state.

Alternatively, your own flow using only public classes and APIs is also an
> option but that's a lot of code copying.

Is it possible to extend or replace a system flow?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list