Pattern 67: Cache transactions
 AKA:

Back to Diagram 1 - Getting started Back to Diagram 2 - Useability Back to Diagram 3 - Adding detail Back to Diagram 4 - Workflow/security

View sensitizing image - tbd

You are designing a workflow site and know that users may want to GO BACK TO A SAFE PLACE (34). You want users to experience a SENSE OF PROGRESS (48).

The problem is to capture transactions accurately. But what if a user's line goes down or their machine crashes halfway through a complex transaction?

Therefore

Cache every transaction on workflow sites. Treat registration as transactional. Cache any details entered by a user registering. Use cookies or registration to identify users returning after an interrupted transaction whether because of a crash or a decision to visit a site outside yours.

This pattern is terminal within this language.

Discussion - forces - known uses

They will be intensely annoyed if they have spent a long time filling a shopping trolley using the search engine only to revisit the site or re-establish the connexion to find it empty.

In another scenario the user may decide, halfway through a purchase, to visit another site – perhaps to check if your prices are competitive. They will be annoyed if they return and all the details they have painstakingly typed have been thrown away or their shopping basket has been emptied.

Browse the language What is Wu? Look at an example pattern sequence Structure of the patterns
Comment on Wu Contributors Return to TriReme home page Links to related sites