US20080155298A1 - Refreshing a Transaction Screen - Google Patents
Refreshing a Transaction Screen Download PDFInfo
- Publication number
- US20080155298A1 US20080155298A1 US12/044,819 US4481908A US2008155298A1 US 20080155298 A1 US20080155298 A1 US 20080155298A1 US 4481908 A US4481908 A US 4481908A US 2008155298 A1 US2008155298 A1 US 2008155298A1
- Authority
- US
- United States
- Prior art keywords
- transaction
- transaction screen
- user
- screen
- user input
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/75—Indicating network or usage conditions on the user display
Definitions
- the present invention relates to data processing by digital computer, and more particularly to refreshing a transaction screen.
- a transaction is a set of actions that either commits (i.e., all the actions occur) or aborts (i.e., all the actions are undone).
- a user can create a transaction by viewing and providing data for the transaction in a transaction screen (displayed on a display device, e.g., a computer monitor) using a keyboard, mouse, or other data entry devices. Over time, the data displayed on the transaction screen may become invalid or incorrect as a result of other processes that are occurring at the same time.
- users can manually trigger a screen refresh, for example, by clicking on a refresh button that is included as part of the transaction screen.
- the present invention provides methods and apparatus, including computer program products, implementing techniques for refreshing a transaction screen.
- the techniques include displaying a transaction screen containing data for a transaction, waiting to receive user input to the transaction screen, and automatically refreshing the screen with updated data if user input is not received within a pre-determined period of time.
- Implementations of the invention can include one or more of the following features:
- Refreshing the screen if user input is not received within a pre-determined period of time comprises starting a timer that times out after a pre-determined period of time has lapsed, once the timer times out, simulating user input requesting that the screen be refreshed; and refreshing the screen with updated data in response to the simulated user input.
- the data processing apparatus includes a client and a server; displaying a transaction screen is performed by the client; and simulating user input is performed by the server.
- the server is a transaction processing application whose execution involves multiple phases including: a first phase that involves displaying a transaction screen, a second phase that involves waiting for user interaction with the transaction screen, and a third phase that involves processing user interaction with the transaction screen.
- the invention can be implemented to realize one or more of the following advantages.
- a screen can be refreshed automatically.
- Input help can be provided automatically.
- One implementation of the invention provides all of the above advantages.
- FIG. 1 is a block diagram of a system in accordance with the invention.
- FIG. 2 is a flow diagram of the system operation.
- FIGS. 3A and 3B are examples of a client-server implementation of the system.
- FIGS. 4 and 5 are examples of a Dynpro implementation of the system.
- FIG. 6 is an example of code invoking the timer.
- FIG. 7 is an example of code for the timer.
- FIG. 8 is an example of code for simulating a user request.
- FIG. 9 is an example of a screen for a process monitoring transaction.
- a system 100 in accordance with the invention includes a data storage module 110 for storing data and a transaction processing module 120 for processing transactions involving the stored data. Users can view data for the transaction and provide input to the transaction through a transaction screen 130 .
- the transaction processing module displays a transaction screen containing data for the transaction (step 210 ) and then waits for the user to respond (step 220 ).
- the nature of what is displayed to the user is something that requires a user response.
- the transaction processing module displays a sales catalog and then waits for the user to select one or more items from the sales catalog.
- the transaction processing module While the transaction processing module is waiting for the user response, the data may have become invalid or incorrect. To keep the transaction screen current, the transaction processing module keeps track of how long it has been waiting for a response (step 230 ). If it does not receive a response within a pre-determined period of time, the transaction processing module automatically refreshes the transaction screen by re-displaying the screen with updated data (steps 240 and 210 ).
- the system 100 is a client-server system 300 that includes a back-end (server) component 310 and a front-end (client) component 320 .
- the client and the server communicate using a request and response protocol where the client sends a request 330 to the server and the server sends a response 340 back to the client.
- the client and server are executed on separate computers, although in some instances the client and server may be executed on the same computer.
- the data storage module 110 and the transaction processing module 120 run on the server while the transaction screen is displayed on the client.
- the client displays the transaction screen 130 based on instructions it receives from server.
- the client then waits for user interaction with the transaction screen.
- User interaction with the transaction screen causes a request to be generated on the client and sent to the server.
- the server If the server does not receive a request from the client for a pre-determined period of time after it has sent the instructions for displaying the transaction screen, the server generates a simulated client request 350 and then responds to that request by sending the client a new transaction screen with updated data (if there has been any change in the data) or with the same data (if no change in the data).
- the server uses a timer mechanism 360 to determine when to generate the simulated client request 350 .
- the timer mechanism 360 runs in a separate thread 380 or process from the main transaction processing thread 370 .
- the timer thread 380 expires and the simulated client request 350 is generated in the main transaction processing thread 370 .
- the above-described client-server system 300 is an R/3 system available from SAP AG, of Walldorf (Baden) Germany, and the transaction processing module is a Dynpro application.
- a Dynpro, or dynamic program is an R/3 screen and its associated processing logic.
- the processing involves multiple phases.
- the first phase 410 Process before Output (PBO), occurs before the transaction screen is displayed and ends when the transaction screen is displayed.
- PBO phase the screen is initialized with the data to be displayed.
- the second phase 420 waiting phase, is the phase where the Dynpro application is waiting to receive a user response.
- the processing enters the third phase 430 , Process After Input (PAI).
- PAI Process After Input
- the user response is processed and when the PAI is finished, the PBO phase is started again. This cycle is repeated until the Dynpro terminates.
- the above-described auto-refresh technique is performed by the Dynpro application as follows. Before the PBO phase terminates, the Dynpro application initiates a timer process 510 ( FIG. 5 ) that runs in a separate thread from the main thread within which the Dynpro application is executing. The timer runs for a pre-determined period of time and then terminates. The Dynpro application sets the duration of the timer when it initiates the timer process.
- FIG. 6 shows example code for invoking the timer process 510 .
- FIG. 7 shows example code for the timer process 510 .
- the function “CRM_MONITOR_I02_WAIT” represents the timer process 510 and the variable “i_sec” 610 represents the duration of the timer.
- the Dynpro application After the timer process 510 has terminated, the Dynpro application generates a simulated client request 520 for a screen refresh.
- the simulated user request 520 causes the Waiting phase 420 to end and the PAI phase 430 to begin.
- the Dynpro application processes the simulated screen refresh request in the same manner as an actual request from the user.
- the Dynpro application enters the PBO phase 410 again and displays the transaction, this time with updated data.
- FIG. 8 shows example code for the simulated client request 520 .
- the form “restart_receive” represents the simulated client request.
- the invention can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them.
- the invention can be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers.
- a computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
- a computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
- Method steps of the invention can be performed by one or more programmable processors executing a computer program to perform functions of the invention by operating on input data and generating output. Method steps can also be performed by, and apparatus of the invention can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
- FPGA field programmable gate array
- ASIC application-specific integrated circuit
- processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer.
- a processor will receive instructions and data from a read-only memory or a random access memory or both.
- the essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data.
- a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
- Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
- the processor and the memory can be supplemented by, or incorporated in special purpose logic circuitry.
- the invention can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer.
- a display device e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor
- a keyboard and a pointing device e.g., a mouse or a trackball
- Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
- the invention can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the invention, or any combination of such back-end, middleware, or front-end components.
- the components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.
- LAN local area network
- WAN wide area network
- the computing system can include clients and servers.
- a client and server are generally remote from each other and typically interact through a communication network.
- the relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
- the invention is not limited to the particular embodiments described.
- the invention has been described in terms of its use in a transaction processing system, its use is not limited to such system.
- it can be used to refresh automatically the screen of a process monitoring program.
- One such screen 900 is shown in FIG. 9 .
- the screen 900 displays data that lists the identity 910 and the status 920 of processes being monitored.
- the screen automatically updates the screen periodically to ensure that the displayed data remains current.
- the invention has been described as an auto-refresh technique, it has other applications as well.
- it can be used to provide input help automatically to the user. If the user does not respond after a pre-determined period of time, the system automatically updates the screen to include help information that instructs the user what type of response is expected, or automatically updates the screen to include a default input which the user can accept or reject.
- Other embodiments are within the scope of the following claims.
Abstract
Methods, systems, and apparatus, including computer program products, implementing techniques for refreshing a transaction screen. The techniques include displaying, on a display device, a transaction screen containing data for a transaction, the transaction being a set of actions that either commits or aborts, where user-provided data is required for the transaction, waiting to receive a user response providing data for the transaction in the transaction screen, and automatically refreshing the transaction screen with updated data if user input to the transaction screen is not received within a pre-determined period of time.
Description
- This application is a continuation of U.S. patent application Ser. No. 10/734,511, filed Dec. 12, 2003, which is incorporated herein by reference in its entirety.
- The present invention relates to data processing by digital computer, and more particularly to refreshing a transaction screen.
- In the context of database processing, a transaction is a set of actions that either commits (i.e., all the actions occur) or aborts (i.e., all the actions are undone). In many systems, a user can create a transaction by viewing and providing data for the transaction in a transaction screen (displayed on a display device, e.g., a computer monitor) using a keyboard, mouse, or other data entry devices. Over time, the data displayed on the transaction screen may become invalid or incorrect as a result of other processes that are occurring at the same time.
- To update the displayed data, users can manually trigger a screen refresh, for example, by clicking on a refresh button that is included as part of the transaction screen.
- The present invention provides methods and apparatus, including computer program products, implementing techniques for refreshing a transaction screen. The techniques include displaying a transaction screen containing data for a transaction, waiting to receive user input to the transaction screen, and automatically refreshing the screen with updated data if user input is not received within a pre-determined period of time.
- Implementations of the invention can include one or more of the following features:
- Refreshing the screen if user input is not received within a pre-determined period of time comprises starting a timer that times out after a pre-determined period of time has lapsed, once the timer times out, simulating user input requesting that the screen be refreshed; and refreshing the screen with updated data in response to the simulated user input.
- The data processing apparatus includes a client and a server; displaying a transaction screen is performed by the client; and simulating user input is performed by the server. The server is a transaction processing application whose execution involves multiple phases including: a first phase that involves displaying a transaction screen, a second phase that involves waiting for user interaction with the transaction screen, and a third phase that involves processing user interaction with the transaction screen.
- The invention can be implemented to realize one or more of the following advantages. A screen can be refreshed automatically. Input help can be provided automatically. One implementation of the invention provides all of the above advantages.
- The details of one or more implementations of the invention are set forth in the accompanying drawings and the description below. Further features, aspects, and advantages of the invention will become apparent from the description, the drawings, and the claims.
-
FIG. 1 is a block diagram of a system in accordance with the invention. -
FIG. 2 is a flow diagram of the system operation. -
FIGS. 3A and 3B are examples of a client-server implementation of the system. -
FIGS. 4 and 5 are examples of a Dynpro implementation of the system. -
FIG. 6 is an example of code invoking the timer. -
FIG. 7 is an example of code for the timer. -
FIG. 8 is an example of code for simulating a user request. -
FIG. 9 is an example of a screen for a process monitoring transaction. - Like reference numbers and designations in the various drawings indicate like elements.
- As shown in
FIG. 1 , asystem 100 in accordance with the invention includes adata storage module 110 for storing data and atransaction processing module 120 for processing transactions involving the stored data. Users can view data for the transaction and provide input to the transaction through atransaction screen 130. - As shown in
FIG. 2 , in amethod 200 of processing of a transaction, the transaction processing module displays a transaction screen containing data for the transaction (step 210) and then waits for the user to respond (step 220). In some cases, the nature of what is displayed to the user is something that requires a user response. For example, to process a sales transaction, the transaction processing module displays a sales catalog and then waits for the user to select one or more items from the sales catalog. - While the transaction processing module is waiting for the user response, the data may have become invalid or incorrect. To keep the transaction screen current, the transaction processing module keeps track of how long it has been waiting for a response (step 230). If it does not receive a response within a pre-determined period of time, the transaction processing module automatically refreshes the transaction screen by re-displaying the screen with updated data (
steps 240 and 210). - In one implementation, illustrated in
FIG. 3A , thesystem 100 is a client-server system 300 that includes a back-end (server)component 310 and a front-end (client)component 320. The client and the server communicate using a request and response protocol where the client sends arequest 330 to the server and the server sends aresponse 340 back to the client. Typically, the client and server are executed on separate computers, although in some instances the client and server may be executed on the same computer. - In such an implementation, the
data storage module 110 and thetransaction processing module 120 run on the server while the transaction screen is displayed on the client. The client displays thetransaction screen 130 based on instructions it receives from server. The client then waits for user interaction with the transaction screen. User interaction with the transaction screen causes a request to be generated on the client and sent to the server. - If the server does not receive a request from the client for a pre-determined period of time after it has sent the instructions for displaying the transaction screen, the server generates a simulated
client request 350 and then responds to that request by sending the client a new transaction screen with updated data (if there has been any change in the data) or with the same data (if no change in the data). - In one implementation, illustrated in
FIG. 3B , the server uses atimer mechanism 360 to determine when to generate the simulatedclient request 350. Thetimer mechanism 360 runs in aseparate thread 380 or process from the maintransaction processing thread 370. When the timer times out, thetimer thread 380 expires and the simulatedclient request 350 is generated in the maintransaction processing thread 370. - In one implementation, the above-described client-
server system 300 is an R/3 system available from SAP AG, of Walldorf (Baden) Germany, and the transaction processing module is a Dynpro application. A Dynpro, or dynamic program, is an R/3 screen and its associated processing logic. - The processing involves multiple phases. The
first phase 410, Process before Output (PBO), occurs before the transaction screen is displayed and ends when the transaction screen is displayed. During the PBO phase, the screen is initialized with the data to be displayed. Thesecond phase 420, waiting phase, is the phase where the Dynpro application is waiting to receive a user response. Upon receiving a user response, the processing enters thethird phase 430, Process After Input (PAI). During the PAI phase, the user response is processed and when the PAI is finished, the PBO phase is started again. This cycle is repeated until the Dynpro terminates. - The above-described auto-refresh technique is performed by the Dynpro application as follows. Before the PBO phase terminates, the Dynpro application initiates a timer process 510 (
FIG. 5 ) that runs in a separate thread from the main thread within which the Dynpro application is executing. The timer runs for a pre-determined period of time and then terminates. The Dynpro application sets the duration of the timer when it initiates the timer process. -
FIG. 6 shows example code for invoking thetimer process 510.FIG. 7 shows example code for thetimer process 510. In the example code, the function “CRM_MONITOR_I02_WAIT” represents thetimer process 510 and the variable “i_sec” 610 represents the duration of the timer. - After the
timer process 510 has terminated, the Dynpro application generates asimulated client request 520 for a screen refresh. Thesimulated user request 520 causes theWaiting phase 420 to end and thePAI phase 430 to begin. During thePAI phase 430, the Dynpro application processes the simulated screen refresh request in the same manner as an actual request from the user. After processing, the Dynpro application enters thePBO phase 410 again and displays the transaction, this time with updated data. -
FIG. 8 shows example code for thesimulated client request 520. In the example code, the form “restart_receive” represents the simulated client request. - The invention can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. The invention can be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
- Method steps of the invention can be performed by one or more programmable processors executing a computer program to perform functions of the invention by operating on input data and generating output. Method steps can also be performed by, and apparatus of the invention can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
- Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both.
- The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in special purpose logic circuitry.
- To provide for interaction with a user, the invention can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
- The invention can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the invention, or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.
- The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
- The invention is not limited to the particular embodiments described. For example, although the invention has been described in terms of its use in a transaction processing system, its use is not limited to such system. For example, it can be used to refresh automatically the screen of a process monitoring program. One
such screen 900 is shown inFIG. 9 . Thescreen 900 displays data that lists theidentity 910 and thestatus 920 of processes being monitored. The screen automatically updates the screen periodically to ensure that the displayed data remains current. - Furthermore, although the invention has been described as an auto-refresh technique, it has other applications as well. For example, it can be used to provide input help automatically to the user. If the user does not respond after a pre-determined period of time, the system automatically updates the screen to include help information that instructs the user what type of response is expected, or automatically updates the screen to include a default input which the user can accept or reject. Other embodiments are within the scope of the following claims.
Claims (33)
1. A computer program product, tangibly embodied in a machine-readable storage device, the computer program product being operable to cause data processing apparatus to perform operations comprising:
displaying, on a display device, a transaction screen containing data for a transaction, the transaction being a set of actions that either commits or aborts, where user-provided data is required for the transaction;
waiting to receive a user response providing data for the transaction in the transaction screen; and
automatically refreshing the transaction screen with updated data if user input to the transaction screen is not received within a pre-determined period of time.
2. The product of claim 1 , wherein refreshing the transaction screen if user input is not received within a pre-determined period of time comprises:
starting a timer that times out after a pre-determined period of time has lapsed;
once the timer times out, simulating user input requesting that the transaction screen be refreshed; and
refreshing the transaction screen with updated data in response to the simulated user input.
3. The product of claim 2 , wherein:
the data processing apparatus includes a client and a server;
displaying a transaction screen is performed by the client; and
simulating user input is performed by the server.
4. The product of claim 3 , wherein the server is a transaction processing application whose execution involves multiple phases including:
a first phase that involves displaying a transaction screen;
a second phase that involves waiting for user interaction with the transaction screen; and
a third phase that involves processing user interaction with the transaction screen.
5. A method comprising:
displaying, on a display device, a transaction screen containing data for a transaction, the transaction being a set of actions that either commits or aborts, where user-provided data is required for the transaction;
waiting to receive a user response providing data for the transaction in the transaction screen; and
automatically refreshing the transaction screen with updated data if user input to the transaction screen is not received within a pre-determined period of time.
6. The method of claim 5 , wherein refreshing the transaction screen if user input is not received within a pre-determined period of time comprises:
starting a timer that times out after a pre-determined period of time has lapsed;
once the timer times out, simulating user input requesting that the transaction screen be refreshed; and
refreshing the transaction screen with updated data in response to the simulated user input.
7. The method of claim 6 , wherein:
displaying a transaction screen is performed by a client; and
simulating user input is performed by a server.
8. The method of claim 7 , wherein the server is a transaction processing application whose execution involves multiple phases including:
a first phase that involves displaying a transaction screen;
a second phase that involves waiting for user interaction with the transaction screen; and
a third phase that involves processing user interaction with the transaction screen.
9. A system comprising:
means for displaying, on a display device, a transaction screen containing data for a transaction, the transaction being a set of actions that either commits or aborts, where user-provided data is required for the transaction;
means for waiting to receive a user response providing data for the transaction in the transaction screen; and
means for automatically refreshing the transaction screen with updated data if user input to the transaction screen is not received within a pre-determined period of time.
10. The system of claim 9 , wherein the means for refreshing the transaction screen if user input is not received within a pre-determined period of time comprises:
means for starting a timer that times out after a pre-determined period of time has lapsed;
means for, once the timer times out, simulating user input requesting that the transaction screen be refreshed; and
means for refreshing the transaction screen with updated data in response to the simulated user input.
11. The system of claim 10 , further comprising a server and a client and wherein:
the means for displaying a transaction screen is part of the client; and
the means for simulating user input is part of the server.
12. The system of claim 11 , wherein the server is a transaction processing system whose execution involves multiple phases including:
a first phase that involves displaying a transaction screen;
a second phase that involves waiting for user interaction with the transaction screen; and
a third phase that involves processing user interaction with the transaction screen.
13. A computer program product, tangibly embodied in a machine-readable storage device, the computer program product being operable to cause data processing apparatus to perform operations comprising:
displaying, on a display device, a transaction screen containing data for a transaction, the transaction being a set of actions that either commits or aborts, where user-provided data is required for the transaction;
waiting to receive a user response providing data for the transaction in the transaction screen; and
if user input to the transaction screen is not received within a pre-determined period of time, automatically refreshing the transaction screen with updated data by simulating user input requesting that the transaction screen be refreshed.
14. The product of claim 13 , wherein simulating user input requesting that the transaction screen be refreshed comprises:
starting a timer that times out after a pre-determined period of time has lapsed;
once the timer times out, simulating user input requesting that the transaction screen be refreshed; and
refreshing the transaction screen with updated data in response to the simulated user input.
15. The product of claim 13 , wherein:
the data processing apparatus includes a client and a server;
displaying a transaction screen is performed by the client; and
simulating user input is performed by the server.
16. The product of claim 15 , wherein the server is a transaction processing application whose execution involves multiple phases including:
a first phase that involves displaying a transaction screen;
a second phase that involves waiting for user interaction with the transaction screen; and
a third phase that involves processing user interaction with the transaction screen.
17. A method comprising:
displaying, on a display device, a transaction screen containing data for a transaction, the transaction being a set of actions that either commits or aborts, where user-provided data is required for the transaction;
waiting to receive a user response providing data for the transaction in the transaction screen; and
if user input to the transaction screen is not received within a pre-determined period of time, automatically refreshing the transaction screen with updated data by simulating user input requesting that the transaction screen be refreshed.
18. The method of claim 17 , wherein simulating user input requesting that the transaction screen be refreshed comprises:
starting a timer that times out after a pre-determined period of time has lapsed;
once the timer times out, simulating user input requesting that the transaction screen be refreshed; and
refreshing the transaction screen with updated data in response to the simulated user input.
19. The method of claim 17 , wherein:
displaying a transaction screen is performed by a client; and
simulating user input is performed by a server.
20. The method of claim 19 , wherein the server is a transaction processing application whose execution involves multiple phases including:
a first phase that involves displaying a transaction screen;
a second phase that involves waiting for user interaction with the transaction screen; and
a third phase that involves processing user interaction with the transaction screen.
21. A system comprising:
means for displaying, on a display device, a transaction screen containing data for a transaction, the transaction being a set of actions that either commits or aborts, where user-provided data is required for the transaction;
means for waiting to receive a user response providing data for the transaction in the transaction screen; and
means for automatically refreshing the transaction screen with updated data if user input to the transaction screen is not received within a pre-determined period of time by simulating user input requesting that the transaction screen be refreshed.
22. The system of claim 21 , wherein the means for automatically refreshing the transaction screen if user input is not received within a pre-determined period of time comprises:
means for starting a timer that times out after a pre-determined period of time has lapsed;
means for, once the timer times out, simulating user input requesting that the transaction screen be refreshed; and
means for refreshing the transaction screen with updated data in response to the simulated user input.
23. The system of claim 21 , further comprising a server and a client and wherein:
the means for displaying a transaction screen is part of the client; and
the means for simulating user input is part of the server.
24. The system of claim 23 , wherein the server is a transaction processing system whose execution involves multiple phases including:
a first phase that involves displaying a transaction screen;
a second phase that involves waiting for user interaction with the transaction screen; and
a third phase that involves processing user interaction with the transaction screen.
25. A computer program product, tangibly embodied in a machine-readable storage device, the computer program product being operable to cause data processing apparatus to perform operations comprising:
displaying, on a display device, a transaction screen containing data for a transaction;
waiting to receive user input to the transaction in the transaction screen; and
if user input is not received within a pre-determined period of time, automatically updating the transaction screen to provide input help to a user.
26. The product of claim 25 , wherein automatically updating the transaction screen to provide input help to a user comprises:
automatically updating the transaction screen to include help information that instructs a user what type of response is expected.
27. The product of claim 25 , wherein automatically updating the transaction screen to provide input help to a user comprises:
automatically updating the transaction screen to include default input that a user can accept or reject.
28. A method comprising:
displaying, on a display device, a transaction screen containing data for a transaction;
waiting to receive user input to the transaction in the transaction screen; and
if user input is not received within a pre-determined period of time, automatically updating the transaction screen to provide input help to a user.
29. The method of claim 28 , wherein automatically updating the transaction screen to provide input help to a user comprises:
automatically updating the transaction screen to include help information that instructs a user what type of response is expected.
30. The method of claim 28 , wherein automatically updating the transaction screen to provide input help to a user comprises:
automatically updating the transaction screen to include default input that a user can accept or reject.
31. A system comprising:
means for displaying, on a display device, a transaction screen containing data for a transaction;
means for waiting to receive user input to the transaction in the transaction screen; and
if user input is not received within a pre-determined period of time, means for automatically updating the transaction screen to provide input help to a user.
32. The product of claim 31 , wherein the means for automatically updating the transaction screen to provide input help to a user comprises:
means for automatically updating the transaction screen to include help information that instructs a user what type of response is expected.
33. The product of claim 31 , wherein the means for automatically updating the transaction screen to provide input help to a user comprises:
means for automatically updating the transaction screen to include default input that a user can accept or reject.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/044,819 US20080155298A1 (en) | 2003-12-12 | 2008-03-07 | Refreshing a Transaction Screen |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/734,511 US7360161B2 (en) | 2003-12-12 | 2003-12-12 | Refreshing a transaction screen |
US12/044,819 US20080155298A1 (en) | 2003-12-12 | 2008-03-07 | Refreshing a Transaction Screen |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/734,511 Continuation US7360161B2 (en) | 2003-12-12 | 2003-12-12 | Refreshing a transaction screen |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080155298A1 true US20080155298A1 (en) | 2008-06-26 |
Family
ID=34653383
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/734,511 Active 2025-12-06 US7360161B2 (en) | 2003-12-12 | 2003-12-12 | Refreshing a transaction screen |
US12/044,819 Abandoned US20080155298A1 (en) | 2003-12-12 | 2008-03-07 | Refreshing a Transaction Screen |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/734,511 Active 2025-12-06 US7360161B2 (en) | 2003-12-12 | 2003-12-12 | Refreshing a transaction screen |
Country Status (1)
Country | Link |
---|---|
US (2) | US7360161B2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102010019191A1 (en) * | 2010-05-04 | 2011-11-10 | Volkswagen Ag | Method and device for operating a user interface |
Families Citing this family (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070011626A1 (en) * | 2005-07-08 | 2007-01-11 | International Business Machines Corporation | Apparatus and Methods for Preventing a Screen Saver or Screen Lockout Feature |
US20070118897A1 (en) * | 2005-11-09 | 2007-05-24 | Munyon Paul J | System and method for inhibiting access to a computer |
US9330246B2 (en) * | 2005-11-09 | 2016-05-03 | Paul J. Munyon | System and method for inhibiting access to a computer |
US20120072872A1 (en) * | 2010-09-21 | 2012-03-22 | Sap Ag | Methods and systems for optimization of hierarchy screen refreshes |
US10146423B1 (en) | 2011-04-07 | 2018-12-04 | Wells Fargo Bank, N.A. | System and method for generating a position based user interface |
KR101719994B1 (en) * | 2011-09-07 | 2017-03-27 | 엘지전자 주식회사 | Mobile terminal and method for controlling the same |
KR101963589B1 (en) * | 2012-06-18 | 2019-03-29 | 삼성전자주식회사 | Method and apparatus for performaing capability discovery of rich communication suite in a portable terminal |
US11516309B2 (en) | 2014-07-16 | 2022-11-29 | Tensera Networks Ltd. | Transparent pre-loading of user applications |
US11095743B2 (en) | 2014-07-16 | 2021-08-17 | Tensera Networks Ltd. | Optimized content-delivery network (CDN) for the wireless last mile |
US11483415B2 (en) | 2014-07-16 | 2022-10-25 | Tensera Networks Ltd. | Background pre-rendering of user applications |
US11922187B2 (en) | 2018-03-05 | 2024-03-05 | Tensera Networks Ltd. | Robust application preloading with accurate user experience |
US11915012B2 (en) | 2018-03-05 | 2024-02-27 | Tensera Networks Ltd. | Application preloading in the presence of user actions |
US11824956B2 (en) | 2019-07-30 | 2023-11-21 | Tensera Networks Ltd. | Pre-rendering of application user-interfaces in user devices using off-line pre-render mode |
CN116670646A (en) | 2020-12-03 | 2023-08-29 | 腾赛拉网络有限公司 | Preloading applications with existing tasks |
Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5535422A (en) * | 1992-03-26 | 1996-07-09 | International Business Machines Corporation | Interactive online tutorial system for software products |
US5995101A (en) * | 1997-10-29 | 1999-11-30 | Adobe Systems Incorporated | Multi-level tool tip |
US6374145B1 (en) * | 1998-12-14 | 2002-04-16 | Mark Lignoul | Proximity sensor for screen saver and password delay |
US20020156812A1 (en) * | 2000-09-08 | 2002-10-24 | Krasnoiarov Boris Andreyevich | Method and system for assembling concurrently-generated content |
US6516421B1 (en) * | 1999-10-27 | 2003-02-04 | International Business Machines Corporation | Method and means for adjusting the timing of user-activity-dependent changes of operational state of an apparatus |
US20030076341A1 (en) * | 2001-10-18 | 2003-04-24 | Hikaru Kuki | Graphical user interface for an appliance network |
US6560711B1 (en) * | 1999-05-24 | 2003-05-06 | Paul Given | Activity sensing interface between a computer and an input peripheral |
US20030182220A1 (en) * | 1999-03-29 | 2003-09-25 | Dlj Long Term Investment Corporation | Method and system for providing financial information and evaluating securities of a financial debt instrument |
US20040130572A1 (en) * | 2003-01-07 | 2004-07-08 | Aravind Bala | Active content wizard: execution of tasks and structured content |
US20040181578A1 (en) * | 2003-03-11 | 2004-09-16 | Kim Elms | Unified network resources |
US20040248637A1 (en) * | 2003-06-06 | 2004-12-09 | Liebenberg Dawid J. | Interactive networked game |
US20050057560A1 (en) * | 2003-09-17 | 2005-03-17 | Viera Bibr | System and method for building wireless applications with intelligent mapping between user interface and data components |
US6973623B2 (en) * | 2001-06-14 | 2005-12-06 | International Business Machines Corporation | System and method for client refresh mode selection |
US7089508B1 (en) * | 2002-09-25 | 2006-08-08 | Bellsouth Intellectual Property Corporation | Method and system for preventing the activation of a computer screen saver |
US7177918B2 (en) * | 2002-12-20 | 2007-02-13 | International Business Machines Corporation | Method and system for efficiently processing multiframe data in a client/server computing environment |
US20110167110A1 (en) * | 1999-02-01 | 2011-07-07 | Hoffberg Steven M | Internet appliance system and method |
US7987246B2 (en) * | 2002-05-23 | 2011-07-26 | Jpmorgan Chase Bank | Method and system for client browser update |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4365897B2 (en) * | 1997-02-21 | 2009-11-18 | キヤノン株式会社 | Video conference system and method for video conference system |
-
2003
- 2003-12-12 US US10/734,511 patent/US7360161B2/en active Active
-
2008
- 2008-03-07 US US12/044,819 patent/US20080155298A1/en not_active Abandoned
Patent Citations (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5535422A (en) * | 1992-03-26 | 1996-07-09 | International Business Machines Corporation | Interactive online tutorial system for software products |
US5995101A (en) * | 1997-10-29 | 1999-11-30 | Adobe Systems Incorporated | Multi-level tool tip |
US6374145B1 (en) * | 1998-12-14 | 2002-04-16 | Mark Lignoul | Proximity sensor for screen saver and password delay |
US20110167110A1 (en) * | 1999-02-01 | 2011-07-07 | Hoffberg Steven M | Internet appliance system and method |
US6839686B1 (en) * | 1999-03-29 | 2005-01-04 | Dlj Long Term Investment Corporation | Method and system for providing financial information and evaluating securities of a financial debt instrument |
US20030182220A1 (en) * | 1999-03-29 | 2003-09-25 | Dlj Long Term Investment Corporation | Method and system for providing financial information and evaluating securities of a financial debt instrument |
US6560711B1 (en) * | 1999-05-24 | 2003-05-06 | Paul Given | Activity sensing interface between a computer and an input peripheral |
US6516421B1 (en) * | 1999-10-27 | 2003-02-04 | International Business Machines Corporation | Method and means for adjusting the timing of user-activity-dependent changes of operational state of an apparatus |
US20020156812A1 (en) * | 2000-09-08 | 2002-10-24 | Krasnoiarov Boris Andreyevich | Method and system for assembling concurrently-generated content |
US6973623B2 (en) * | 2001-06-14 | 2005-12-06 | International Business Machines Corporation | System and method for client refresh mode selection |
US20030076341A1 (en) * | 2001-10-18 | 2003-04-24 | Hikaru Kuki | Graphical user interface for an appliance network |
US7987246B2 (en) * | 2002-05-23 | 2011-07-26 | Jpmorgan Chase Bank | Method and system for client browser update |
US7089508B1 (en) * | 2002-09-25 | 2006-08-08 | Bellsouth Intellectual Property Corporation | Method and system for preventing the activation of a computer screen saver |
US7177918B2 (en) * | 2002-12-20 | 2007-02-13 | International Business Machines Corporation | Method and system for efficiently processing multiframe data in a client/server computing environment |
US20040130572A1 (en) * | 2003-01-07 | 2004-07-08 | Aravind Bala | Active content wizard: execution of tasks and structured content |
US20040181578A1 (en) * | 2003-03-11 | 2004-09-16 | Kim Elms | Unified network resources |
US20040248637A1 (en) * | 2003-06-06 | 2004-12-09 | Liebenberg Dawid J. | Interactive networked game |
US20050057560A1 (en) * | 2003-09-17 | 2005-03-17 | Viera Bibr | System and method for building wireless applications with intelligent mapping between user interface and data components |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102010019191A1 (en) * | 2010-05-04 | 2011-11-10 | Volkswagen Ag | Method and device for operating a user interface |
US9489435B2 (en) | 2010-05-04 | 2016-11-08 | Volkswagen Ag | Method and apparatus for operating a user interface |
US10503747B2 (en) | 2010-05-04 | 2019-12-10 | Volkswagen Ag | Method and apparatus for operating a user interface |
Also Published As
Publication number | Publication date |
---|---|
US7360161B2 (en) | 2008-04-15 |
US20050132302A1 (en) | 2005-06-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20080155298A1 (en) | Refreshing a Transaction Screen | |
EP1568189B1 (en) | Session-return enabling stateful web applications | |
US6393605B1 (en) | Apparatus and system for efficient delivery and deployment of an application | |
US7757239B2 (en) | Systems and methods for suspending and resuming of a stateful web application | |
US6728960B1 (en) | Techniques for managing multiple threads in a browser environment | |
US7900190B2 (en) | Business object templates | |
US8042055B2 (en) | Replaying captured network interactions | |
US20050081105A1 (en) | Undoing user actions in a client program | |
WO2001084379A3 (en) | Method and apparatus for providing a highly interactive transaction environment in a distributed network | |
US20140358855A1 (en) | Replicating data to a database | |
US7330894B2 (en) | System and method for preventing timeout of a client | |
US10951667B1 (en) | System and method for session management | |
US20070156649A1 (en) | Source-context aware object-based navigation | |
EP2739097B1 (en) | A mobile telecommunication device in a cellular-digital wireless telecommunication system and a method for operating thereof | |
US7685526B2 (en) | Providing navigation in a browser | |
US8407368B2 (en) | Tracking network socket usage in a data communication network | |
US20060242600A1 (en) | Providing user input values in input controls | |
US20040215710A1 (en) | Mechanism for intelligent user interface presentation of a software agent | |
US11615097B2 (en) | Triggering a user interaction with a device based on a detected signal | |
US11170012B2 (en) | Determining session count of unique sessions for requested time periods | |
US20060080302A1 (en) | Input control for identifying objects | |
CN1622513A (en) | Method and system for displaying JMX monitoring information | |
US20220416960A1 (en) | Testing networked system using abnormal node failure | |
WO2005050440A1 (en) | Blocking input with delayed message | |
US20070156629A1 (en) | Target context aware object-based navigation |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SAP AKTIENGESELLSCHAFT, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CINA, MIROSLAV;REEL/FRAME:021809/0841 Effective date: 20031211 |
|
AS | Assignment |
Owner name: SAP SE, GERMANY Free format text: CHANGE OF NAME;ASSIGNOR:SAP AG;REEL/FRAME:033625/0223 Effective date: 20140707 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |