Looking for 'clean exit' from application

[cgorr]

I have written a simple phone application that allows users to enter their employee id and a pin number and then choose to either clock in or clock out. The last page displays a message letting them know whether they were successful. I would like to then either automatically or by pressing a softkey either go back to the idle phone screen or at least go back to the main services screen without having to exit/cancel the whole way back through the screens of this application. Is there a way to accomplish this? Having to manually back out through 4 or 5 screens gets a bit tedious.

[ipitts]

The expiration header can control which URLs are added to the phone URL

history. This behavior differs slightly from traditional web browsers but is

implemented to perform the same function. Disable the back button functionality

to avoid calling a URL twice.

This functionality allows you to make the content of any page that is sent to the

phone expire. When a user presses the Exit softkey, the user goes back to the last

URL that did not expire when it was loaded. This differs from traditional browsers

by not considering the current freshness of the data but the freshness of the data

when the URL was requested. This requires you to have a page expire when it is

first loaded and to not set a time and date in the future.

The following example shows how to have content on IIS expire by using

Active Server Page (ASP):

<%@ Language=JavaScript %>

<%

Response.ContentType = "text/xml";

Response.Expires = -1;

%>

The "Expires" property specifies the number of minutes to wait for the content to

expire. Setting this value to -1 subtracts 1 minute from the request time and

returns a date and time that have already passed.

[stephan.steiner]

Here's an alternative:

Send a CiscoIPPhoneExecute with url: Softkey:Service to the phone. That is the same as pressing the services button.

[aaronw.ca]

You can automatically return by setting a refresh on the status page (such as 5 seconds, 10 seconds, or however long you decide is appropriate) to Stephane's suggestion of CiscoIPPhoneExecute with url: Softkey:Service.

So it would show a message indicating success/failure/status message whatever, and then return to the idle url after the specified timeout.