Yellow messages (business constraints) in practice

[stefjoosten]

Problem

A yellow message contains the violations of a business constraint (aka process rule) to all users with the ROLEs that maintain that business constraint. When an information system is being used by one or a few users, this is no problem. In reality, information systems serve many users simultaneously. In such cases we need a mechanism to get yellow messages only to the people who need them.

Use cases

1. In the Kruk.adl prototype, we integrate three small demos into one. Two of the demos each start with one of their business constraints being violated, so we'd like to see one yellow message bar in each demo. However, we get to see both yellow bars in each of these demos because they are combined in the same script.
2. In the Semantic Treehouse project of TNO, Ampersand is running in production with many different users. The authors have systematically avoided using business constraints, precisely for this reason. Instead, they have implemented an exec-engine rule that triggers a user to do whatever is needed.

Solution

@sjcjoosten, I understand you have an idea? Please describe it here by editing this comment, so the proposed solution appears in the first comment of this issue.

I suggest that @hanjoosten, @Michiel-s, @sjcjoosten, and @stefjoosten discuss this issue further.