Difference between revisions of "Auto Values"
Jump to navigation
Jump to search
Line 198: | Line 198: | ||
|- | |- | ||
|nowrap="1"|''secure'' | |nowrap="1"|''secure'' | ||
− | |This generates a UUID that cannot be traced to the | + | |This generates a UUID that cannot be traced to the Ethernet address of the computer on which it was generated |
|- | |- | ||
Line 210: | Line 210: | ||
|- | |- | ||
|nowrap="1"|'''sess( ''prop_name'' )''' | |nowrap="1"|'''sess( ''prop_name'' )''' | ||
+ | | | ||
+ | :{| class="prettytable" | ||
+ | |||
+ | |- | ||
+ | | | ||
+ | | | ||
+ | |||
+ | |- | ||
|The current user’s session property. | |The current user’s session property. | ||
+ | |} | ||
|- | |- |
Revision as of 17:27, 20 February 2015
Home > Administration > Data > Auto Values
Introduction
The Auto Values feature lets an administrator define how auto-generated values, such as reference IDs, are constructed. Places where more than a sequence number (000001234) is required, an Auto Value can be modified to include dates, time, location, teams, user IDs and more. There are many situations where this type of sequence is much more preferable over a simple numeric sequences. Some examples include:
- Shipment numbers
- Document or Article Reference Numbers
- Stock Item Codes
- Asset ID's
- Access Code numbers
Available Auto Value Component Parts
The following lists of component parts are available to construct an auto value.
seq( z, r ) |
| ||||||||||||||||||||||
seqd( z, r ) |
| ||||||||||||||||||||||
seqm( z, r ) |
| ||||||||||||||||||||||
seqy( z, r ) |
| ||||||||||||||||||||||
| |||||||||||||||||||||||
date( [part] ) |
| ||||||||||||||||||||||
udate( [part] ) |
| ||||||||||||||||||||||
uuid( [type] ) |
| ||||||||||||||||||||||
sess( prop_name ) |
| ||||||||||||||||||||||
param(param_name) | A value passed into the function when invoking the sequence. | ||||||||||||||||||||||
rec( column_name ) | will be translated into the value that will be written to the database record. |