This page describes how to avoid unwanted workflow transitions (if using updated parameter on the state macro) when using the StiltSoft Talk app.

You will need Talk app version 2.6.0 or above.

The problem

In many cases, workflow state macros marked as final=true (published) also, use the updated parameter to automatically transition back to a draft state should the page be edited.

When a talk is added or resolved, data is stored back on the page (or blog post) causing the updated transition to occur – because the content has been updated.

From an end-user perspective, this seems odd, because they were only "talking" and not editing the page (they are unaware that the talking caused updates to the page).

The solution

The solution is to not use the updated parameter on the state macro, but instead use a trigger.

In order to prevent large numbers of notifications to page watchers, the StiltSoft Talk app marks its content updates as "Minor change" (the same as if you clear the "Notify Watchers" checkbox while editing a page). With triggers and conditions, we can filter out "Minor Change" events and then use an action to do the state transition.

For example, if your original workflow looks like this:


You would change it to this:



The following changes were made:

  1. We removed the updated=Draft from the Published state
  2. We replaced it with a pageupdated trigger filtered to non-minor updates ( isminorchange=false ) and, when applicable, invoke the set-state macro to transition the workflow to the Draft state.

With the updated workflow, minor changes are ignored, but normal changes will still trigger the transition.

(blue star) The isminorchange parameter is a workflow condition that can only be used in a pageupdated  or newsupdated trigger.

App configuration

There is also a Document Management app setting which may be affected by the Talk app updating content...

Page Update Reset ApprovalIf enabled, content updates will reset any approvals in an active content review.

See also