The following table describes the fields in the Adjustment Rule form.
|Short Description||Required. Short description of the rule. This value is displayed during manual accounting in the list of step rules the user can select.|
|Class of the Step||The class of the page that holds the Step data. Specify a Rule- Obj-class name that is a concrete class and is a child of the PegaAcct-Step- class.|
|Activity for Verification Flow||An activity at the class of the step that calls a verification flow. If blank, the system automatically passes the accounting through without verification. One activity delivered with the product specifies a verification flow based on amount values. The activity lets you do verification up to four levels, which can be used based on the amount of the step.|
|Model to create Step||A Rule-Obj-Model rule name at the class of the step. If specified, the system creates the step page based on the model. The step rules in the product do not use a model.|
|Validate Activity||Reserved for future use.|
|Likelihood||An integer between 0 and 100 that is used to preselect the most likely step rule (the one with the highest number) during the manual flow actions that create accounting steps.|
Specifies whether this accounting transaction is part of a group of transactions such that only one transaction in the group is used when the accounting is created. In manual processing, the user chooses a transaction from the group (the Label property is displayed in a selection box so that only one transaction can be chosen). In automatic processing, the first transaction in the group is selected automatically so the transaction order is significant.
Note that Smart Dispute does not use groups because there is a single internal account for Receivable, Write-Off, and so on.
|Label||Appears in the window during manual accounting creation flow actions to indicate the name of the transaction.|
|DR/CR||Indicates whether the transaction is a Debit or a Credit. The rule requires that debits are listed before credits for consistency. The order of the transactions in the rule is the order in which they are displayed during manual accounting creation flow actions.|
A unique string identifier for each transaction in this step. Its value is placed into a property named Role in the transaction of the step and can be used to find or report on the transaction.
|Txn Class||The class of the page that holds the transaction data. Select a Rule-Obj-Classname that is a concrete child class of PegaAcct- Txn-.|
|Pymt Type||Name of the Rule-PegaAcct-Financial-Payment Type rule to use for this transaction. The payment type rule associates correspondence with the transaction.|
|Default Account From||Specifies how to determine the account name and number for this
|Account From Value||Specifies a party role if the Default Account From value is Party. Specifies an internal account name (as defined in the map value FinChartOfAccts) if the Default Account From value is Chart of Accounts.|
Select to prevent input in the Account Name and Number fields of the user interface during manual accounting creation. If not selected, users can modify these values during manual accounting creation.
Specifies where to acquire the amount value for this transaction:
|Amount From Value|
Specifies a property reference if DefaultAmountFrom is Property. A reference can be any fully qualified property reference from any page. If the property reference is not dot qualified,then Smart Dispute assumes that the property is on the top level of the work object page.
Specifies an actual amount number value if Default Amount From is Literal. Do not use quotation marks, $, or commas (for example, if the value is one thousand, enter 1000.00 and not any of the following: $1,000.00 or $1000.00 or "1000.00").
|Protect Amount?||Select this check box to prevent input in the Amount field of the user interface during manual accounting creation. If not selected, users can modify this value during manual accounting creation.|
|Security Tab||Optional. Enter the name(s) of any named privileges where access to the privilege allows this step to be executed.|
|Class||Optional. Enter the class of privileges you specify in this window.|
|When Name||Optional. Enter a Rule-Obj-When rule that equal true for this step to be executed. Most Smart Dispute step rules use When rules to allow step access only if the referenced Party Role exists in the work object.|
|History Tab||Full description of the adjustment rule and information on its usage.|