User (Employee) Admin Screen

This article describes some of the features of the screen.

Leave Date

If a leave date is set against an Employee record then it will not be possible for that user to log into the system.

You can only add a leave date via the web on this screen if leaverdatesourceweb flag for the Client is set to true. If the flag is set to false it is likely that this information is imported from an external system.  It will not be possible to allow the changing of the leave date on the web as well as it being imported from another system as there may well be conflicts.  One of 2 other conditions also has to be met for this functionality to be available on this screen:

1. the HideLeavers flag agains the Shop (Client) has to be false OR
2. the user has to have the RoleFunctions.WearerAdminShowLeavers

 Password Reset

To be able to access this functionality users should have enhanced privileges :

- shop with security level enabled

1. Reset User Passwords
2. Security Override - Allow Password Rst to Default

- other shops : Security Override - Allow Password Rst to Default

Points Adjustment

Adding points

Points are added for the Employees (Clients) current cycle unless a start date or end date for the points has been entered.

Current Point Adjustment value

This represents the points for the current cycle and is the same as the Additional Points shown on the Mini Shopping Basket on the right hand side of the Order page. 

Technical Info Only:

- Formatting of the Points table using the TableCloth look / feel by copying the following Content from an existing web site: 901 <!-- tablecloth code - Rows only -->

- Addition of DatePickers to the 3 Date fields can be done by copying the following Content from an existing web site:

903 <!-- CSS / Javascript - JQuery Widget Code --> and

904 <!-- EMPL - Wearer Admin - Specific Javascript - JQuery -->

Points remaining against a Catalogue during the ordering process

Points remaining against a Catalogue during the ordering process are calculated on the fly and will depend upon what, if anything, has been ordered from (or returned to) a Catalogue (Wardrobe), and if the user has access to multiple Catalogues whether they vary in the way they are set-up.  If Catalogues that allow multiple orders to be placed against them vary in set-up then more or less points may be deducted depending on if all items ordered from the first Catalogue in previous orders during the users current Replenishment Cycle are present in the second Catalogue, and indeed the points Allocation values set against each Catalogue.

This is a powerful feature in that it means that:

• you never have to keep track of an individuals points, and can increase all users points by simply changing the points allocation against a Catalogue.  Indeed if another Catalogue is set-up to replace the first, but a higher points allocation has been set against the second catalogue to take account of different items / set-up, then this is automatically taken care of without the need to adjust every users points value
• You can adjust the number of points against an item and this will also be taken care of automatically and will be reflected in the points a user has available next time they place an order

Because of this:

• You have to be mindful that if you remove items from Catalogues that have been ordered in the past otherwise it will free up users points and they will be able to place an order for a similar item.  It will best simply to mark the item as 'Hidden' in the Catalogue in this case.
• It may not be sensible to allow a user to access more than 1 Catalogue at any time against which they can place orders.