PROD-I-764 Default "queue and notify later" in Org Settings

[Deleted User]

Nuveen has requested the ability to set a default in Org Settings for "queue and notifiy later"

Created date : 2022-10-19

Votes : 3

Comments for the idea :
product-response-mgmt product-response-mgmt Oct 21, 2022
Hi Kimberly,

Thanks for submitting the idea. In the current implementation, once the user has enabled Queue and notify toggle it will be enabled for all the future assignments, same is applicable when disabled. This helps the user to enable and disable based on the user preference. May I know why do we need have it in the org level.

Thanks,

Deepan M

Mattie Scull Jan 25, 2023
Gordian requested this today to have this at the global level

product-response-mgmt product-response-mgmt Jan 27, 2023
Hi All,

I don't understand the usecase here to have this at "Global Level" because it is at user preference where they can enable/Disable. Do they like to have a control over it?

Thanks,

Deepan M

Tara Kolinsky Jan 27, 2023
In the case of my customers, they want to have it on by default. Since we have it off by default, they ask for an org setting. I imagine if we had it on by default, there are likely other customers who prefer to have it off by default as it is now. So an org setting allows each org to decide what they want the default to be.

product-response-mgmt product-response-mgmt Jan 27, 2023
We will think through and prioritize it when we have similar request from the clients. The "Queue and Notify" later made it sticky at the user level because of the feedback from the clients. if it is set at org level, it will be cumbsersome for the other clients who currently work. We will analyze and add it to the enhancement list.

Deepan M

sunder sunder Jan 27, 2023
@Tara @Mattie

As you may know, we recently changed the system behavior so that it remembers the last setting. With this change users no longer have to toggle it each time.

Sounds like this is not sufficient. And our customers would like for it to start with ON by default for all users.

If we have Queueing ON by default, will it solve the problem? The current user-behavior will not change. i.e., if they toggle it OFF, it will remain OFF for them.

Adding an Org setting is not a major effort. However, we are trying to limit the number of org settings to reduce the burden on system admins.

Sunder

Tara Kolinsky Jan 27, 2023
I think On by default would be better for most of my customers than the current state of off by default. There may be some that feel differently though. That said, I think customers want more control over this in general. I've had a number of customers also request the ability to set a frequency in which the queue sends automatically (thus reducing the chances of them forgetting to send the queue). I think desired workflows vary so drastically from customer to customer that they appreciate the ability to customize in the org settings.

Khalees V

Update: Reached out to Dev team to check if we can run a script to Nuveen to turn on "Queue & Notify later" for all users instead of introducing a new setting in Org Settings.