Release Notes for ReportServer 3.4.0

These release notes reflect the changes with respect to ReportServer 3.3.0.

• Some Important Features and Noteworthy Improvements
• Datasinks
• Provide Details for ViolatedSecurityExceptions (List Missing Permissions)
• System Console / Live Memory
• Support Sending Reports to SFTP
• Allow to Test Reports
• Allow to Export Dynamic List as JXLS Template
• Allow to Set Name and Description of Scheduling Jobs
• Allow to Change Report of Scheduling Jobs
• Allow to Configure if Grid Report should allow to add/duplicate/remove records
• Allow to Select Compression in New Scheduler Jobs by Default
• Allow to Execute Dadgets from Dashboard
• Refresh Preview
• Allow to List/View Catalina Log Files and Send these via E-mail
• Allow to Modify Directory's Web Access by Terminal
• Allow to Configure Excel Sheet Titles
• Allow to configure URL whitelist
• New Features, Improvements and Bug Fixes for RS3.4.0-6032
• New Features, Improvements and Bug Fixes for RS3.4.0-6033
• New Features, Improvements and Bug Fixes for RS3.4.0-6034
• New Features, Improvements and Bug Fixes for RS3.4.0-6035
• New Features, Improvements and Bug Fixes for RS3.4.0-6036

Some Important Features and Noteworthy Improvements for ReportServer RS3.4.0

Datasinks

Datasinks are the counterpart of datasources in ReportServer. Reports can be sent to any datasink defined, e.g. to a FTP or SFTP datasink. Reports may be sent directly to a datasink (via the SendTo button) or scheduled to be sent to a specific datasink. Multiple datasinks of the same type are allowed, analogously as datasources. Further, as with most other objects in ReportServer, datasinks are maintained in a hierarchical structure. The datasink management module can be found in the Administration module under Datasinks.

Note that that FTP datasinks are supported as of ReportServer 3.4.0. For scheduled reports using the legacy FTP functionality, a dummy FTP datasink is created on ReportServer start (found in the Administration area, in the datasink root folder). This dummy FTP datasink must be adapted in order for these reports to further work. You can see the "dummy ftp datasink" in the screenshot above.

Currently, SFTP datasink authentication supported is by username/password. Note that for SFTP to work, you have to add your SFTP host to your .ssh/known_hosts file (https://en.wikibooks. org/wiki/OpenSSH/Client_Configuration_Files#~/.ssh/known_hosts) in order to verify the identity of the remote host, thus protecting against impersonation or man-in-the-middle attacks. Its location be configured in the /fileserver/etc/security/misc.cf file as described in the Configuration Guide. For manually adding a public key to the .ssh/known_hosts file, check here: https://en.wikibooks.org/wiki/OpenSSH/Client_Configuration_Files#Manually_ Adding_Public_Keys_to_~/.ssh/known_hosts.

The complete /fileserver/etc/security/misc.cf file is the following (check the knownHosts option):

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
   <juel>
      <expression>
         <blacklist>getClass</blacklist>
      </expression>
   </juel>
   <errorMessages>
      <hideViolatedSecurityExceptionDetails>false</hideViolatedSecurityExceptionDetails>
   </errorMessages>
   <knownHosts>/path/to/.ssh/known_hosts</knownHosts>
</configuration>

Datasinks can be enabled/disabled in the /fileserver/etc/datasinks/datasinks.cf file.

Datasinks are supported as of ReportServer 3.4.0. The legacy FTP configuration in /fileserver/etc/exportfilemd/storage.cf is ignored as of version 3.4.0.

The complete /fileserver/etc/datasinks/datasinks.cf is the following:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <sftp disabled="false" supportsScheduling="true" />
  <ftp disabled="false" supportsScheduling="true" />
</configuration>

The texts used during scheduling can be configured in the /fileserver/etc/scheduler/scheduler.cf file analogously as the other texts. The complete file is the following (note the fileactionSftp and fileactionFtp sections):

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
   <scheduler>
      <mailaction html="false">
         <subject>ReportServer: ${subject}</subject>
         <text>${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['mailactionMsgText']}
		 
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelJobName']} ${job.getName()}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelMessage']} ${message}
      </text>
         <attachment>
            <name>rep-${report.getName()}-${RS_CURRENT_DATE}</name>
         </attachment>
      </mailaction>
      <fileaction disabled="false" html="false">
         <subject>ReportServer: ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['fileactionMsgSubject']}</subject>
         <text>${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['fileactionMsgText']}
		 
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelJobName']} ${job.getName()}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelFilename']} ${filename}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelDescription']} ${description}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelTeamspace']} ${teamspace.getName()}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelFolder']} ${folder.getName()}
      </text>
      </fileaction>
      <fileactionSftp disabled="false" html="false">
         <subject>ReportServer: ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['fileactionSftpMsgSubject']}</subject>
         <text>${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['fileactionSftpMsgText']}
		 
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelJobName']} ${job.getName()}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelFilename']} ${filename}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelFolder']} ${folder}
      </text>
      </fileactionSftp>
      <fileactionFtp disabled="false" html="false">
         <subject>ReportServer: ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['fileactionFtpMsgSubject']}</subject>
         <text>${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['fileactionFtpMsgText']}
		 
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelJobName']} ${job.getName()}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelFilename']} ${filename}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelFolder']} ${folder}
      </text>
      </fileactionFtp>
      <notification disabled="false" html="false">
         <scheduled>
            <subject>ReportServer: ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['notificationMsgScheduledSubject']}</subject>
            <text>${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['notificationMsgScheduledText']}

${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelJobName']} ${job.getName()}
${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelUser']} ${scheduleUser}
${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['notificationMsgScheduledNextDates']} ${nextDates}
		</text>
         </scheduled>
         <unscheduled>
            <subject>ReportServer: ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['notificationMsgUnscheduledSubject']}</subject>
            <text>${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['notificationMsgUnscheduledText']}

${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelJobName']} ${jobName}</text>
         </unscheduled>
         <failed>
            <subject>ReportServer: ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['notificationMsgFailedSubject']}</subject>
            <text>${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['notificationMsgFailedText']}

${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelJobName']} ${job.getName()}
${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelErrorMessage']} ${errMsg}
${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelRecipient']} ${recipients}
${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelErrorDetails']} ${stacktrace}
		</text>
         </failed>
      </notification>
      <properties>
         <disabled>false</disabled>
      </properties>
  </scheduler>
</configuration>

Provide Details for ViolatedSecurityExceptions (List Missing Permissions)

Previously, when a user did not have sufficient permissions for accessing some object in ReportServer, it was difficult to determine which permissions exactly were missing, since no details were given in the error message.

In ReportServer 3.4.0 this changed. The following screenshot depicts two examples. On the left side, you see the error messages of previous ReportServer versions, which did not contain any details. On the right side you can see which permissions exactly are missing (Execute rights) for two different objects: above, for the ExportSecurityTarget (i.e. the user does not have Execute-"Ex/Import" generic right). Below, for the dynamic list with id 108158. For the administrator it will be easier to give the user appropriate permissions.

If this level of detail is not desired, it can be configured in the /etc/security/misc.cf configuration file. Here, you can select the level of detail of error messages shown to the user. Currently, the following is supported:

• hideViolatedSecurityExceptionDetails When a security rule is violated, e.g. when a user tries to execute a report the user is not allowed to, specific details of the security violation are being printed to the user by default. This includes the specific security target, the rights/permissions being violated, the objects and the method where this happens, if available. This helps administrators to exactly understand which rights/permissions are needed for a specific object to be accessed by a user. If not desired, you can set this to false in order to hide these specific details from the user, which may be preferable in some cases. Defaults to false.

Below you can see the complete default /etc/security/misc.cf file including error message level of detail settings.

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
   <juel>
      <expression>
         <blacklist>getClass</blacklist>
      </expression>
   </juel>
   <errorMessages>
      <hideViolatedSecurityExceptionDetails>false</hideViolatedSecurityExceptionDetails>
   </errorMessages>
</configuration>

System Console / Live Memory

A new administration area "System Console" was added. For a user to see this, the user needs "System Console" read-access generic permission as shown in the following screenshot. Note that users having this permission can access the complete "System Console" area, i.e. all system console subsections.

We added the subsection "Live JVM Memory", which allows you to analyze live JVM memory usage. Example screenshots are shown below. Per default, it is refreshed every second. This can be configured with the "Refresh interval" field.

Support Sending Reports to SFTP

Analogous to the current FTP functionality, reports can now be sent to a SFTP server. Scheduling is supported here as well.

SFTP server configuration is done in the /fileserver/etc/datasinks/datasinks.cf configuration file:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <sftp disabled="false" supportsScheduling="true" />
  <ftp disabled="false" supportsScheduling="true" />
</configuration>

Note that for SFTP to work, you have to set the location of your .ssh/known_hosts file (https://en.wikibooks.org/wiki/OpenSSH/Client_Configuration_Files#~/.ssh/known_hosts) in order to verify the identity of the remote host, thus protecting against impersonation or man-in-the-middle attacks. This may be configured in the /fileserver/etc/security/misc.cf file as follows.

<?xml version="1.0" encoding="UTF-8"?> 
<configuration>
	<knownHosts>/path/to/.ssh/known_hosts</knownHosts>
</configuration>

For manually adding a public key to the .ssh/known_hosts file, check here: https://en.wikibooks.org/wiki/OpenSSH/Client_Configuration_Files#Manually_Adding_Public_Keys_to_~/.ssh/known_hosts.

SFTP Email text configuration is done in the /fileserver/etc/scheduler/scheduler.cf file:

<fileactionSftp disabled="false" html="false">
      <subject>Email subject</subject>
      <text>
         Email text
      </text>
</fileactionSftp>

Following you can see the complete default /fileserver/etc/scheduler/scheduler.cf file:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
   <scheduler>
      <mailaction html="false">
         <subject>ReportServer: ${subject}</subject>
         <text>${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['mailactionMsgText']}
     
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelReport']} ${report.getName()}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelMessage']} ${message}
      </text>
         <attachment>
            <name>rep-${report.getName()}-${RS_CURRENT_DATE}</name>
         </attachment>
      </mailaction>
      <fileaction disabled="false" html="false">
         <subject>ReportServer: ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['fileactionMsgSubject']}</subject>
         <text>${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['fileactionMsgText']}
     
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelReport']} ${report.getName()}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelFilename']} ${filename}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelDescription']} ${description}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelTeamspace']} ${teamspace.getName()}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelFolder']} ${folder.getName()}
      </text>
      </fileaction>
      <fileactionSftp disabled="false" html="false">
         <subject>ReportServer: ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['fileactionSftpMsgSubject']}</subject>
         <text>${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['fileactionSftpMsgText']}
     
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelReport']} ${report.getName()}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelFilename']} ${filename}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelFolder']} ${folder}
      </text>
      </fileactionSftp>
      <fileactionFtp disabled="false" html="false">
         <subject>ReportServer: ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['fileactionFtpMsgSubject']}</subject>
         <text>${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['fileactionFtpMsgText']}
     
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelReport']} ${report.getName()}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelFilename']} ${filename}
  ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelFolder']} ${folder}
      </text>
      </fileactionFtp>
      <notification disabled="false" html="false">
         <scheduled>
            <subject>ReportServer: ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['notificationMsgScheduledSubject']}</subject>
            <text>${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['notificationMsgScheduledText']}

${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelReport']} ${report.getName()}
${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelUser']} ${scheduleUser}
${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['notificationMsgScheduledNextDates']} ${nextDates}
    </text>
         </scheduled>
         <unscheduled>
            <subject>ReportServer: ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['notificationMsgUnscheduledSubject']}</subject>
            <text>${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['notificationMsgUnscheduledText']}

${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelReport']} ${reportName}</text>
         </unscheduled>
         <failed>
            <subject>ReportServer: ${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['notificationMsgFailedSubject']}</subject>
            <text>${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['notificationMsgFailedText']}

${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelReport']} ${report.getName()}
${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelErrorMessage']} ${errMsg}
${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelRecipient']} ${recipients}
${msgs['net.datenwerke.rs.scheduler.client.scheduler.locale.SchedulerMessages']['labelErrorDetails']} ${stacktrace}
    </text>
         </failed>
      </notification>
      <properties>
         <disabled>false</disabled>
      </properties>
  </scheduler>
</configuration>

Allow to Test Reports

Reports and variants may be now directly tested. This allows to check if the report's query/columns/configuration is correct without having to explicitly execute the corresponding report. This may be done via terminal or GUI. Example screenshots below.

Allow to Export Dynamic List as JXLS Template

JXLS templates are a powerful feature in ReportServer. Nevertheless, creating JXLS templates is sometimes cumbersome. ReportServer now supports exporting dynamic lists as JXLS templates. These can then be easily adapted/configurated as needed with Excel and may be uploaded to ReportServer either as a JXLS report or a JXLS template for the dynamic list. Example screenshots below.

Note that you can configure the default column widths in the /fileserver/exportfilemd/jxlsexport.cf configuration file.

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
   <jxls>
      <numberColumnWidth>8</numberColumnWidth>
      <textColumnWidth>8</textColumnWidth>
      <dateColumnWidth>8</dateColumnWidth>
      <currencyColumnWidth>8</currencyColumnWidth>
   </jxls>
</configuration>

Allow to Set Name and Description of Scheduling Jobs

Scheduling jobs contain now a name and a description, analogously to other elements in ReportServer. For existing jobs, the report's name and description are being copied into these new fields.

Allow to Change Report of Scheduling Jobs

You can now change the report of an existing scheduling job. This allows you to keep current job configuration while scheduling a different report. A screenshot is shown below.

Allow to Configure if Grid Report should allow to add/duplicate/remove records

You can now turn off adding/duplicating/removing records per grid report. Default is true (allowed).

This can be done via the following settings:

def adapter = definition.getAdapter()
adapter.setCanAddRecords(false)
adapter.setCanDuplicateRecords(false)
adapter.setCanRemoveRecords(false)

Allow to Select Compression in New Scheduler Jobs by Default

While scheduling new jobs, you can select the option "Compress report" if you want the report to be compressed in the email sent. Normally, this option is not selected by default. Now you can set this setting to be selected by default (in /fileserver/etc/main/main.cf):

<scheduler>
    <email>
       <defaultcompression>true</defaultcompression>
    </email>
</scheduler>

If you set this to true, "Report compression" will be automatically selected when scheduling new jobs. Defaults to false.

Following you can see the complete default /fileserver/etc/main/main.cf file.

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
   <install>
      <basedata>true</basedata>
   </install>
   <default>
      <charset>UTF-8</charset>
   </default>
   <tempdir>tempdir</tempdir>
   <tempfile>
      <lifetime>3600</lifetime>
   </tempfile>
   <maintenance>
      <tasks>
         <interval>600000</interval>
      </tasks>
   </maintenance>
   <search>
      <timeout>5000</timeout>
   </search>
   <pagetitle>ReportServer</pagetitle>
   <scheduler>
     <email>
       <defaultcompression>false</defaultcompression>
     </email>
   </scheduler>
</configuration>

Allow to Execute Dadgets from Dashboard

Reports may now be opened/executed directly directly in the dashboard. You can see this in the following screenshots. When clicking on the "execute" button, the report opens in the report execution view.

Refresh Preview

You can now refresh the report preview directly, refer to the screenshot below. This of course works with the rest of report types as well.

For dynamic lists, you will see a new context menu entry as well:

Allow to List/View Catalina Log Files and Send these via E-mail

You can now list the catalina log files in your catalina.home directory by the terminal command "listlogfiles". If you need to explicitly set the log file path, you can use the logdir setting in the /fileserver/etc/main/main.cf configuration file. You can specify the sorting column(s) by a semicolon-separated list of column numbers in the -s option. Allowed are values 1, 2, and 3 for the first (filename), second (last modified) and third (size) columns, respectively. If you need to sort a given column in descending order, you can enter a - prefix in front of the column’s index. Default sorting is by filename (ascending order). Example output is shown below.

Further, you can use Java regular expressions for filtering files.

The example below lists all log files starting with “reportserver” and sorting them by size in descending order.

listlogfiles -s -3 -f "reportserver.*"

The example below lists all log files starting with “reportserver” and sorting them by size in descending order, followed by filename in ascending order.

listlogfiles -s -3;1 -f "reportserver.*"

Further, you can use the -e option if you want to send the (filtered) log files via e-mail. For example, the following allows you to ZIP and send all log files starting with “reportserver” to the current user via e-mail.

listlogfiles -s -3;1 -f "reportserver.*" -e

By using the viewlogfile command you can see the last 500 lines of a given tomcat file as you can see in the following screenshot.

If needed, you can explicitely set the log directory in /fileserver/etc/main/main.cf (logdir). If not set, it uses the catalina.home path. The default /fileserver/etc/main/main.cf file is the following:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
   <install>
      <basedata>true</basedata>
   </install>
   <default>
      <charset>UTF-8</charset>
   </default>
   <tempdir>tempdir</tempdir>
   <!-- Explicitly sets the log directory path. Default uses catalina.home path.
   <logdir>logdir</logdir>
   -->
   <tempfile>
      <lifetime>3600</lifetime>
   </tempfile>
   <maintenance>
      <tasks>
         <interval>600000</interval>
      </tasks>
   </maintenance>
   <search>
      <timeout>5000</timeout>
   </search>
   <pagetitle>ReportServer</pagetitle>
   <scheduler>
     <email>
       <defaultcompression>false</defaultcompression>
     </email>
   </scheduler>
</configuration>

You can configure the texts in the email with the /etc/security/notifications.cf file (logfiles). The default file is the following:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <createdpassword disabled="false">
    <email>
      <subject>${msgs['net.datenwerke.rs.passwordpolicy.service.locale.PasswordPolicyMessages']['createdPasswordSubject']}</subject>
      <text>${msgs['net.datenwerke.rs.passwordpolicy.service.locale.PasswordPolicyMessages']['createdPasswordSalutation']} ${user.getFirstname()} ${user.getLastname()},
        
${msgs['net.datenwerke.rs.passwordpolicy.service.locale.PasswordPolicyMessages']['createdPasswordIntro']}
        
${user.getUsername()}
        
${msgs['net.datenwerke.rs.passwordpolicy.service.locale.PasswordPolicyMessages']['createdPasswordEnd']}
       
      </text>
    </email>    
  </createdpassword>
  <changedpassword disabled="false">
    <email>
      <subject>${msgs['net.datenwerke.rs.passwordpolicy.service.locale.PasswordPolicyMessages']['changedPasswordSubject']}</subject>
      <text>${msgs['net.datenwerke.rs.passwordpolicy.service.locale.PasswordPolicyMessages']['changedPasswordSalutation']} ${user.getFirstname()} ${user.getLastname()},
        
${msgs['net.datenwerke.rs.passwordpolicy.service.locale.PasswordPolicyMessages']['changedPasswordIntro']}

${user.getUsername()}

${msgs['net.datenwerke.rs.passwordpolicy.service.locale.PasswordPolicyMessages']['changedPasswordEnd']}
      </text>
    </email>    
  </changedpassword>
  <lostpassword indicateWrongUsername="false">
    <email>
      <subject>${msgs['net.datenwerke.rs.passwordpolicy.service.locale.PasswordPolicyMessages']['lostPasswordSubject']}</subject>
      <text>${msgs['net.datenwerke.rs.passwordpolicy.service.locale.PasswordPolicyMessages']['lostPasswordSalutation']} ${user.getFirstname()} ${user.getLastname()},

${msgs['net.datenwerke.rs.passwordpolicy.service.locale.PasswordPolicyMessages']['lostPasswordIntro']}
  
        ${msgs['net.datenwerke.rs.passwordpolicy.service.locale.PasswordPolicyMessages']['lostPasswordUsername']}: ${user.getUsername()}
        ${msgs['net.datenwerke.rs.passwordpolicy.service.locale.PasswordPolicyMessages']['lostPasswordPassword']}: ${password}

${msgs['net.datenwerke.rs.passwordpolicy.service.locale.PasswordPolicyMessages']['lostPasswordEnd']}		
      </text>   
    </email> 
  </lostpassword>
  <logfiles>
    <email>
      <subject>${msgs['net.datenwerke.rs.adminutils.service.locale.AdminUtilsMessages']['emailLogFilesSubject']}</subject>
      <text>${msgs['net.datenwerke.rs.adminutils.service.locale.AdminUtilsMessages']['emailLogFilesSalutation']} ${user.getFirstname()} ${user.getLastname()},

${msgs['net.datenwerke.rs.adminutils.service.locale.AdminUtilsMessages']['emailLogFilesIntro']}

${filter}

${msgs['net.datenwerke.rs.adminutils.service.locale.AdminUtilsMessages']['emailLogFilesEnd']}		
      </text>
    </email> 
  </logfiles>
</configuration>

Allow to Modify Directory's Web Access by Terminal

You can now modify the web access of a fileserver directory or directories by the new dirmod command. E.g. the following command adds web access to all filesystem directories containing “report” in their name:

dirmod webaccess "hql:from FileServerFolder where name like '%report%'" true

Allow to Configure Excel Sheet Titles

You can specify the title of the data and configuration sheets in the exported Excel file by the "datasheet" and "configsheet" parameters in the /fileserver/etc/exportfilemd/excelexport.cf configuration file. The default file is the following:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
   <xls>
      <format>xlsx</format>
      <stream>true</stream>
      <datasheet>Dynamic list</datasheet>
      <configsheet>Configuration</configsheet>
   </xls>
</configuration>

Allow to configure URL whitelist

Certain operations, e.g. redirect, are not allowed for external URLs. If you need to allow a URL you can add it to the whitelist in the /fileserver/etc/security/whitelist.cf configuration file.

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
   <urls>
      <!-- <url>http://www.host.com</url> -->
   </urls>
</configuration>

New Features, Improvements and Bug Fixes for ReportServer RS3.4.0-6032

New Features, Improvements and Bug Fixes for ReportServer RS3.4.0-6033

New Features, Improvements and Bug Fixes for ReportServer RS3.4.0-6034

New Features, Improvements and Bug Fixes for ReportServer RS3.4.0-6035

New Features, Improvements and Bug Fixes for ReportServer RS3.4.0-6036