PO lines editability changes

Changes coming the week of July 28th to simplify the current PO line and PO status experience.

Why are we making these changes?

To simplify both the buyer's experience and integrations built on top of ION's API, we are making the following changes. Not only does this simplify the experience, but it also makes it more intuitive and easier to navigate cleanly between purchase order states and avoids situations where you get blocked as you need to receive more of a fully received PO line.

What are the changes?

1. The purchase order line status will now be calculated, and the editability of the PO lines will be tied to the PO status. All properties and attributes in a purchase order line are editable if its corresponding PO is in a Draft status, regardless of the status of the PO line.

   • To edit a Purchase Order Line, you will need to change the PO to Draft . For all of our customers, you should remain unaffected, as this was a mostly hidden change from the ION application UI.

   • For example, a PO line may be fully received, but we will allow you to increase the quantity of the PO line if the PO is in Draft, if you received more than what was written on the PO line.

The only PO line attributes that can be edited when the Purchase order is not in a Draft status are:

• ETA

• Paid status

• Custom attributes

1. You will no longer have the ability to manually change the Purchase Order Line status to anything outside of Canceled. Lines can only be uncanceled when their PO is in Draft state.

2. We are deprecating the Approved and Requested statuses for Purchase Order lines. They will be removed from ION moving forward. The Purchase Order Line will remain in Draft until the Purchase Order is placed in an Ordered status, then the PO line will be in an Ordered status.

There are breaking changes as listed below, please follow these instructions to maintain integrity to any integration you have built with the purchasing module

Actions To Take

If you are:

• Using the PO Line Status of Approved or Requested or

• Manually updating the PO Line Status to any status that is not Canceled.

through the API, webhooks or rules, these will no longer work due to the above changes. The API calls, webhooks, and rules will need to be updated to use the purchase order object instead.

We strongly recommend using the purchase order status going forward for all webhooks, rules, queries, and mutations.

For example:

If you use PO Line webhooks and check if the first PO line in a purchase order is Approved before creating a purchase order in another system, then this will need to be changed to now check the status in the Purchase Order webhook.

• From: PURCHASE_ORDER_LINES Resource and UPDATE Action

• To: PURCHASE_ORDERS Resource and UPDATE Action

Other API Changes

With these changes, we've cleaned up how editability is returned in our API.

editable field is now returned as a Boolean instead of a String field.

Old:

purchaseOrderLine {
    editable: "true"
}

New:

purchaseOrderLine {
    editable: True
}