Allow Notification Rules to use SQL like Report "Advanced SQL Conditions"

by Paul Thompson on September 07, 2018

Allow Notification Rules to use SQL to detect the conditions for determining if a Notification should be fired.  The SQL would be similar to the "Advanced SQL Conditions" used by Reports.  This would require a "macro" syntax for passing the TS_IDs of the current item's table, the current item, current user and perhaps current Project, State and Transition to the user-supplied SQL clause. 

I forsee the user-supplied SQL being used in an "EXISTS" clause.

  • I would like to fire notifications when the field referenced by a sub-relational field changes, but the item doesn't change.  SBM is currently not capable of this behavior.

     

    Using the example context from the App Admin manual:

    When a Sub-Relational field is selected as the object, notifications are fired when the field's value is changed in an item using the workflow for which the rule is defined.  For example, if your Issues workflow contains a relational field to the Incidents table and a Sub-Relational field to the Company field within that table, you can create a notification that fires when the selection in the issue changes the value of the Incident Company field. 

     

    The Notification is on the Issue, the Issue is not being transitioned.  The related Incident is updated and the Company field is changed.  From the Issue’s “point of view”, it’s Company (sub-relational field) just changed.  I would like to fire a Notification under these conditions.

     

     

     

    When a Sub-Relational field is selected as the object, notifications are fired when the
    field's value is changed in an item using the workflow for which the rule is defined.
    For example, if your Issues workflow contains a relational field to the Incidents table
    and a Sub-Relational field to the Company field within that table, you can create a
    notification that fires when the selection in the issue changes the value of the
    Incident Company field.
  • Please login to view any attachments.

  • There are no user comments for this idea.
    Already have an account? or Create an account
     

PrintEmail

Recent Tweets