Message-ID: <408819619.7.1711661421803.JavaMail.tomcat8@139-162-214-5> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_6_1612889959.1711661421622" ------=_Part_6_1612889959.1711661421622 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Order exporter framework allows to create arbitrary export implementatio= n that are bound to specific order export eligibility.
The main process is facilitated by a cron (recurring) job that retrieves= all orders that have export eligibility status set. This job uses order's = shop (i.e. shop where order is placed) in order to retrieve configurations = for the bound exporters. If applicable exporter is determined export is exe= cuted.
Once an exporter is executed it can either:
Transition | State | Notes |
---|---|---|
Payment (both online and offline) is confirmed f= or the order. This is the initial payment confirmation transition. | INITPAID | Used as the initial order export hook. Exporters= can use this state in order to export newly created paid order. |
A delivery has been set to a "shipment completed= " state | DELIVERY | Could be used by exporters to notify third party= systems of the completed delivery. Note that this may not necessarily indi= cate that all deliveries are shipped |
Full order cancellation | CANCELLED | May be used to notify fulfilment systems of the = cancellation. Cancellation indicates orders that have not yet been shipped<= /td> |
Full order return | RETURNED | May be used to notify fulfilment systems of the = return of the items that were shipped previously. |
Supplier email notification exporter is a basic order exporter that send= s email notification to specified supplier with only items that are applica= ble to be full filed by this supplier. Supplier in this context refers to s= pecific fulfilment centre.
In order to enable this exporter for a given shop business user can use = SHOP[ORDER_EXPORTER_MAIL_SUPPORTED_SUPPLIERS] attribute, which is of type P= roperty and should contain mapping of [Fulfilment = Center Code].[Export eligibility]=3D[CSV of emails to send the email to]
Example configuration for Fulfilment centre with code "Main" and "Second= ary" to export when "INITPAID" eligibility is set:
Main.IN= ITPAID=3Dneworder@mainff.com Secondary.INITPAID=3Dspecialorder@specialff.com,viporders@specialff.com=20
Manual state proxy is not a real exporter but rather is a tool to set th= e desired export eligibility state on the order and also to facilitate manu= al export flows for specific eligibilities i.e. when export button appears = in Admin app for the order and requires business user to click if to actual= ly "approve" the export.
Manual export flow is achieved by setting "Block export" flag if necessa= ry to enable manual export flow for a specific export eligibility.
In order to enable this exporter for a given shop business user can use = SHOP[ORDER_EXPORTER_MANUAL_STATE_PROXY] attribute, which is of type Propert= y and should contain mapping of [Fulfilment Center= Code].[Export eligibility]=3DNEXT|BLOCK or NEXT|UNBLOCK
For example business requirement is not to automatically send email noti= fication to suppliers via "Supplier email notification exporter" but rather= put the order into blocked state with EMAILNOTIFY eligibility. Then bind t= he "Supplier email notification exporter" to EMAILNOTIFY. Thus when manual = export button is pressed in Admin app the exporter will proceed with EMAILN= OTIFY.
Example configuration for blocking default INITPAID export eligibility t= o EMAILNOTIFY and enable the manual export button in Admin app:
INITPAI= D=3DEMAILNOTIFY|BLOCK=20
And then "Supplier email notification exporter" configuration would be s= et to:
Main.EM= AILNOTIFY=3Dneworder@mainff.com Secondary.EMAILNOTIFY=3Dspecialorder@specialff.com,viporders@specialff.com<= /pre>=20