# 1. Setup

# Role and eCom Employee

## Summary

The eCom system requires its own employee with a dedicated role.

This role controls which functions the shop offers — just like with the field service client.

Without an eCom licence, the main menu item **eCom** does not appear in the web backend.

## Procedure

1. Ensure that an eCom licence is available.
2. Create the eCom employee under *Basic configuration > Employee*.
3. Check the box **Ist eCom** for this employee.
4. Create a role and assign it to the eCom employee.
5. Set the eCom-relevant rights in the role.
 

### The checkbox *Ist eCom*

This makes the employee the user under which the shop operates. Without it, the eCom system does not recognise the employee as its own — role and rights then remain ineffective, even though everything appears maintained.

> **Important:** Only **one single** employee may have this checkbox. A second eCom employee is not intended.

## Which rights must be set

You can recognise the eCom-relevant rights by the **blue cart symbol** behind the entry. Rights without this symbol do not affect the shop.

A complete list with the respective effect in the shop is available in the specification on the page *eCom rights at a glance*.

> **Important:** You define the **scope of functions** via the role, not the question of whether ordering is allowed. A customer with access can always order. If a customer should not be able to order, they need a **lock at the customer**. There is no right for this in the role, and it cannot be set in the backend either: it comes from the **ERP system** and is delivered with the customer data.
> 
> **Note:** How the lock affects the shop is currently under review. It has been observed that a locked customer can **submit** the order and receives a confirmation without an order being created. For the moment, do not rely on a lock to properly block the shop. See [Order completion](https://wiki.dedesales.de/books/leistungsbeschreibung-ecom/page/bestellabschluss) in the specification.

## E-mail address of the employee

The e-mail address stored for the eCom employee has a special significance: **In the test system, all shop e-mails go to this address**, not to the customer. This also applies to the e-mail with the visible password during registration.

The address is maintained under *Basic configuration > Employee*.

# Provision of Data

> **Attention, current limitation:** Provisioning of data currently does **not** work for pictures. If you have changed pictures — container, login graphic or logo — please use the **Rollout** button in the **Employee overview** instead. The limitation has been reported; as soon as it is fixed, the procedure described below will apply again.

## Summary

Amendments to the eCom configuration only take effect once the data has been provisioned.

The eCom system then automatically retrieves the provisioned data — depending on the setting every 15 or 30 Minutes.

The process is the same as with a normal client.

## Procedure

1. Change and Save configuration in the web backend.
2. Provision data.
3. Wait until the eCom system has retrieved the data.
 

## When the Pictures checkbox must be set

<table id="bkmrk-%C3%84nderung-haken-bilde"> <thead> <tr> <th>Amendment</th> <th>Pictures checkbox</th> </tr> </thead> <tbody> <tr> <td>Settings, Texts, Rights, Order templates</td> <td>not required</td> </tr> <tr> <td>Container with new or changed picture</td> <td>**required**</td> </tr> <tr> <td>Login graphic or shop logo</td> <td>**required**</td> </tr> </tbody> </table>

Without this checkbox, the pictures will not be transferred, although the rest of the configuration arrives.

## Most common error case

An uploaded picture does not appear in the shop. The cause is almost always one of the two:

- After uploading, it was **not Saved**. An uploaded picture initially only resides in the temp folder; only *Saving* moves it to the correct folder.
- It was provisioned **without the Pictures checkbox**.