search

bmlt-enabled / bmlt-workflow

supports automation of meeting adds/changes/deletes
Other
4 stars 3 forks source link

Service Body field is inactive for "Change Existing Meeting" #157

Closed tempsaint closed 1 year ago

tempsaint commented 1 year ago

I was just testing and updating an existing meeting. I noticed there was nothing displaying in the Service Body field and it's not able to be selected when Change Existing Meeting is chosen. This doesn't allow a group to change the Area they choose to associate with.

I think this field needs to be editable just like the other fields. Not only is it possible for a group that's near a geographic border between Areas to want to switch Area service bodies, but it's possible a group switches location and wants to switch Area service body because of a geographic change.

tempsaint commented 1 year ago

I'm also wondering if the field data should be displayed even if the decision is made to keep the service body field inactive.

tempsaint commented 1 year ago

Interesting... when I just tried to submit the form, I received an error: ERROR: Form field "service_body_bigint" is required..

After the error, I was then able to select a service body, but I'm not seeing the Areas only the region... I'm double checking my configuration on this.

tempsaint commented 1 year ago

Hmm... I went back in an made sure all Area Service Bodies and the Regional Service Body were checked to Display on Form in the Service Bodies configuration. I thought maybe that's why the existing Area service body wasn't displaying on the Change Existing Meeting form. But even after making sure all of the settings were correct, the Service Body field on the form is still disabled until after I try to submit and receive the error. Then the field is editable, BUT, the only service body available for selection is the Regional service body. I'm going to wait a while and try again... there might be caching happening that is causing me to only see the regional service body.

tempsaint commented 1 year ago

The specific issue I was having was a result of caching... so everything is working properly. Although, this ticket addresses the broader issue of meetings changing service bodies. @nigel-bmlt - feel free to close the issue if you'd rather have a different issue/conversation about the broader issue.

nigel-bmlt commented 1 year ago

yah lets do that. I'll make a feature request to keep the discussion alive.