Differenze tra le versioni di "ItmSUITE® - Introduction to basic configuration"
(→Admin creation) (Etichetta: visualeditor) |
|||
| Riga 17: | Riga 17: | ||
|- | |- | ||
| − | |Name || The name of the ''[[Glossary#C|company]].'' | + | |<u>Name</u> || The name of the ''[[Glossary#C|company]].'' |
|| Mandatory | || Mandatory | ||
|| | || | ||
|- | |- | ||
| − | |Status || The status of the ''[[glossary#C|company]].'' | + | |<u>Status</u> || The status of the ''[[glossary#C|company]].'' |
|| Mandatory | || Mandatory | ||
|| The initial status of a new ''[[Glossary#C|company]]'' is: "Provisory | || The initial status of a new ''[[Glossary#C|company]]'' is: "Provisory | ||
| Riga 28: | Riga 28: | ||
|- | |- | ||
| − | |Application Url || The url where itmSUITE® is available. | + | |<u>Application Url</u> || The url where itmSUITE® is available. |
|| Mandatory | || Mandatory | ||
|| This url is placed in emails and used by ''[[Glossary|users]]'' to directly access itmSUITE® from them. | || This url is placed in emails and used by ''[[Glossary|users]]'' to directly access itmSUITE® from them. | ||
|- | |- | ||
| − | |Disable Email Notification || The ''[[Glossary#C|company]]'' not send email notification | + | |<u>Disable Email Notification</u> || The ''[[Glossary#C|company]]'' not send email notification |
|| Discretionary | || Discretionary | ||
|| If unset, this configuration disable any mail notification for the ''[[glossary|company]]''. This may be useful until it is not live to avoid useless communication. | || If unset, this configuration disable any mail notification for the ''[[glossary|company]]''. This may be useful until it is not live to avoid useless communication. | ||
| Riga 47: | Riga 47: | ||
|- | |- | ||
| − | | | + | |<u>Login</u> || The ''[[Glossary|user]]'' identifier for the login. |
|| Mandatory | || Mandatory | ||
|| | || | ||
|- | |- | ||
| − | | | + | |<u>Password</u> || The password to access when the ''[[Glossary|user]]'' logs in. |
|| Mandatory | || Mandatory | ||
| − | || The | + | || The password shall be confirmed in the <u>Confirm Password</u> field. |
| − | |||
|- | |- | ||
| − | | | + | |<u>Confirm Password</u> || The url where itmSUITE® is available. |
|| Mandatory | || Mandatory | ||
|| This url is placed in emails and used by ''[[Glossary|users]]'' to directly access itmSUITE® from them. | || This url is placed in emails and used by ''[[Glossary|users]]'' to directly access itmSUITE® from them. | ||
|- | |- | ||
| − | | | + | |<u>Change Password Mode</u> || The ''[[Glossary#C|company]]'' not send email notification |
|| Discretionary | || Discretionary | ||
|| If unset, this configuration disable any mail notification for the ''[[glossary|company]]''. This may be useful until it is not live to avoid useless communication. | || If unset, this configuration disable any mail notification for the ''[[glossary|company]]''. This may be useful until it is not live to avoid useless communication. | ||
Versione delle 08:50, 22 mar 2015
Indice
Configuration steps from scratch
This section covers the basic configuration of itmSUITE® from scratch.(when no data is present) This includes:
- Company creation
- Admin creation
- System settings
- Cross master data
- Users and resources
- Notifications
- MB - Message bus
It is recommended to perform the configuration in the order listed. For more information on how to perform each configuration step refer to the dedicated page.
Company creation
As a first step the activation of a company is needed. itmSUITE® is a multi company organization and more than a company maybe activated on a single instance of the system by repeating the steps below. See the configuration scenarios page for more information on why and when to create multiple companies. To create a company first of all you shall access as a superadmin to the system. Then you may create a company. After listing companies with General/System/Companies, Add New allows to create a new company. To complete the company creation, the information listed in the following table shall be provided.
| Field | Description | Characteristics | Comments |
|---|---|---|---|
| Name | The name of the company. | Mandatory | |
| Status | The status of the company. | Mandatory | The initial status of a new company is: "Provisory
Additional and subsequent statuses are "Active" and "Inactive". It is possible to operate on the company only if its status is "Active". |
| Application Url | The url where itmSUITE® is available. | Mandatory | This url is placed in emails and used by users to directly access itmSUITE® from them. |
| Disable Email Notification | The company not send email notification | Discretionary | If unset, this configuration disable any mail notification for the company. This may be useful until it is not live to avoid useless communication. |
These are not all the company information but only those needed to create a new one. For details on the full configuration of the company please refer to the itmSUITE® - Cross master data configuration page.
Admin creation
The next step is to define an admin for the created company. Still logged as superadmin goto to General/System/User Management and add a user. Add New allows to do it. To complete the user creation, the information listed in the following table shall be provided.
| Field | Description | Characteristics | Comments |
|---|---|---|---|
| Login | The user identifier for the login. | Mandatory | |
| Password | The password to access when the user logs in. | Mandatory | The password shall be confirmed in the Confirm Password field. |
| Confirm Password | The url where itmSUITE® is available. | Mandatory | This url is placed in emails and used by users to directly access itmSUITE® from them. |
| Change Password Mode | The company not send email notification | Discretionary | If unset, this configuration disable any mail notification for the company. This may be useful until it is not live to avoid useless communication. |
Configuration steps with the default database installed
itmSUITE® installation pacakge is provided with an initial configuration corresponding to a demo environment, It is still recommended to go through the configuration steps described in the previous paragraph in order to get acquainted with the demo environment content and to change configurations according to the needs.
