HTTP Session Object Pattern

   Journey Manager (JM) The transaction engine for the platform.  |    Form Builder Platform Developer  |  All versions This feature is related to all versions.

You can store and retrieve data against the http session object in the usual way. However, the session object is (by definition) temporary/volatile, and may "go away" under several circumstances, such as save-and-resume. Data stored in the session object cannot be easily viewed in Manager, and therefore makes debugging difficult. Don't mess with the session object itself, because it is used internally by Manager. For example, the following code will cause all sorts of problems:

request.getSession(false)?.invalidate() // DON'T do this!!!!

As a general recommendation, you should strongly consider storing and retrieving data using the Manager built-in services.

Next, learn more about the server-side persistence pattern.