Better document factDefinitions

Describe your use-case which is not covered by existing documentation.

The readme has a nice looking example message:

However I can't see any documentation on how to achieve this.

The closest thing I see is this:

Lines 145 to 147 in ddd8cd0

    
                       office365ConnectorSend webhookUrl: "https://outlook.office.com/webhook/123456...", 
        
                           factDefinitions: [[name: "fact1", template: "content of fact1"], 
        
                                             [name: "fact2", template: "content of fact2"]]

I'm guessing that the fact names correspond to things like Status or Remarks, but I have no idea about what "template" I should be using to match the screenshot from the documentation.

Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.

No response

Some of them are available when you use git plugin that integrates Jenkins and the PR, however this plugin is deprecated nowadays.

Is there a way to mimic that behaviour using factDefinitions?

@damianszczepanik

however this plugin is deprecated nowadays

This in the sense of this connector?

Referenced plugin is deprecated, office-365-connector-plugin is not

	office365ConnectorSend webhookUrl: "https://outlook.office.com/webhook/123456...",
	factDefinitions: [[name: "fact1", template: "content of fact1"],
	[name: "fact2", template: "content of fact2"]]