New Apex Trigger dialog UX enhancements

[Dmytro Kurylo]

Please make the New Apex Trigger modal 2x wider.

The modal popup which allows selecting an SObject truncates long API names of SObjects, especially when they have namespace.

It becomes even harder when there are several SObjects starting with the same text (the list shows such things as namespace__sobject__c and namespace__sobject__ChangeEvent together with namespace__sobject_other__c). With the last half truncated, it becomes a matter of guess which item in the list is the correct one. Since you can not enter the API Name of the SObject manually, this results in one or two triggers being created, deleted and then created again but for a different picklist item until the correct one is found.

‌

Additionally, if it’s not too hard, please add a set of radio buttons or a picklist that filters the list of SObjects:

All (default value)	All SF SObjects (same list as now)
Standard	Standard SF SObjects only (Account, Contact)
Custom (Local)	Custom SObjects / Platform Events that have no namespace, or, if that’s a dev org, it is the same as the NS of the managed package that sits on the current dev org (Sobject__c / Local_Ns__Sobject__c)
Custom (External)	Custom SObjects / Platform Events that have a different namespace than the NS of the current dev org (if there’s a NS attached to a managed package that is being developen on a dev org), or any SObject that has a NS (if there’s no NS attached to the managed package on that org) (Non_Local_Ns__Sobject__c)

‌

[Scott Wells]

I've committed a change to size the dialog to accommodate the widest SObject type name in the drop-down:

That will be included in the next build (currently tracking for tomorrow morning). I'll keep the other requests for additional filtering open as a future enhancement.

[Scott Wells]

Changing the subject and component so the remaining work is more obvious for when I return to this later.

[Scott Wells]

Dynamic width fix delivered in 2.1.8.4.

[Dmytro Kurylo]

Thanks!