OK - the logs are of no help. And there's a ton of old posts on the subject of LOGOUT, so here's what I'm trying to achieve:
My customers (all gliding clubs) sell trial flying lessons on their own websites. Purchasers are sent a voucher containing a unique number, together with a button link to "Book Online"
Customer clicks the link/button which then logs them into AIM as a guest which sends them to a special perspective (all good)
Customer picks a date on the availability calendar, enter their voucher number + additional security details
AIM records the booking date on the voucher record, a few bits of other stuff, Thanks them for their purchase (all good)
Customer is then redirected back to my customer's own website (not so good - BECAUSE)
2-line process is called ("Logout To Website" )
Line 1 - DISPLAY URL SessionObj.URL_website = works for all customers except one who is using NGINX
Line 2 - LOGOUT LoggedInSystemUser - kinda works I think, in that the page closes down to be replaced by the customers webpage, but occasionally I get a flash of a message saying there's a problem (not recorded in the production logs or the tomcat logs). The production log says the process is suspended BEFORE line 2 is triggered.
My documentation says that the COMMAND Logout should accept a url as a parameter but it doesn't seem to like a bo.attribute containing a URL as a param. That's a shame because it would then be a 1-line process. LOGOUT in a process however seems to want a user rather than a URL and from what I've read, that user cannot be the logged in user
I've banged my head against the wall so hard it hurts
I've now asked my NGINX customer to contact them to try to resolve the issue as I don't really think it's my problem - but it would be good to know what the issue might be
