Introduction

Getting started

Walkthrough Guides

CafeX Apps

Workflows

Using CafeX Collaborate App

Reporting

Managing CafeX

Integrating CafeX

Security

App Studio

App Studio

Timer Management

Modified on Tue, 5 Nov at 9:03 AM

The User Inactivity Timer Management feature provides App Builders with the capability to configure timers that respond to user inactivity or resumed activity. 

 

A user is considered active when performing actions such as mouse movement, clicking, scrolling, or keyboard input. If none of these actions are detected within the specified time frame, the user is considered inactive.

 

Creating a Timer

The Timer management page can be accessed through the Timer management menu item () within the App Studio.

This menu item displays a list of all timers set for the current App and provides the option to create a new one.

 

To create a timer:

  1. Navigate to the Timer management page and click the plus icon to create a new timer.
     
  2. Provide the following details for the timer:
    Name: Specify the name for the timer.
    Delay (Seconds): Specify the delay period, which is the amount of time the system waits before triggering the event handler. The default value is 300 seconds.
    Event handlers: Click the plus icon to add one or more event handlers.
     
  3. Configure the following parameters for the event handler(s):
    Handler name: Enter a name for the event handler.
    Event type: Choose the event type, User Inactive or User Activity Resumed.
        - User Inactive is triggered when the user is inactive for the specified delay period.
        - User Activity Resumed is triggered when the user becomes active again after being inactive.
    Action: Choose the action to be taken when the event occurs. Depending on the selected action, additional configurations may be required.

 

As a result of the configuration used in the example screenshot above, the warning overlay appears after 600 seconds of user inactivity and can be followed by the App auth logout action (configured separately), which triggers if no further activity is detected.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article