-
Notifications
You must be signed in to change notification settings - Fork 181
Description
Description
We are updating the IBM Resilient case connector again to be more user-friendly. In a previous release, we added the ability to add additional fields to the connector through a JSON editor.
While the JSON editor unblocks some of our customers, it does not provide a great UX. E.g. Select item values need to be ids but the ids are not known to customers.
With this change we are providing actual form elements that have the correct ids and labels as they have been defined in the customer's IBM resilient instance.
Misc. notes
- Required IBM fields will now appear as required in the case creation form (in Elastic).
- Empty values in boolean fields are interpreted (auto-set?) as false.
- Fields that are set on incident creation or change (e.g., closing the incident) cannot be selected from the Additional fields field. This detail should be added to the docs.
Resources
Which documentation set does this change impact?
Elastic On-Prem and Cloud (all)
https://www.elastic.co/docs/reference/kibana/connectors-kibana/resilient-action-type
Feature differences
They will be the same
What release is this request related to?
9.3
Serverless release
The week of Dec 1
Collaboration model
The documentation team
Point of contact.
Main contact: @janmonschke
Stakeholders: @melissaburpo