Behaviours

Standard behaviour

In the endpoint example in the configuration we are using the method: parse_email_as_communication(). The description of this method is as follows:

Processes an email data and fills the given unit of work with limeobjects to create and returns the unsaved sys_communication object.

• It will automatically create sys_follower for each new CC:d e-mail and the sender if it's also new.
• It will create sys_communicationdocument for each attachment in the E-mail. (It will only create attachments that is supported by Lime MS Inbox)
• It will create one sys_communication connecting it all together.

This is the standard behaviour and if that's enough for your customer you are all set with using the example.

Contribute or just found flaws?

If you feel like some property or helper method is missing, or if you just have an idea of another flow for Communication flow. Please share your thoughts in Github, by creating an issue