ACS "FILE_CREATED" Trigger - Error when trying to erase the nodeType constraint field
When we try to erase an existing value for the nodeType Field (of the ACS “FILE_CREATED” trigger), it raises an error. Plus, after erasing the value, if you come back to this config page you’ll see that the nodeType is not blank but valued with the old value (please see the attachment).
Steps to reproduce
1. Create a content trigger with the “FILE_CREATED” Event source
2. Specify a value for the “nodeType” input value & Save the trigger.
3. Remove the value set previously. An error “cannot read property value of ‘null’” is now raised.
4. Save the trigger again and then refresh the page. You’ll see that the previous value is now again selected for the “nodeType” input value as if the field was mandatory.
Erase the “nodeType” value shouldn’t raise an error. Same if you refresh the page after removing the value, “nodeType” value should be set to a blank value and not to the old value.
When you remove an existing value for the nodeType Field, an error is raised. Plus, after deleting the value, if you refresh the page you’ll see that the nodeType is not blank but set to the old value.