System Preferences

Under the “System Preferences” tab, you’ll find some options for customizing Yesplan:

  • System Language: the language in which Yesplan is displayed.

  • Currency Sign: the currency sign that is displayed in Yesplan.

  • Notification Email Address: the email address to which mails are sent (with the most recent information regarding the selected event) if you click on the “Mail an Update” button in the event inspector. If nothing is entered here, the button will not be active and clicking on it will have no effect.

  • Day line: In Yesplan it is possible to have a day start at the time of your choice instead of at midnight. This is set to 7 AM (07:00) by default.

    Please note: you can edit this setting when configuring Yesplan. Since editing the day line has a big impact (for example on the calculation of costs and on conflicts), this setting cannot be changed once your organization starts working with Yesplan. To prevent accidental alterations, this value cannot be changed by an administrator. Contact the Yesplan Customer Success Manager or support for assistance.

  • Repeat Limit: specifies the maximum number of repeats of an event, service, unavailability, etc. when setting repeats. This value is set to 100 by default; this value must be between 1 and 365.

  • Earliest Possible Year in Date Picker: The earliest possible years that you can navigate to in the calendar via the date picker. This date is set to ‘2005’ by default.

  • Events are a Production by Default: If this setting is set to true, then all newly created events are automatically also a production. This parameter is set to false by default.

  • Event inspector always opens with focus on

  • Event sorting order with status type ‘option’: Events with a status of type ‘option’ are numbered and sorted in the calendar display. The order is displayed so that you know which option came first in the calendar later on. If this is set to “By event creation time”, then it will be sorted by the moment when the event appeared on the calendar for the first time. If this is set to “By location booking time”, then it will be sorted by the moment when the event was booked in the location.

    For example:

    • Option A was booked in the Grote Zaal the day before yesterday.
    • Option B was booked in the Kleine Zaal yesterday.
    • Option A was moved from the Grote Zaal to the Kleine Zaal today.

    For the sorting order “By event creation time”, option A will be before option B in the Kleine Zaal; option A was created before option B. For the sorting order “By location booking time”, option A will be after option B in the Kleine Zaal; option A was booked in the hall later than option B.

    Please note that ‘options’ are not sorted according to the start time of the show. They are displayed in a separate section under the ‘confirmed’ events on that day.

  • Default Rate Unit for New Price Definition: the default unit that will be chosen when creating a new price definition and when booking an ad hoc resource. This value has the options ‘fixed’, ‘per hour’, ‘per day’, ‘per week’ and ‘per month’.

  • Default VAT Rate for Resources: the default VAT rate that is set when creating price definitions for resources. (The VAT rate can of course also be changed for the resource, when defining the prices.) The default setting is 21% (21.0) and can be any value between 0% and 100%.

  • Filter Setting for Search: determines whether and how the filter will be displayed in the general search box (where you can search through all Yesplan elements).

    • Disable: the filter buttons will not be active; the user will always see all results that they have permission to see.
    • Enable, and by default show everything: the filter buttons will be active in the general search box and the initial value of the filter is set to “All User Groups”; initially the user will be able to see all results that they have permission to see.
    • Enable, and by default only show items owned by a member of the user’s primary group: the filter buttons will be active in the general search box and the initial value of the filter is set to “My User Group Only”; initially the user will only be able to see those elements whose owner is a member of their primary user group.

    If the filter is active, this setting determines the initial value of the filter (the first time that the user sees this filter). A user can always set the filter to suit their needs. The setting is remembered per user. The last setting that was used will remain valid the next time the user signs in.

  • Filter Settings for Events: determines whether and how the filter will be displayed in the events finder.

    • Disable: the filter buttons will not be active; the user will always see all results that they have permission to see.
    • Enable, and by default show everything: the filter buttons will be active in the events finder and the initial value of the filter is set to “All User Groups”; initially the user will be able to see all results that they have permission to see.
    • Enable, and by default only show items owned by a member of the user’s primary group: the filter buttons will be active in the events finder and the initial value of the filter is set to “My User Group Only”; initially the user will only be able to see those elements whose owner is a member of their primary user group.

    If the filter is active, this setting determines the initial value of the filter (the first time that the user sees this filter). A user can always set the filter to suit their needs. The setting is remembered per user. The last setting that was used will remain valid the next time the user signs in.

  • Filter Settings for Resources: determines whether and how the filter will be displayed in the resources finder and in the search field for adding resources (to events or as custom data).

    • Disable: the filter buttons will not be active; the user will always see all results that they have permission to see.
    • Enable, and by default show everything: the filter buttons will be active in the resources finder and in the search field for adding resources, and the initial value of the filter is set to “All User Groups”; initially the user will be able to see all results that they have permission to see.
    • Enable, and by default only show items owned by a member of the user’s primary group: the filter buttons will be active in the resources finder and in the search field for adding resources, and the initial value of the filter is set to “My User Group Only”; initially the user will only be able to see those elements whose owner is a member of their primary user group.

    If the filter is active, this setting determines the initial value of the filter (the first time that the user sees this filter). A user can always set the filter to suit their needs. The setting is remembered per user. The last setting that was used will remain valid the next time the user signs in.

  • Filter Settings for Contacts: determines whether and how the filter will be displayed in the contacts finder and in the search field for adding contacts (to events, resources or as custom data).

    • Disable: the filter buttons will not be active; the user will always see all results that they have permission to see.
    • Enable, and by default show everything: the filter buttons will be active in the contacts finder and in the search field for adding contacts, and the initial value of the filter is set to “All User Groups”; initially the user will be able to see all results that they have permission to see.
    • Enable, and by default only show items owned by a member of the user’s primary group: the filter buttons will be active in the contacts finder and in the search field for adding contacts, and the initial value of the filter is set to “My User Group Only”; initially the user will only be able to see those elements whose owner is a member of their primary user group.

    If the filter is active, this setting determines the initial value of the filter (the first time that the user sees this filter). A user can always set the filter to suit their needs. The setting is remembered per user. The last setting that was used will remain valid the next time the user signs in.

  • Filter Setting for Tasks: determines whether and how the filter will be displayed in the tasks finder.

    • Disable: the filter buttons will not be active; the user will always see all results that they have permission to see.
    • Enable, and by default show everything: the filter buttons will be active in the tasks finder and the initial value of the filter is set to “All User Groups”; initially the user will be able to see all results that they have permission to see.
    • Enable, and by default only show items owned by a member of the user’s primary group: the filter buttons will be active in the tasks finder and the initial value of the filter is set to “My User Group Only”; initially the user will only be able to see those elements whose owner is a member of their primary user group.

    If the filter is active, this setting determines the initial value of the filter (the first time that the user sees this filter). A user can always set the filter to suit their needs. The setting is remembered per user. The last setting that was used will remain valid the next time the user signs in.

  • Allow Credentials to be Remembered for Users: determines whether users can use ‘Remember me’ when signing in.

  • Show Abbreviation of Location in Tree View: determines whether the abbreviation of the location can be displayed in the tree view.

    If the “Abbreviation” field is entered in the location inspector, then this abbreviation will appear in tree views – in front of the event name - unless this preference was deactivated.

  • Users Allowed to Modify Date Decorations in the Calendar: determines which users can edit date decorations in the calendar; only administrators or all users.

  • Separator for File Exports in CSV Format: determines which separator is used when exporting CSV files; a comma or semicolon.

  • Use the deprecated tp_comment resource booking custom data field: in version 26 of Yesplan, the comment field for resource bookings (tp_comment) is no longer a custom data field but a system field. Consequently, you can no longer add the comment field to tabs of your choosing in inspectors. If you select “Yes” for this setting, the field will continue to behave like a custom data field and you can add it to any tab.

Attention

If changes are made on this screen, you must click on the “Save” button (under the list) to save the changes.