System - Configurations
Description
The configuration determines how Cyclos looks like, feels and behaves for groups of logged users or for guests. Some examples of options that can be set in a configuration are the language, the address, the address layout, the number format, the mail server and much more.
Also most content management items are bound to a theme. E.g. per configuration you can edit the banners that are visible. These content management items are however edited through the content menu:
Business rules
Configurations are defined in an hierarchical fashion. There is one, hard-coded configuration, which is the system default. This system default configuration is always the root of any configuration tree. When creating a new configuration an existing 'parent' configuration need to be chosen, this can be the system default configuration or any other configuration the admin has the permission to manage. This means that all configurations descend directly or indirectly from the (hard-coded) system default configuration. An admin can chose to inherit the options from the respective 'parent' configuration or customize them (by selecting the edit icon). It is also possible to 'lock' options (by selecting the lock icon), when options are locked lower level configurations cannot change them anymore. Configurations which have child configurations cannot be deleted. Besides that, configurations may be set for specific guests (matching an URL parameter) and/or to specific users (through group and / or group set).
On runtime, always the most specific configuration is used for guests:
- Specific guest (matching URL parameter), if any
- System default
For logged users, the group determines the configuration that will be applied. A group has a configuration property; a configuration does not have a group property. A group can only have one configuration and must have a configuration - it may not be null. Groupsets also have a configuration. The groupset's configuration only determines what the default configuration will be in the form for creating a new group. However, the admin may just choose another configuration for this new group. The default configuration when creating a new groupset is always system default. As stated above, a user group can only have one configuration. However, a configuration is always part of a hierarchical configuration tree. A new configuration always needs to extend a higher level one. This means that all configurations in the system are part of a hierarcal configuration tree. The built-in 'global default' configuration is the top of the hierciarchy
Configuration applicabilitly
When viewing Cyclos as guest (not logged in) the configuration that will be applied is determined by the URL (domain or path) the user accesses. The URL/path is defined in the config.
When a user logs in to Cyclos the configuration will be applied that is bound to the group the user. Be aware, it does not take in account the access URL/path defined in the configuration of the user group.
A user can login in to a URL/path defined in configuration at a higher level. But the only difference is that he logs in at another URL. What he sees (layout, pages etc) is from the configuration that is bound to his user group.
Example, system with the following two configurations:
- Config1: bound to group1, URL: www.mybank.com
- Config2: bound to group2, extends config1, path: www.mybank.com/city
- A user from group2 can access both domains, www.mybank.com/city and www.mybank.com. And will get the same result once logged in.
- A user from group1 can access only by URL www.mybank.com
Restrictions
- It is also possible to set in a configuration 'access only by URL/path'. This means that users can only login at the path (not at higher defined URL/paths).
The advantage of this is that you can restrict specific access (e.g. global admins or Web services access) to a path, wich can be a hard to find path like www.domain.com/sdlf893knd9234rd.
- The 'access only by URL/path' restrictions, as well as the white lists restriction are applied when a session is established.
- If a global admin has session he can switch to lower level configurations without the restrictions being applied.
Therefore, when implementing IP and URL restrictions it is important that the higher global admin groups have similar or more restrictive permissions.
Rules for fields
- By default the value of the higher configuration is shown for each field, an edit icon is shown in the right column next to the field to customize the field.
- When a field is not customized (thus inherited) an edit icon is shown.
- When a field is not edited (customized) no lock icon is shown.
- When the field is customized an revert to inherited value icon is shown.
- When a field is customized, and not locked, a green unlocked icon is shown.
- When a field is customized and locked, a yellow locked icon is shown.
- When a field is locked in a higher configuration a grey lock icon is shown.
- In the case of the inheritance from a higher configuration of the selected options in a multi-selection field there are only two options:
- When the field is customized and locked at a higher configuration level all children have to follow the definitions in the parent.
- When the field is customized and not locked, each following configuration can select among the available options until on one level the field is locked.
Permissions
- System configuration - View - Allows the admin to see all configurations.
- System configuration - Manage - Allows the admin to manage all configurations.
- Manage specific configurations - Allows the admin to manage the specific configurations selected in his permissions.
- Manage content for configurations - Allows the admin to manage the content only specific configurations selected in his permissions, the admin is not allowed to make changes to the configuration itself.
Pages
Search (filters)
| Fields | Type | Rules |
| Filter by groups | Multiple selection | Allows filtering by groups |
| Name | Text | Allows filtering by configuration name |
| URL | Text | Allows filtering by URL (defined in the configuration)
|
| New | Multi action button | When creating a new configuration an existing 'parent' configuration needs to be chosen, this can be the system default configuration or any other configuration the admin has the permission to manage. At clicking the selected option, an empty details page for creating a new configuration opens based on the chosen 'parent' configuration. |
| Advanced | Action button | Switch to advanced mode
|
| Single | Action button | Switch to simple mode
|
Search result (list)
* Automatically shows all configurations, shown hierarchical and sorted alphabetically by name.
| Fields | Type | Rules |
| Name | Text (read only) | Shows the name of the configuration and an arrow icon before the name indicating the location in the configuration hierarchy. |
| URL | Text (read only) | The URL of the configuration. |
| Preview | Icon | Displays the selected configurations settings in view only mode. It shows the 'active' configuration, meaning it combines all applied settings (also those inherited from higher level configurations) |
| Remove | Icon | Allows the admin to remove the configuration.
|
Details page
| Fields | Type | Rules |
| Parent | Text (read only) | Indicates which is the direct parent configuration of which the new configuration descends from. All configurations are extended directly from another configuration being or the main configuration which is part of the default database (system default), or any other lower level configuration.
|
| Name | Text | The name of the configuration.
|
| Description | Text | Here you can put an explanatory text for the configuration. |
| Main URL | Text | The root URL.
|
| URL path | Text |
|
| Used by groups | Links | Shows the groups currently using this configuration, with links to the details page
|
| User data | ||
| Privacy-controlled profile fields | Multi selection | The selected fields will be included in the privacy control lists (see: System configuration - User configuration - Privacy control lists) |
| Require e-mail | Boolean | Determines whether the e-mail is required or not for users with this configuration. |
| Unique e-mail | Boolean | Determines whether the e-mail needs to be unique.
Note Making the e-mail not unique effectively disables e-mail as an identification method for access or performing / receiving payments in this configuration and its affected children. Please, proceed with caution |
| Validate e-mail on | Multi selection | Determines when the e-mail must be validated by the user
|
| Default email privacy setting | Single selection | When a user registers or changes his profile he can determine whether to hide or show his email for others. Here the admin can select the default value for this setting. In general for businesses this value will be visible and for consumers it will be hidden. Options:
|
| Require profile image | Boolean | When selected the user must upload a profile image upon registration. |
| Default image for newly registered users | Image | When users are registering without uploading a profile image a system wide default image is shown. With this setting it is possible to have customized default profile images per configuration/group. |
| Generated login name | Boolean | Determines whether new users with this configuration will have their usernames automatically generated (when checked) or will need to provide the username manually (when unchecked). When the username is automatically generated, the length will be the maximum set in the field "Generated login name length". The username will be an integer, when the maximum number of digits is reached another digit will be added. |
| Generated login name length | Integer | The length of generated usernames.
|
| Regular expression for login name | Text | Defines the regular mask used to validate manually entered usernames.
|
| Username length | Integer range | Determines the minimum and maximum number of characters for usernames.
|
| Individual documents directory | Single selection | Content manager configuration, in cyclos properties
|
| Localization | ||
| Default language | Single selection | Indicates the default language for the application and data translations.
|
| Additional languages | Multi selection | Indicates the additional languages, besides the default, users can choose.
|
| Country | Single selection | Defines the country which will be used as default for address and phones.
|
| Number format | Single selection | Indicates the way how numbers will be formatted.
Possible values:
|
| Distance unit | Single selection | Defines the scale unit used in the calculations of address distances in user / advertisement search.
|
| Date format | Single selection | Indicates the way how dates will be formatted.
|
| Time format | Single selection | Indicates the way how the time (hours / minutes) will be formatted.
|
| List separator | Single selection | Indicates which separator to use in CSV exports.
|
| Time zone | Single selection | Indicates the time zone used to display / parse dates.
|
| Addresses | ||
| Enabled address fields | Multi selection | Allows to determine the address fields listed in the profile of the groups with this configuration.
|
| Required address fields | Multi selection | Allows to determine the required address fields listed in the profile of the groups with this configuration. Only the address fields selected in the Enabled address fields plus Country will be shown in the option list. |
| Default city | Text | Allows to define a default city that will show up in the address of each user who inherits the configuration. |
| Default region or state | Text | Allows to define a default region or state that will show up in the address of each user who inherits the configuration. |
| Require address | Boolean | If checked, when registering a user with this configuration at least one address is required. |
| Default address privacy setting | Single selection | When a user registers or changes his profile he can determine whether to hide or show his address for others. Here the admin can select the default value for this setting. In general for businesses this value will be visible and for consumers it will be hidden. Options:
|
| Phones | ||
| Always show international phone number | Boolean | If checked the phone number from users having this configuration will always be shown in international notation. |
| Unique mobile phone | Boolean | If checked, the phone number must be unique.
Note Making the mobile phone not unique effectively disables the SMS channel and mobile phone as an identification method for access or performing / receiving payments in this configuration and its affected children. Please, proceed with caution. |
| Require mobile phone | Boolean | If checked, at least one mobile phone number from users having this configuration has to be informed at registration. |
| Require landline phone | Boolean | If checked, at least one landline phone number from users having this configuration has to be informed at registration. |
| Enable landline extension | Boolean | If checked, an extension can be entered for landline phone numbers:
|
| Default phone privacy setting | Single selection | When a user registers or changes his profile he can determine whether to hide or show his phone number for others. Here the admin can select the default value for this setting. In general for businesses this value will be visible and for consumers it will be hidden. Options:
|
| Display | ||
| Application name | Text | The simple name of the current Cyclos instance, or the project it belongs to.
|
| Application description | Text | A small description for the application. Is the value of the description meta tag (SEO) of the index page |
| Administration name | Text | An identifier to be shown to regular members instead of the name of a specific administrator, since regular members should never know the specific administrator.
|
| Results on autocomplete fields | Integer | The number of results on fields that use autocomplete (for example, the quick user selection field in the payment window).
|
| Maximum results on requests / PDF / CSV | Integer | The maximum number of returned results. Even if more than that is requested, it will be limited by this setting. Mainly used to limit the export results in a report (CSV, PDF). |
| Skip total count on searches | Boolean | This setting will not show the total count in searches (shown under the search result list). This will improve the search performance for large databases. The 'total count' indicator is not considered relevant information for end-users, and therefore an admin might consider to skip it when it improves the search performance. |
| User format for managers | Custom widget | Indicates how users will be displayed for managers. Has a separator and fields that can be added to the format.
Note: The changes on User format for managers will not be reflected on users until the user profile is saved or a reindex bulk action is executed |
| User format for others | Custom widget | Indicates how users will be displayed to other users (non managers).
Note: The changes on User format for others will not be reflected on users until the user profile is saved or a re-index bulk action is executed |
| Name label for users | Text | It is possible to define a custom 'Name' label. For example, for a specific user group you might want to show 'Business name' instead of Name. This can be done with this setting. |
| User search in menu | Single selection | With this setting the user search can be hidden in the menu, and it is also possible to limit the search for specific groups.
Note This setting will overwrite the visibility settings in the product. |
| Groups allowed in user search | Multi selection | Only shown when above setting (user search in menu) is set to 'specific groups'. |
| Maximum left banners | Integer | When set, indicates the maximum amount of banner sections on the left of the main window (below the menu and notification windows). When there are more banners than the defined maximum, the banners will rotate (change per period).
Note: This setting applies only to the classic interface |
| Maximum right banners | Integer | When set, indicates the maximum amount of banner sections on the right of the main window. When there are more banners than the defined maximum, the banners will rotate (change per period).
Note: This setting applies only to the classic interface |
| Seconds before rotating banners | Integer | When set, indicates the time interval the banners rotate, if exceeding the maximum amount of banners. |
| Use left spaces for guest pages | Boolean | If selected, the left column of the main window will display the guest page definitions instead of banners. |
| Default result sort order for users | Single Selection |
Available options:
|
| Default result type for users | Single selection | Defines which is the default type of results of a user search.
Available Options
|
| Advertisement initial search | Single selection | New front-end only
|
| Default result sort order for advertisements | Single selection |
|
| Default result type for advertisements | Single selection | Defines which is the default type of results of an advertisement search.
Available options
|
| Advertisement categories | Single selection |
Available options:
|
| Advertisement sub categories results | Integer | Will show subcategories (inf configured)
note For classic front-end only |
| Default account history period | Single selection |
|
| Profile field in account history print title | Single selection | This field will be shown in the title of the account history PDF file.
Available options: Any Profile custom fields in network plus Use default user formatting |
| Profile fields in account history print | Multi selection |
Available options: Any Profile custom fields in network |
| Account status indicators | Multi selection | This are the optional fields that will show up above the account in the account history (if selected in this setting).
|
| Menu type for users | Single selection | Indicates which menu type(s) is (are) shown for logged users who have this configuration.
Note: Classic front-end only |
| Menu for voucher buying | Single selection |
Available options:
|
| Redirect login to URL | Text | In case Cyclos is accessed from within another site (e.g. word press) the URL of that front-end needs to be set here. |
| URL to redirect after logout | Text | Same as above. If you want to redirect the user to an external site after logout. |
| Notify users when logging-in on new devices | Boolean | The user will get an notification (in Cyclos and by email) when there is a login from a new device. |
| Link generation script | Single selection | Link generation is also needed when you users login from a different site. It make sure that links that are sent in emails will point to the correct URL.
The link generation needs a script. An example can be found at the reference guide
|
| Link generation script parameters | Text area | Possible script parameters for link generation script
|
| IP geolocation script | Single selection | IP geolocation is used to show the location of an IP (e.g. in: User - Management - IP addresses - details)
|
| IP geolocation script parameters | Text area | The geolocation will need a script (see above)
|
| Cache geolocation results for | Time interval | This is the time the IP location will be cached. This can diminish the costs of the geolocation services. |
| New frontend | ||
| Public API URL | Text | The front-end uses (just like the mobile app) the Restful API. It is possible to change the default (public) URL in this setting. |
| Front-end to use | Radio button |
Available options:
Note: Network administrators will always have to possibility to switch from the new to the classic front-end |
| Allow switching between front-ends | Boolean | The option in the new front-end can be find under the 'Personal - Settings' menu. It is also possible to create a dashboard item (shortcut). |
| Application title | Text | The title that will show up at the top left (next to the system logo) |
| Application title on mobile | Text | The title that will show up in the top bar of the mobile application. |
| Application menu title on mobile | Text | Title will show up in the top bar.
Note: The launch icon and title can be customized at mobile code level. Instructions are provided in the read-me file in the mobile download. |
| Mobile landing page | Radio button | Usually the landing page is the home page. To make the login process quicker the login page can be displayed directly with this setting.
Available options:
|
| Split the top bar and the menu bar | Boolean | The top bar can be split in two bars, one with the quick access items (e.g. logout, shopping cart) and one with the menu items. Having two menus can be useful when there are many menu menu items (as there is more space). |
| Accounts in the dashboard | Single selection | If users can have more than one accounts they can be presented in different ways in the dashboard.
Available options:
|
| Show latest users in dashboard | Boolean | This window will show the latest users that registered. |
| Show latest advertisements in dashboard | Boolean | This window will show the latest advertisements that have been published. |
| Mobile application | ||
| Map preference | Single selection |
|
| Default zoom level | Single selection |
|
| Show QR scan option at login page | Boolean | This will show a QR code icon at the top of the login page. The QR scan will initiate any action that is allowed (e.g. confirm payment or redeem voucher). If login in required for the operation the login credentials are requested in order to confirm the operation. |
| Enable Bluetooth printing | Boolean | This will add an option in the mobile settings menu to add an blue-tooth receipt printer.
See also Wiki page mobile printer |
| Url in the Apple store | Text | The URL pointing to the apple store where the mobile app is published. |
| URL in the Google Play store | Text | The URL pointing to the Google play store where the mobile app is published. |
| Firebase JSON private key | Text area | If Firebase is configured (to enable in app messaging) the private key needs to be provided here.
Note: The Cyclos mobile reference guide has detailed information about the Firebase configuration. |
| Maps & directory | ||
| Use Google maps | Boolean | Google maps can be used for locating users, advertisements and vouchers. |
| Google maps server API | Text | |
| Google maps browser API | Text | |
| Maximum users / advertisements on map | Integer | The maximum result that can be shown on map per request.
|
| Default map location (lat,lng) | Text | |
| Default zoom level on web | Single selection |
|
| Default filter for map directory | Single selection |
|
| Account number (only visible in global or network default configurations) | ||
| Enable account number | Boolean | When checked, indicates that account number settings will be defined for this configuration. |
| Mask | Text | The mask used for input and formatting of account numbers.
This masks can restrict which characters will be generated, the size and the format, using the following constructors.
An account number example would be: UUU-######## It will generate account numbers like: ABC-12345678
|
| Script to generate numbers | Single selection | Custom script used to generate account numbers
|
| Script parameters | Text area | Parameters passed to the custom script
|
| Custom session handling (only visible in global or network default configurations) | ||
| Enable custom session management | Boolean | The cyclos session mechanism can be customized. We advice only to do it with solid knowledge of the session mechanism, and only if it is really needed |
| Session handling script | Single selection |
|
| Script parameters | Text area |
|
| E-mails | ||
| Host | Text | The URL or IP address of the SMTP server.
|
| Port | Number | The SMTP port.
|
| User | Text | The SMTP user. Not used when empty. |
| Password | Password | The SMTP password. Not used when empty. |
| Security protocol | Radio | Available options:
|
| Max. mailing recipients (against spam) | Integer | |
| From address on sent e-mails | Text | The address used for sent e-mails. Always visible when the user receives the email.
|
| Display name on sent e-mails | Text | The displayed name which can be seen in sent e-mails. Always visible when the user receives the email.
|
| Outbound SMS messages | ||
| Enable outbound SMS messages | Boolean | When checked, indicates that SMS gateway settings as a whole will be enabled for this configuration. The SMS gateway server settings can be set separatly for any child configuration if it is not locked in the father configuration. If it is locked in the father configuration, the settings will be inherited to any child configuration. |
| Gateway URL | Text | Full URL of Gateway
|
| HTTP username | Text | The username (given by gateway provider)
|
| HTTP password | Password | The password (given by gateway provider)
|
| HTTP headers | Text area |
|
| HTTP request type | Radio | POST or GET (depending on the method used by the gateway provider)
|
| HTTP request POST body | Text area |
|
| Send ASCI characters only | Boolean | Only allow ASCI characters. ASCI characters with accents will be converted to normal ASCI characters.
|
| Character encoding | Text | This option allows to customize which encoding to use for both request parameters encoding and body.
|
| SMS sender script | Single selection | Custom script used to send SMS messages
|
| Script parameters | Textarea | Parameters passed to the custom script
|
| Maximum global messages per month | Integer | The the total maximum of SMS for all the users that use this configuration.
|
| Maximum global messages per unregistered phone | Integer | The the total maximum of SMS for all the users that use this configuration.
|
| Restrictions | ||
| Allow access | Single selection |
Note: There are various use cases for these options. For example, it is good practice to create a specific configuration for administrators, and set a difficult to guess URL path in the configuration with the Allow access option set to: 'From this URL only'. |
| Maximum upload size | File size | The maximum size accepted for uploads.
|
| Maximum full image dimensions | Integer (range) | The maximum dimensions (resolution) for uploaded images. Images larger than these will be resized.
|
| Maximum medium thumbnail dimensions | Integer (range) | The maximum dimensions for medium thumbnails.(for example detail page advertisement or profile)
|
| Maximum small thumbnail dimensions | Integer (range) | The maximum dimensions for small thumbnails.(for example results list tiled view)
Examples: User and ads results
|
| Maximum tiny thumbnail dimensions | Integer (range) | The maximum dimensions for tiny thumbnails.(for example results list bullet view)
|
| Maximum PNG images size | File size | The maximum size accepted for PNG images. PNG images larger than this size will be converted to JPEG.
|
| JPEG images quality | Integer |
|
| Maximum temporary images for authenticated users | Integer | I some page images can be uploaded (e.g. advertisement or profile) but they are only saved to the database when user clicks on the button 'Save'. Before the advertisement (or any entity that has an image upload and a save button) has been saved the images will remain in cache. In this setting the maximum of images in cache can be defined.
|
| Maximum temporary images for public registration (per IP address) | Integer | Same as above, but for non logged users.
|
| Allow multiple system reports at once | Boolean | The report feature (Report - Reports - System Reports) can be quite heavy for a system with much data. This can have an impact on the performance, and therefore the number of options that can be select at once can be limited. |
| Maximum user identification attempts (login) per hour | Integer | |
| Maximum user identification attempts (receive payments) | Integer | |
| After failing login names, block remote IP for | Time interval | |
| Maximum blocked users per day by IP address | Integer |
|
| After maximum blocked users reached, block remote IP for | Time interval |
|
| Alerts | ||
| Given very bad references | Integer | When set, an user alert is generated when a member gives the defined amount of very bad references.
|
| Received very bad references | Integer | When set, an user alert is generated when a member receives the defined amount of very bad references. |
| Notifications | ||
| Notification script | Single selection | It is possible to customize the notifications send to users. An example can be found in the Cyclos reference guide.
|
| Notification script parameters | Text area |
|
| CAPTCHA | ||
| Provider | Radio buttons |
|
| Text length | Integer |
|
| Text color | Color picker |
|
| Effect | Radio button |
|
| reCAPTCHA site key | Text |
|
| reCAPTCHA secret key | Password |
|
| Use captcha on registration | Boolean | |
| Use captcha on forgot password | Boolean | |
| Data visible to guests | ||
| Include in sitemap (used by web search engines) | Boolean | If you want the URL to be available to search engines (SEO) this option needs to be selected. |
| Search users on groups | Multi selection | When the user search is available for guests the groups that can be search in can be defined with this setting. |
| User directory (map) on groups | Multi selection | When the user search is available for guests the users of groups that can be shown on the map can be defined with this setting. |
| View profile on groups | Multi selection | Allows defining groups / group sets visible to guest users.
The profiles of users belonging to these groups can be shown for guests. |
| User profile fields | Multi selection | The profile fields of users belonging to these groups can be shown for guests.
|
| Possible groups for public registration | Multi selection | Defines which groups can be used on public registration for guest users.
|
| Registration wizard for large screens | Single selections | Here you can select to show a wizard (with steps) instead of a single page registration form. This setting will be applied for registrations done from large screens sizes |
| Registration wizard for medium screens | Single selection | Here you can select to show a wizard (with steps) instead of a single page registration form. This setting will be applied for registrations done from medium screen sizes. |
| Registration wizard for small screens | Single selection | Here you can select to show a wizard (with steps) instead of a single page registration form. This setting will be applied for registrations done from small screen sizes. |
| Forgotten passwords retrieval | Single selection |
|
| Require security question on registration | Boolean |
|
| Forgotten passwords medium | Radio buttons |
|
| Menu type for guests | Single selection |
Note: Classic front-end only |
| Visible advertisement groups | Multi selection | The advertisement search results will be limited to advertisements of the selected groups (in this setting).
Note: Show simple/webshop ads must be enabled (see settings further below) |
| Visible ad fields | Multi selection | Define what custom advertisement fields can be seen by guests.
|
| Show simple ads | Boolean | If selected simple ads (non web-shop) will show up in the guests page (non logged users).
|
| Show web-shop ads | Boolean | If selected web-shop ads will show up in the guests page (non logged users).
|
| Hide advertisements owner to guests | Boolean | Don't show advertisement owner to guests (login is required to see all advertisement details) |
| Hide advertisements price to guests | Boolean | Don't show advertisement price to guests (login is required to see all advertisement details) |
| Custom users search menu label | Text | Allows a customized label used for the user search in the menu for guests.
|
| Custom advertisement search menu label | Text | Allows a customized label used for the advertisement search in the menu for guests.
|
| Dynamic OpenID Connect / OAuth 2 clients | ||
| Dynamic OIDC clients | Boolean | Select to overwrite higher level configuration setting |
| Enable dynamic OIDC clients | Boolean | Enable dynamic (user generated) OIDC clients
|
| Allow non HTTPS connections | Select box |
|
| Permissions (scopes) | Multi select | Types of allowed operations |
| Allowed account types | Multi select | |
| Allowed payment types | Multi select | |
| Allowed ticket types | Multi select | |
| Single payment per consent | ||
| Access token expiration | ||
| Logging (Only visible for Global or Network default configurations) | ||
| Tasks logging | Radio button | Tasks logging will log all scheduled tasks (recurring and background tasks).
Please be aware that both recurring and background and tasks have tabs with an execution log and a history log. This is the recommend place to retrieve information about the tasks. The task logging should only be used in case for in-depth analyses and trouble shouting. Much care should taken with the verbose logging setting, as it will generated a large amount of data.
|
| Enable services logging | Boolean | All operations in Cyclos a part from a service. Enabling service logging will log those operations, for example a 'Search User' operation. |
| Log parameters on services | Boolean | This will log also the parameter of the service. For example, continuing the above example (Search User), it will also log the search variables/filters that were used in the search.
|
| Log results on services | Boolean | This will log also the result of the service. For example, continuing the above example (Search User) it will also log the search result.
|
| Log services for guests | Boolean | This will log also the services for guests (non logged users)
|
| Log writes only in services | Boolean | This will skip the read only services requests, and will result in much smaller log sizes. |
| Maximum error log entries | Integer | Defines the maximum of error log entries in Reports - Alerts & Logs - Error logs.
The number of maximum logs that will be returned. Older logs will be removed. Zero means unlimited.
|
Channels (Tab)
The channels are described in a dedicated wiki page.