ACAS-834: Provide appropriate inputs for bulk loader default values

[bffrost]

Description

The original ticket was narrowly scoped to provide a date picker when entering the lot date synthesized. I did that, and then extended it to also provide dropdowns for any fields that have constrained possible values / data dictionaries.

Related Issue

https://schrodinger.atlassian.net/browse/ACAS-834

How Has This Been Tested?

Tested locally:

• Changing dbProperty back and forth between normal, dropdown, and date type parameters
• Submitting the form for validation and inspecting the request to confirm all types get the defaultValue inserted
• Tested creating a template, and how the form renders when a premade template is selected and then the file is loaded.

Screenshots / Videos

Dropdown:

Date picker:

Known Issues

• Many of the cmpdreg routes don't support searching by labelText so they don't update when a user types into the select2 search box. @brianbolt do you know if we have a feature to do frontend filtering of options rather than backend?

[dalejerikson]

LGTM! Looks nice! :)

[brianbolt]

Many of the cmpdreg routes don't support searching by labelText so they don't update when a user types into the select2 search box. @brianbolt do you know if we have a feature to do frontend filtering of options rather than backend?

I see what you mean when playing around with the project select list. Typing doesn't seem to change anything and is basically broken. In my testing, getting this if block to return false does the trick:

acas/modules/Components/src/client/PickList.coffee

Line 367 in 2f581ea

if @collection.url?

So I think it would be as easy as adding an option that skips the select2Options.ajax function creation if provided.

[brianbolt]

LGTM with a small nit but I do think its worth adding the fix for the select2 widget type ahead so I'm requesting changes.

[bffrost]

Many of the cmpdreg routes don't support searching by labelText so they don't update when a user types into the select2 search box. @brianbolt do you know if we have a feature to do frontend filtering of options rather than backend?

I see what you mean when playing around with the project select list. Typing doesn't seem to change anything and is basically broken. In my testing, getting this if block to return false does the trick:

acas/modules/Components/src/client/PickList.coffee

Line 367 in 2f581ea

if @collection.url?

So I think it would be as easy as adding an option that skips the select2Options.ajax function creation if provided.

Thanks for this @brianbolt . I've added a backendSearch option that can be set to false to bypass that ajax function creation, and it works great:

[brianbolt]

nice LGTM