Release 19.01.2024

Release 03.01.2024

Select tenant

(RTC-23950)

When having access to more than one tenant, user sees modal where last used tenant is proposed as first. Last login on that tenant is given as well. In the bottom section of modal user can search for different tenants, as well as see proposition of the other available tenants.

The user is authenticated during login, and cannot access modules after logging out.

Select tenant

(RTC-37586)

When having access to more than 10 tenants, user is able to login and sees modal where last used tenant is proposed as first. Last login on that tenant is given as well. In the bottom section of modal user can search for different tenants, in order of last login, as well as see proposition of the other available tenants.

Card ID for cashiers

(RTC-36444)

Cashiers can have assigned Card IDs, and it is possible to add such ID's manually or by import. For users with no cashier, no information about card ID is visible. If cashier has no Card ID, then there is a text 'Card ID is not added' under Card ID section. To add Card ID, user has to click on the 'edit cashier' button and select 'Add Card ID' option. Card ID can be any string, but cannot be empty or have spaces in front or in the end. After saving entered value, text changes to 'Active Card ID'. It is possible to change card ID or deactivate it, both by choosing correct option is dropdown in 'edit cashier'.

Card ID is saved in database as hash and it is also exported as hash to 3rd party in UserManagement.User.Export blobs. Export is triggered when there are made any changes to Card ID - that means it is added to user, changed or deactivated. For inactive Card IDs, they are exported as empty brackets.

Release 03.11.2023

Release 20.09.2023

Release 22.08.2023

Release 19.07.2023

Release 31.05.2023

Release 15.05.2023

Managing cashiers

(RTC-30012)

Editing options for cashier user are displayed in a dropdown with the 4 different options:

• Change PIN
• Reset PIN
• Change cashier number
• Deactivate

Options are visible in dropdown when clicking edit cashier button. Information on deactivated cashier is
shown above Cashier number.

Improvement

Release 29.03.2023

System administrator role

(RTC-27421)

• The SystemAdministrator role includes permission "ManageAdministrators". 
• A user with ManageAdministrators permission can:
  • Add and remove this permission from the role (otherwise it is greyed out)
  • Add to a user and remove from a user a role containing this permission.
• If the user has a role that does not contain ManageAdministrators permission, he cannot remove or add a role containing this permission, he will be informed about it with a notification.

Active flag on cashiers:

(RTC-29354)

• When a user is sent with CashierNumber, he has his cashier active. 
• When a user doesn't have a CashierNumber at all - nothing changes (Cashier is not added).
• If user that currently has a cashier, will be sent without CashierNumber, the cashier is deactivated for him.
• When a cashier is inactive, it's not exported to POS (Cashier, not user).
• All users that are cashiers right now, are updated as active ones. 

Cashier management

(RTC-29674)

When adding or editing cashier, there is no notification about required field if selecting option "Get next available number".

Secure cashier password

(RTC-28865)

Cashier password is stored as hash in database.

Release 02.02.23

Automatically creating users as part of the invitation process

(RTC-28888)

In the job InviteFromAzureAdToAzureAD it is possible to specify a permission for the invited Azure AD group. This enables us to automatically create the user in User Management and assign a role to the user.

If the property "OfficeLocation" is set in Azure AD and the permission group in User Management is per store (not common) we will assume that this contains a store number and assign this store number to the user created. If this group has one or more POS permissions enabled we will automatically create an active cashier for this user. 

If the role is a common role, then it is not required to have the OfficeLocation parameter set in Azure AD.  

Release 01.02.2023

Manage cashier pin code

(RTC-26198)

In User Management you can manage cashiers with pin code for login to POS.

• A cashier can be deactivated and activated.
• Pin can be changed and reset.
• Cashier number can be changed. 
• In case of 'PIN set in POS' CashierPin is the same as CashierNo.
• Creating new user with PIN does not have cashier creation (but without pin has).
• There is validation for wrong old password and cashierNo already set to other user.
• It is not possible to create a new password with the same as already existing. 
• Password must be of the appropriate length, specified by the parameter.
• Configuration parameter in database CashierPasswordMinLength.

Release 25.01.2023

Import of cashiers

(RTC-26872)

API for importing users as cashiers is extended:

Additional fields and business rules in contract: Cashier.CashierNo

• CashierNo is set based on values in import file, it can be imported regardless of ExternalUserIdentifier
• If there's no cashierNo, but there's externalUserIdentifier, Cashier No and cashierPassword are set based on externalUserIdentifier
• Otherwise CashierNo is set based on the value in file, CashierPassword and CashierPasswordHash are set based on CashierNo
• If CashierNo is not changed for user, CashierPassword and CashierPasswordHash are not changed either (if the CashierNo is changed in import, they're changed as well)
• CashierNo must be unique
• CashierNo and CashierPassword, CashierPasswordHash are exported with cashier user
• CashierInStore Table is no longer maintained
• User can have username changed in import, it is then matched by ExternalIdentifier (lookup by CashierNo is not supported)
• When user has role with POS permissions on all stores level, he's exported with cashiers on each store. When new store is created, user is exported again, with cashier in new store.

Manage cashier 

(RTC-26844)

• Parameter PasswordExpiryInDays defines how many days the password will be valid for the cashier. By default, it has a value of null.
• Using a method from Shell API, you can check if the password is valid, and when it expires.
• Using a method from the Shell API, you can change the password for the cashier.
• The Identity.UserProfile table contains CashierPasswordLastChangedUtc column, which is updated when the password is changed.

Release 24.11.2022

Release 18.10.2022

Release 04.08.2022

Release 29.06.2022

Import of cashiers

(RTC-21094)

Cashiers are automatically created if the imported user has any cashier permissions. Adding a role with POS permission or POS permission to a role that user already has creates cashiers for all relevant stores.

Removing a role or POS permission from a role that user already has removes the cashiers for all relevant stores.

Adding a store to team/profile (when user has team/profile role), creates cashiers on all relevant users/stores

Removing a store from team/profile (when user has team/profile role) removes the cashiers.

Improvements

Release 11.03.2022

Release 19.11.2021

Release 28.09.2021

Release 27.08.2021

Release 16.08.2021