Workflow and Actions
There are currently 26 different types of action, with more being developed as ZEDI customers need them. Some of the most commonly used action types are:
There are currently 26 different types of action, with more being developed as ZEDI customers need them. Some of the most commonly used action types are:
Converts the data contained within a separated (CSV) or fixed-position (flat) file to XML format so that it can be mapped.
Scans the contents of a file for the presence of EDI data, and extracts the EDI messages it contains. Those messages can then be mapped to produce files that can be imported into your business systems.
Produces an Excel spreadsheet which can then be delivered to a colleague or a trading partner.
Allows information within Excel spreadsheets to be automatically converted into a sensible XML format so that it can be mapped into your business systems.
Runs a mapping to create a file in a different format from the original file. This could be an EDI, CSV, XML, flat file or SQL script.
Extracts useful information from a file, such as a list of document numbers, as well as control information that can be used to influence how the transaction get processed. For example, when receiving EDI orders, you may need to handle new orders differently from order changes.
Metadata can also be used when running searches, for example, if you need to find all the transactions that relate to a specific order number.
Records information about the transaction in a register.
Registers are customisable logs of transactions that can be used to provide information to non-technical colleagues.
Sends an e-mail to the originator of a transaction to automatically report an error and request a corrected version of the file.
Delivers a transaction to a business system or a trading partner using your choice of communications method.
Validates the data within a transaction prior to processing it further.