Difference between revisions of "Version 10.1 Platform"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
Line 30: | Line 30: | ||
==== Deprecation of JSP-based Documentation Templates==== | ==== Deprecation of JSP-based Documentation Templates==== | ||
:JSP pages can no longer be used as the basis for a [[Document Template]], due to limitations on the number of contexts in which they work. Existing document templates that employ a JSP page can still be used and modified, but new document templates that use a JSP page can no longer be created. | :JSP pages can no longer be used as the basis for a [[Document Template]], due to limitations on the number of contexts in which they work. Existing document templates that employ a JSP page can still be used and modified, but new document templates that use a JSP page can no longer be created. | ||
:For background information and alternatives, see the deprecation note | :For background information and alternatives, see the deprecation note here: [[Create a JSP Page Document Template]]. | ||
==== New in the Docs ==== | ==== New in the Docs ==== |
Revision as of 02:35, 20 March 2014
See also:
- Version 10.0 Platform (previous releases)
- All Release Notes
Coming Next
Invoke a Web Service Directly from a Rule
- For a simple data fetch, it is possible to invoke a Web Service directly, without having to wrap it in a Process. Processes continue to provide power and flexibility, while direct invocation from a Rule adds convenience.
Web Services Enhancements
- Outputs from one web service can be designated as inputs to another service.
Process Enhancements
- ...
Only Configured Tabs Appear in Service Portal
- Previously, giving portal users the ability to add related records to a case had the unintended side effect of causing a tab to appear for the related object, allowing the portal users to see and add unrelated records. Now, portal users see only the tabs configured for the Service Portal. Additional tabs no longer appear.
Deprecation of JSP-based Documentation Templates
- JSP pages can no longer be used as the basis for a Document Template, due to limitations on the number of contexts in which they work. Existing document templates that employ a JSP page can still be used and modified, but new document templates that use a JSP page can no longer be created.
- For background information and alternatives, see the deprecation note here: Create a JSP Page Document Template.
New in the Docs
- AJAX and REST#Using AJAX in a Form - Use jQuery's .ajax function to access a REST API
- Form Scripts#On Load Examples - Two ways to add a button to a form
- Java Code Samples#Invoke Web Services Programmatically - Invoke external Web Services from Java code
- Building a Dynamic Case Management Application in the AgileApps Cloud (pdf) has been updated to:
- Take advantage of the ability to specify object labels and field labels when creating an app.
- Show how to customize the application banner and logo.
- Improve form layout.
- Correct templates to use revised variable names.
- Reflect changes in the way processes and process tasks are defined.
- Deprecation Index - Occasionally, platform features need to be removed. When they are, a note is added to the release notes. This page collects those references for historical use.
1 Mar 2014
New Application Preferences
- New preference-settings are available to determine how records are displayed, by default:
- Expand or hide record details
- Show absolute dates and times or relative durations
- Specify which activities are be shown in the record history
- Learn more:
Email Signatures
- Set up an email signature that will be attached to messages you send.
- Learn more: My Information#Email Signature
Editable Subforms
- Editable Subforms let users enter and edit detail records while they are viewing a master record. Long available for Web Forms that are displayed on an external web page, they are now available for forms displayed in the platform, as well.
- Learn more:
External Lookups and External Data Sources
- An External Lookup field lets a designer access a Web Service to select a record from an external source, such as a database that is maintained elsewhere on the web. Fields from the external record can then be displayed as part of the object record in the platform.
- An External Data Source lets a designer access a collection of related records from such data.
- Learn more:
Fault Handling for Web Services
- Web Service error conditions are recognized as outputs. They can be stored in Process Variables, and then used to change the flow of control in a Process Model.
- Learn more:
24-hour Window to Reset Forgotten Password
- The link a user receives to reset their password is now good for 24 hours, rather than for all time.
New in the Docs
- Setting up Your Account (for when you're just getting started)
- HowTo:Create Cases from Mobile Devices
- HowTo:Send Messages to Multiple Recipients
- Working with Tasks#Working with Process Tasks (new section)
- ServiceDesk application#About ServiceDesk (new section)
- Case Analytics (the statistics-gathering feature of ServiceDesk)
- Application Testing
- Java Debugging Tips Use a macro or rule. Use a JSP page.(new sections for developers)
- Creating Dynamic Case Management Apps (a new index page for PDF articles)
- Building a Dynamic Case Management Application in the AgileApps Cloud (pdf) updated:
- "Introduction to DCM" extracted to a separate article.
- "Choosing your development approach" extracted to a separate article.
17 Jan 2014
LDAP Integration
- LDAP integration allows admins to manage enterprise users in a single location. On-premise installations will want to take advantage of this feature to automatically recognize LDAP entries as platform users, allowing the users to log in with their normal credentials, while automatic synchronization with the LDAP server keeps the platform up to date.
- Learn more: LDAP Configuration
Language Packs
- The platform interface can be presented in a variety of different languages, including French, Italian, German, and Spanish, as well as English. The choices available to users are determined by your Company Settings.
- Learn more: Company Information#Available Language Settings
Specify Catalog Description and Icon when Publishing a Package
- The icon and description that appear in the catalog can be specified when the package is published.
- Learn more: Packages#Publish a Package
Post-Selection Javascript for Lookup fields
- Javascript code can be executed after a Lookup target has been selected.
- Learn more: Post Selection JavaScript
REST API Enhancements
- When uploading a file using the REST API, the isBase64Encodedquery parameter can be used to specify that the file contains encoded binary data.
- Use the appId query parameter to restrict a list of returned objects to those that are part of a specific application.
- Learn more: REST API:object Resource##Retrieve all Objects
- When returning data for an enumerated field, the REST API:record Resource returns the field label in addition to the field value, using the XML attribute, displayValue.