Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This section guides the user through the menu options that are available under the Import menu.
This option allows billing changes to be imported in order to update a subscriber’s renewal delivery method, rate code, auto renew credit card, or auto renew bank draft information. For example, this tool can be useful in cases where a renewal delivery method (such as eBill) is tracked by another system. The import format is user-defined, and must be set up in advance using File Map (“SubTranImprt” usage). See Appendix B for a list of data elements that can be included.
Select Billing Change from the Import menu to display the Billing Change Import screen.
Select Add and complete the following fields.
READ OPTION
predefined
Indicate whether the import should be run in commit mode (transactions imported into Circulation) or edit mode (no transactions imported—the file is simply read and any errors displayed). We recommend running this option in edit mode first to confirm that there will be no errors during the import.
TRAN TYPE
predefined
Enter the transaction type to be exported. Currently, “Billing Change” is the only choice.
SOURCE, SUBSOURCE REASON
setup
If the import is being run in commit mode, enter the source, subsource (if applicable) and reason code for the billing change transaction.
TRAN DATE
date
If the import is being run in commit mode, enter the transaction date for the billing changes. If a transaction date is contained in the file, the file’s transaction date will override this date.
FILE FORMAT
setup
Enter the ID of the subscriber transaction import format that should be used. This must be defined in advance in File Map.
FILE NAME
open (30)
Enter the import file name. This file must be in the /dti/exchange/cm directory. The file name may default from the file format.
Select Continue to do the import. This will create unprocessed billing change transactions for the subscribers in the file. When the import is complete a processing report will be displayed, listing how many records were exported and any errors that occurred.
After addresses have been exported using the and updated outside of Circulation, use this option to import them back into Circulation. A file map for this import (“CleanseFlagImp” usage) must be set up in advance.
Select Update Cleanse Flag from the Utilities | Import menu to display the Update Cleanse Flag Import screen.
Select ADD and complete the following fields.
Select Continue to import the addresses.
Communication history is a record of the newsletters, alerts, and other communications sent to an occupant. Communication history can be generated by Targeted Marketing when selecting customers opting into a communication (see ), or imported into Circulation from an outside source using this option. For example, if you currently manage a newsletter e-mail list in another application but want the ability to view which newsletters and alerts were sent to an occupant in Customer Service, you can import that history into Circulation.
Note:
In order to import communication history for a customer, the customer must have opted in to the communication item using the communication method and detail (e-mail, phone or address) contained in the import file. Also, the customer’s occupant ID must be contained in the import file.
The import format is defined by file mapping. You must define a file map with a usage of “CommHistImport” (see Appendix B for a list of elements).
In Graphical Utilities, select Communication Hist from the Import menu. The Communication History Import screen displays.
Click Add and enter criteria for the import in the fields described in the table below.
Click OK and Continue to read the file. If Read Option is “Commit”, communication history records will be imported and can be viewed in Customer Service.
The Communication History Import processing report displays the number of records validated or imported.
READ OPTION
predefined
Indicate whether the import should be run in commit mode (addresses imported into Circulation) or edit mode (no addresses imported—the file is simply read and any errors displayed). We recommend running this option in edit mode first to confirm that there will be no errors during the import.
FILE FORMAT
setup
Enter the ID of the update cleanse import format that should be used. This must be defined in advance in File Map with a usage of “CleanseFlagImp”.
FILE NAME
open (30)
Enter the file name for the import. The addresses will be imported from this file in the /dti/exchange/cm directory. The file name may default from the file format.
READ OPTION
predefined
Indicate whether to read or commit the import file. The communication history records will only be imported if the read option is “Commit”. A report is generated in both cases.
FILE FORMAT
setup
Select the file format to use for the import. This must be defined in file mapping with the “CommHistImport” usage.
FILE NAME
open (30)
Specify the name of the file to import. The file name may default from the file map, but can be changed. The file should be in the /dti/exchange/cm directory (or your [defaultdir] directory, if other than “cm”).
DELIVERY DATE
date
The delivery date can be specified in the file format, using the DeliveryDate element in the file map. If the file map does not contain this element, this field opens, and you must enter the delivery date for the communication history here. This is typically the date on which the newsletter or other communication was sent to the customer.
Use this utility to import address additions, changes, and deletions. All of the imported data will be validated just as if the addresses were being added or modified manually. If Business Rules are set not to parse addresses, detailed information such as house number, street name, predirectional, street type, etc., will not be validated.
After importing the address data, an audit report will be created that displays the number of records added, changed and deleted along with any errors encountered. Error messages are written to the log.
File mapping is used to define the format of the import file (see Appendix B).
Note: If you cleanse addresses, run Batch Address Hygiene after importing addresses to cleanse them. The Address Information import only validates address elements, such as street type.
Select Import | Address Information to display the Address Import window.
Click Add and complete the following fields.
READ OPTION
predefined
Indicate whether the import should be run in commit mode (transactions imported into Circulation) or edit mode (no transactions imported—the file is simply read and any errors displayed).
TOWN OF 25
setup
If you selected commit above, select the town of 25 to which these addresses belong.
FILE FORMAT
setup
Select a File Map format to use for this address import.
FILE NAME
open (30)
Enter the name of the address file being imported. The file must be in the /dti/exchange/cm directory.
Click OK and then Continue to import address information.
Circulation has the ability to import data from a telemarketing system or other source. Starts, stops, restarts, moves, delivery schedule changes, payments, complaints, billing changes and combo changes can all be imported. Solicitation codes can also be updated. After the import, Circulation in turn creates an export file, detailing records that were rejected or have warnings.
Subscriber Activity reads in a file from /dti/exchange/cm/secure, and creates subscriber transactions using the guidelines described in the following table. A separate section of Business Rules, Import Sub Activity (see Import Sub Activity in the Setup Manual) allows you to configure some aspects of the import.
All transactions
If the Circulation Occupant ID, Address ID, or Subscription ID is supplied by the interface file, the address, occupant, or subscription in Circulation must match the information in the file. If no Occupant ID, Address ID, or Subscription ID is supplied, Subscriber Activity will attempt to match a Circulation address based on address data in the file. All address elements must match, except for the unit designator (Apt, #, Room, etc.). If the file contains a name, the occupant first and last name in the file must exactly match the occupant first and last name in Circulation for the subscriber matched. If no Occupant ID, Address ID, or Subscription ID is supplied, Subscriber Activity will attempt to match a Circulation address based on address data in the file. All address elements must match, except for the unit designator (Apt, #, Room, etc.). If the file contains a name, the occupant first and last name in the file must exactly match the occupant first and last name in Circulation for the subscriber matched.
Start
If this is a mail delivery start, the occupant cannot have an address that the router determines should be route delivered. If this is a route delivery start, the occupant must have an address that is route delivered, as determined by the router. When creating a new start, Subscriber Activity will create a new occupant record if there is no matching occupant at that address in Circulation. It will then assign the subscription to a label group (based on the Zip code) or a route (based on the router). It will also determine the subscription rate, occupant type, credit status, AAM zone, unlisted phone number flag, and send invoice and send renewal flags, if this information is not supplied by the interface file.
Stop
The occupant must have an active subscription, and no pending stop transactions.
Restart
The occupant must have a subscription that is temp stopped on the record’s transaction date (cannot be perm stopped or active), and cannot have a restart between the temp stop date and the record’s transaction date.
Delivery Schedule Change
The occupant must have an active subscription. There cannot be a pending delivery schedule change transaction for the subscriber. Business Rules can be set to require the delivery schedule in the file to contain a higher number of delivery days than the subscriber’s current delivery schedule. For example, a delivery schedule change that upgrades a subscription from Mon-Fri to 7-day would be accepted, but a delivery schedule change that downgrades a subscription from Mon-Fri to Sat-Sun would be rejected. When creating the delivery schedule change, Subscriber Activity will determine the new subscription rate, if not supplied by the interface file.
Move
The occupant must have an active subscription, and no pending stop transactions.
Payments
The occupant must have a subscription (it does not have to be active). Cash, check, credit card or bank draft payments can be interfaced. Business Rules determine the number of days that are added to the payment date when importing cash or check payments.
Billing Changes
The occupant must have an active subscription.
Combo Changes
Combo changes are supported for both non-combo to combo subscription changes and combo to combo subscription changes.
Complaints
An occupant or address must be supplied. The occupant does not need to be a subscriber.
Demographic Answers
An occupant or address must be supplied. The occupant does not need to be a subscriber.
Solicitation Update
Up to two solicitation codes can be included in the file. If they are, the occupant matched in Circulation w ill be updated with the solicitation code(s).
Select Subscriber Activity from the Import menu to display the Subscriber Activity Import screen.
Select Add and complete the following fields.
FILENAME
open (25)
Enter the name of the import file. The import file can have any name, but must be located in the /dti/exchange/cm directory.
BANK
setup
Enter the bank for cash, check or bank draft payments being interfaced.
READ OPTION
predefined
Indicate whether the import should be run in Edit only or Commit mode. Commit will create transactions and update solicitation codes. Edit only will not update any information, but it will validate the data in the interface file and display warnings and errors on an error report. When first implementing the interface, we recommend running the interface in Edit only mode before committing.
CREATE EXPORT FILE
yes/no
Indicate whether an output file should be exported to the /dti/exchange/cm directory. The output file lists the status of each imported record.
AUTO ACCEPT
yes/no
Indicate if you want all open batches to be accepted automatically. Transaction Security controls whether the default answer can be changed.
SUSPEND ALL STARTS
yes/no
Set this field to “y” if all new starts should be suspended.
ALLOW START FOR EXISTING SUBSCRIPTION
yes/no
Set this field to “y” if new starts are allowed for addresses that already receive a subscription. Set this field to “n” if starts are not allowed for addresses with existing subscriptions.
Select Continue to run the interface. If the read option is Commit, transactions will be created in Circulation, solicitation codes will be updated, and an output file will be exported. If the read option is Edit only, the data will only be validated. In both cases, a report will be displayed after processing is complete. If Create Export File is set to “y”, an output file will be also be created in the /dti/exchange/cm/secure directory, listing the status of each imported record. The standard view/print options are available.
For the format of the import and output files, see Appendix B. For descriptions of the reject codes, see Subscriber Activity Import | Reject Codes.
Note: The Token Account Updater is for use only with Payway Complete Hosted Order Page (HOP) at this time.
The Token Updater utility is used to update credit card information using the token and an external import file from the Payment Vendor. The default File Map to match the Edgil export is named EdgilUpdate and has a usage of TokenUpdater.
This utility uses the Updated Accounts export from Edgil Payway. In the export file, there will be Update Type Codes that define what information in the Auto Renew is being updated. The following list describes the update codes.
1 = New Expire Date
2 = New Card Number and Expire Date
3 = Account Closed (Discontinue Auto Renew)
The Token Updater will create unprocessed Billing Change transactions with an Update Expire = “No” reason code to update credit card information.
To use this import, follow these steps.
Select Import | Token Updater in the graphical Utilities module.
Select Edit to view the records to be imported or Commit to import the records.
In the File Name field, enter the name of the file to import. This file must exist in the default exchange secure folder.
In the File Format field, enter the name of the file map created for this option. The “TokenUpdater” Usage is used for this import. The table below describes the possible data elements.
Select desired Tran Date, Source and Reason.
Click OK to run the utility.
Note:
The file map can be modified to use a “,” delimiter and the file be imported as-is from Payway Complete. If the file is not modified and the first two lines removed after exporting from Payway Complete, the import process can produce an Error message when reading in the first line “Expected 30 elements; Received 1.” The first line in the file is a time date stamp so this error can be ignored.
The following Data Elements are required or recommended.
UpdateCode – Required
FirstName – Recommended
LastName – Recommended
Token – Required
MaskedCard – Recommended
ExpireDate – Required
LastFour – Required
The Federal Trade Commission administers a national Do Not Call (DNC) list for telemarketing. Most telemarketers are forbidden from calling consumers that place their phone numbers on the list.
The Do Not Call List utility assists newspapers in complying with federal DNC lists. The utility will allow full DNC lists or changes to DNC lists to be imported. State lists may also be imported, provided they are in the same format as the federal DNC list. Federal DNC lists can be downloaded from http://telemarketing.donotcall.gov. The list can be in flat text or XML format—choose flat text for use with Circulation.
When a list is imported, phone numbers contained on the list are flagged as Do Not Call numbers. The Do Not Call setting can be used as a selection parameter in Targeted Marketing (which is the method most often used to generate telemarketing lists) and viewed for a specific occupant in the Occupant Phone window in Customer Service. Old DNC records can be deleted via the .
Select Do Not Call List from the Utilities | Import menu to display the Do Not Call Import screen.
Select Add and complete the following fields.
Select Continue to run the import. The phone numbers in the DNC list will be read and compared to Circulation’s Do Not Call records. If no record exists for a phone number, it will be added; if one does exist, the record’s start date will be updated with the effective date entered at run time. If importing a full DNC list, after the import all phone numbers not contained in the file will have their Do Not Call records end dated (the end date will be the day prior to the effective date).
LIST
setup
Specify the list (e.g., “federal”, “Minnesota”) that is being imported. This must be defined in advance (see Do Note Call List in the Setup Manual).
LIST TYPE
predefined
Indicate whether this is a full list or a list containing changes only.
EFFECTIVE DATE
date
Enter the date on which this list becomes effective.
ALL AREA CODES, AREA CODE
yes/no, integer (3)
Indicate whether the phone numbers for all area codes should be read in and, if not, enter the area code that should be read (enter “*” to multi-select area codes).
FILE FORMAT
setup
Select the file map to use for this import.
INPUT FILE NAME
open (30)
Enter the file name of the DNC list file sent by the government. The file must be placed in the /dti/exchange/cm directory.
For the full list, each record in the file should contain only the occupant’s area code and phone number, separated by a comma. For example: 788,7643087.
Use this option to import answers to single copy demographics from an external file. The format of the file must be Route | Answer.
The file can be any name, but must be placed in the [DefaultDir]/exchange/cm directory.
Select Utilities | Import | SC Demo Answer to display the SC Demographic Answer screen.
Select Add.
Select the demographic for which answers are being imported, and enter the file name to import.
Select Continue to import the file. The demographic answers will be set for the routes contained in the file, and a processing file will display details of the import process.
This utility loads authentication control history from a flat file. Authentication history is used to track subscriber digital access, for AAM and other purposes. This utility can be used as an alternative to iServices Authentication.
Select Import | Auth Import to display the Authentication Import window.
In the File Format field, enter the name of the file map created for this option. The “AuthImport” file mapping usage is used for this import. See Appendix B for the possible data elements.
In the File Name field, enter the name of the file to import. This file must exist in the /dti/exchange/cm folder.
Select Edit to view the records to be imported or Commit to import the records.
Click OK to run the utility.
Note:
If the AuthControl data element is not included in the specified file, you will be prompted to enter a valid authentication control ID before continuing with the import.
Rewards are exported to the rewards management application via the Rewards Export. To insure that the records were interfaced correctly, a response file may be sent back from the rewards application. The response file determines whether a reward was accepted or rejected. Once a response has been received for a reward record, the reward will be considered completed rather than pending. Importing responses is optional.
Select Reward Response from the Utilities | Import menu to display the Reward Response Import screen.
Select Add and complete the following fields.
READ OPTION
predefined
Indicate whether to Edit or Commit the import file. Reward records will be updated only if the read option is “Commit”. If “Edit” is selected, a report will appear, but no records will be updated.
REWARD PROGRAM
setup
Select the rewards program that you are interfacing.
IMPORT FORMAT
predefined
Select the format for the rewards import.
FILE NAME
open (16)
Enter the name of the response file being imported. The file must be placed in the /dti/exchange/cm directory.
Select Continue to import rewards file. See Appendix B for the format. A processing report will list details about the import and any errors that occurred.
This utility uses a file map to import Note Transactions into Customer Services for selected subscriptions. The file format of this import is determined by file mapping (NoteImport usage). See Appendix B for a list of data elements available for this format.
Note: Product was not included in the file map as it is assumed by the SubscriptionID. The Note transaction’s is Permanent? automatically defaults to No. Remarks can be up to 2000 characters.
Create an ASCII file containing the desired data elements.
Note: SubscriptionID and Remarks are required data elements.
Select Import | Note Transaction to display the Note Transaction Import window.
Click Add and complete the following fields.
Read Option
predefined
Indicate whether to commit or edit the note transactions in the ASCII file. If you choose “Commit” the Note transactions will be created. If you choose “Edit”, only the processing report will be created (you can then look the report over for errors before committing).
File Format
setup
Select the file format to use for the import. At least one format for the Note Import usage must be defined in the File Map setup (see Appendix B).
File Name
open (30)
Dependent on File Format. Will populate if File Format has a default.
Tran Date
date
Pre-populates with current run date.
Source
setup
Valid Source from setup. If Source is included in the import file, the value from the import file is used regardless of what is entered during run-time.
Reason
setup
Valid Reason from setup. If Reason is included in the import file, the value from the import file is used regardless of what is entered during run-time.
Click OK and then Continue to import the Notes transactions. A Note transaction will be created in Customer Services for each SubscriptionID in the import file. A processing report will display the number of records created along with any error and/or informational messages related to the import of the data elements.
