1 New EDI Order Generator
2 ^^^^^^^^^^^^^^^^^^^^^^^
7 . New database tables exist for configuring vendor-specific EDI order
11 ** List of EDI order generation toggles, e.g. "INCLUDE_COPIES" to add
14 ** Collection of edi_attr's. Each edi_account may be linked to one
16 ** One edi_attr_set per known vendor is added to the stock data, matching
17 the stock configuration found in the JEDI template.
18 * acq.edi_attr_set_map
19 ** Link between edi_attr's and edi_attr_set's.
21 . EDI Attribute Sets are manged via a new (browser client only) configuration
22 interface at Administration -> Acquisistions Administration -> EDI
25 . Each acq.edi_account should be linked to an acq.edi_attr_set. If a link
26 is not set, default values will be used. Links between an EDI account
27 and an attribute set are managed in the EDI Accounts configuration
30 . Local modifications to the stock EG JEDI template are managed by modifying
31 and/or adding additional edi_att_set's as needed.
33 . A new edi_order_pusher.pl script is added which replaces the functionality
34 of edi_pusher.pl. edi_pusher.pl is still avaialable.
36 . After moving to edi_order_pusher.pl, the JEDI Action/Trigger event
37 definition is no longer required. It can be disabled.
42 EDI accounts have a new boolean field "Use EDI Attributes" (use_attrs) that
43 specifies whether PO's generated via the account should be built using
44 EDI attributes or fall back to traditional JEDI A/T template generation.
46 This allows sites to activate EDI attributes on a per-account basis, making
47 it possible to migrate piecemeal to EDI attributes. For the initial roll
48 out of this new features, no accounts will be configured to use EDI
49 attributes by default.