Coming next release
Managing cashiers
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.
Release 29.03.2023
System administrator role
- 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:
- 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
When adding or editing cashier, there is no notification about required field if selecting option "Get next available number".
Secure cashier password
Cashier password is stored as hash in database.
Release 02.02.23
Automatically creating users as part of the invitation process
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
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
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
- 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
Module | Description |
|---|---|
| System | Configuration of new modules for tenants (RTC-26815) When a tenant is not fully configured or a tenant is registered in one of the modules, but not in Cloud shell, then after a module restarts, the module will work for other tenants. |
Release 18.10.2022
Module | Description |
|---|---|
| Import users | Import of users RTC-26046) When importing a user into User Management and store/team/profile doesn't exist, the user is imported and a placeholder is created for store/team/profile. |
| Roles | Fix: Saving permissions on store roles (RTC-23482) Store roles with Manage local item permission can be saved. |
| System | Job exceutions with CompletedWithNoEffected (RTC-22786) When StagingMerger job (In IdentityServiceIntegration/Shell) executes with no effect, the status is 'Completed with no effect'. |
Release 04.08.2022
Module | Description |
|---|---|
| Import users | Import of users (RTC-24804) New cashier can be created directly from JSON contract file (having externalUserIdentifier and store role with POS permission). |
| System | Fix: Configuration cleared when switching between tenants (RTC-22045) Configuration browser cache is cleared each time the user logs in. Fixes issue when switching tenants that have different configuration (user needs to log out and log in, in order to switch tenants). |
Release 29.06.2022
Import of cashiers
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
Module | Description |
|---|---|
| Export users/cashiers | Export users/cashiers (RTC-20015) User profile can be exported with all permissions and scoped permissions to JSON file (UserManagement.User.Export blob) After manually create cashier in database, cashiers are also exported as in case of users. All users can be exported to JSON (To do this, change the "version" value to 0 in Export.BlopType in db). |
| Import users | Import of users (RTC-18492) Users are created and update with new common/scoped roles when using API with JSON contract for import. |
| User Management | Searching for users (RTC-23440) A user with SystemAdministator role (only) can search for users in Find User component in User Management, while creating new users. |
| User roles | Fix: Delete store row from user roles view (RTC-22649) While assigning store scoped role to user it is possible to delete this role right after creation. |
Release 11.03.2022
Module | Description |
|---|---|
| User Management | Create new users with alternative emails (RTC-15501) When creating new users in the system will also persist the users alternative emails. Fix: Invitation job for users (RTC-21363) When users are invited into our tenant specific AAD from the source AAD (managed by the customer), we will also copy the 'alternative emails' of the source user. |
Release 19.11.2021
Module | Description |
|---|---|
| User Management | Unblocking users (RTC-18167) If user is unblocked in Azure Active Directory, the user is unblocked in User Management. |
Release 28.09.2021
Module | Description |
|---|---|
| User Management | Creating users from Azure AD (RTC-15608) First name and Last name, split from Display name, are added automatically to the user when creating it in User management. First name, Last name, Display name of existing users can be edited. Users removed from Azure AD (RTP-13388) When a user is removed from the Azure AD Group in source AAD the user is blocked from logging in in the destination AD. If the user is added to the Azure AD group again in the source AD we did not unblock the user in the destination AAD. This is fixed and we are checking the "Block sign in" flag on the user from the destination AAD. |
Release 27.08.2021
Module | Description |
|---|---|
| User Management | ''All stores" option in store roles (RTC-15018) There is an option to select all stores in Store level when adding new store role to the user. This option is only visible if user has access to all stores in the user's details tab. |
Release 16.08.2021
Module | Description |
|---|---|
| User Management | Users with pending invitations to Azure Active Directory (RTC-15096) If a user has a pending invitation to a tenant and is added to User Management of this tenant, they will be granted access to this tenant when they try to login. When they select the tenant in the tenant selector, they will be presented with the window to accept the invitation and they will be immediately logged in after accepting it. |