Enable an Event to Trigger an Outcome
The ArchiMate 3.1 specification does not currently allow the modeller to express that "an Event causes an Outcome" using the most intuitive notation in the toolbox for this purpose: the Triggers relationship.
In modelling The Open Group's own OpenFAIR risk methodology, we have the following statement in the Risk Assessment methodology (O-RA) Stage 1.
A Threat Agent breaches or impairs an information Asset that causes an observable Loss Event that has direct economic consequences (Primary Loss) and may have economic consequences initiated by reactions from others (Secondary Loss). Conceptually a Loss Scenario then looks like the figure below.
By modelling the 'Observable Loss Event' as a Business Event and the 'Direct Consequences' as an Outcome (both of which seem natural), its seems overly restrictive not to be able model the end-to-end chain as a series of 'Triggers'.
In the diagram below, we had to express this in a sub-optimal way - a directed association named 'materialises'