We use cookies (just for analytics) on this website. If you continue we will assume you are happy with it. ok

BeBanjo

Back to release notes

Job_updated events reflect changes to the end date

Release date: July 17th, 2020 (Revision 1), print this page

Good news! You can now rely on job_updated events to tell you when a job’s ends-at has changed.

We have included an ends-at value in the changes attribute so that you can detect these changes in external systems. Here is an example of what a job_updated event looks like now:

<?xml version="1.0" encoding="UTF-8"?>
<events type="array">
  <event>
    <id type="integer">111234847</id>
    <event-type>job_updated</event-type>
    <timestamp type="datetime">2020-08-07T10:44:41Z</timestamp>
    <changes>ends-at</changes>
    <link rel="self" href="https://staging-sequence.bebanjo.net/api/events/111234847"/>
    <link rel="subject" href="https://staging-sequence.bebanjo.net/api/work_areas/280/jobs/5081171"/>
  </event>
</events>

The ends-at value has been added to the list of values already available for the changes attribute in a job_updated event:

  • name
  • due-date
  • ends-at
  • licensor-name
  • tasks-status
  • assets-status
  • title-external-id
  • tag-list

You can have a look at the updated Event API documentation here.

We hope you find this useful! Don’t hesitate to contact your TAM if you have any questions.

References

  • sequence#1099 job_updated events should reflect changes to the end date