Difference between revisions of "Version 10.4 Platform"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| (45 intermediate revisions by the same user not shown) | |||
| Line 8: | Line 8: | ||
| | | | ||
'''''See also:''''' | '''''See also:''''' | ||
* [[All Release Notes]] | * [[All Release Notes]] | ||
* [[ | * [[Release calendar]] | ||
|} | |} | ||
__TOC__ | __TOC__ | ||
| Line 21: | Line 20: | ||
</blockquote> | </blockquote> | ||
--> | --> | ||
=== | === 28 Mar 2015 === | ||
<blockquote> | |||
==== Rollup Summary Enhancements==== | |||
:* When a Rollup Summary field is added, or the definition of an existing field changes, a background job is scheduled to re-calculate values for all existing records. | |||
:: ''Learn more:'' [[Rollup Summary Fields#Technical Considerations]] | |||
:* When adding or modifying a [[Related Record]] in a form, new Rollup Summary results are immediately visible in the parent record. | |||
:* When changing the definition of a field that is targeted by a Rollup Summary, the change in the Rollup Summary value is immediately visible when a record is viewed. For example: | |||
::* A change in the field's precision (number of decimal places). | |||
::* A change to the calculation of a formula field. | |||
::* A change to a formula field's return type: Number <==> Currency, or Date <==> DateTime. | |||
====Bug Fixes==== | |||
:ServiceDesk requests | |||
::{| border="1" cellpadding="5" cellspacing="1" | |||
| Case #008289 || Resolved: Read-only priority field is still editable in header | |||
|- | |||
| Case #008359 || Resolved: Problems with validation in popup windows | |||
|} | |||
:iTrac issues: | |||
::{| border="1" cellpadding="5" cellspacing="1" | |||
|- | |||
| LJP-51 || Message is not correct when trial Tenant limit on user licenses is reached | |||
|- | |||
| LJP-54 || Unable to compile a class for JSP page due to login issue | |||
|- | |||
| LJP-59 || Removing a field from a form needs to warn when the field is used in a layout rule | |||
|- | |||
| LJP-65 || User-creationg via Java-API fails when "send welcome message" flag is included | |||
|- | |||
| LJP-68 || Confirmation button missing when two consecutive process steps need the same role | |||
|- | |||
| LJP-76 || Validate fields when a layout rule sets the Required attribute | |||
|- | |||
| LJP-99 || date_created field not available when creating report | |||
|- | |||
| LJP-103 || Getting action in Form On Load Script | |||
|- | |||
| LJP-112 || Using the REST API to change a read-only TextField to a Lookup leaves the field as read-only--an invalid option for Lookup fields | |||
|- | |||
| LJP-114 || UI issue seen on Multiple Check Boxes field in accessibility mode. | |||
|- | |||
| LJP-116 || Business Rules: Set-Status action throws JavaScript error when a new rule is added | |||
|} | |||
==== Documentation Enhancements ==== | |||
:* [[Package Items]] - Expanded to list the items that go into a package and how they behave. | |||
:* [[Choosing a Deployment Strategy for Development Systems]] - | |||
:*: Lists the steps to fully replicate a development-environment application in a target system. | |||
:* [[Heartbeat Check]] - Revised for accuracy. | |||
:* [[Template Variables]] - Expanded with a more comprehensive list of variables. | |||
</blockquote> | |||
=== 28 Feb 2015 === | |||
<blockquote> | <blockquote> | ||
==== Change to the Support-Request Process ==== | |||
:Beginning with this release, support requests will be made using the standard Software AG support process. (Existing users will be able to use a new "Historical Cases" link to get to past requests.) | |||
: ''Learn more:'' [[Open a Support Incident]] | |||
==== Accessibility Fixes ==== | ==== Accessibility Fixes ==== | ||
: | :Multiple issues relating to the Accessibility feature have been fixed. | ||
:{| border="1" cellpadding="5" cellspacing="1" | |||
| Case #7932 || Links generated with a span-tag need to be converted to use the A-tag, so they can receive focus. | |||
|- | |||
| Case #7936 || After a pop-up opens, set the active focus to the first element in the pop-up | |||
|- | |||
| valign="top"| Case #7933 || | |||
* Use the keyboard to open records from entries listed in data tables | |||
* Use the keyboard to format text in the editors. | |||
* Use the keyboard to select elements from a ComboBox | |||
* Use the keyboard to access field hints | |||
|} | |||
:''Learn more:'' [[Accessibility Mode]] | :''Learn more:'' [[Accessibility Mode]] | ||
| Line 30: | Line 99: | ||
:{| border="1" cellpadding="5" cellspacing="1" | :{| border="1" cellpadding="5" cellspacing="1" | ||
|- | |- | ||
| Case # | | Case #7805 || Look-up fields required by layout rule are not validated | ||
|- | |- | ||
| Case # | | Case #8152 || Empty WebForm area in Internet Explorer | ||
|- | |- | ||
| Case # | | Case #8165 || Layout Rules not working with prefilled fields | ||
|- | |- | ||
| Case # | | Case #8248 || Attempting to change Name or E-Mail Address of top team (My Team) fails | ||
|} | |} | ||
Latest revision as of 06:24, 21 February 2017
See also:
28 Mar 2015
Rollup Summary Enhancements
- When a Rollup Summary field is added, or the definition of an existing field changes, a background job is scheduled to re-calculate values for all existing records.
- Learn more: Rollup Summary Fields#Technical Considerations
- When adding or modifying a Related Record in a form, new Rollup Summary results are immediately visible in the parent record.
- When changing the definition of a field that is targeted by a Rollup Summary, the change in the Rollup Summary value is immediately visible when a record is viewed. For example:
- A change in the field's precision (number of decimal places).
- A change to the calculation of a formula field.
- A change to a formula field's return type: Number <==> Currency, or Date <==> DateTime.
Bug Fixes
- ServiceDesk requests
Case #008289 Resolved: Read-only priority field is still editable in header Case #008359 Resolved: Problems with validation in popup windows
- iTrac issues:
LJP-51 Message is not correct when trial Tenant limit on user licenses is reached LJP-54 Unable to compile a class for JSP page due to login issue LJP-59 Removing a field from a form needs to warn when the field is used in a layout rule LJP-65 User-creationg via Java-API fails when "send welcome message" flag is included LJP-68 Confirmation button missing when two consecutive process steps need the same role LJP-76 Validate fields when a layout rule sets the Required attribute LJP-99 date_created field not available when creating report LJP-103 Getting action in Form On Load Script LJP-112 Using the REST API to change a read-only TextField to a Lookup leaves the field as read-only--an invalid option for Lookup fields LJP-114 UI issue seen on Multiple Check Boxes field in accessibility mode. LJP-116 Business Rules: Set-Status action throws JavaScript error when a new rule is added Documentation Enhancements
- Package Items - Expanded to list the items that go into a package and how they behave.
- Choosing a Deployment Strategy for Development Systems -
- Lists the steps to fully replicate a development-environment application in a target system.
- Heartbeat Check - Revised for accuracy.
- Template Variables - Expanded with a more comprehensive list of variables.
28 Feb 2015
Change to the Support-Request Process
- Beginning with this release, support requests will be made using the standard Software AG support process. (Existing users will be able to use a new "Historical Cases" link to get to past requests.)
- Learn more: Open a Support Incident
Accessibility Fixes
- Multiple issues relating to the Accessibility feature have been fixed.
Case #7932 Links generated with a span-tag need to be converted to use the A-tag, so they can receive focus. Case #7936 After a pop-up opens, set the active focus to the first element in the pop-up Case #7933
- Use the keyboard to open records from entries listed in data tables
- Use the keyboard to format text in the editors.
- Use the keyboard to select elements from a ComboBox
- Use the keyboard to access field hints
- Learn more: Accessibility Mode
Bug Fixes
Case #7805 Look-up fields required by layout rule are not validated Case #8152 Empty WebForm area in Internet Explorer Case #8165 Layout Rules not working with prefilled fields Case #8248 Attempting to change Name or E-Mail Address of top team (My Team) fails Documentation Enhancements
- Process Models#Calling Java Code from a Process - Outlines a quick hack to do the deed.
31 Jan 2015
Editor Shortcuts in Accessibility Mode
- The keyboard shortcuts that can be used to drive the rich text editor (HTML editor) in normal mode work in Accessibility Mode, as well.
- Learn more: Keyboard Shortcuts
10 Jan 2015
Access Custom User Fields in JavaScript
- Use the userCustomFields structure to access custom fields that have been added to the Users Object.
- Learn more: JavaScript Functions#Accessing User Information
Promotion Codes
- Platform administrators can create promotion codes for new tenants, "sweetening the pot" for a specified period of time to encourage new business. (This is really an installable-version feature. But since it will be in the cloud first, the sales organization now has the capacity to define promotion codes it needs.)
- Learn more: Promo Code Configuration
Promotion Code APIs
- Along with the new promotion codes comes the ability to manage them using APIs. So it becomes possible to define a custom interface, rather than requiring the sales organization to use the platform admin interface.
- Learn more: REST API:promoCode Resource