[frontend] Add support for dynamic configurable required fields to Events #8960
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
This PR builds upon the capabilities from #6972. This PR will add all capabilities from the previous PR to the 'Events' section of the platform, to include creating and editing the following entity types:
Related issues
Checklist
Further comments
The customization menu for 'Observed Data' includes a 'Content' field, but there is no 'Content' field in either the create or edit form, so requiring this field makes it impossible to submit the form.
Incident and Observed Data creation forms include the field objectLabel but the edit forms do not. This field is not in the 'Customization' menu. Adding it would break the edit forms.