deprecated

Deprecating non-compliant JSON in incoming requests

Historically, Targetprocess API supported non-standard JSON in incoming requests. The most prominent example is omitting quotes around field names and using multi-line strings. For example, the following API v1 request was allowed:

deprecated

Retiring of custom fields v1

The transition from custom fields v1 to v2

added

Streaming Service

We now have available a streaming service that allows users to export data from Targetprocess via APIv2 read calls, without paging and without impacting the overall performance.

fixed

Changes to working with Tags in Automation Rules

📘

The fixes will be rolled out to all public clouds in the beginning of April, 2020

deprecated

Retiring of Webhooks

The time has come for the Webhooks plugin to retire. It is being replaced with the Automation Rules, which can do everything Webhooks did and a lot more.

improved

Changes in History APIv2 in Targetprocess 3.13.8

Ever since we have introduced the notion of Simple History in the version 3.10.9, we have kept both endpoints /api/v2/*histories and /api/v2/*simplehistories to point to Simple History resource for the purpose of back compatibility.

improved

Changes in History APIv1 in Targetprocess 3.13.5

Ever since we have introduced the notion of Simple History in the version 3.10.9, we have kept both endpoints /api/v1/*histories and /api/v1/*simplehistories to point to Simple History resource for the purpose of back compatibility.

added

System custom fields in Targetprocess 3.11.6

Starting with Targetprocess version 3.11.6 you can mark a custom field as System:

added

New field for Comments in Webhooks in Targetprocess 3.11.6: RawDescription

Starting from Targetprocess 3.11.6 there is one more field available for Comments in Webhooks: RawDescription. The difference between Description and RawDescription field is only in the way it handles @mentions in comments.

deprecated

Retiring of IsPrivate field for Impediments in Targetprocess 3.11.3

We have recently made a decision to deprecate private impediment and have all the impediment in the system public. Mode details and reasons behind this decision is available in our blog: https://www.targetprocess.com/blog/2017/03/deprecating-private-impediments/