Version 10.6 Platform

See also: All Release Notes Release calendar

April Release (18 Apr 2016)

External Document Storage

If the enterprise has an external Content Management System (CMS), the platform can use it for Document Storage for File Fields and Image Fields of AgileApps Live.

Learn more: External Document Storage

Site User Creation Through SSO

Site User creation through SSO. SSO feature has been enhanced to create Site Users through SSO feature through SAML.

Learn more: SAML

Bug Fixes

• LJP-1193

Problem Summary: Object id was shown instead of Object title on merge lookup for DCM application.

Detailed Description: Object id was shown Instead of Object title for the title of case lookup popup window, when user clicks on magnify glass to select merged to record for DCM Application

Resolution Statement: This has been corrected and now object title is shown instead of object id in place of title of popup window

• LJP-1164

Problem Summary: Javascript error is seen when user tries to execute update action on record, if object title contains single quotes characters..

Detailed Description: Clicking on Choose Field button on Update Record Action was showing javascript error if Object title contains single quotes characters.

Resolution Statement: Escape single quotes character property now this issue has been fixed.

• LJP-1149

Problem Summary: Column widths to be customizable.

Detailed Description: This issue is related to Related information table in object record. Related information table column text was not expanded to available width.

Resolution Statement: This has been fixed now.

• LJP-1126

Problem Summary: AKA-Process can not advance due to field verification / error message: please enter an agenda.

Detailed Description: This issue occur when user make richtext area field required by using layout rules.

Resolution Statement: This has been fixed now.

• LJP-1074

Problem Summary: Security Answer was accessible in browser console.

Detailed Description: Security Answer was accessible as plain text from userData in the browser console.

Resolution Statement: This has been fixed by not having security answer in userData.

• LJP-1071

Problem Summary: [AccessibilityMode] Rendering of controls changes after action, making them unusable

Detailed Description: This is an issue in accessibility mode on.In Accessibility mode select list is not showing as traditional select element after submitting a comment

Resolution Statement: This has been fixed now.

• LJP-1070

Problem Summary: [AccessibilityMode] Table column header "Action" is output as "link", even though it does not perform any (useful) function.

Detailed Description: The "Action" header is output as a "Link", but that link does not perform any useful action, whereas the other column headers are having the "Sort" feature.

Resolution Statement: This issue is now fixed.

• LJP-1066

Problem Summary: [AccessibilityMode] In Accessibility mode For the notifications button, the screen reader does not output the number of notifications.

Detailed Description: The screen reader does not read the number of notifications present on the top right of the page.

Resolution Statement: This issue is now fixed.

• LJP-1063

Problem Summary: [AccessibilityMode] "X" button will read, "unpin this record button" although it closes the form.

Detailed Description: The value of title attribute and aria-label of button not was not correct.

Resolution Statement: This issue is now fixed.

• LJP-1062

Problem Summary: [AccessibilityMode] View link with repetitive screen reader output.

Detailed Description: In the list of records, the View button reads, "e.g. View link view record details A 1,500,052". Should not repeat the word "view".

Resolution Statement: This issue is now fixed. It will read it as "view record details {record-name} Link".

• LJP-1059

Problem Summary: [AccessibilityMode] Screen reader sometimes reads label of other element.

Detailed Description: While navigating through the widget's toolbar items in dashboard, the screen reader will sometimes output the label of the previous element rather than the one with the focus. The same issue occurs for edit buttons for form fields as well.

Resolution Statement: This issue is now fixed.

• LJP-1058

Problem Summary: [AccessibilityMode] "Add file" dialog reads "close" even though there is no button.

Detailed Description: The unnecessary 'close' text has to be removed. The screen reader out puts the 'close' text. When the user tries to navigate using arrow keys, this 'invisible' element gets read. The screen reader will say that there is a Close item even though the dialog does not show such a button.

Resolution Statement: This issue is now fixed and the 'close' text has been removed from this dialogue.

• LJP-1055

Problem Summary: [AccessibilityMode] Navigation not possible when there are no KB topics

Detailed Description: This issue occur when there is no topic in Articles.

Resolution Statement: This has been fixed now. "No record present" alert message is show in accessibility mode on.

• LJP-1045

Problem Summary: Web service was not working when Content-Type or Accept had dot (.)

Detailed Description: When web service Content-Type or Accept had dot(.) (eg., application/vnd.com.nsn.cumulocity.operation+json) as hard-coded values, exception was seen.

Resolution Statement: This has been fixed now.

• LJP-1035

Problem Summary: Without entering any data in pop up and saving it, shows no error message.

Detailed Description: When user add a case while adding a case, if a new account record is added without providing required fields, form was not showing the error message.

Resolution Statement: This has been fixed now.

• LJP-1027

Problem Summary: Dashboard/Widget-- while adding more than one widget to a dashboard, it is adding only the last widget added and the previous ones were not getting added

Detailed Description: This issue is because widget counter is not incrementing correctly.

Resolution Statement: This has been fixed now.

• LJP-1026

Problem Summary: Error messages from Messages bundle was displaying internal field name.

Detailed Description: Error messages from Messages bundle was displaying internal filed name. So the translated label from Translation Workbench was not shown in the message.

Resolution Statement: This has been fixed and it will display the fields Display label, not the internal field name. Now the translated label from the translation workbench is getting displayed in the messages.

• LJP-1018

Problem Summary: Session Timeout Window height issue with Non-English languages users.

Detailed Description: Continue and Logout button were not getting displayed properly in Non-English languages user's due to height issue of Session Timeout Window.

Resolution Statement: This issue has been fixed by setting Session Timeout Window height to 'auto'.

• LJP-1014

Problem Summary: Record filtering was not working in case of subforms.

Detailed Description: In Record filtering , even though we specified the filtering criterion for a lookup in subform, still that lookup used to display wrong values and not the ones which it should have filtered.

Resolution Statement: This issue is now resolved and records are getting filtered properly.

• LJP-973

Problem Summary: In form text-area re-sizing should be fixed horizontally.

Detailed Description: The horizontal re-sizing feature for the text-area distorts the form layout.

Resolution Statement: This issue is now fixed. The vertical re-sizing feature is retained as it is.

• LJP-969

Problem Summary: Case view id+priority column not presentable.

Detailed Description: This issue occurs when text length of Case id and Priority column is more than available cell width then the value of Priority is pushed to the second line and since cell background is in white color the value of Priority is not easily readable.

Resolution Statement: This has been fixed.Now we show trailing … when the values go long; and when somebody hovers over it- show the entire long text.

• LJP-966

Problem Summary: Getting response as success while deleting some of the objects, but the objects its not deleted.

Detailed Description: When user tried deleting system /standard objects through rest API , the response was giving a success message but internally it was not getting deleted.

Resolution Statement: System/Standard objects can't be deleted and so now response shows proper error message.

• LJP-964

Problem Summary: Unable to update the records using bulk update.

Detailed Description: While trying to update records in bulk of an object through bulk update rest API, exception was being thrown as a response saying "Record Id can't be null".

Resolution Statement: This is issue has been fixed and it is working fine as expected.

• LJP-957

Problem Summary: Lookup Copy data does not work for rich-text fields.

Detailed Description: This issue is because rich text editor was not refreshed after setting the value.

Resolution Statement: This has been fixed.Now rich text editor is refreshed after setting the value.

• LJP-941

Problem Summary: Reports using column grouping are not working in Longjump - Urgent

Detailed Description: This issue occurs when row/column Group contains null or blank value. In this case the product name was blank.

Resolution Statement: This has been fixed .Now blank value will be displayed as "Unspecified" in English language.

• LJP-889

Problem Summary: Exception seen when using Web Services

Detailed Description: When the Web service response had JSONArray, exception were seen.

Resolution Statement: This has been fixed.

March Release (15 Mar2016)

Bug Fixes

• LJP-1074

Problem Summary: Security Answer was accessible in browser console.

Detailed Description: Security Answer was accessible as plain text from userData in the browser console.

Resolution Statement: This has been fixed by not having security answer in userData.

• LJP-957

Problem Summary: Lookup Copy data does not work for rich-text fields.

Detailed Description: This issue is because rich text editor was not refreshed after setting the value.

Resolution Statement: This has been fixed. Now rich text editor is refreshed after setting the value.

• LJP-1018

Problem Summary: Session Timeout Window height issue with Non-English languages users.

Detailed Description: Continue and Logout button were not getting displayed properly in Non-English languages users due to height issue of Session Timeout Window.

Resolution Statement: This issue has been fixed by setting Session Timeout Window height to 'auto' .

• LJP-745

Problem Summary: Formatting is not maintained in the Activity email.

Detailed Description: This issue is because no style definition was sent with the html email content.

Resolution Statement: This has been fixed. Now style definition is send with the html email content.

• LJP-972

Problem Summary: Layout rule interfering with tab navigation

Detailed Description: Tab navigation not working when Layout Rule hides a section.

Resolution Statement: This is fixed Now.

• LJP-975

Problem Summary: Unable to add a sandbox.

Detailed Description: After Record Level Visibility tenant capability is enabled, Admin user is not able to add a sandbox. This is because the global Record Level Visibility access profile was not enabled.

Resolution Statement: Wrote a database patch to enable global Record Level Visibility by default for Admin profiles.

• LJP-943

Problem Summary: User cannot navigate to/from all input fields in a form.

Detailed Description: If keyboard users navigate to the "X" button on the "Sign in" Popup they cannot leave the popup using either the tab key or "shift + tab". Blind and motoric impaired users can thus not fill out all fields and not complete the form.

Resolution Statement: This issue is now fixed. Removed the "X" button as the dialogue already has a cancel button. Tab focus has been restricted within the dialog's form controls itself, to prevent users from accidental tabbing elements out side the dialogue and unable to tab back to the dialogue controls.

• LJP-974

Problem Summary: Cannot select value from Multi Pick list.

Detailed Description: This issue is because of focus was not set on current Multi Pick list when use click on the multi pick list field.

Resolution Statement: This has been fixed. Now focus is set on the Multi Pick list field when user clicks on Multi Pick list field.

• LJP-891

Problem Summary: Accessibility issues with menu items in the drop-down list.

Detailed Description: Then menu items in the header section is not easily recognized or understood by the accessibility mode user. The combo box based menu items do not have a default value present. Identifying the currently active role is difficult for the user.

Resolution Statement: This issue is now fixed.

• LJP-939

Problem Summary: Radio button options are read multiple times.

Detailed Description: While traversing through the radio button options, the option text was getting read multiple times.

Resolution Statement: This issue is now fixed. Minor performance improvements for radio button is also made.

• LJP-928

Problem Summary: Translated labels in case of Reports were not showing up.

Detailed Description: When in Translation Workbench for a particular language, we update translated labels for Reports ,the user wasn't able to see that change reflected in Reports tab. It was still showing default labels.

Resolution Statement: This issue has been fixed and now user can see the updated labels in Reports tab.

• LJP-937

Problem Summary: Date format is different in related information table.

Detailed Description: This was a bug. The date format should be same when you view related information table before adding a record and after adding a record.

Resolution Statement: This has been fixed and now the date format is same in both the cases.

• LJP-947

Problem Summary: Hiding the first section in a form using layout rule, does not hide the details of first section.

Detailed Description: This was a bug. When executing layout rule related to hide section then only section tab. It should hide the section details also with section tab.

Resolution Statement: This has been fixed. Now section details is also hiding with the section tab.

• LJP-948

Problem Summary: Layout Rule: On applying rule, focus stays on one field only.

Detailed Description: When a layout rule is applied on any field item, the tab navigation of fields are not working well. When the user tries to navigate away (using tab key) from a 'layout rule applied field', the focus is automatically assigned back to the first field item in the section. It happens only when there're multiple sections available in the form. This prevents the users from navigating to other field items in the form, using tab key.

Resolution Statement: This issue is now fixed.

• LJP-927

Problem Summary: Many To Many record access URL is not working.

Detailed Description: User is not able to see the details of selected record, when he/she clicks on the selected record, in Multi Value Lookup field. This is supported in LongJump but was not working in AgileApps Application.

Resolution Statement: This has been fixed. Now user can see the detail of selected record by clicking on it.

• LJP-866

Problem Summary: Accessibility- Several links will not be issued & A few "X" button will be issued with the label "time".

Detailed Description: There are two accessibility issues. 'A few "X" button will be issued with the label "time" ' and 'the application mode not activated automatically on "Team" dialogue popup'.

Resolution Statement: These two issues are now fixed. Now, the navigation between the popup contents (Team tree and the close (x) button) can be done using the 'tab key' and using the 'Arrow Keys' the user can interact with the currently focused element. The 'application mode' is activated automatically on the 'team tree popup'.

• LJP-846

Problem Summary: Owner Lookup Reference Fields are visible on the form but do not show any values.

Detailed Description: When additional field related to owner lookup, which is a standard field in case object is placed in the form then its value is not populated because we are not allowing the users to add the owner lookup on the form .

Resolution Statement: This has been fixed. Now owner field can be placed in the form so that value of additional Lookup Reference Fields can be shown.

• LJP-906

Problem Summary: Page styling issues

Detailed Description: This issue is because of incorrect css class is set for the element when the first tab is the community tab.

Resolution Statement: This has been fixed. Now the correct css class set for the element when the first tab is the community tab.

• LJP-907

Problem Summary: Accessibility Mode: Multi check box hint is being read twice.

Detailed Description: While focusing on the field hint, the hint text is getting read multiple times. This issue is happening for both multi check-boxes and radio buttons. It should be read only once.

Resolution Statement: This issue is now fixed for both multi checkboxes and radio buttons.

• LJP-897

Problem Summary: Accessibility Mode: Hint in Reports page is not read by JAWS.

Detailed Description: No hint texts displayed in the "New Report" section are read by the JAWS. There are inconsistencies on the hint text displayed on each of the hints.

Resolution Statement: This issue is now resolved; the hint text links have been replaced with the ? icon. The jaws can now read the hint text.

• LJP-899

Problem Summary: UI Defect; Developer Resources: Tool tip hidden behind script editor.

Detailed Description: The tool tip displayed on the "Developer Resources » Pages » new/edit Page" is not completely visible. It displayed behind the script editor.

Resolution Statement: This issue is now resolved.

• LJP-909

Problem Summary: SSO page: Upload certificate pop up is not aligned properly.

Detailed Description: The uploaded certificate details are displayed in a popup. But the popup's alignment is not proper and hence resulting in vertical and horizontal scrollbars.

Resolution Statement: This issue is now fixed.

February Release (15 Feb2016)

Site User Creation Via SSO

Site user can also be created through SSO over SAML.

Learn more: SAML#SAML

Bug Fixes

• LJP-914

Problem Summary: On complete/approve of certain tasks, sometimes error message indicating lack of viewing permission was being shown to the user.

Detailed Description: This used to happen because on completing/approving the task, an underlying process changed the ownership of the task.

Resolution Statement: This has been fixed and now UI consumes the exception and takes the user to record-list view of the previously visited object / tab.

• LJP-902

Problem Summary: When site user submit a case form he cannot see what value he has submitted.

Detailed Description: This is because the detail form is hidden for site user.

Resolution Statement: This has been fixed and .we started to show the record detail form to site user after submitting a case form, so that he can see the submitted value.

• LJP-893

Problem Summary: : Fields disappear when the package is exported and then the resulant exported package is imported.

Detailed Description: If field(s) present in Form layout are used in Subform then fields are disappear after export and import.

Resolution Statement: This has been fixed.

• LJP-888

Problem Summary: Deleting Application Access using java api deleteRecord() is not working for the customer.

Detailed Description: Customer added a platform class with a method to delete application access using javaAPI deleteRecord(). Calling this method from one of the objects events business rule. When the customer is doing that action, it is giving the success result but the application access was not deleted. The api used was Functions.deleteRecord("application_access", recordId);

Resolution Statement: Customer was passing only object name and recordId to the api. For application access app_id and referenceId are also needed as params. The correct one is Functions.deleteRecord("application_access", recordId, params);

• LJP-876

Problem Summary: Important information imperceptible for blind users.

Detailed Description: Multiple issues in accessing the important information for blind users.

Multiple "X" links will be issued with the label "time" or "X"

The access keys are imperceptible

Pop-up contents are not easily perceptible

content of tooltips are imperceptible.

Resolution Statement: All the four issues mentioned are now resolved. Web-services>REST settings screen UI has been improved for better user experience.

• LJP-870

Problem Summary: Clicking on an object view in LongJump mobile UI was throwing error.

Detailed Description: A view with multiple color codes on the same field and with lookup as a sorting field was not working properly in LongJump mobile.

Resolution Statement: This has been fixed.

• LJP-868

Problem Summary: 404 error while trying to load "~/images/pbar-ani.gif".

Detailed Description: The message doesn't harm the functionality of the UI. 404 error needs to be fixed.

Resolution Statement: This issue is now resolved.

• LJP-865

Problem Summary: Two issues were resolved as part of this bug

1. "The buttons are now shown in the HTML layer behind the respective link. The screen readers therefore read the buttons with the proper labeling and proper role. The buttons are read with the addition ""pressed"" by the screen reader. The reason for this is the attribute aria-pressed = "true". The additional output is troublesome for blind users.

2. "The focus on the ""Close"" button, which belongs to the open tab, is barely visible. Motor-impaired users may therefore not recognize the focused button well.

Detailed Description:

1. User was annoyed with Jaws speaks extra speech saying "aria-pressed" when a button is pressed or clciked,it maintains the state of the button whether it is pressed or not.

2.As focus is not available on the buttons,it is difficult for the motoric impaired to recognise the focussed eleemnts.

Resolution Statement:

1. made changes to the elements, so that screen readers don't read the extra parameters as aria-pressed.

2.Focus has been brought to the elements to make the elements to be easily recognisable by the impaired users.

• LJP-862

Problem Summary: Accessibility Hurdles and recommendation implementation.

Detailed Description: In some cases

- Elements cannot be reached or can’t be activated for keyboard users

- Information is presented only with background images

- Titles are not labeled or not labeled correctly, leading to accessibility issues along with other accessibility recommendations.

Resolution Statement: These issues are now resolved.

• LJP-860

Problem Summary: When Auto Number field is placed in the form then it is not appearing in an update form.

Detailed Description: This is due to incorrect implementation.

Resolution Statement: Corrected the implementation to display Auto Number field . Now Auto Number field is appearing in the update form but in 'read-only' mode.

• LJP-858

Problem Summary: On Case Details View Page, Details Section not honoring the last entered user choice.

Detailed Description: Any actions on the page, used to revert to preferences for the 'Hide and View Details', instead of honoring the last entered user choice (user explicitly hiding or viewing details section)

Resolution Statement: The behavior is now corrected to remember the last entered user choice, the change though has been implemented for limited scenarios.

• LJP-857

Problem Summary: NullPointerException in logs.

Detailed Description: Whenever a record is submitted from a webform, there is a reported NullPointerException Exception in the localhost.logs where as the same error is thrown back to UI in CTP.

Resolution Statement: Fixed the NullPointerException.

• LJP-841

Problem Summary: No Error message is appear If rich Text Area field is mandatory and blank value is Submitted.

Detailed Description: This issue is because the value return by the redactor rich text editor was not blank.We are getting html tag "

" instead of blank value.

Resolution Statement: This is fixed by checking the text value instead of html value.

• LJP-838

Problem Summary: Password policy is not getting validated in case of forgot password link.

Detailed Description: This situation occurs when user clicks on the mail link to reset their AAL account password. The screen prompts for entering a new password. That new password gets accepted even though policies set for password in the application isn't met.

Resolution Statement: The issue is now resolved and an error message shows up in case of violations.

• LJP-833

Problem Summary: Data Policy on delete trigger for LongJump Contracts (Standard) object was not working.

Detailed Description: Support for Data Policy on delete for Contracts object was not available.

Resolution Statement: This has been implemented.

• LJP-830

Problem Summary: On deploy of a package into any sandbox tenant with the override flag option, the changes / settings of the Multi-Object-Lookup fields were not reflecting in the Sandbox tenant application.

Detailed Description: On deploying a package into Sandbox Tenant, the override flag was ignored.

Resolution Statement: This has been fixed. Now the override flag is checked / added on package deployment for Sandbox tenants and the changes made to any Multi-Object-Lookup fields will impact in the application after package deployment.

• LJP-826

Problem Summary: Advance Merge option is not coming for some scenarios

Detailed Description: Advance Merge option is shown when user select a case form Case popup window .This works correctly on first page but it does not work when the user selects a record from next page . This is because select record event was not firing in the next page when user clicks on the selected record.

Resolution Statement: This has been fixed .Now select record event is firing in the other pages also.

• LJP-818

Problem Summary: Accessibility Mode- Issue with tabbing in Add Recipient pop up.

Detailed Description: : Interaction with add recipient popup is not friendly for an accessibility mode user. Keyboard navigation for 'added recipients', interaction with the autoSuggest functionality, screen reader issues with the autoSuggestion list, UI getting hung while JAWS (screen reader) tries to read the auto suggestion list etc. makes it difficult for an 'accessibility mode' user to operate the 'Add recipient' popup.

Resolution Statement: This issue is now resolved.

• LJP-813

As the Vertical Reponse is no longer supported in Agile Apps disabled all the functionality related buttons in the jsp like Campain Jsps and Billing pages (where end user has the capability to buy more email credits')

• LJP-807

Problem Summary: Auto complete in Lookup Field does not work with "special characters"

Detailed Description: Lookup Auto complete does not work/show any result when search string contains "special characters".This is because we are not encoding search parameter.

Resolution Statement: This has been fixed .Fixed this by encoding the search parameter.

• LJP-804

Problem Summary: Task delegatee was getting Cast Exception.

Detailed Description: When the record visibility was based on a Checkbox field, the task delegatee was getting Integer Cast exception

Resolution Statement: This has been fixed.

• LJP-798

Problem Summary: Page distortion on rearranging the sequence of application tabs

Detailed Description: This issue because of incorrect css class when user rearranges the application tabs from Personal setting->Application tab and keeps Articles as the first tab and then Cases.

Resolution Statement: This has been fixed. Fixed this by adding correct css class.

• LJP-797

Problem Summary: When user used to edit any RICH_TEXT_AREA field, the user wasn't warned with a Navigation Popup message to save / leave the changes.

Detailed Description: On change of any RICH_TEXT_AREA field, the dirty-flag was not updated as we have integrated Redactor plugin and which (the implemented version) doesn't have options / events to capture the changes for such fields.

Resolution Statement: This has now been fixed by binding additional events to the RICH_TEXT_AREA fields which will capture any change in the field & make the dirty-flag ON. It'll now trigger the navigation-popup message when user tries to navigate out without saving the edited form.

• LJP-796

Problem Summary: Error message should be shown inline after multi check box label and radio label

Detailed Description: Validation error message was not nested in case of the required multi check box, it was appearing for each Multi Check box and Radio button.

Resolution Statement: This has been fixed. Now only one validation message is showing for multi checkbox and radio field, below the field Title.

• LJP-786

Problem Summary: No error message shown in the GUI, if the password policy is not met.

Detailed Description: This situation occurs when the application prompts for a password change forcefully. When user enters a password which doesn't match with the specified password policy, the system freezes without any error message on the screen. But relationals log has the stack trace of the error.

Resolution Statement: This issue is now resolved and a proper error message shows up when password policy is violated.

• LJP-785

Problem Summary: File type labels are not accessible

Detailed Description: Visually challenged users needs to get the whole information of the elements available on the screen, the label of the field type "file" are not read by jaws.

Resolution Statement: Has made the file field label to be read by jaws by focusing on to the element and using aria-labels.

• LJP-780

Problem Summary: The userid was not removed from the cookie when user used to logout through Integration Live.

Detailed Description: Whenever any user logs out from the platform, the cookie details should be flushed out especially when the cookie contains sensitive info like the username or id's. This was not handled properly in the class which is used to handle the login / logout of Integration Live users.

Resolution Statement: As the login request from the client to the server will add cookie if the URL containing "/" and during the logout, it is expected from the server to send set-cookie with the same path to flush out the userId information from browse's cookie. Hence, the same path is added in the logout response.

• LJP-763

Problem Summary: Internationalization Issues

Detailed Description: Some labels were not getting displayed properly in Non-English languages.

Resolution Statement: Have solved it, by including the corresponding texts in the language bundles.

• LJP-738

Problem Summary: There is a java script error related to Zapatec library in browser console when report widget contains both chart and table.

Detailed Description: This issue only occurs when language is other than English.This is because we have not removed the Zapatec library reference for other languages

Resolution Statement: This has been fixed .We are not using Zapatec library for showing calendar in a form. We are using Jquery calendar so we have removed all the reference of Zapatec calendar library from our code

• LJP-734

Problem Summary: Clicking on new Document Template button was throwing Service Encountered error.

Detailed Description: Creation of Document Template by a user with German language was not working properly.

Resolution Statement: This issue is resolved.

• LJP-711

Problem Summary: Field name (column header) should not scroll while traversing to last record of resultset.

Detailed Description: User has to use two vertical scollbar ( Browser as well as SQL Browser ) to see the last record of resultset which is insufficient because user cannot see the column header.This is because of SQL browser container height is more than browser height.

Resolution Statement: This has been fixed. Now there is only one vertical scrollbar so the Column header will not scroll while traversing to last record in resultset.

• LJP-690

Problem Summary: In case of Multi-Checkbox fields, when user used to click on the labels the values were not saving properly on form Save.

Detailed Description: When the form had more than one multi-checkbox fields, the changes were not saved on check / uncheck by clicking on their associated labels as there was some problem in event-binding on the field's label.

Resolution Statement: The event bindings is corrected in JavaScript and now the value saving issue is fixed for multi-checkbox fields.

• LJP-659

Problem Summary: Automatic text inserted in Email Templates not showing up as per user's language.

Detailed Description: This situation occurs when a mail is received in case any event gets triggered, e.g : Creation of a task/case etc. We can create a business rule as well to trigger such actions(sending mails, etc.). The issue is when user receives any such mail , a default text gets automatically inserted at the starting of the content. This text always shows up in English irrespective of user's language. This creates a difficulty in case of foreign languages.

Resolution Statement: This issue has been resolved and the automatically inserted text appears as per user's language.

• LJP-631

Problem Summary: File links on the Dashboard widget fail to download / open file.

Detailed Description: This situation occurs when user has created a widget of 'Report' type on the application dashboard and the report contains file field. Clicking that link opens another tab/window with 'Http status 401 -Invalid Access' message.

Resolution Statement: This issue is now resolved and the file downloads successfully.

• LJP-538

Problem Summary: Response should contain child case type id in case list rather than root case type id.

Detailed Description: In case of child case type in case list, API is returning root case type id instead of child case type id. Because of this, services related to case record like get processes or tasks for a case record not working as expected.

Resolution Statement: It has been fixed.

October Release (15 Oct 2015)

Record Level Visibility

Visibility criteria can be specified on individual records, making the records visible only to a select audience. Visibility can be restricted to individuals, teams, roles, or to users who have a specified setting in a custom field. Multiple values can be specified for each record. Only users who match one of those values can see the record.

Learn more: Record Level Visibility

Integration with MS Azure

Microsoft Azure Active Directory can be used to supply user credentials, providing users with "single sign-on" capability.

Learn more: SAML#SAML Settings for MS Azure

Trust Site

How well is the AgileApps Cloud platform public cloud performing? Find out at the Trust Site! See uptime history, current status, and schedule of upcoming maintenance activities.

Learn more: Trust Site

Email Events

Incoming emails related to a Case can trigger email-event rules, allowing actions to be taken based on the content of the email fields, or simply on the presence of the message.

Learn more: Event Rules

JavaScript Functions to Hide Action-Menu Items and Assignment Buttons

Use these functions to hide items in the action menu, as well as the claim-record and assign-record buttons.

Learn more: JavaScript Functions#Hiding Action Items and Assignment Buttons

Bug Fixes

• LJP-459 Information that was available only in background images was made available to the visually impaired
• LJP-460 Improve section headings and page headings, pop-up captions and titles for accessibility
• LJP-461 Correct problems with UI-focus related to popups and input fields for keyboard users
• LJP-466 Warn the user to save changes when a macro has made changes in a Form
• LJP-470 Improve contrast ratios in UI
• LJP-471 Maintain readability when browser font size is increased
• LJP-481 Calendar/Report Date Filter was using U.S. locale instead of user locale
• LJP-529 Not possible to put an upper case "Q" in an email, in some browsers
• LJP-537 Layout Rules - Could not assign an empty string () to a Multiple Checkbox field
• LJP-548 Description was appearing before Report Name in a list of reports
• LJP-576 Lookup filter was working differently in a related information section, vs. a subform
• LJP-578 A field marked "Always Required" should required by default in a record Form
• LJP-592 Not possible to put capital Q in a record Note, as shift+Q quits the editor
• LJP-606 Active links in the print browser preview window were going to the old UI
• LJP-614 Thousands-separator in some countries caused Charts to fail in a report
• LJP-616 Navigation-confirmation dialog was appearing at inappropriate times
• LJP-621 Sidebar was not refreshing properly when navigating via JavaScript
• LJP-627 Lookup to a Child object was incorrectly opening to Parent object form
• LJP-629 Process was failing when creating a new request-record
• LJP-631 Dashboard widget had the wrong link to report document
• LJP-634 Picklist field was not showing the cursor focus
• LJP-645 Tab-redirection was not working properly for a button added to a Form
• LJP-661 Word-in-progress indicator was needed when a complex rule set is running after task completion
• LJP-666 A disabled checkbox was still editable
• LJP-676 Completed task was not removed from task list