Hi there,
thank you for your awesome work.

I have a little problem here: the test_card works perfectly with out Teams-Channel.
But the following does not work for me:

Send a card with a list of facts

content = {
title: "Teams Connector Readme",
subtitle: "A list of facts",
facts: {
"Usage": "Testing the facts Card"
}
}
TeamsConnector::Notification::Message.new(:facts_card, "This is a summary", content).deliver_later

C:/Users/username/.gem/gems/teams_connector-0.1.5/templates/teams_connector/facts_card.json.erb:11:in deliver_later': undefined method present?' for {:Usage=>"Testing the facts Card"}:Hash (NoMethodError)
from C:/SVSW/Ruby/lib/ruby/2.7.0/erb.rb:905:in eval' from C:/SVSW/Ruby/lib/ruby/2.7.0/erb.rb:905:in result'
from C:/Users/username/.gem/gems/teams_connector-0.1.5/lib/teams_connector/notification.rb:21:in deliver_later' from tc.rb:23:in

Do you have any ideas or tips?

Thank you!

--Werner.

Many systems require a persistent papertrail of events and actions for traceability.

Currently TeamsConnector does not log or store a record when a notification was sent and whether this was successful or not.

To fix this a logger should be configurable which allows the output to different targets.

• stdout
• File
• Rails ActiveRecord
• Other (user configurable)

Concept

During configuration a logger can be defined. The interface is similar to a Rails ActiveRecord to allow easy integration without a layer in between.

This logger is a class that defines the class method ::create for initializing a new notification entry. For persistent papertrails the result must contain an id that will be passed to the template (e.g to display it in the notification).
The entry will be updated after the HTTP request is made. For this the class must support ::find(id) and the object must implement the #update method.

The attributes of the entry are:

• id (integer/string)
• target_channels (string)
• created_at, updated_at (timestamps)
• template (string)