This table lists and describes the actions on the Activity Setup page:
| Action | Description |
|---|---|
| Web Log | Gives the user access to log entries related to the web API requests and responds. This is normally used for debugging purposes when a new API is being tested. This action can, however, also be used to monitor the health and status of the API transactions. With this option the user can test the APIs, that is create bookings, cancel bookings, request availability, and so on. The XML output of the responds can be reviewed as well. |
| Required Fields | Lets the user set up which fields are required for input during reservation or activity entry. The input is then validated whenever a status is assigned, except when setting status to the internal status Draft which is excluded for required fields. |
| BI Utilization | Allows the user to run the BI worktable preparation process manually, and also to run the process backwards (into the past), if this functionality is being implemented with existing information for the past which needs to be provided to the LS Central Insight for Bookings functionality. Here, the user can also review the data being populated. This process can also be set up as an automated task by a job scheduler. |
- On Reservations, the reservation type can also determine which fields are required, as well as the status which is being assigned.
- On Activities, the activity type can also determine which fields are required, as well as the status which is being assigned.
Use the Entry Code field on the Reservation Required Fields page to determine for which reservation type or activity type the field is required. Leave the field blank if it is always required.
Note: Settings that require no specific status (that is Status Code field is blank), will show the field in question on the Reservation or Activity card with an asterisk (*) to indicate that the field is required during entry. If Status Code is blank, the related field is always checked, regardless of the status assignment. If Entry Code is set (reservation type or activity type depending on table), the asterisk is only shown on the required fields if that related record is belonging to that reservation type or activity type.
Note: Only a limited set of tables is supported, but you can press F4 (Lookup) to see a list of supported tables in the Table ID field.
To set up structure and results
- Fields that are always required should have a blank Entry Code and Status Code. These fields will have asterisks either in the Reservation card or the Activity card.
- Fields which are only required at certain status assignments should have the Status Code field set as the status to be assigned. This will trigger the check of required fields. The fields will not have any asterisk indication in the cards, since the system does not know which status will be assigned.
-
Fields that are required only for certain reservation types or certain activity types should have an Entry Code assigned accordingly.
Asterisks will only be shown in the related field, if the reservation type or activity type matches the required field setup for that reservation and activity type.