Page History
Advarsel |
---|
I stopped due to the fact (and built in automation has the same) - The event "page updated" or "page status changed" fires after the page is persisted with the content status. So - When my automation - or Scriptrunner listener - sets the content status back from "Verified" to "In Progress" - the will be an extra Page version (14) shown as "Verified" in the History, but it has actually changed from the actually verified (13): For this to be acceptable, we needed to change the Content Status due save, before creating a new version with "Verified" |
This was a test for using Content Status in Cloud:
...