
TINE 2.0 RELEASENOTES
===
                    
  Release:     Nele (2018.11)
  Last change: 2018-02-01

GENERAL CHANGES
---

* PHP 7.2 Support

* AreaLocks
It is possible to define protection for certain areas of Tine 2.0. For example, it might be required to give a PIN if you
 want to access the Sales application.

 Example configuration of a Sales app AreaLock with PIN:

     'userPin' => true,
     'areaLocks' => [
         'records' => [
             [
                 'area' => 'Sales',
                 'provider' => 'Pin',
                 'validity' => 'session', // it is only required to give the pin once per session
             ]
         ]
     ],

* Sentry.io integration
If you have a sentry.io server which collects your errors, you can just add it to Tine 2.0 by setting this config:

    'sentryUri' => 'https://USER:PW@sentry.my.domain/2', // note: no double slashes in uri except after "https:"

see 0013706: integrate sentry.io error handling (https://forge.tine20.org/view.php?id=13706)

* Access Log Cleanup

Access Log Entries are not removed if older than 7 days be default. You can use the config option
 'accessLogRotationDays' to define a custom rotation.

FILEMANAGER
---
* PIN Protection / Data safe
Folders can be PIN protected: its contents are only visibly if user provides a valid second factor / PIN.
 - use an AreaLock with area 'Tinebase.datasafe' to activate pin protection

ADDRESSBOOK
---

CALENDAR
---

* Link to event in event notification mails

To have the correct URL, you need to set this config:

    'tine20URL' => 'https://my.tine20.domain',

EMAIL
---
