Picture of Configuring Connect: Flow for different suppliers  | CI_Flow_005

Configuring Connect: Flow for different suppliers | CI_Flow_005

Here, we will learn how we can configure the Connect: Flow plugin to push different information to different suppliers specified on our storefront. For example, if one supplier expects the data via email and another expects it via FTP then we are able to accomplish that using this functionality. Suppliers are configured independently within Infigo, and creating supplier entries will not be the primary focus of this tutorial. Other Infigo Academy resources exist around that topic. Other than with Connect: Flow, suppliers are primarily used with Infigo's RFQ module.

Tutorial Video Transcript

00:00:08:18 - 00:00:09:18
Here we learn how we

00:00:09:18 - 00:00:13:07
can configure the Connect Flow plugin
to push different information

00:00:13:07 - 00:00:16:15
to different suppliers
specified on our storefront.

00:00:17:12 - 00:00:22:06
For example, if one supplier expects
the data via email and another expects

00:00:22:06 - 00:00:26:22
it via FTP, then we're able to accomplish
this using this functionality.

00:00:28:03 - 00:00:31:01
Suppliers are configured
independently within Infigo..

00:00:31:10 - 00:00:35:28
And creating supplier entries will not be
the primary focus of this tutorial

00:00:36:14 - 00:00:37:11
Other Infigo.

00:00:37:11 - 00:00:41:12
Academy resources exist around that topic
other than with connect

00:00:41:12 - 00:00:44:15
flow suppliers are
primarily used with Infigos.

00:00:44:15 - 00:00:47:16
RFQ module.

00:00:48:29 - 00:00:51:26
Okay,
so firstly, lets navigate to the suppliers

00:00:51:26 - 00:00:54:04
area.

00:00:56:14 - 00:00:57:13
Now if preconfigured,

00:00:57:13 - 00:01:00:23
a couple of sample suppliers here.

00:01:00:23 - 00:01:03:14
So suppliers are configured
in their own unique area

00:01:03:14 - 00:01:06:06
that we can see here
within Infigo admin.

00:01:06:17 - 00:01:09:09
The setup is pretty much straightforward
with suppliers

00:01:09:09 - 00:01:13:15
requiring contact details
such as an address and an email address.

00:01:13:26 - 00:01:18:07
You can get to that either by creating
a new supplier or editing an existing one.

00:01:18:07 - 00:01:20:09
Here.

00:01:21:09 - 00:01:23:27
Now let's navigate to the supplier section

00:01:23:27 - 00:01:34:04
on the Connect Flow Configuration Settings
page.

00:01:34:04 - 00:01:37:04
Select one of your suppliers
and then click

00:01:37:04 - 00:01:39:11
on Add Supplier.

00:01:40:29 - 00:01:43:12
Click on the
Go to Arrow button on the left hand

00:01:43:12 - 00:01:47:22
side of the supplier
to show additional details.

00:01:53:11 - 00:01:55:18
The majority of these options
are identical

00:01:55:18 - 00:01:59:05
to what we see in the main connect
flow configuration settings.

00:01:59:18 - 00:02:02:26
So the version of these settings
under each supplier allows you

00:02:02:26 - 00:02:07:11
to configure the behavior of the plugin
on a supplier by supplier basis.

00:02:08:09 - 00:02:13:04
For example, if a supplier has product
one or a sample product mapped to them,

00:02:13:12 - 00:02:16:29
but not product to an order,
including a job of product,

00:02:16:29 - 00:02:20:23
one will trigger this version
of the connect flow settings.

00:02:21:16 - 00:02:24:02
A job of product two will either trigger

00:02:24:02 - 00:02:26:28
the settings based on a supplier
with product two.

00:02:27:16 - 00:02:30:10
Alternatively,
if product two is not mapped to

00:02:30:10 - 00:02:33:18
any supplier,
then the main settings will be utilized.

00:02:33:19 - 00:02:38:06
So the one we've we've been configuring
during the last tutorial is.

00:02:38:27 - 00:02:40:28
So we do
have a couple of additional settings here.

00:02:40:28 - 00:02:44:27
So we do have this mode option
over on the right hand side.

00:02:45:15 - 00:02:48:05
This allows you to select
whether all products mapped to

00:02:48:05 - 00:02:52:05
this supplier trigger
the supplier actions of this plugin.

00:02:53:01 - 00:02:55:16
Two options include all linked products.

00:02:55:28 - 00:02:59:05
If you have created supplier
mapping entries for a product,

00:02:59:05 - 00:03:04:16
which is true for two suppliers,
both suppliers would get the output.

00:03:04:16 - 00:03:09:20
And then also we have only use
best matching supplier if you have created

00:03:09:20 - 00:03:14:00
supplier mapping entries for a products,
which is true for two or more suppliers.

00:03:14:23 - 00:03:18:13
Only ever one
supplier will get the product ordered

00:03:18:17 - 00:03:22:09
and it will be the one that's considered
most relevant.

00:03:23:21 - 00:03:24:27
If utilizing web

00:03:24:27 - 00:03:29:21
hooks, do note that the link will change.

00:03:29:21 - 00:03:32:13
Dependent on the supplier that we are

00:03:32:24 - 00:03:35:16
writing to here.

00:03:38:16 - 00:03:41:21
Okay, now scroll down the page
a little and go to the message

00:03:41:21 - 00:03:45:26
template instructions.

00:03:45:26 - 00:03:48:25
In order to trigger status updates
via web hooks,

00:03:49:04 - 00:03:53:10
the admin would be required to create
some new email message templates.

00:03:53:20 - 00:03:56:17
so these templates can target
individual suppliers,

00:03:56:24 - 00:03:59:05
so they can receive
particular information.

00:03:59:20 - 00:04:02:19
When a specific job status is set.

00:04:03:15 - 00:04:06:27
Alternatively,
the templates can be a general update.

00:04:07:26 - 00:04:11:11
This is essentially a fallback
in case no specific message

00:04:11:11 - 00:04:15:17
template has been defined for a supplier
or status configuration.

00:04:16:17 - 00:04:21:00
If a supplier is used within the connect
flow settings, we will see

00:04:21:00 - 00:04:26:01
if there is an active message template
for the current status and supplier.

00:04:26:23 - 00:04:29:25
If yes, then we'll use
that particular template, but

00:04:29:25 - 00:04:32:28
otherwise will check if there is an active
message template named.

00:04:33:04 - 00:04:35:20
Production Management dot generic mis

00:04:35:29 - 00:04:38:16
dot status update dot general dot.

00:04:38:21 - 00:04:41:10
And then the status name in curly
brackets.

00:04:41:10 - 00:04:45:03
If that's available, then we'll use that.

00:04:49:12 - 00:04:51:09
So just around this off, let's have a look

00:04:51:09 - 00:04:55:06
at creating new message templates
which can be utilized in this sense.

00:04:55:06 - 00:04:59:07
So I'm just going to go to the email
message templates part of my Infigo

00:04:59:07 - 00:05:01:18
admin area.

00:05:04:19 - 00:05:05:29
Click on the custom tab

00:05:05:29 - 00:05:09:08
at the top of the screen.

00:05:09:08 - 00:05:14:06
And then we have the ability
to add a new message template.

00:05:17:04 - 00:05:19:06
Now the name of this template

00:05:19:06 - 00:05:21:08
must be correctly populate it

00:05:22:07 - 00:05:25:06
in order to well for this function to work

00:05:25:06 - 00:05:29:00
as it's intended
and applicable naming conventions are.

00:05:29:28 - 00:05:33:09
So for specific suppliers
you would have something like

00:05:34:06 - 00:05:37:02
this.

00:05:37:02 - 00:05:40:13
So product management,
generic and status update.

00:05:40:26 - 00:05:45:00
Then you would have supplier
name and status name.

00:05:45:00 - 00:05:47:07
If it's something
that applies to any supplier,

00:05:47:11 - 00:05:50:02
then you wouldn't need
the specific supplier section of that.

00:05:50:02 - 00:05:52:26
So I could just put something like this

00:05:53:02 - 00:05:56:00
and then replace what's in the curly
brackets with the status

00:06:00:18 - 00:06:01:01
variable.

00:06:01:01 - 00:06:05:18
Status options that can be utilized in
here can be found is extra information

00:06:05:29 - 00:06:08:14
on the connect flow configuration screen.

00:06:09:01 - 00:06:12:24
So if you go down to webhook actions,
click on more information

00:06:12:24 - 00:06:16:29
for the status updates
and you can see the available statuses.

 

Incomplete
Step by Step Guide

Configuring Connect: Flow for different suppliers

Here, we will learn how we can configure the Connect: Flow plugin to push different information to different suppliers specified on our storefront.

For example, if one supplier expects the data via email and another expects it via FTP then we are able to accomplish that using this functionality.

Suppliers are configured independently within Infigo, and creating supplier entries will not be the primary focus of this tutorial. Other Infigo Academy resources exist around that topic.

Other than with Connect: Flow, suppliers are primarily used with Infigo's RFQ module.

Creation Date: Jul 13, 2023
Created By: Sam Webster

1. Navigate to Suppliers

Navigate to Suppliers

2. Supplier configuration

Suppliers are configured in their own unique area within the Infigo admin area.

Their setup is straightforward, with suppliers requiring contact details such as an address and email address.

Once the supplier is created, mappings can be applied. These allow admins to define which products, categories, etc are applicable to that particular supplier.

Supplier configuration

3. Navigate to the Suppliers section on the Connect: Flow configuration settings. Select a supplier and click Add supplier.

Navigate to the Suppliers section on the Connect: Flow configuration settings.
Select a supplier and click Add supplier.

4. Click the > button to show additional details

The majority of these options are identical to what we see in the main Connect: Flow configuration settings.

The version of the settings under each supplier allows you to configure the behaviour of the plugin on a supplier-by-supplier basis.

For example, if a supplier has "Product 1" mapped to them, but not "Product 2", an order including a job of "Product 1" will trigger this version of the Connect: Flow settings.

A job of "Product 2" will either trigger the settings based on a supplier with "Product 2" mapped to them. Alternatively, if "Product 2" is not mapped to any supplier then the main settings will be utilised.

Click the > button to show additional details

5. Select a product mode

This option allows you to select whether all products mapped to this supplier trigger the supplier linked actions of this plugin.

Include all linked products - If you have created supplier mapping entries for a product which is true for 2 suppliers, both suppliers would get the output

Only use the best matching supplier- If you have created supplier mapping entries for a product which is true for 2 suppliers, Only ever one supplier will get the product order..

Select a product mode

6. Webhook actions…

If utilising webhooks, note that the link will change based on the supplier.

Webhook actions…

7. Scroll down the page and navigate to the Message Template instructions

In order to trigger status updates via webhooks, the admin would be required to create some new Email Message Templates.

These templates can target individual suppliers, so they receive particular information when a specific job status is set.

Alternatively, the templates can be a general update. This is essentially a fallback in case no specific message template has been defined for a supplier/status configuration.

If a supplier is used within the Connect: Flow settings, we will see if there is an active message template for the current status and supplier.


If yes we will use that template, otherwise we will check if there is an active message template named "ProductionManagement.GenericMis.StatusUpdate.General.{statusname}" available and use that.

Scroll down the page and navigate to the Message Template instructions

8. To create a new message template, navigate to Email Message Templates

To create a new message template, navigate to Email Message Templates

9. Click on Custom

Click on Custom

10. Click on Add New

Click on Add New

11. Click on Name

Click on Name

12. The "Name" field must be correctly populated for this function to work

Applicable naming conventions are:

For specific suppliers:

ProductionManagement.GenericMis.StatusUpdate.{SupplierName}.{statusname}

For any supplier:

ProductionManagement.GenericMis.StatusUpdate.General.{statusname}

Available status options include:

shipped -> can use TrackingNumber

printed

awaitingApproval

awaitingData

awaitingParts

awaitingProof

inArtworking

inFinishing

inPacking

inProduction

inReprographics

onHold

misAssetsOk

misAssetsFailed

cancel

custom -> can use CustomStatusHeader/CustomStatusDescription properties

The "Name" field must be correctly populated for this function to work
Alternate Search Terms