Difference between revisions of "Version 10.1 Platform"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
(90 intermediate revisions by the same user not shown) | |||
Line 8: | Line 8: | ||
| | | | ||
'''''See also:''''' | '''''See also:''''' | ||
* [[All Release Notes]] | * [[All Release Notes]] | ||
* [[Release calendar]] | |||
|} | |} | ||
__TOC__ | __TOC__ | ||
<!-- | <!-- | ||
===New Features=== | |||
<blockquote> | |||
==== Feature ==== | |||
: description | |||
: ''Learn more:'' [[TBD]] | |||
</blockquote> | |||
--> | |||
=== 15 Apr 2014=== | |||
<blockquote> | |||
==== Search Option for Web Service Records ==== | |||
: A web service can return multiple records, and users can interactively choose which record to reference. | |||
: ''Learn more:'' [[External Lookups]] | |||
</blockquote> | |||
=== | ===29 Mar 2014=== | ||
<blockquote> | <blockquote> | ||
==== | ==== Fault Handling for Processes and Web Services ==== | ||
: | :* Error-response data structure can be defined for REST-based web services. | ||
:''Learn more:'' [[link]] | :: ''Learn more:'' [[Web Services Integration#Setting Up a REST Web Service]] | ||
:* Exception events (also known as "boundary events" can be managed in [[Processes]]. | |||
:: ''Learn more:'' [[Process Models#Exception Event]] | |||
:* Errors and exceptions that occur during an [[External Lookup]] or when accessing an [[External Data Source]] are displayed to the user. | |||
==== Web Service Chaining==== | |||
:A two-step service chain can be configured, allowing outputs from the first to be used as inputs for the second. Such a configuration is desirable, for example, when an initial login is required to obtain a valid session ID for subsequent requests, or when some other access key must be obtained in order to make requests. | |||
:With this enhancement, process modelers are no longer required to configure two web services in their processes (although it is still possible to do that). Instead, the chained services can be accessed as a single service. In addition, this enhancement makes it possible to use such services for an [[External Lookup]] or an [[External Data Source]]. | |||
:''Learn more:'' [[Web Services#Configuring a Two-Step Service Chain]] | |||
====Service Portal Enhancements==== | |||
:With these enhancements, the externally-accessible [[Service Portal]] becomes even more flexible: | |||
::* '''Case Submissions tab -''' The Cases tab can be enabled independently, allowing portal users to create and view cases without requiring the organization to host a community or provide a knowledge base, in order to do so. | |||
::* '''Case Forms -''' Designers can specify which Case form is used by registered portal users, and which one is used by guests (or none). | |||
::* '''Case Types -''' When specialized [[Case Types]] are defined, customers can create cases for them, as well, and designers can specify which form to use. | |||
:''Learn more:'' [[Service Portal#Service Portal Settings]] | |||
====Compliance Bcc's for Outgoing Messages==== | |||
:Outgoing messages can be copied to an external archive for storage and compliance monitoring. | |||
:''Learn more:'' [[Company Information#Email Settings]] | |||
====Display Details of a Multi Step Task==== | |||
:When a process is listed in the sidebar, clicking on it pops up a picture of the process model. That feature now works for manually-created Multi Step Tasks, as well. | |||
:''Learn more:'' [[Multi Step Tasks#Displaying a Multi Step Task]] | |||
====Direct Access to Contact Records using Phone Numbers==== | |||
: An external phone system can be integrated with the platform by using a phone number to link to a Contact record. | |||
:''Learn more:'' [[URL Addresses#Accessing Contacts using Phone Numbers]] | |||
====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. | |||
====Mass Ownership Change for Teams==== | |||
:When assigning a new owner for a large block of records, a Team can be specified as the new owner, or (as before) an individual. | |||
:''Learn more:'' [[Mass Ownership Change]] | |||
==== Additional Labels in Translation Workbench ==== | |||
:The lengthy list of labels and UI text that can be translated using the [[Translation Workbench]] has been extended to include field help text, help text defined for fields in form layouts, and multi value lookup labels. | |||
==== | ==== Additional Notification Comments for Scheduled Reports==== | ||
: | :When setting up [[Report Schedules]], it is now possible to add a comment that will be included in the notification message that goes out when the scheduled reports are ready. | ||
==== | ==== 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]] | ||
==== | ==== API Enhancements ==== | ||
: | :* Additional options are available in the [[Java API:Email]], <tt>sendEmail</tt> and <tt>sendEmailUsingTemplate</tt> | ||
:* The REST [[REST API:companyInfo Resource|companyInfo]] resource has a new parameter: <tt>compliance_bcc_email</tt> | |||
:* In the REST [[REST API:Dynamic Search|Dynamic Search]] APIs, the <tt>getTotalRecordCount</tt> query parameter tells how many records there are in total, in addition to the number returned in the current batch. | |||
==== New in the Docs ==== | ==== New in the Docs ==== | ||
:* [[ | :* [[AJAX and REST#Using AJAX in a Form]] - Use jQuery's <tt>.ajax</tt> function to access a REST API | ||
:* {{^Article Build a DCM App}} has been updated to ... | :* [[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 | |||
:* [[Java Code Samples#Batch Update of Related Record Owners]] - Change owner for a collection of records | |||
:* [[URL Addresses]] - Collects the URL-patterns that can be used to access the platform | |||
:* {{^Article Build a DCM App}} 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. | |||
:* [[Using the Agent Portal#Record Form Sidebar]] - Added section for new users shows how the sidebar works. | |||
:* [[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. | |||
</blockquote> | </blockquote> | ||
Line 47: | Line 106: | ||
<blockquote> | <blockquote> | ||
==== New Application Preferences ==== | ==== New Application Preferences ==== | ||
:New preference-settings are available | :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:'' | :''Learn more:'' | ||
::* [[Company Information#Application Settings]] | ::* [[Company Information#Application Settings]] | ||
::* [[ | ::* [[Preferences]] | ||
====Email Signatures==== | ====Email Signatures==== | ||
Line 74: | Line 136: | ||
::* [[Web Services Integration]] | ::* [[Web Services Integration]] | ||
::* [[Process Models]] | ::* [[Process Models]] | ||
==== 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 ==== | ==== New in the Docs ==== | ||
Line 125: | Line 190: | ||
<noinclude> | <noinclude> | ||
[[Category:Release Notes]] | [[Category:Platform Release Notes]] | ||
</noinclude> | </noinclude> |
Latest revision as of 05:52, 28 February 2017
See also:
15 Apr 2014
Search Option for Web Service Records
- A web service can return multiple records, and users can interactively choose which record to reference.
- Learn more: External Lookups
29 Mar 2014
Fault Handling for Processes and Web Services
- Error-response data structure can be defined for REST-based web services.
- Exception events (also known as "boundary events" can be managed in Processes.
- Learn more: Process Models#Exception Event
- Errors and exceptions that occur during an External Lookup or when accessing an External Data Source are displayed to the user.
Web Service Chaining
- A two-step service chain can be configured, allowing outputs from the first to be used as inputs for the second. Such a configuration is desirable, for example, when an initial login is required to obtain a valid session ID for subsequent requests, or when some other access key must be obtained in order to make requests.
- With this enhancement, process modelers are no longer required to configure two web services in their processes (although it is still possible to do that). Instead, the chained services can be accessed as a single service. In addition, this enhancement makes it possible to use such services for an External Lookup or an External Data Source.
- Learn more: Web Services#Configuring a Two-Step Service Chain
Service Portal Enhancements
- With these enhancements, the externally-accessible Service Portal becomes even more flexible:
- Case Submissions tab - The Cases tab can be enabled independently, allowing portal users to create and view cases without requiring the organization to host a community or provide a knowledge base, in order to do so.
- Case Forms - Designers can specify which Case form is used by registered portal users, and which one is used by guests (or none).
- Case Types - When specialized Case Types are defined, customers can create cases for them, as well, and designers can specify which form to use.
- Learn more: Service Portal#Service Portal Settings
Compliance Bcc's for Outgoing Messages
- Outgoing messages can be copied to an external archive for storage and compliance monitoring.
- Learn more: Company Information#Email Settings
Display Details of a Multi Step Task
- When a process is listed in the sidebar, clicking on it pops up a picture of the process model. That feature now works for manually-created Multi Step Tasks, as well.
- Learn more: Multi Step Tasks#Displaying a Multi Step Task
Direct Access to Contact Records using Phone Numbers
- An external phone system can be integrated with the platform by using a phone number to link to a Contact record.
- Learn more: URL Addresses#Accessing Contacts using Phone Numbers
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.
Mass Ownership Change for Teams
- When assigning a new owner for a large block of records, a Team can be specified as the new owner, or (as before) an individual.
- Learn more: Mass Ownership Change
Additional Labels in Translation Workbench
- The lengthy list of labels and UI text that can be translated using the Translation Workbench has been extended to include field help text, help text defined for fields in form layouts, and multi value lookup labels.
Additional Notification Comments for Scheduled Reports
- When setting up Report Schedules, it is now possible to add a comment that will be included in the notification message that goes out when the scheduled reports are ready.
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
API Enhancements
- Additional options are available in the Java API:Email, sendEmail and sendEmailUsingTemplate
- The REST companyInfo resource has a new parameter: compliance_bcc_email
- In the REST Dynamic Search APIs, the getTotalRecordCount query parameter tells how many records there are in total, in addition to the number returned in the current batch.
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
- Java Code Samples#Batch Update of Related Record Owners - Change owner for a collection of records
- URL Addresses - Collects the URL-patterns that can be used to access the platform
- 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.
- Using the Agent Portal#Record Form Sidebar - Added section for new users shows how the sidebar works.
- 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.