Dgarratt:

[[File:System_Keys.png|800px|thumb|left|System Keys]] 

System Keys are a set of global settings used by the application to determine how certain functions work. These settings will include such items as :- 

{| border="1"
|+ SYSTEM KEYS
! scope="col" | System Key
! scope="col" | Typical Value
! scope="col" | Description
|-
! scope="row" | BATCH EXPIRY TIME
| - || A flag which is used to determine how the time portion of the Expiry Date is calculated. Can be - = or +
|-
! scope="row" | BATCH FORMAT
| {YEAR1}{JULIAN_DAY}{PLANT} || Used to construct the batch number when creating/printing new Pallet Tickets (SSCC's)
|-
! scope="row" | BATCH REGEX
| || Optional Regular Expression which can be used to validate the Batch Number after user has edited by hand.
|-
! scope="row" | COMPANY NAME
| My Company || Text that you want to appear at the top of reports.
|-
! scope="row" | DEFAULT BATCH STATUS
| Restricted || Deprecated - no longer used. Now held in Material Master record.
|-
! scope="row" | DEFAULT HELPSET ID
| || Deprecated - no longer used. Help now linked to Wiki pages.
|-
! scope="row" | DEFAULT PALLET STATUS
| Unrestricted || Deprecated - no longer used. Now held in Process Order record.
|-
! scope="row" | DEFAULT_LOCATION
| MYLOCATION || Should be a valid Location Id from the locations screen and is used by the Despatch function
|-
! scope="row" | DESPATCH NUMBER
| 1 || Used to determine the numeric element of the next despatch number.
|-
! scope="row" | DESPATCH NUMBER FORMAT
| XX{NNNNNN} || Defines the structure of the Despatch Number. {NNN} indicates the number above. XX is a literal prefix.
|-
! scope="row" | EXPIRY DATE MODE
| BATCH || Can be either BATCH or SSCC. This value should be set before go-live and not changed. BATCH will store the Expiry Date in the Batches table using the MATERIAL/BATCH NUMBER as the key. All production which shares the same Material and Batch will therefore have the same Expiry (Best Before End) date. The format of the Batch Number is defined above and can include a Julian Date component so that it automatically changes at midnight. SSCC mode will store the Expiry Date in the PALLET record and as such allow you to change the expiry date independently of the Batch Number.
|-
! scope="row" | HELPSET FILENAME
| help/helpset.hs || Deprecated - no longer used. Help now linked to Wiki pages.
|-
! scope="row" | INTERFACE LOG ID
| 1 || Sequential Unique ID used to record all Interface activity (Inbound and Outbound).
|-
! scope="row" | INTERFACE REQUEST ID
| 1 || Sequential Unique ID used by outbound interface queue.
|-
! scope="row" | LABEL_HEADER_COMMENT
| Free Format Text || Optional free format text than can appear on Finished Goods Label.
|-
! scope="row" | MAIL_POP_AUTH_PWD
| password || Not currently used.
|-
! scope="row" | MAIL_POP_AUTH_USER
| user || Not currently used.
|-
! scope="row" | MAIL_POP_HOST_NAME
| host.com || Not currently used.
|-
! scope="row" | MAIL_SMTP_AUTH_PWD
| password || SMTP password.
|-
! scope="row" | MAIL_SMTP_AUTH_REQD
| true || Indicates if SMTP server requires authentication.
|-
! scope="row" | MAIL_SMTP_AUTH_USER
| user || SMTP username
|-
! scope="row" | MAIL_SMTP_FROM_ADDRESS
| user@me.com || Specifies SMTP sending email address.
|-
! scope="row" | MAIL_SMTP_HOST_NAME
| host.com || SMTP Host Name
|-
! scope="row" | MAIL_SMTP_MSG_TYPE
| text/plain || Format of mail message
|-
! scope="row" | MAIL_SMTP_PORT
| 25 || SMTP Port Number
|-
! scope="row" | MHN INITIAL DECISION
| Pending || Master Hold Notice default/starting decision for Pallet.
|-
! scope="row" | MHN NUMBER FORMAT
| XX{NNNNNN} || Defines the structure of the Master Hold Notice Number. {NNN} indicates the numeric element. XX is a literal prefix.
|-
! scope="row" | PASSWORD ATTEMPTS
| 3 || Maximum number of invalid password attempts before an account is locked out.
|-
! scope="row" | PASSWORD EXPIRY
| 30 || Number of days before a users password expires and they are prompted to change it.
|-
! scope="row" | PLANT
| 1234 || Deprecated - no longer used.
|-
! scope="row" | PROCESS ORDER NUMBER
| 1 || Used to determine the numeric element of the next Process Order number (when created manually).
|-
! scope="row" | PROCESS ORDER NUMBER FORMAT
| {NNNNNN} || Defines the structure of the Process Order Number. {NNNNNN} indicates the number above.
|-
! scope="row" | PROGRAM VERSION
| 3.63 || Stores the current version of the Application. Users are warned if they attempt to connect with different version.
|-
! scope="row" | REPORT REQUEST ID
| 3.63 || Used internally for queuing report requests generated by user of the web interface on RF Barcode Scanners.
|-
! scope="row" | RESOURCE LIST
| \01\02\03\04\ || Delimited list of values. User can select these values when using the Process Order Barcode printing facility.
|-
|}

2024-01-05T11:21:23Z

Dgarratt:

Permissions

2024-01-05T11:21:08Z

Dgarratt:

Permissions within Commander4j work like this. 

Individual screens and reports are referred to within the application as Modules.

A module can be :-

* Form (screen)
* Report (JasperReport or Barcode Label)
* Functions (actions assigned to buttons)
* Menus
* Executables (External programs)
* User Report (reports which can override default reports)

Modules are put into logical groups which perform a role (logical group of associated functions).

Groups can then be assigned to a User

== Assigning [[Modules]] to [[Groups]] ==
 
[[File:Commander4j_Permissions.png|800px|thumb|left|Assign Modules to Groups]] 

== Assigning [[Users]] to [[Groups]]. ==

[[File:Permissions.png|800px|thumb|left|Assign Groups to User]]