Description:
The Event Collector (EC) schema can be extended to introduce a custom attribute. Doing so requires the creation of a custom component and the attributes associated with it. The custom audit data is written into the extended attribute table EC_EVENT_ATTR. If the custom attribute is passed into the EC Event API's with an invalid value for its declared data type, the event itself is successfully populated into the EC_EVENT table. However, this invalid custom attribute is not written into the EC_EVENT_ATTR table.


Symptoms:
The invalid custom attribute value is not getting populated into the EC_EVENT_ATTR table. Though there is an entry in the EC_EVENT table.

Below is an example how this issue can be reproduced -

1). Register the component. See the registerComponent.xml file.

2). Register an attribute of type DATE, named as “NLSONPASSDT”. Use the componentId from the response of the register component (Response of registerComponent.xml). See the registerAttributes.xml file. 

3). Once the attribute is registered, it will be listed in EC_ATTRIBUTE table.

4). Send an event with this custom attribute containing an invalid millisecond.

<value>2015-10-10T13:58:59.35-04:00</value>  <--- Notice .35 is not a complete millisecond declaration, it needs to be three digits.

Obtain the attribute ID from the response of register attributes (Response of registerAttributes.xml). See the sendEvent.xml file.

5). An entry with message_id=”CUSTOM_AUDIT” is added to the EC_EVENT table. However, there will not be an entry in EC_EVENT_ATTR table.

6). Change the value as follows and resend the event. An entry can be seen in the EC_EVENT_ATTR table.

<value>2015-10-10T13:58:59.350-04:00</value>
Cause:
This is a defect. Contact TIBCO Support to check if this has been fixed.

An invalid Event Collector custom attribute value is ignored.

Workaround. Confirm that the custom attributes are set as per their data type.

For a DATE type attribute.

1). Always ensure that milliseconds are supplied in a three digit format.

2). Do not include milliseconds if second granularity is acceptable.

3). Use a value which complies with a supported literal format.

JIRA : WRM-8652 has been opened to log a warning/error when an attribute value is ignored.

See the attached file for reference. (Filenames: registerAttributes.xml, registerComponent.xml, Response_of_registerAttributes.xml, Response_of_registerComponent.xml, sendEvent.xml).

https://docs.tibco.com/pub/amx-bpm/3.1.0/doc/html/bpmhelp/GUID-0353B84C-C43C-49C5-A5AE-DA893B55E4B0.html
https://docs.tibco.com/pub/amx-bpm/3.1.0/doc/html/bpmhelp/GUID-488A8CCF-927B-4397-A5C7-1B0E4B2025E4.html
https://docs.tibco.com/pub/amx-bpm/3.1.0/doc/html/bpmhelp/GUID-D522CAE2-DDFF-414B-8F61-E9BACBEAF1FE.html