Skip to content

[SF.app timeout timer] Reset the timeout timer during an escalated session when the user starts typing instead of message sent. #1256

Open

Description

@ear-dev

If the visitor is typing a message, we don't want the timer to go off. We would like the timer to reset when the visitor starts typing, instead of when the visitor sends the message.

Since our timer is controlled by the app and not the widget, maybe we need to use 'sneak peek'?

FYI - I think that I am still seeing sneak peek as flaky..... but in the meantime we should design and implement this in any case.

Activity

  1. ear-dev commented on Jul 26, 2022

    @ear-dev
    Author

    @bhardwajaditya can you please look at sneak peek to verify our fixes are still in? not sure why my tests show it to be flaky.
    Also, please come up with a design how to do this if possible.

  2. csmith14 commented on Sep 1, 2022

    @csmith14
    Collaborator

    Two PRs have been created in relation to this story:

    EDIT: These are now out of date.

  3. ear-dev commented on Sep 22, 2022

    @ear-dev
    Author

    ISSUE: In order to reset the timeout banner on the widget when the visitor starts typing, we need to send a message from the SF.app down to the widget that resets the customFields. However we do not want to display any message content to the visitor for this type of message/payload.
    Maybe we need to create a new listener where the app can publish a message that the widget will listen for. This is kind of the way the widget sends visitor typing (for example) to the app..... but we need it to work in the other direction.

  4. ear-dev commented on Sep 27, 2022

    @ear-dev
    Author

    @csmith14 Please verify if the apps-engine PR is still required and reference it in this story if it is. If not please close the PR on apps-engine repo. thanks.

  5. ear-dev commented on Sep 29, 2022

    @ear-dev
    Author

    Update: Shailesh has suggested a design where we continue to use the same mechanism for passing info to the widget (a message), but only send one when the timeout warning banner is to be displayed, as opposed to every time the user types in order to reset the customFields.

    This design will give all control to the RC.server/SF.app, and take it away from the widget entirely.

    Perhaps we need a second scheduled_task for the warning banner. Currently we have a schedule_task for the timeout.

    @Shailesh351 please comment on this design and point @csmith14 to some relevant links in the code.

  6. ear-dev commented on Sep 29, 2022

    @ear-dev
    Author

    NOTE: consolidating stories for this story to include the Bug:
    When the setting on SF.app is toggled to "App", currently the widget is still also in control of killing the session when the timer goes off. We only want this control coming from the RC.server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions