AgileApps Support Wiki

Difference between revisions of "Version 10.4 Installable (Apr 2015)"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 16: Line 16:
:{| border="1" cellpadding="5" cellspacing="1"  
:{| border="1" cellpadding="5" cellspacing="1"  
| LJP-59  || Validation when field removed from a form is used in a layout rule
| LJP-59  || Validation when field removed from a form is used in a layout rule
|-
| LJP-89  || Correct sorting issue in Tasks view
|-
|-
| LJP-98  || New dashboard was not visible to all
| LJP-98  || New dashboard was not visible to all
|-
|-
| LJP-102 || CAC for list view is not applied in combination with other expressions
| LJP-102 || Custom Access Criteria for list view was not applied in combination with other expressions
|-
| LJP-115 || When formula return type is changed, wrong validation message is shown
|-
|-
| LJP-121 || Report presentation in dashboard did not match the actual report
| LJP-121 || Report presentation in dashboard did not match the actual report
|-
|-
| LJP-126 || Layout rules could not be used to disable Radio buttons
| LJP-126 || Layout rules could not be used to disable Radio buttons
|-
| LJP-135 || Accessibility issue: Edit link label is not assigned using title attribute in Dashboard
|-
| LJP-138 || Accessibility Issue: User is not able to add a class
|-
| LJP-139 || Unsupported JSP-option for Lookups was present in the interface
|-
|-
| colspan="2"|
| colspan="2"|
Line 40: Line 34:
|-
|-
| LJP-{{TBD|??}} || Reinstalling a package with a field change doesn't remove the additional properties that were on the original field (the read-only field problem)
| LJP-{{TBD|??}} || Reinstalling a package with a field change doesn't remove the additional properties that were on the original field (the read-only field problem)
|}
|}
</blockquote>
</blockquote>
<!--
<!--

Revision as of 19:15, 10 April 2015

Release Notes for the installable version of the AgileApps Cloud platform.

See also:

About the Installable Version

The installable version of the platform lets you create and manage a private cloud behind your corporate firewall. It can also be used to set up a public cloud that serves multiple clients--generally with a shared application and global data. This page highlights changes to the installation process, along with features of the new release.

Platform Functionality

Bug Fixes

LJP-59 Validation when field removed from a form is used in a layout rule
LJP-89 Correct sorting issue in Tasks view
LJP-98 New dashboard was not visible to all
LJP-102 Custom Access Criteria for list view was not applied in combination with other expressions
LJP-121 Report presentation in dashboard did not match the actual report
LJP-126 Layout rules could not be used to disable Radio buttons
LJP-98 New dashboard not visible to all __TBD: ??-not in recent fix list__
LJP-__TBD: ??__ Customer doesn't have a database
LJP-__TBD: ??__ Reinstalling a package with a field change doesn't remove the additional properties that were on the original field (the read-only field problem)

Installing and Upgrading

Ensure that Software Requirements are Met

Before starting either a First-Time Installation or a platform upgrade, ensure that dependent utilities are at the minimum levels specified in the Software Requirements.

Upgrade Notes

Changes to the Software Requirements

These software requirements have been upgraded:
  • JDK 8
    Note:
    While the installation and operation of the platform requires Java 8, custom code in a Java Class continues to be validated against Java 6 syntax -- in part because the instrumentation engine responsible for monitoring resource utilization only works on version 6 byte codes.

Additional Installation Step for RedHat 6

Installations on RedHat version 6 need to ensure that the 32-bit version of the gcc library is found on the Java path. If the 64-bit version is found, and Java Code Governors are enabled, a StaticProbeInstrumenterException occurs when attempting to compile a Java class in the platform. To eliminate that problem:
  1. Login as a root
  2. Install the 32-bit instrumentation library:
    yum install libstdc++.i686 libstdc++.x86_64
  3. Verify that it is working:
    • Go to ${TOMCAT_DIR}/bin/instrumentation/os/linux/x86 folder
    • Execute the binary: /probeinstrumenter
      You should see usage instructions for the probeinstrumenter.

Learn More

Retrieved from "https://agileappscloud.info/aawiki-src/index.php?title=Version_10.4_Installable_(Apr_2015)&oldid=25721"