We have workflows that update entries after creation, meaning they are shown as new/unread even for the user that just created the item... I'd suggest to split the modified property so that workflows update another property than a human. It will of course also be needed to have the choice (in the UI or programmatically) to show as unread only the entities that are modified by humans (or workflows, though we don't need to know that for now in our solution).


  • Agree! For certain scenarios and use cases it would be good to be able to configure if an entry should be shown as modified or not when a workflow transition / state change occured.