Stage 4: Review, update & test process flows (Shopify & Brightpearl)

Introduction

Having installed the Shopify & Brightpearl blueprint, process flows are pre-configured and ready for you to review and test.

Some general considerations for review are noted below. Out of the box, flows provide base functionality/logic, but you may need to update (for example) mappings and/or scripts if your setup varies.

Process flows are described in the Available process flows section, including guidelines for shapes and configurations that can be changed.

General considerations for review

The following items should be considered when reviewing any process flows associated with this blueprint:

• Error handling for Shopify GraphQL

Error handling for Shopify GraphQL

Most flows installed via the Shopify & Brightpearl blueprint follow a try/catch design for high-level error handling. Typically, a shape will fail if it does not receive a payload, and it's this that triggers try/catch to 'catch' the error and follow the error handling path.

However, if a Shopify GraphQL connector fails to retrieve data, a payload is still returned, albeit containing an error message or error data - for example:

As such, a 200 (success) response is returned, and the logic for triggering a failure is bypassed. With this in mind, you may wish to include additional error handling throughout your process flows. For example, at the end of a flow (and/or at the end of any branches where data is expected for the next branch), add a route shape. From here, define one route for 'no errors' (no further action) and another for 'errors' (notify):

Here, if the route shape does not receive a payload, we know that the final, target connector didn't either, and the error route is followed. Otherwise, the flow/branch completes down the no errors route.