Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Summary

This page shows some some diagrams illustrating the role played by JEMH Field Processors, that are responsible for parsing incoming messages and building a map of data to be used during issue creation/update.

 

 

When the Field Processor consumes the email, it generates a map of keys and values, usually text in content.  The keys can be either the 'as seen on screen' name of an existing Custom Field, or some pre-defined values (e.g. IJEMHFieldProcessorKeys.KEY_LABELS, IJEMHFieldProcessorKeys.KEY_DESCRIPTION etc).  IJEMHFieldProcessorKeys is defined in the API package that third party Field Processors need to add their classpath.

  • No labels