[SOLVED] Event data status field in content changed web hook not as expected

Hi,

We’re using a rule to call a web hook when the content changes for a particular schema.
What we are seeing is that when a new draft version of a previously published piece of content is changed the event data sent to the web hook still has the status as “Published”

e.g.

{
“type”: “DocumentCreated”,
“payload”: {
“$type”: “EnrichedContentEvent”,
“type”: “Created”,
“id”: “f8dc96d0-2d4a-4e19-a626-c1f563b57001”,
“created”: “2021-06-16T21:26:12Z”,
“lastModified”: “2021-07-07T10:01:03Z”,
“createdBy”: “subject:606c28e95240954b9ea79fdb”,
“lastModifiedBy”: “subject:606c28e95240954b9ea79fdb”,
“data”: {

}
},
“status”: “Published”,
“partition”: 3897648,
“schemaId”: “5408b06a-f59f-43f8-b55c-f3a5537b16c6,document”,
“actor”: “subject:606c28e95240954b9ea79fdb”,
“appId”: “deaf9eb9-e52d-4b23-a310-66f18a143921,ieg4-council-web-dev”,
“timestamp”: “2021-07-07T10:01:03Z”,
“name”: “DocumentCreated”,
“version”: 2
},
“timestamp”: “2021-07-07T10:01:03Z”
}

I don’t know if this is by design or a problem, but we were expecting the status to be “Draft” or whatever stage currently set in the workflow.

Is there any way to get the current status of the latest version in the event data payload please?

Environment

  • [X ] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [ ] Cloud version

Version: [5.6.0]

Browser:

  • [ ] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [X ] Edge

Others:
Self hosted in Azure as per instructions here https://docs.squidex.io/01-getting-started/installation/platforms/install-azure

Thanks
Andrew

Yes, there is a property “newStatus” missing. Each content has 2 status actually.

Thanks
I may have mis-understood the reply but do we need to be on a later version to see this property, or it’s coming down the line?

It needs to be implemented.

Hi, Sebastian. I can see [Solved] in header. Does that mean “newStatus” got in place in API?

It has nothing to do with the API…