AutoCommand 20036 Guia de Instalação descarregar pdf (Página 71)

An autosold item can now be prevented from being put on account by using MACRO2(NOACCOUNT()) as a

Dynamic Pricing rule attached to the item.

Note: Since this is set as a Dynamic Pricing rule, the original pricing of the item will not be honored when scanned

through GateKeeper module. The item will still be autosold but the amount sent to the autoscan invoice will be

$0.00.

Changes to the Memberships/Passes module

When SetPass is performing a validation and the validation template specifies a Revenue

Recognition rule, SalesEZ application now checks the SiriusUtil.DLL file

When SetPass is performing a validation and the validation template specifies a Revenue Recognition rule, SalesEZ

application now checks that the SiriusUtil.DLL file (which is necessary for Revenue Recognition) is

available. If it is not, SalesEZ application will now return an invalid message, "314 - Configuration error.

SiriusUtil.DLL is not available."

If a validation needs to perform Revenue Recognition via the SiriusUtil.DLL, it is now performed at the

beginning of the validation process instead of at the end. If the Revenue Recognition process reports an error, the

user will be notified with the message, "Pass is good but Revenue Recognition could not be processed". The

message will also include the error message from the DLL. Validation will be halted and not take place.

Two new .INI settings in the [Preferences] section of SalesEZ.INI:

MinRevenueRecognitionTransactions = NNN (defaults to 0 if not present)

MaxRevenueRecognitionTransactions = NNN (defaults to 9999 if not present)

If a validations scan needs to perform Revenue Recognition, these are the minimum and maximum number of

revenue recognition transactions you would expect to be created, depending on how you set up your revenue rules.

If the number of created transactions falls outside of this range, the validation will not take place and a new "114 -

Error In Validation Revenue Recognition" activity log record will be created in the acc_actv or gst_actv

tables. Even though the validation did not take place, SalesEZ application will still return the message, "OK (Pass

is good but Revenue Recognition did not generate the expected number of revenue transactions)" to the calling

scanner so as not to interfere with the guest access.

If a validation needs to perform Revenue Recognition but the "MaxRevenueRecognitionTransactions"

.INI setting is set to zero, then Revenue Recognition will NOT be performed, regardless of the fact that the pass

template is configured to perform revenue recognition. This is useful for a situation where all scanners using this

1 2 ... 66 67 68 69 70 71 72 73 74 75 76 ... 182 183

Sem comentários

AutoCommand 20036 Guia de Instalação Página 71