US English (US)
ES Spanish

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Log in
English (US)
US English (US)
ES Spanish
  • Home
  • Releases

RIO Education Reporting Engine (Generic) 1.7

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • RIO Certification
    RIO Certification Program RIO Academy RIO Challenge RIO Recipe Training
  • Releases
    Release Notes
  • Help & Support
    Install RIO Education RIO Insights RIO Recipe Support
  • About Us
    Who is RIO Education? Start Your RIO Journey Housekeeping
  • Experience RIO in action
+ More

Table of Contents

RIO Education Reporting Engine (Generic) 1.7 1.7 New Installer Before you upgrade Enhancements and Bug Fixes Bug Fix - Compliance and Reporting

RIO Education Reporting Engine (Generic) 1.7

Release date: 20th Jan 2025

 

1.7 New Installer

https://login.salesforce.com/packaging/installPackage.apexp?p0=04tGB000002ujAe

 

Before you upgrade

We recommend you to test new versions in a sandbox first (according to your own test cases), before rolling it into production.

Following steps are required if you are upgrading from Reporting Engine (Generic) 1.6.

  1.  Delete Apex Scheduler introduced in v1.6
    1. Navigate to Setup >> Scheduled Jobs and delete the following jobs:
      • dataScheduler 1
      • dataScheduler 2
      • dataScheduler 3
      • dataScheduler 4
      • dataScheduler 5
      • dataScheduler 6
      • dataScheduler 7
      • dataScheduler 8
      • dataScheduler 9
      • dataScheduler 10
      • dataScheduler 11
      • dataScheduler 12
 

 

Enhancements and Bug Fixes

Bug Fix - Compliance and Reporting

ISS-001999 Report in XML format

The HESA (UK) reporting process requires comprehensive information from multi-level child records to be exported in XML format. In version 1.7, significant enhancements have been introduced to support this requirement. 

These include:

  1. Ability to generate reports in XML format
  2. Capability to handle multi-level sub-queries, allowing reporting across up to five levels of child relationships. 
    1. These improvements is currently available for reporting with XML format only.
 
 

ISS-002244 Allow running number across multiple reporting section

In 1098-T positioned reporting, a key requirement is maintaining a running number across different sections of the report, such as Header, Body, and Footer. The running number starts in the Header and continues sequentially through the Body and Footer.

This functionality can be achieved using the existing logic by leveraging the data holder generation feature:

  1. Instead of mapping reporting elements or fields directly to Salesforce objects and fields, they are mapped to the data holder object and fields. 
  2. The Aggregation/Group By Field feature is used to extract values from Salesforce fields and populate them into corresponding fields in the data holder. 
  3. A custom flow or Apex code is then introduced to populate the running number in the data holder records. Ultimately, the data stored in the data holder object is utilized for reporting automation.

However, this method has a limitation: the batch size for the reporting scheduler job must be set to 1 to ensure that all sections are processed sequentially. While this guarantees correct sequencing, it significantly increases the time required to complete the reporting process.

To address this limitation, we introduced an enhancement that allows the scheduler batch size and interval (in minutes) to be configured directly in the reporting export record, rather than relying on values in the custom setting. This improvement provides greater flexibility, enabling different batch sizes and intervals to be specified for each reporting export, thereby optimizing performance without compromising accuracy.

As part of the enhancements, the scheduled job that was introduced in v1.6 to run every 5 minutes will be deprecated. Instead, the scheduler will now be initiated and executed automatically based on the configuration specified in the reporting export record. This change ensures that the scheduling process is more dynamic and adaptable to individual reporting requirements, eliminating the need for a fixed interval job.

 
 

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • RIO Version Releases
  • RIO Education 3.14.5 Release Notes
  • RIO Education Reporting Engine (Generic) 1.8
RIO Education

RIO Education, a WDCi Company. This information is proprietary, confidential and protected by copyright ©2024.

CONTACT

Get in touch

  • Privacy
  • Terms of service

Knowledge Base Software powered by Helpjuice

Definition by Author

0
0
Expand