Release 2021.21

On the 27th of May, 2021, WeSeeDo version 2021.21 was released.

Waiting room messages

This release allows you to set a waiting_room_text key, this message will be shown to participants that are already in the waiting room as well as participants that will go to the waiting room at a later time. This allows you, for example, to set a message when a Meeting will be delayed by a few minutes due to some more urgent matter. This feature is also incorporated into the WeSeeDo user interface. Below you can find an example object to POST or PATCH a Meeting.

JSON

{
  "site": "<site_id>",
  "agent": "<user_id>",
  "is_appointment": true,
  "time_start": "2021-05-19 14:00",
  "time_end": "2021-05-19 14:30",
  "participants": [
    {
      "name": "Participant 1",
      "email": "participant@visitor.nl"
    }
  ],
  "subject": "Appointment conversation",
  "invitation": "Please click on the link in this email",
  "waiting_room_text": "I will be ready in a minute!" // This is the new field that you can set, the field is not required and will default to not set a message in the waiting room.
  "send_email": true
}

Improved email address validation

Email address will now be validated according to fully comply to the RFC-2821 standard. It applies to POST, PUT and PATCH on Meeting objects and output an error when the email address is not valid. In the WeSeeDo user interface an error will be shown to visually indicate that the given email adress is not valid. The below example will be the shown error when one of the

JSON

{
    "success": false,
    "result": null,
    "error_code": "485_EMAIL_INVALID",
    "error_message": [
        "participant1.@visitor.nl", // Incorrect email
        null, // Correct email
        "participant3.@visitor.nl", // Incorrect email
    ]
}

Note: all participants are shown in the array error_message when one of the participants have a wrong mail address. If the value is 'null' it means that the mail address is correct for this participant.

Bugfixes

Under some specific circumstances the local video in the right container would display in portrait mode when it should be landscape mode, or vice-versa