Below is a summary of the known issues and their corresponding fixes or workarounds for the CTK Email Parser.
Issue 1.0.1:
When a user creates an Email Parser for an ‘Event’ object and completes the email parser requirements, an error log related to the ‘Event’ object is generated in the “Email Parser Jobs” section. The error states that the ‘Duration’ field is required, but when building the “Email Parser action,” the mapping field for ‘Duration’ is not highlighted as required.
Workaround:
It appears that the Salesforce backend metadata does not designate the fields ‘Duration,’ ‘StartDatetime,’ and ‘EndDatetime’ as mandatory. As a result, the automation displays these fields as non-required. To address this, we need to highlight the required field from the backend.
Issue 1.0.2:
User is not able to get the ‘Boolean” value within the ‘Target Entity’ object’s list which should be available within the Account Contact Role object. As per the backend norms IsPrimary in ‘Account Contact Role’ object is Boolean type but, when user creates a ‘Field Parser’ there user is not getting the Boolean value in ‘Output Type’ field.
Workaround:
It seems this is a known limitation. Boolean values are not supported.
Issue 1.0.3
Users are unable to retrieve data from the Email Parser Job when extracting data from the “Source” as Attached File Names.
Workaround:
It seems this is a known issue. This is out of scope. This is a salesforce (platform) limitation, so can’t fix.
Issue 1.0.4:
Users are unable to retrieve data from the Email Parser Job when extracting data from the Header. Additionally, the filter criteria do not match with the given scenario, resulting in the value not being extracted.
Workaround:
This issue is also a known problem. However, it is planned to be addressed in future releases, and the implementation for this specific functionality will be included in those updates.