Automation Advice - Catching Content.BeforeUpdate after Abuse Appeal rules not-abusive

Have you investigated the "Forbidden Word Counts" automated abuse plugin included with Community? (Administration > Moderation > Abuse Automation > Forbidden Word Counts) This may cover a lot of the functionality you're looking for here.

Otherwise, you can look at adding additional checks in the BeforeUpdate logic, for instance to check if the content is being changed from not approved to approved, and prevent putting the user back in moderation in that case.

Yes, the forbidden word counts is something we have enabled and configured for words. It hadn't always caught things before the emails to subscribers went out which is why we had actually blocked the characters in a customization of the ui.js on the relevant post code, but that's a pain to support upgrade to upgrade and automations are safer for upgrades.

Could you recommend documentation to review to catch the content transition from not approved to approved?

The common design pattern when checking for changes to an entity is to handle the BeforeUpdate event, and in that event retrieve the item from the API using its id, etc. Then you can compare the values provided in the BeforeUpdate event arguments (the "new" values that have yet to be applied) to the values from the API (the "old" values). For instance, you could compare the IsEnabled flag to see if the content is changing from not enabled to enabled.

A few notes:

• I'm not sure how you are using the term, but ReviewableContent refers to a specific Review Workflow process implemented only on specific content types, which is a different use case than abuse checking.
• I'd still recommend you take a look at the example IAbuseDetector plugin type, as this plugin type (and its controller) exposes methods for interacting directly with the Moderation Queue. You can handle events in this plugin like in an automation.

The common design pattern when checking for changes to an entity is to handle the BeforeUpdate event, and in that event retrieve the item from the API using its id, etc. Then you can compare the values provided in the BeforeUpdate event arguments (the "new" values that have yet to be applied) to the values from the API (the "old" values). For instance, you could compare the IsEnabled flag to see if the content is changing from not enabled to enabled.

A few notes:

• I'm not sure how you are using the term, but ReviewableContent refers to a specific Review Workflow process implemented only on specific content types, which is a different use case than abuse checking.
• I'd still recommend you take a look at the example IAbuseDetector plugin type, as this plugin type (and its controller) exposes methods for interacting directly with the Moderation Queue. You can handle events in this plugin like in an automation.