 |
|
What I'd changed in 2003 year? |
|
V3.30.01 – November 9, 2003.
- Software-Promoter checks validity of input custom field's names now. If you have entered invalid custom field name and unable to run Software-Promoter then using this release is important. This release ignores all invalid entered names when start.
- Software-Promoter can import and export report's records.
- I have implemented custom fields and macros for sites and submissions entities.
- "Split" rule for registration letters works more correctly: matched text adds to the end of each detection piece.
V3.30 - October 23, 2003.
Since this version, Software Vendor Assistant (SVA) has a brand new name: "Software-Promoter". I have created new site www.software-promoter.com especially for Software-Promoter's support.
Software-Promoter has ability to create powerful user-designed reports. I use FastReport ( www.fast-report.com) engine to provide reporting service. You may create reports for registration orders, site collection items and submission items. Once defined, reports are available under "Reports…\XXXX" items in the popup menus in grids.
I divided "Global Preferences" dialog into 2 pieces of data: "Identities" and "Options". Identities define your personal information. You can have as many identities as you want. Each version record can point to different identity record. This is useful if you have multiple products and/or multiple sites. As example, you can distribute "ProductOne" as John Smith, and distribute "ProductTwo" as "ProductTwo LLC" at same time and using one Software-Promoter's database. It is very useful to create your own submission service, too.
NOTE: Your user data in the "Global Preferences" will be converted into "Default Identity". All exists versions will be linked to "Default Identity".
You can define custom fields for registration orders. Define, tune and use any fields according to your needs. Custom fields are available through macros; registration orders detectors and data grids.
Software-Promoter now checks POP3 account(s) for new registration orders. Define one or more POP3 accounts to use it. *.rod files syntax has extended to use this feature. In the [CommonRules] section you may define "POP3Header" regexp-based rule. First, Software-Promoter loads all headers from POP3 server. Then, it evaluates these headers with "POP3Header" rule. Then, Software-Promoter will download message body for each header that matches the rule. Finally, loaded message will be passed to detection engine. Software-Promoter does not delete any messages from POP3 server.
Software-Promoter pass messages with POP3 header when it is possible to the registration order detectors. It helps to detect some details. Some registration services do not gives order date in the message body. In this case, one way to assign right date is to extract it from POP3 header. See file "rods\shareit.rod" for example. NOTE: Software-promoter cannot provide POP3 header always because some mailers do not pass this information outside. I can guarantee that header will pass full header information only when you use direct POP3 checking mode.
Date field detection from registration orders is improved. You can define separate rule for day, month and year for each date field. When all parts are detected, Software-Promoter will combine date value from parts. Both regexp and macros rules types are acceptable.
Software-Promoter manual is revised dramatically.
ROD files editor can check *.rod files for missing field rules and insert empty rules according to your registration order structure. Custom fields are supported.
Registration keys can be wrapped in the outgoing letters. For instance, use "Registration.RegKey, 70" macro to wrap your key for every 70 characters.
Detected messages can be stored in the inbox not only during current session. You can commit or delete registration orders any time later.
All fields in the dialogs were separated into "required" and "non-required". Required fields are marked using bold font. Required fields cannot be blank.
Better expired orders handling. Now you can filter out expired customers when sending e-mail messages.
Checking for duplicates in the registration orders detection engine was improved. By default, Software-Promoter considers order as duplicate using these fields: "VersionGUID;FirstName;LastName;OrderID". Add "KeyFields" parameter into [CommonRules] section of *.rod file and specify other key fields, as you want. For instance, you can use your custom field as key field: "KeyFields=VersionGUID;FirstName;LastName;CF_MyCustomField". Then Software-Promoter will evaluate these fields for each new registration order and detect duplicates. Moreover, you can turn duplicates detection off using checkbox in the "New orders" toolbar.
Opened auto-forms count is displayed at the left switching tab.
Site with opened auto-forms no more displayed in the "New submission…" dialog.
Changing auto-forms in the site properties refreshes auto-forms list in the Auto-submit tab.
New registration order detector for "Softkey" orders, Russian Federation.
Left sidebar was re-implemented.
Bug reporting feature allows you to report any bugs information easy.
Fixed bug: "FileName" field from description entity was not displayed.
Fixed bug: sites that have submission(s) with status "Message posted" was displays again in the "Append submission…" dialog.
Fixed bug: auto-submit switching buttons were display incorrect.
Fixed bug: Custom fields were not displayed at the "New orders" tab.
Fixed bug: Error was in the "PAD Import" routine. Newly created version did not get linked into identity.
Fixed bug: submission status was not refreshed in the sites tab after using auto-form.
Fixed bug: your modified registration orders detectors will not be overrode during re-installation.
Fixed bug: tunes for grid in the "New orders" tab were not restored.
Fixed bug: Sometime Boolean values were not detected properly from registration orders.
Fixed bug: Author info and Company info were not filled out even if it selected.
V3.2.33 - April 5, 2003
New predefined field in registration order: "Registrar". By default, all registration orders detectors will assign this field to his name.
New registration order macros: "Registration.WhereHeard", "Registration.HardwareID", "Registration.Registrar", "Registration.CustomerIP".
"<Keygen>.parameters" file will contains all registration orders macros, not only started with "Registration_XXX" and "Customer_XXX". See online manual for details.
It is ability to pass macros in the environment for console keygen or not. See appropriate parameter in the "version" dialog.
It is ability to turn off Registration orders detection overrides mechanism. Parameter "Use Registration order detection overrides" in Global preferences handles it.
All sorts in grids are case-insensitive.
Bug fixed: Setup checks if SVA is running when you start svasetup.exe.
Bug fixed: New MAPI classes. New implementation is more stable than old.
Bug fixed: "HardwareID" field was not editable in registration order dialog.
Bug fixed: Checking dupes when detecting registration orders was changed. SVA will consider registration order as duplicate only if it contains VersionGUID + FirstName + LastName + Company fields same as another.
V3.2.32 - April 2, 2003
13 registration orders formats supported. Moreover, you can define more detectors and/or tune shipped, as you want.
Last awaited feature: Drag message(s) from E-mail application directly to SVA window and extract incoming registration orders with one mouse click. Outlook, Outlook Express and any other OleDrop-capable mailers are supported.
It is possible to run console keygen for new or existing customers. There are three ways to pass parameters to console keygen: environment variables, command-line parameters and special parameters file. As example, if you use console keygen "C:\KEYGEN.EXE", SVA will create file "C:\KEYGEN.EXE.PARAMETERS" before call this keygen. Environment for this process will be filled out with "Registration.XXX" and "Customer.XXX" macros. Dots in macro names will be replaced using "_" character. See on-line manual for details. Using parameter "Show console window" you can decide to show keygen in separate console window or not.
Drag file with registration orders to SVA window. SVA will extract all customers' information from dragged file(s).
*.rod files syntax had changed. There are two string for each field in [CommonFieldsRules] and [ProductRowFieldsRules] sections. Example for field "RegName":
regname.regexp=[\n\r]Customer name (.*?)[\n\r]
regname.macros=%%REGEXP%% - personal license
If you define "regname=[\n\r]Customer name (.*?)[\n\r]", SVA will mean this line as regexp-based rule by default.
Pre-defined macro %%REGEXP%% for each field passes ".regexp" value to ".macros" value. As before, detection is two-phase process. First, we detect only regexps; two we resolve SVA macros (based on regexp or not). See on-line manual for details.
Auto-reload ROD detectors when *.rod files are changed without restart SVA.
Registration order extraction process detailed diagnostics is shown in ROD editor.
All data columns in grids can be resized and moved using mouse. Grids can be scrolled horizontally and you can place as many columns as you want on any screen resolution.
Quick search works separately for each grid column.
All registration order fields (OrderID, CustomerIP etc.) are selectable to grid.
ROD editor handles missing fields in ROD files.
SVA checks dupes of emails in Outbox and prevents to post one message to one customer twice.
V3.01.31 - February 20, 2003
"Product name alias" for national description. If defined, it is use to resolve "Product.Name" macro value. If clear, real product name will be used.
Robosoft PAD extensions are supported.
Bug fixed: Trying to eliminate delivering errors at some SMTP servers.
Bug fixed: Multilanguage description dialog does not close while you did not fill out "Descr45", "Descr80" or "Descr250" fields or press "Cancel" button.
Bug fixed: SVA did not operable under Windows 95 since previous maintenance update.
Bug fixed: Access Violation error was fired after sites collection imported if products tab was active and untouched sites was deleted.
V3.01.30 - January 31, 2003
"Accessibility" tab was deleted from "Message template" editor. Now using each template is based only on template's kind.
Workaround: preventing of Access Violation errors when close auto-form.
It is possible to use non-English characters for quick search in grids.
"Set canceled and close" command did not work correctly in auto-form window.
Refresh bottom grid in sites browser after closing auto-form.
Changes in PAD generation: routine according to validation warnings from http://sharewarepromotions.com/PAD_Validation.asp.
Regsoft registration order detector was corrected.
It was corrected untouched sites detecting (import sites process).
Prev Next