With version 3.87 the ChurchTools Sync goes into the next stage. Now you can synchronize financial transactions<\/strong> as well as people. With the announcement that we will no longer be licensing orders, but instead licensing connections in the future, the Sync module will become a faithful companion for you to further improve workflows between multiple ChurchTools installations or even a ChurchTools installation and Optigem.<\/p>\n\n\n\n The sync for transactions behaves very similar to the person sync. The external system must be set up in the sync and if it supports transactions as a type, you will be offered the selection Transactions on new sync jobs.<\/p>\n\n\n\n You will need to set the property pairs for the accounting data, and then set the actions for the job.<\/p>\n\n\n\n The transactions will then be displayed in the ChurchTools Finance module. If the Finance module has not been explicitly licensed, then the module is available in read-only mode.<\/p>\n<\/div>\n\n\n\n Depending on the assignment of tasks, you may need a more flexible assignment of security levels. This is the case, for example, when you want to maintain different administrative details in ChurchTools. For example, some of you may want to allow the profile picture to be changed, but otherwise not allow any changes to the personal data.<\/p>\n\n\n\n To do this, go to the master data in Persons and Groups<\/em> and edit the security levels. There you will find the new field Sort Order, whose value will be taken over into the ID when saving (the ID ultimately determines the effect of the security level). This allows you to pull the security levels apart, so to speak, so that you can insert others in between.<\/p>\n<\/div>\n\n\n\n Things change quickly in ChurchTools. Therefore, ChurchTools documents the most important changes in the log, so that everything remains trackable for you.<\/p>\n\n\n\n For example, the changes of values are documented with the new as well as the previous value. We have adapted this format and made it more legible.<\/p>\n\n\n\n Until v3.86, the log format looked like this: Occupation: Salesman (previously: Trainee). With the new version we have changed the format as follows. So the log messages are more legible: Occupation: Trainee \u2192 Salesman.<\/p>\n\n\n\n In version 3.82<\/a> it was announced that we moved the person functions to the menu column on the left side. We have now done the same with the group functions.<\/p>\n\n\n\n The group functions, like the person functions, are given a more prominent place in the software so that they can be accessed quickly.<\/p>\n\n\n\n Using the group functions, changes to many groups can be completed in just a few steps.<\/p>\n<\/div>\n\n\n\n For data protection and performance reasons, from 26\/08\/2022 selected system log entries* will be deleted after 6 months and other log entries after 3 years. Exception: Log entries for personal data that are required to view personal history will not be deleted.<\/p>\n\n\n\n Log entries about log-ins, log-outs, cron calls, e-mail sending, rate limiting, JS errors, consolidation, sync.<\/em><\/p>\n\n\n\n If this is not enough for you, you will find all changes of this and earlier versions in our Changelog<\/a>.<\/p>\n\n\n\n![\"\"](\"https:\/\/blog.church.tools\/en\/wp-content\/uploads\/sites\/2\/2022\/07\/v3.87-sync-job.png\")
<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n<\/figure>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nSecurity level: sorting easier to change<\/h2>\n\n\n\n
<\/a><\/figure>\n<\/figure>\n<\/div>\n<\/div>\n\n\n\nNotes<\/h3>\n\n\n\n
\n\n\n\nLog messages improved<\/h2>\n\n\n\n
<\/a><\/figure>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nGroup functions moved to menu<\/h2>\n\n\n\n
<\/a><\/figure>\n<\/figure>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nNote on changing the storage duration of log entries<\/h2>\n\n\n\n
If you would like a complete data extract of your current logs, you can request one until 08\/26\/2022 via support@churchtools.de.<\/p>\n\n\n\n
\n\n\n\nFurther changes<\/h2>\n\n\n\n