Support » Plugin: Easy Appointments » Feature request: cloned Connections

  • I often clone Connections when all the settings are the same as a new Connection I want to create. This is a great feature — thank you! However, the default setting for the newly cloned Connection is to set “Is Working” to Yes. Since I usually need to go in and change some of the settings (e.g. the date or time), it means the new bookings are active for a moment, until I Edit and switch the Is Working to No and Save.

    It’s a bit awkward and potentially confusing for the front end user (if appointments get booked quickly, which they do for my client). I wondered if it’s possible to change the default setting for “Is Working” to No when a Connection is initially cloned? Or, if others would find that annoying to have to go in and switch it to Yes, maybe there could be something in the overall plugin options to set the default for “Is Working” to Yes or No.

    Anyway, thanks for considering this. I know I would find it really helpful. Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Nikola Loncar

    (@loncar)

    Hi,

    I will see how to add this. New option is maybe the best solution because of the other users. I will see what can be done here and let you know 🙂

    Best regards,
    Nikola

    Thread Starter Evolvingdoor

    (@evolvingdoor)

    Thanks! 🙂

    Plugin Author Nikola Loncar

    (@loncar)

    Hi,

    maybe the best work flow for it will be to create cloned connection change the working status and then clone that one. In that way you will need to edit only one connection and all others will be clone of that one.

    Best regards,
    Nikola

    Thread Starter Evolvingdoor

    (@evolvingdoor)

    Well, as soon as I’ve cloned the active Connection and then edited it to change the status, I already have what I’m looking for, so cloning that would be redundant. And I would still have duplicate Connections for a time before I could change the status of the first clone. And creating deactivated Connections to clone later seems cumbersome and complicated. Having a feature where you can have the default state being Off seems to make a lot more sense.

    Thread Starter Evolvingdoor

    (@evolvingdoor)

    I’m bumping up this issue again, since it is still a problem. When I clone a connection, new appointments are created in the same time slots as the original appointments. Since Multiple Work is unchecked (meaning there cannot be 2 appointments at the same day/time that have the same worker, venue and service), there should not be double appointments in those time slots, correct?

    The problem is that the cloned appointments show as new, open appointments, even though the original appointments (same day/time as the clones) are still there and are reserved and their status marked as Confirmed. To the front end user, this looks like there is an open appointment available, when in fact it should only show the reserved appointment for that slot. Instead, it shows an open (unreserved) appointment.

    If the dates of the cloned Connections are in the past, this doesn’t seem to be an issue since the calendar automatically blocks past dates, but if the original Connection dates are in the future then I wind up with duplicate slots.

    The alternative is to create new appointments from scratch, setting all the options from scratch, but that can be very time consuming. And I would think the whole point of cloning Connections is to save time, yes? And if I have Connections set to “not working” to use as originals for cloning, they can get lost in the list of Connections and become awkward and complicated to maintain.

    Since my client’s schedule fills up FAST (often as soon as I open up new appointment slots), this creates a problem. If someone sees what they think is an available appointment slot before I have a chance to edit the cloned Connection to mark it as “not working.” That means my client must contact the person and rescheduling them manually, which is time consuming and goes against the whole purpose of having the calendar on the website (to save time and help her keep track of appointments).

    This should be easy to solve by allowing cloned Connections to be created with a default setting of “not working.” I imagine not everyone would want it this way, so a new setting to select our preference should work for everyone.

    Since this problem should be prevented by having the Multiple Work setting unchecked, and this is happening anyway, this is a bug more than just a feature request. I would really appreciate it if you could take another look at this issue and see if you could add a setting to have cloned Connections set to “not working” as the default. Thanks in advance.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Feature request: cloned Connections’ is closed to new replies.