Difference between revisions of "Version 10.1 Platform"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 59: Line 59:


==== Fault Handling for Web Services ====
==== Fault Handling for Web Services ====
:Web Service outputs that specify errors conditions can be stored in Process Variables, and then used to change the flow of control in a Process Model.
: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:''  
:''Learn more:''  
::* [[Web Services Integration]]
::* [[Web Services Integration]]

Revision as of 20:24, 26 February 2014

See also:

Coming Next

New Application Preferences

New preference-settings are available: at the company level, at the level of personal preferences, or both. Use them to determine how records are displayed, for now. (Expect additional options in coming months.)
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:

New in the Docs

  • "Introduction to DCM" 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

Notepad.png

Note:
For the AgileApps Cloud platform running in the public cloud, a support request must be filed to enable language choices other than English.

Post-Selection Javascript for Lookup fields

Javascript code can be executed after a Lookup target has been selected.
Learn more: Post Selection JavaScript

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.
Learn more: REST API:record Resource#Multipart Operations for Raw 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.