Difference between revisions of "Version 10.1 Platform"

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


==== Fault Handling for Processes and Web Services ====
==== Fault Handling for Processes and Web Services ====
:--Error-response data structure can be defined for REST-based [[Web Services]]
:* Error-response data structure can be defined for REST-based web services.
:: ''Learn more:'' [[Web Services Integration#Setting Up a REST Web Service]]
 
:--Exception events (also known as "boundary events" can be managed in [[Processes]]  
:--Exception events (also known as "boundary events" can be managed in [[Processes]]  
:--Errors and exceptions reported for [[External Lookups]]
 
:Errors and exceptions that occur during an [[External Lookup]] or when accessing an [[External Data Source]] are displayed to the user.


==== Two-Step REST Web Services ====
==== Two-Step REST Web Services ====

Revision as of 00:28, 26 March 2014

See also:

Coming Next

Application-specific Status and Priority Fields

Previously, these fields were defined by Global Picklists, which meant that changes affected all applications. They are now defined as local Picklist field types, so each application can have its own uniquely appropriate set of choices.

Fault Handling for Processes and Web Services

  • Error-response data structure can be defined for REST-based web services.
Learn more: Web Services Integration#Setting Up a REST Web Service
--Exception events (also known as "boundary events" can be managed in Processes
Errors and exceptions that occur during an External Lookup or when accessing an External Data Source are displayed to the user.

Two-Step REST Web Services

  • REST-based web services that require a separate login step are now accommodated.

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 Attachments

A Document Template based on a JSP page cannot be used as an Email Attachment, due to limitations on the number of contexts in which it can be used.
Learn more: JSP Attachment Deprecation

New in the Docs

  • 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

  • "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

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.

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.