FAQs

University employees needing Banner Data access must complete a Data Usage Request (DUR) form. Submissions will be sent for review to the University Registrar’s Office and be routed for additional approval, as necessary. All persons requesting data will be asked to: 

• Provide a statement of legitimate educational interest for needing the requested data. 
• Provide relevant documentation such as a Security Design Review and Cloud Addendum. 
• Sign-off on an understanding and commitment to follow University policies regarding data use. 

If you need access to Argos, please submit an Argos Access Request. 

Argos access is handled via the Banner Access request form and should be submitted by a supervisor. Your supervisor must provide a statement of legitimate educational interest for access. Please see the FAQ page for more information.  

Once a user is approved for Argos, access to data is controlled by a security feature called a role. The role or roles assigned to each user define what data a user can see within a report. For example, a user who has been assigned the role of LAW_REGISTRAR may be able to access fields that contain academic data for students in the School of Law but would not be able to access those same fields of data for students in the School of Architecture. Likewise, there may be categories of data within the School of Law that are only available to users who are assigned the role of LAW_FINAID, so the user with a role of LAW_Registrar would not be able to view that data. 

Request Report 

If you need to convert an existing Brio report, please select New Report Request.  

Please note that report requests are dependent upon approval by the relevant data steward. If you are requesting a report with data attributes not previously available to you (such as race and gender) you may be required to fill out a Banner Data Usage Request form. 

The development team will review your request and contact you within a week to discuss your specific needs. Please note that report build times vary depending on the complexity of the request. 

Oracle no longer supports Hyperion Brio. There is a risk Brio reports could stop working at any time and no fixes could be implemented to address. Users are encouraged to transition to Argos for multiple reasons, including the end of vendor support, information security guidelines, and usability.  

The IT reporting team is working on the development and deployment of a backlog of Brio reports based on the needs of the functional users. The long-term goal of this initiative is to retire Brio from operational reporting in the student systems space. 

For assistance or questions about reporting, please select Help.  

Office Hours are also available and can be scheduled directly with the reporting development team.  

Argos does not work with Internet Explorer. Compatible browsers include Microsoft Edge, Chrome, Firefox, and Safari.

Yes! A report can be customized.

To request a change to an existing report, please select Enhancement to Current Report or schedule an office hour with the reporting development team. 

While clients cannot create their own data blocks, end users can create and customize their own reports, depending on the users’ level of security access. Report Writer role access is needed, and users must meet RW role training, requirements, and approval before access will be granted.  

Check out the Argos User Guides for more information about building reports. 

To learn more or submit a request to add a filter setting, please contact reports.sis@yale.edu 

To learn more or submit a request to add a report schedule, please contact reports.sis@yale.edu 

Evisions Help - Shortcut 

Shortcuts allow you to save links to frequently used DataBlocks in one convenient location. Shortcuts created via the Argos Windows client appear in Web Viewer, and vice versa. To create a shortcut in Web Viewer, click the star icon next to the DataBlock. 

In the Create Shortcut dialog, you can edit the name of the shortcut, specify whether it should be a “Shared Shortcut” (visible to everyone) or “My Shortcut” (visible only to you), and choose an optional subdirectory for the shortcut. 

Note: By default, Report Viewers are only able to create private shortcuts. Your MAPS Administrator may add the ability to create shared shortcuts to your user role if it is needed. 

Initially, all shortcuts are stored in the root shortcut directory. To add the shortcut to a subfolder, click Change Location and either select a folder or create a new one. 

To accept the settings, click Create. 

Click View Shortcut to go to the Shortcut tab, or Close to return to the previous location in the Explorer tab. 

To access the shortcut from the Explorer, go to the Shortcuts tab and navigate to the appropriate directory. 

Notice the lock icons showing next to the shortcut and also on the Shortcuts folder in the breadcrumb trail. Both the shortcut and its containing folder (the Shortcuts folder) are private. 

The other icons to the far right of each shortcut allow you to Locate, Edit, or Remove a shortcut. Locating a shortcut opens the folder where the DataBlock resides. The Edit button brings up the Edit Shortcut dialog, where you can rename or move the shortcut. 

You may wish to remove a shortcut if it is no longer valid– e.g., if a DataBlock Designer has deleted the underlying DataBlock. In this case, the name of the shortcut appears in red text, and you will see an error message when attempting to launch it. 

Stay Tuned!

Based on user feedback, a pivot/export feature is being piloted and will be released in early January.  

Ability to save pivots coming Spring 2025.

Once a user is approved for Argos, access to data is controlled by a security feature called a role. The role or roles assigned to each user define what data a user can see. For example, users who has been assigned the role of LAW_REGISTRAR will have access to reports and fields that contain academic data for students in the School of Law, but they will not be able to access data from other schools or departments. 

An entire report might be restricted, so only users with certain roles will see the report in Argos, or columns of data within a report could be restricted. If columns of data are restricted, users may still be able to run the report, but they will not be able to access all the data columns within the report. More information about security for specific domains and reports is available in the report documentation. 

If you need access to Argos, please submit an Argos Access Request. 

Argos access is handled via the Banner Access request form and should be submitted by a supervisor. Please see the FAQ page for more information.  

Once a user is approved for Argos, access to data is controlled by a security feature called a role. The role or roles assigned to each user define what data a user can see within a report. For example, a user who has been assigned the role of LAW_REGISTRAR may be able to access fields that contain academic data for students in the School of Law but would not be able to access those same fields of data for students in the School of Architecture. Likewise, there may be categories of data within the School of Law that are only available to users who are assigned the role of LAW_FINAID, so the user with a role of LAW_Registrar would not be able to view that data. 

To request a new report, please select New Report Request.  

Please note that report requests are dependent upon approval by the relevant data steward. If you are requesting a report with data attributes not previously available to you (such as race and gender) you may be required to fill out a Banner Data Usage Request form. 

The development team will review your request and contact you within a week to discuss your specific needs. Please note that report build times vary depending on the complexity of the request. 

Request Report 

If you need to convert an existing Brio report, please select New Report Request.  

Please note that report requests are dependent upon approval by the relevant data steward. If you are requesting a report with data attributes not previously available to you (such as race and gender) you may be required to fill out a Banner Data Usage Request form. 

The development team will review your request and contact you within a week to discuss your specific needs. Please note that report build times vary depending on the complexity of the request. 

To request a change to an existing report, please select Enhancement to Current Report. 

Please note that report requests are dependent upon approval by the relevant data steward. If you are requesting a report with data attributes not previously available to you (such as race and gender) you may be required to fill out a Banner Data Usage Request form. 

The development team will review your request and contact you within a week to discuss your specific needs. Please note that report build times vary depending on the complexity of the request. 

For assistance or questions about reporting, please select Help.  

Office Hours are also available and can be scheduled directly with the reporting development team.  

Jasper Server does not work with Internet Explorer. Compatible browsers include Microsoft Edge, Chrome, Firefox and Safari. 

While clients cannot create their own domains, end users can create and customize their own ad hoc views and reports, depending on the users’ level of security access. Check out the Jaspersoft User Guides for more information about customizing your reports. 

Yes! If the report is an Ad Hoc View (VW_) you can edit it directly in the Ad Hoc Editor (if the report is in Public, you can find information about saving a copy into your organizational folder by going to Saving Reports from the Public Folder). If it is a Report, there is a good chance that it has an underlying Ad Hoc View in Data Sources. Search for the Report Name and see if you find a version prefixed with VW or look in the Data Sources Folder. For more details on using the Ad Hoc Editor, see Jaspersoft Ad Hoc Views - User Guides. 

Data sets within a domain may contain multiple rows for a single field. When creating an ad hoc view, you can use the DistinctQuery field to limit data to distinct rows.  

For example, a single course section may have several faculty members associated with it:  

The data is structured in such a way that even if Faculty Name is not added as a Column in the ad hoc view, separate rows for each faculty member per course will display, even if those rows have exactly the same values for the chosen fields (for example, Course Name, Course Section, Term, and CRN). 

By adding the DistinctQuery field to this ad hoc view, you can limit the data to return distinct rows only.  For step-by-step instructions on adding the DistinctQuery field, see the Jaspersoft Ad Hoc Views - User Guides. 

AD HOC VIEW 

An ad hoc view pulls data from a domain and allows clients to view and analyze the data in the Jaspersoft ad hoc editor. The ad hoc view is highly customizable. 

AD HOC REPORT 

An ad hoc report is a fixed report that is created from an ad hoc view and is designed to meet a specific need or objective. Clients can save or export a report but are not able to alter the basic structure of the report.  

Once a user is approved for the Jaspersoft Server, access to data is controlled by a security feature called a role. The role or roles assigned to each user define what data a user can see. For example, users who has been assigned the role of LAW_REGISTRAR will have access to reports and fields that contain academic data for students in the School of Law, but they would not be able to access data from other schools or departments. 

An entire report might be restricted, so only users with certain roles will see the report in the Jaspersoft Server, or columns of data within a report could be restricted. If columns of data are restricted, users may still be able to run the report, but they will not be able to access all the data columns within the report. More information about security for specific domains and reports is available in the report documentation. 

If you need access to Jaspersoft Server, please submit a Jaspersoft Access Request. 

Jaspersoft access is handled via the Banner Access request form and should be submitted by a supervisor. Please see the FAQ page for more information.  

Once a user is approved for the Jaspersoft Server, access to data is controlled by a security feature called a role. The role or roles assigned to each user define what data a user can see within a report. For example, a user who has been assigned the role of LAW_REGISTRAR may be able to access fields that contain academic data for students in the School of Law but would not be able to access those same fields of data for students in the School of Architecture. Likewise, there may be categories of data within the School of Law that are only available to users who are assigned the role of LAW_FINAID, so the user with a role of LAW_Registrar would not be able to view that data. 

To request a new report, please select New Report Request.  

Please note that report requests are dependent upon approval by the relevant data steward. If you are requesting a report with data attributes not previously available to you (such as race and gender) you may be required to fill out a Banner Data Usage Request form. 

The development team will review your request and contact you within a week to discuss your specific needs. Please note that report build times vary depending on the complexity of the request. 

Request Report 

If you need to convert an existing Brio report, please select New Report Request.  

Please note that report requests are dependent upon approval by the relevant data steward. If you are requesting a report with data attributes not previously available to you (such as race and gender) you may be required to fill out a Banner Data Usage Request form. 

The development team will review your request and contact you within a week to discuss your specific needs. Please note that report build times vary depending on the complexity of the request. 

To request a change to an existing report, please select Enhancement to Current Report. 

Please note that report requests are dependent upon approval by the relevant data steward. If you are requesting a report with data attributes not previously available to you (such as race and gender) you may be required to fill out a Banner Data Usage Request form. 

The development team will review your request and contact you within a week to discuss your specific needs. Please note that report build times vary depending on the complexity of the request. 

For assistance or questions about reporting, please select Help.  

Office Hours are also available and can be scheduled directly with the reporting development team.