-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
Minor
-
Issue Summary
When using a Create Object Action, you have to select the Schema, then the Object Type to create an Object in. For the Object Type Dropdown, the dropdown populates with the first 25 Object Types alphabetically. You can search for the rest by typing into the Field, and if you select one that's past those first 25 in the list, the Field will populate with that Object Type's name briefly before disappearing. This is a UI issue, as the actual value in the Field is still the selected Object Type.
Steps to Reproduce
- Configure the Create Object Action in an Automation Rule while having >25 Object Types in the selected Schema.
- Filter for an Object Type that's not in the initial dropdown and select that one.
Expected Results
The selected Object Type will visually remain in the Field.
Actual Results
The selected Object Type will disappear from the Field, making it appear like it has no value, even though it does have a value. This can be verified by saving & exporting the Automation Rule. The JSON for that Action will have the correct Object Type.
Workaround
There is no workaround. There is not an issue with saving the Rule and letting it run as normal, as this is a UI bug, not a functionality bug.
- duplicates
-
JSDCLOUD-12354 Assets Automation: Unable to select Object Type/Schema in any Assets action if the schema has many Object Types or Schemas
-
- Closed
-