Campus Portal Common Features - Archive
Tip
Only releases with enhancements or resolved issues for this module have content below.
Resolved Issues
Enhancements
Several enhancements have been made to the Online Payment Administration feature in the Campus Portal to help make payment transactions easier. Updates include:
A signature key is no longer required.
New Authorize.Net Payment Form options will allow you to require, show, or hide card verification, billing address, and email address.
A preview and test option for the payment form will allow you to see what users will see when they make a payment on your Campus Portal. You can choose to go through the entire payment process by entering valid credit card or banking information, and completing a small $0.01 transaction.
Completed transactions will automatically be added to the general ledger as receipt transactions.
Jenzabar delivered several legal and campus name enhancement with 2019.4 that impacted web salutations. These changes mean several things that were not detailed in the 2019.4 Release News:
Web salutations no longer control how names are shown in the Campus Portal. Campus Portal users now submit name changes using Profile Setting options. These changes are reviewed using the Desktop Process Internet Submissions window and if approved, added and shown in accordance with the individual's preferences in both systems.
Web salutation codes no longer need to be associated with an individual or organization on the Desktop Name Entity window, Salutations tab.
For more detailed information about how legal names and campus names are now handled in the system and in conjunction with the Campus Portal, see the 2019.4 Release News information on MyJenzabar (https://www.myjenzabar.net/ICS/Portlets/ICS/Handoutportlet/viewhandler.ashx?handout_id=a504120b-8a93-441c-ab76-aafab6156bb6).
2020.1
Enhancements
Order options have been added to the Site Manager, Login messages options. Your Campus Portal site administrator can determine the order messages will appear in and make more important messages appear first. For example, if your school is requiring students to sign a data privacy form, a message letting them know about the form can appear when they first sign in.
Enhancements
2019.4 introduces Campus Name, which allows users to designate a name they prefer to be called on campus. This preferred campus name is now shown in name fields, processes, searches, and reports throughout Desktop, J1 Web, and the Campus Portal except where legal name is required. To keep legal name information private, new permissions have been added that control which user groups can view it.
For detailed information about campus names, see the Common, New Campus Name Feature section.
With 2019.4, many Campus Portal Student features have been enhanced to meet the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines (WCAG) 2.0. Jenzabar is utilizing these guidelines to start making our web content more accessible and user friendly for all people. Interfaces for many features now have
improved color contrast, making content easier to read
significantly improved keyboard navigations for quicker access to content
more efficient and reliable screen reader compatibility
additional improvements based on WCAG 2.0 requirements that benefit all users
Note
Feature functionalities are not impacted.
Note
Formbuilder, FormFlow, My Advisor Meetings, Student Registration, and View My Students features will have WCAG 2.0 guidelines applied to them in upcoming releases.
Resolved Issues
Issue | Description |
|---|---|
172217 | Receipt transactions are now created when students paid with credit cards that have longer names (e.g., American Express and Master Card). |
172220 | Authorize.net is phasing out the MD5-based transaction hash element January 31, 2019, which impacts schools using their hosted online payment option. You must install this update 1) to ensure there is no disruption between Authorize.net and the Online Payment feature, and 2) to use the new SHA-512 based hash, which enhances the security of your transactions. |
2019.3
Resolved Issues
Issue | Description |
|---|---|
149591 | The credit card type was not passed back from Authorize.net to the payment transaction generated in J1 Desktop when using the payment launch out method. This issue has been corrected so that the credit card information is correctly passed through from the launch out form. |
150885 | When the launch out payment method is used, the Authorize.net form was opening in a separate tab, causing pop-up blocker issues. The Authorize.net form now opens in the same tab to avoid the pop-up blocker warnings. Additionally, a return link to the correct portlet page has been added. |
Resolved Issues
Issue | Description |
|---|---|
149591 | The credit card type was not passed back from Authorize.net to the payment transaction generated in J1 Desktop when using the payment launch out method. This issue has been corrected so that the credit card information is correctly passed through from the launch out form. |
150885 | When the launch out payment method is used, the Authorize.net form was opening in a separate tab, causing pop-up blocker issues. The Authorize.net form now opens in the same tab to avoid the pop-up blocker warnings. Additionally, a return link to the correct portlet page has been added. |