Aztec - 3.22.0

Head Office Configuration

1. At Head Office, open Staff & Security | Configuration | Password Policy

2. To enable a Back of House role with permissions to edit the Password Policy screen, this can be enabled in Staff & Security | Back of House Roles | [Select Role Name] Assign Permissions | Staff & Security roles | Configuration | Password Policy

   

   If a user doesn't have the "Edit Password Policy" role permission they will still be able to view the Password Policy screen, but will have no option to edit

   If the role has read only access, there is no option to Save or Discard.

   

Configurations that are included in this release are:

• Minimum password length (currently supporting 6-20 characters)

• Maximum password length (currently supporting 6-20 characters)

• Special characters required (from a subset)

In addition to the configurations listed above, this feature also includes some enhancements that aren't configurable:

• Preventing a password from being the same as the user name

  

• Password cannot be the same as the current password.

  

• There is now a hint to advise of password rules configured Show password policy rules.

Any existing passwords will be valid until a password is changed

Any Aztec pre 3.22.0 sites will not be included in any password configuration policies

Head Office Configuration

There are some configurations within Password Policy which are enabled by default in this version of Aztec. These configurations can be changed as described below.

1. At Head Office, open Staff & Security | Configuration | Password Policy.

2. Within the new Password Policy page Password Rules configurations will be available to configure.

3. Once you have configured your password policy, you will need to save your changes.

Password Policy configurations are configurable on a per Estate basis

Minimum Password Length

Minimum password length is enabled by default to 10 characters. This can be changed to an absolute minimum of 6 characters and a maximum of 20 characters.

You will not be allowed to set Minimum password length to less than 6 characters.

It is recommended that the minimum password length is set as no less than 10 characters

You will be alerted and prevented if you try and change the Minimum password length to be greater than the Maximum password length

Maximum Password Length

Maximum password length is enabled by default to 20 characters. If the Maximum password length is changed the maximum length allowed can be set to be the same or higher than the minimum password length. The absolute maximum password length is 20 characters.

You will not be allowed to set Maximum password length to more than 20 characters.

You will be alerted and prevented if you try and change the Maximum password length to be less than the Minimum password length

If you don't make changes to the minimum and maximum password lengths, then the defaults will apply

Special Characters Required

Special characters required is enabled by default which requires a user to include a special character from a subset (listed below) in their password.

The following special characters that are supported for Special Character required are !"#$%&'()*+,-./:;<=>?@[\]^_`{|}~

If you de-select Special Character required, it is still possible to include a special character in your password, but it wont be enforced

Special characters required is enabled by default

Head Office Configuration - Send Changes to Sites

For the new settings made at Head Office to take effect at site, perform a communications job to the required sites.

For detailed information on running communications jobs click here.

At Site

After a password policy configuration has been made at Head Office and successfully sent to an upgraded site, when a user logs onto Aztec, they will be prompted with the below dialogue box where they will be required to enter their existing (old) password, followed by entering a new password and then confirming the new password.

When a password policy has been configured or changed, a hint will be provided to the end user via a link label to assist them when changing their password.

When you click on the Show password policy rules hints will be provided based on what has been configured at Head Office. Please see example below.

If you fail to meet the criteria set when changing your password, you will be provided with a further notification to assist of what is still required.

You will also be prompted if you don't correctly enter your old password first

Password Expiry configurations are configurable on a per Estate basis

Head Office Configuration

This feature does not operate by default in this version of Aztec, it must first be configured as described below.

At Head Office, open Staff & Security | Configuration | Password Policy.

There are 2 configurations that are applicable for Password Expiry:

Password expiry (days)

This allows a Head Office user with relevant role permissions to configure the number of days before a password expires.

The configuration is set at 0 days by default which means that it doesn't expire.

The minimum number of days that this can be configured for is 0 days and the maximum number of days before a password will expire is 999 days.

The default of 0 days is set (ie the password doesn’t expire). This is the recommended setting.

 

Once you have configured your password policy, you will need to save your changes.

Password notification (days)

This allows a Head Office user with relevant role permissions to configure the number of days where you will be notified before your password will expire .

The configuration is disabled by default.

When this configuration is enabled, the default is 1 day. Please note that if changing from the default, the minimum number of days that this can be configured is 1 day and the maximum number of days before a password will expire is 14 days.

There is a hint to explain this configuration

Once you have configured your password policy, you will need to save your changes.

It is not possible to set the Password expiry notification to be greater than or equal to the Password Expiry period

It is not possible to set the Password expiry period to be less than or equal to the Password Expiry notification

To prevent having to change your password on the same day as when it was last changed, it is not possible to set Password expiry to 1 day

Please note that if the Password expiry is set at 0 days (ie that it won't expire), then you will not be able to set a notification period

Head Office Configuration - Send Changes to Sites

For the new settings made at Head Office to take effect at site, perform a communications job to the required sites.

For detailed information on running communications jobs click here.

At Site or at Head Office

When a password expiry has been configured along with a password notification, a user will be notified when their password is due to expire. Before the existing password has expired, there is an option to change the password (selecting Yes) or continue without changing the password (selecting No).

The message is slightly different if the password is due to expire that day.

If the password has already expired, the following message will be displayed to the user. If the user selects No, then they will be taken back to the login screen. They will be unable to continue until they select Yes and change their password.

Password Enhancements - Ability to change own or another user's password - AZT-650

Some security enhancements have been made to changing a user's own Aztec password and also the ability for a user at Head Office or Site to change another user's password.

 

This is not a configurable setting. Account number will show on the POS post upgrade to Aztec 3.22.0

If there are more than 3 items to be displayed on the account such as Acc No, Table, Customer Name and Held status some of this information will be displayed intermittently
US Locale will show Acc No. as Chk No (as per wording on the order display)

This is a US only customised feature for a specific loyalty integration only. This is not for general use.

Head Office Configuration

This configuration does not operate by default.

This can be configured at Aztec Head Office Theme Modelling | Site Setup | Printing Print QR code for Check Payment.

Print QR Code Code for Check Payment is configurable on a per site basis and will be off by default.

UK locale name for this configuration is Print QR Code for Bill Payment

It is also possible to configure the text that prints above and below the QR code on the bill/check. This can be configured in Theme Modelling | Estate Setup | MessageDisplay.

UK locale name for this configuration is Print QR Code for Bill Payment

It is possible to enter 5 lines of text that will appear above the QR code and 4 lines of the text below the QR code. It is also possible to format the text: Alignment, Bold, Double-Width and Double-Height.

Head Office Configuration - Send Changes to Sites

For the new settings made at Head Office to take effect at site, perform a communications job to the required sites.

For detailed information on running communications jobs click here.

At Site

When a bill is printed at site, a QR code will also be printed which can then be used to pay the bill.

Promotion Details Maintenance configuration is off by default

Head Office Configuration

At Head Office, open Theme Modelling | Estate Setup | Global Configs.

Promotion Details Maintenance checkbox is disabled by default. When enabled, this will allow a retention period (in days) of how long a deleted promotion will be archived in the database during which time it is possible to restore the promotion. Out with the retention period any deleted promotion will be permanently deleted from the database.

The minimum retention period that can be set is 3 months (90 days) and maximum retention period that can be set is 36 months (1096 days).

When Promotion Details Maintenance check box has been enabled, a default retention period of 13 months (395 days) is applied

A hint is provided to the end user.

It is possible to change the Retention Period (days) either by typing the number directly into the box or by using the arrows to the right of the box

When Promotion Details Maintenance has been enabled with a configured retention period, note that when the Promotions module is first run there will be a slight delay as the maintenance to the promotion tables is carried out.

When Promotion Details Maintenance has been configured with retention period, the first run of the Promotions module by a user each day where you see the Please Wait messages briefly may take slightly longer than at other times whilst this process of permanently deleting and archiving promotions are carried out

The first comms link to sites post configuration may also take slightly longer due to updates of archiving and deleting of promotion tables

There is a new View Deleted button added to the main Promotions screen which when clicked on, presents the user with all of the deleted promotions that are available to be restored within the configured retention period.

When there are no deleted promotions to restore, the View Deleted button will be greyed out

If there any deleted promotions available to be restored, the headers of these promotions will be displayed when you click on View Deleted.

Click on the deleted promotion that you wish to restore which will highlight the promotion in blue and click on Restore Selected

When a deleted promotion has been selected to be restored, a warning prompt will be displayed to make sure that you want to proceed (OK or cancel with X).

A confirmation message will be displayed that the selected promotion has been successfully restored.

The restored promotion will then be removed from Deleted Promotions list.

There is an option to filter on the deleted promotions available to restore.

Promotion Details Maintenance configuration is applicable to both Head Office created promotions and Site created Promotions

On multi-user environments, a user will be alerted if a deleted promotion is restored before another user tried to restore it

At both Head Office and Site, post upgrade, when a user first logs in, they will be prompted to change their password (which will then be stored using both MD5 and BCrypt formats). Pre Aztec 3.22.0 sites (non-upgraded sites) will continue to use existing MD5 encryption for passwords until they upgrade.

Upon upgrade to Aztec 3.22.0 sites will no longer be able to access the Rewards for Reservations module via the Aztec shell. The application can still be used using Aztec password, but will need to access this out with the shell (such as via icon on desktop).

Upon upgrade to Aztec 3.22.0, if using APOS from within the Aztec shell, when you open the APOS module, you will be prompted to authenticate again using the same password.