Web Messages
Before creating your site, it is advised to read the documentation:Before beginning.
This function is used to modify the messages used by the XTEND server.
The messages are different from those sent by the X3 actions via call up of the sub-programs 'ADDMESSERR'.
The Web messages are managed by the XTEND engine and sent when the engine notices a error in processing or access rights.
Getting started
The XTEND messages are processed as the X3 application messages and are integrated in the translation process.
Message setups
Use syntax below to add setups in the messages:
Value of setup no.1={1} - Value of setup no.2={2}
Messages of the XTEND engine
All messages whose code begins with 'A' are messages of the XTEND engine.
You can modify these messages by asociating them with another chapter in which the new texts have been entered by keeping the setups.
|
Code |
Parameters |
Description |
|
AERRACCESSDENIED |
None |
Access to a protected page not authorized |
|
AERRACCESSPROFDENIED |
None |
Access to a protected page not authorized for this profile |
|
AERRACTION |
CodeAction |
Error in an action processing |
|
AERRCRITMANDATORY |
Name of criteria |
Mandatory criteria not entered |
|
AERRDATA |
Interface code |
Error during an 'Access to data' |
|
AERRJAVA |
|
Java exception |
|
AERRPAGE |
Page code |
Eror while reading or parsing the tokens in the HTML page |
|
AERRPROTOCOL |
Page code |
Code page http protocol mandatory to read this page |
|
AJSWEBFLDBADVAL |
None |
Control of the values of mandatory Web fields |
|
AJSWEBFLDMANDAT |
None |
Control of mandatory Web fields |
|
ASESSLOGIN1 |
None |
Welcome message of the login page if user not logged in |
|
ASESSLOGIN2 |
None |
Welcome message of the login page if user logged in |
|
ASESSLOGINKO |
None |
Login message KO |
|
ASESSLOGINOK |
None |
Login message OK |
|
ASESSLOGOUT |
None |
No Logout message |
|
ASESSRESTORED |
None |
Indicates that the session has been restored after closing/opening the browser |
|
ASESSLOGRESTORED |
None |
identical ASESSRESTORED for a logged in user |
|
ASESSTIMEOUT |
None |
Relogin request if the inactivity delay of the session is inactivity delay (user logged in) |
|
ASESSTRACESET |
None |
Activation/Deactivation of the log file |
Display messages in the HTML page
User messages are displayed via the token AXUSERMSG.
For example:
<span id="userMsg" class="userMsg" adx="aMsgUser"></span>
Display messages in JavaScript
In order to display a message that is no XTEND engine message, call up JavaScript function xtdAlert(aId,aP1,aP2,aP3,aP4) from the HTML page.
Function xtdAlert requests the message to the XTEND server via an AJAX request.
Parameters
- aId is the code for the XTEND message
- aP1,aP2.. are (optional) setups
This may happen during the control of a HTML form for instance.
<script>
function xtdAlert(aId,aP1,aP2,aP3,aP4);
// The following example displays
// 'You are connected to the application with DIS001 use code'
xtdAlert("ASESSLOGIN2","DIS001");
</script>
Refer to documentation Screen management
Entry screen
Block number 1
| Message code (field MESCOD) |
|
Code of the message |
| Site (field FCYLIB) |
|
Current Web site |
| Description (field INTIT) |
|
Use this field to assign a description to each record. |
Type of message
| Category (field CAT) |
|
This optional information is used to sort messages by category. |
Location
| Chapter (field LANCHP) |
|
Identifier of the local menu containing the message. |
| field CHPDES |
| Number (field LANNUM) |
|
Select a number (index in local menu). The XTEND message can be formed of two messages coming form the local menu. |
Message
| field LANMES |
Reports
By default, the following reports are associated with this function :
PRTSCR : Screen print
This can be changed using a different setup.
Specific Buttons
|
Copy |
This button is used to copy a Web message |