Reg.Net Custom Component Fulfillment
Model
Purpose: To define the methods that a Reg.Net client
can program against to perform license key generation.
Assumptions:
- Reg.Net
clients will support all methods, parameters and properties defined by the
key generator spec.
- Reg.Net
client is NOT required to use all the methods, parameters and properties
as supplied, but will use only those items pertinent to their generator.
- Reg.Net
client supplied code will not use any internet protocol and is NOT allowed
to write anything to the hard disk it resides on (no email attachments may
be generated)
- Reg.Net
client will supply full source code in C++ or Visual Basic for their
component for review.
- Reg.Net
will compile the component for use
- Non-standard
data may be used, but a setup fee of $250.00 will be charged for a custom
Reg.Net wrapper component.
Properties:
|
Property Name
|
Property Data Type
|
|
OrderID
|
Double
|
|
ProductID
|
Double
|
|
CustomerFirstName
|
String
|
|
CustomerLastName
|
String
|
|
CompanyName
|
String
|
|
Quantity
|
Integer
|
Method Call:
Method Name: GenerateCode
Input Parameters: None
Return Type: String
Description:
The GenerateCode method should validate that each
author-utilized property contains valid data.
For instance, if the license requires a company name, then the component
should validate that the CompanyName property contains data. Once validating the required fields, the
component should perform the appropriate process to return a license code as a
string.
Note: Do not
use the quantity property to return multiple codes. The Reg.Net calling function will call the author component
multiple times to generate the appropriate number of codes based on the
Generate Multiple Code flag (see product edit)
The code(s) generated will be merged into the fulfillment
email. Each code generated will contain
the phrase Code #: preceding the code itself.
For example, if two codes are required, they will be merged into the
fulfillment email as:
Dear…
Code 1: ASDF-GHHJ-1999
Code 2: FDSA-JHHG-9991