At the salespoint processing the Self Entry records (Sales Host running in Rental mode)

Rentals : Pay-up-front: System configuration and use : Pay-up-front: Selling rental packages : Pay-up-front: Self Entry after rental purchase : At the salespoint processing the Self Entry records (Sales Host running in Rental mode)

The process of Self Entry after the rental purchase requires the installation of Sales Host utility running in RentalSelfEntry mode. (See the Salesware .INI Settings Reference and Salesware User Guide for Advanced Users documents for more information on this mode.) It is important that certain .INI settings are in place for the Sales Host computer that processes the rental Self Entry records.

[Preferences]

DeferRentals=FALSE

[Rental]

FormIsTrans=TRUE

LockFormNumber=TRUE

SelfEntry=TRUE

SelfEntryPath=C:\Program Files\Siriusware\SelfEntryRecords\

;directory where the self-entry records are generated

RentalShop=name of shop

;The rental shop should be the shop that is using this set of the self-entry pages

RequireShoeSize=FALSE

[Server]

RentEZ=0.0.0.0:4207 (IP address of RentEZ machine used by the shop)

StartupRentEZ=TRUE

[WebInterface]

RentalSelfEntryMode=TRUE

Delay=2

All other settings for things such as credit cards may be removed.

Rental Self Entry mode − details

Rental Self Entry mode is activated by a single .INI file setting:

[WebInterface]

RentalSelfEntryMode=TRUE

and causes Sales to run very differently. (For a detailed description of how Sales Host utility operates, see the Salesware E-Commerce User Guide.) Sales looks for records in the SelfEntryPath of the form *.se and writes the contents of these files into ww_sales records as follows:

date_time	Creation date/time of the Self Entry file
sale_text	Contents of the Self Entry file, bracketed with <se> tags
sale_no	Empty
salespoint	Salespoint name of Sales Host
fwd_status	0
sale_no	Empty
fwd_time	Empty
result	Empty
wwsale_id	New sale ID generated by Sales Host

It then deletes the Self Entry file.

During the main processing loop, if the <se> tags are found, the record is processed by creating a form_no record matching the guest_no passed to the form_no. Also, a call is made to RentEZ finalize to start the contract.

If this succeeds, the record is marked with a fwd_status of 1, otherwise with a 4 (which get converted to 2 and 5, just like in regular mode). Errors can be reprocessed without any trouble. No sale_no is ever filled into the ww_sales table for these records.

Important: The use of Trans_no for rental contracts has been supplanted by the use of form_no. The changes listed below reflect this change in configuration. Any layout that uses trans_no for the rental contract number must be changed to use form_no instead. The ability was added to collect FormNo instead of Trans no. In addition to the new FormNo.ascx control needing to be in the WebControls folder, make the following changes to Pages.xml to enable this feature:

Remark (surround with ) or remove the TransNo section so it looks like this:

<!--<DynamicControls_GD2>

<Name>TransNo</Name>

<DBField>TransNo</DBField>

<WebControl>TransNo.ascx</WebControl>

<LabelText>Trans No:</LabelText>

<LabelCSS>lblText</LabelCSS>

<RequiredText>Required</RequiredText>

<RequiredCSS>lblInfoAlert</RequiredCSS>

<InfoLabelCSS>lblText</InfoLabelCSS>

<CustomValidatorText>Invalid Trans No</CustomValidatorText>

<CustomValidatorCSS>lblInfoAlert</CustomValidatorCSS>

</DynamicControls_GD2>-->

and add the following in it's place:

<DynamicControls_GD2>

<Name>FormNo</Name>

<DBField>FormNo</DBField>

<WebControl>FormNo.ascx</WebControl>

<LabelCSS>lblText</LabelCSS>

<RequiredText>Required</RequiredText>

<RequiredCSS>lblInfoAlert</RequiredCSS>

<InfoLabelCSS>lblText</InfoLabelCSS>

<CustomValidatorText>Invalid Form No</CustomValidatorText>

<CustomValidatorCSS>lblInfoAlert</CustomValidatorCSS>

</DynamicControls_GD2>