Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-15154

Assets for JSM Trigger: Provide a more specific Object Updated Trigger mimicking the Field Changed Trigger.

XMLWordPrintable

    • 1

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      The Object Updated Trigger isn't specific enough.
      Some Rules only need to run when specific Attributes are updated.

      Suggested Solution

      Allow for selecting which Attributes to watch for updates in the Object Updated Trigger.
      Alternatively, make the Object History/Activity available via Smart Values.
      Then Conditions could be used to achieve the same effect.

      Workaround

      Currently, a known workaround is to use a Send Web Request Action to get the Object History via the Assets REST API, then check to see if the most recent entry is for the appropriate attribute(s).

      This consumes Automation Executions every time though, so be mindful of this.

      Also, be mindful that this workaround isn't full-proof. Due to timing issues between Assets & Automation, if an Object receives a series of quick updates, the Automation can "miss" the correct entry in the History, causing it to not run as expected.

          Form Name

            [JSDCLOUD-15154] Assets for JSM Trigger: Provide a more specific Object Updated Trigger mimicking the Field Changed Trigger.

            There are no comments yet on this issue.

              36bd3fea80e3 Makarand Gomashe
              992127aa63ec Payden Pringle
              Votes:
              14 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: