Global Settings
- Amelia Witka (Unlicensed)
Below are presented and explained:
Global parameters
Global parameters
- List of all parameters
| Parameter | Description | Obligatory? | Remarks |
|---|---|---|---|
WD8_DBM_JOB_ABGRU | VSS order rejection reason | Yes | Used only for VSS<->SRS interface |
WMA_DTR_TXT_ID | Decision Tree text ID | Yes | Used for Decision Tree processing in SRS |
WMA_ICS_DEF_METHOD | REQUEST | No | Used only for ICS file generation functionality |
WMA_ICS_ORG_ADDR | No | Used only for ICS file generation functionality | |
WMA_OAS_SITE_KEY | Site Captcha key | No | Required for Captcha functionality in OAS |
WMA_OAS_CAPTCHA_KEY | Secret Captcha key | No | Required for Captcha functionality in OAS |
WMA_OAS_COUNTRIES | OAS country filter | Yes | Used by OAS API to limit list of possible countries shown in OAS application |
WMA_OAS_LANGUAGES | OAS communication languages filter | Yes | Used by OAS API to limit list of possible communication languages shown in OAS application |
WMA_OAS_SAP_USER | Name of technical user for OAS | Yes | Determines if OAS is called in internal or external mode |
WMA_OAS_URL_EXT | URL for appointment in OAS | Yes | |
WMA_OAS_USER_LOGIN_T | OAS user login token validity time | Yes | Determines OAS user login token validity period (in sec.) |
WMA_OAS_TMP_PASSWD_T | Specifies how long temporary password is valid (after password reset operation) | No | In sec Default value: 30 min |
WMA_OAS_USER_VERIF_T | Specifies how long link in verification mail is valid after OAS user creation | No | In sec Default value: 2h |
WMA_OAS_USER_CONFM_T | Specifies how long link in confirmation mail is valid after OAS user creation by Backoffice | No | In sec Default value: 24h |
- Detailed description
VSS 2.0 parameters
- WD8_DBM_JOB_ABGRU
- Parameter used by SRS >VSS interface (package /DBME/WD8)
OAS specific parameters
- WMA_OAS_COUNTRIES
- Limits number of entries returned by OASCountrySet API request
- If not specified, all countries defined in SAP system will be returned (about 250 entries)
- Format: country ISO codes separated by comma
- Example: DE,IT,FR,US
- WMA_OAS_LANGUAGES
- Limits number of entries returned by OASLanguageSet API request
- If not specified, all languages defined in SAP system will be returned (about 40 entries)
- Format: language ISO codes separated by comma
- Example: DE,EN,IT
- WMA_OAS_SAP_USER
- Defines technical user name, that is used by OAS application called in external mode to connect to backend system
- WMA_OAS_USER_LOGIN_T
- Time in seconds; means how long OAS used login token is valid after successful login/verification
- WMA_OAS_TMP_PASSWD_T
- As described in the table
- WMA_OAS_USER_VERIF_T
- As described in the table
- WMA_OAS_USER_CONFM_T
- As described in the table
- WMA_OAS_URL_EXT
- Defines URL that will be sent via email with appointment confirmation
- It should point to OAS application screen with appointment detail
ICS file parameters
- WMA_ICS_DEF_METHOD
- Defines value of METHOD attribute used for ICS file generation (for scheduling new appointment/change data of existing appointment)
- WMA_ICS_ORG_ADDR
- Defines email address of appointment organizer, that will be put into ICS file
- Organizer attribute is important in case of rescheduling; otherwise calendar application is not able to change date of existing meeting (at least MS Outlook works this way)
Captcha parameters
- WMA_OAS_SITE_KEY
- Site key for captcha verification
- Determined during domain registration in Google Captcha service
- WMA_OAS_CAPTCHA_KEY
- Secret key for captcha verification
- Determined during domain registration in Google Captcha service
Example:
SAP User Settings
SAP User Settings - hierarchy assignment
Here the data administrator should define the hierarchy assignment of internal users, who will use Workshop Planner, To-Do Basket etc. applications.
Example assignment looks like following:
SAP User default setting
Notifications
Activate notifications
User can define here notification determination. For single criteria value, more data value lines can be defined. Each data value provides following attributes:
- Recipient type – can be end customer, plant manager etc.
- Active flag
- ICS attachment flag – if *.ICS attachment should be sent with e-mail
- Template for subject – html template (Object key / OAOR transaction)
- Template for body - html template (Object key / OAOR transaction)
Example settings looks like following:
