Skedulo Booking Application Release Notes v22.28.0

The Salesforce admin can now configure complex profanity checks by concatenating responses to multiple questions. With this capability, they can have tighter limitations around the profanity bookings. We've enhanced the environment variable profanityQuestion. Please update the schema of this variable as shown in the following sample:

[
  {
    questionIds: ['q.patient.firstName', 'q.patient.lastName'],
    separator: ''
  },
  {
    questionIds: ['q.patient.lastName', 'q.patient.firstName'],
    separator: ''
  },
  {
    questionIds: ['q.patient.email'],
    separator: ''
  }
]

The updated profanity checker verifies and makes sure the following combination of the value held by the message keys and separator doesn't match the profanity words as shown below:

• If the firstName + lastName matches profane words.

• If the lastName + separator + firstName matches profane words.

• If the provided email address has any profanity words.

In addition to identifying the bookings with profanity, the Salesforce package now flags them and keeps them On Hold for further investigation. It also notifies the users about its status on the confirmation page. Please add the following message keys to add the notification section:

Message Keys	Suggested Values	Booking Application
confirmation.onHoldAlertHeader	Your booking is On Hold.
confirmation.onHoldAlertDescription	Your booking has been placed On Hold for review. We will update you shortly on its status.

Please note that the users can not access the /next-booking, and /manage page for the On Hold bookings which means that they can not reschedule or cancel the bookings with On Hold status either. 

The Salesforce admin can now change the status of a job so that any unintended change made by mistake can be reversed. With this capability, a Salesforce admin can reverse a job’s status from Completed to Pending Allocation again which allows the users to reschedule their appointments. The latest status of an appointment in Salesforce is also synced to the Skedulo booking application so that both entities have the same status. The Salesforce admin can reset an appointment status from Cancelled to Pending Allocation by using the /resyncBooking API with the following sample payload:

    [
        {
            "confirmationCode": "83ugcezhqb",
            "appointments": [
                {
                    "status": "Pending Allocation",
                    "appointmentId": "123e3f36-e0e2-4b19-b64f-4ef5022bf4c8"
                }
            ]
        }
    ]

If appointment with id "123e3f36-e0e2-4b19-b64f-4ef5022bf4c8" had previously been cancelled then its cancelled_at and cancel_reason fields are updated to null. 

We've updated the Booking app to use the Large Group Size on the Screening page instead of the Large Group Details page. Carry out the following steps to enable this:

The booking application treats profane bookings differently than regular bookings. The behavior of some of the existing APIs has been updated in the following ways:

• The /sendReminders, /sendBookingConfirmation, and bookings/confirmationCode APIs now exclude the profane booking in their search results. These APIs return a "Booking not found" error if the booking in question is a profane booking.
• The /cancelBulk,  /rescheduleBulk, will not process any profane bookings if any of the bookings in question is profane, then that booking is not processed further. The confirmation codes of the profane booking are included in notFound section of the response. (Previously, if an invalid confirmation code was passed in the request, then those confirmation codes appeared in notFound section). For example, the response of /cancelBulk API for a profane booking will look like this:

  {
      "total": 1,
      "processed": 0,
      "notFound": [
          "nyyqf35y1b"
      ]
  }