Difference between revisions of "Version 10.0 Platform"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
(242 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
:{| border="1" align="right" cellpadding="5" cellspacing="1" | |||
| | |||
'''''See also:''''' | |||
* [[All Release Notes]] | |||
* [[Release calendar]] | |||
|} | |||
__TOC__ | __TOC__ | ||
=== | ===20 Dec 2013=== | ||
<blockquote> | |||
==== Enhancements to Web Services ==== | |||
:* Fields in SOAP headers are available for mapping | |||
:* A service that publishes a REST API can be configured, as well as one that uses SOAP | |||
:* Web Services can be added when creating a [[Package]] | |||
:''Learn more: [[Web Services]] | |||
====Accessibility Compliance==== | |||
:AgileApps has basic compliance to accessibility standards like 508, WCAG 2.0, ISO 9241-171, and ISO 9126-1. However, to maintain a generic support for accessibility across NA and EU regions, AgileApps has chosen not to be certified with any of these standards explicitly. | |||
:Any issues experienced by the users are resolved as per the support request raised on https://empower.softwareag.com. | |||
:''Learn more:'' [[Accessibility Mode]] | |||
<!--==== Facebook and Twitter for DCM Apps ==== | |||
:Social channels like [[Facebook]] and [[Twitter]] can be used to create cases in a [[Dynamic Case Management application]], as well as in [[ServiceDesk]].--> | |||
==== Unification of Processes and Process Models ==== | |||
:When creating a new Process, the process model editor is automatically launched. When the model is saved, the Process is created. Thereafter, the Process record contains a link to the model--so the model is intimately tied to the Process. (In the UI, "Process Models" is removed from the sidebar. To modify a model, you start by visiting the Process that wraps it.) | |||
:''Learn more:'' [[Processes]] | |||
</blockquote> | |||
=== 15 Nov 2013 === | |||
<blockquote> | |||
====Mobile Interface is Production-Ready!==== | |||
:The mobile interface has emerged from it's beta period, and has been declared ready for production use. | |||
==== Enhanced Parameter-access for Web Services (beta) ==== | |||
:Web Services are closing in on production status. In this enhancement, the full hierarchy of Web Service parameters is exposed, allowing any data element to be selected. | |||
:''Learn more:'' [[Web Services]] | |||
==== Process Models allow Step Assignments, Case Forms, and Compound Conditions ==== | |||
:Process model enhancements include: | |||
::* Task step assignments can be designated by Role, as well as by Team. | |||
::* Task steps can include a Case form that allows the task worker to see and modify data. | |||
::* Decision switches can test for multiple conditions using and/or logic | |||
:''Learn more:'' [[Process Models#Process Steps and Flow Control]] | |||
==== User Rules can Process Login Events ==== | |||
:Rules can be created that fire when a User logs in. | |||
:''Learn more:'' [[User Rules]] | |||
==== SQL Browser ==== | |||
:Developers can test their SQL statements interactively before adding them to their code. | |||
:''Learn more:'' [[SQL Browser]] | |||
==== Auto Copy Scheduled Reports to Managers ==== | |||
:Automatically deliver copies of scheduled reports to each recipient's manager, or to both their immediate management and second-level management. | |||
:''Learn more:'' [[Report Schedules]] | |||
==== Dates and Times Exported in User Format ==== | |||
:The user's date format and time zone are used when exporting date/time data, allowing backup data exported by a user to be re-imported by the same user, without requiring a data conversion. | |||
:''Learn more:'' [[Export Data#Data Formats]] | |||
</blockquote> | |||
===25 Oct 2013=== | |||
<blockquote> | |||
==== Mobile Enhancement: Geolocation Fields (beta) ==== | |||
:A Geolocation field stores current latitude and longitude at the click of a button. Another button allows the viewer of a record to see the location on a map. | |||
:''Learn more:'' [[Field Display Types]] | |||
==== Scheduled Reports ==== | |||
:Schedule reports for a future date, and run them at regular intervals. | |||
:''Learn more:'' [[Report Schedules]] | |||
==== Drill Down to Underlying Report from Dashboard ==== | |||
:Click to go from a Dashboard widget to the report that created it, then take advantage of [[Quick Filters]] and other filtering options to customize the report. | |||
:''Learn more:'' Dashboard [[Widget Types#Report]], [[Quick Filters]] | |||
==== Localized Time Formats ==== | |||
:Users can select the time format appropriate for their locale, in either 12 or 24 hour format. | |||
:New Java and JavaScript APIs can be used to manage Time and DateTime values. | |||
:''Learn more:'' [[Dates and Times]], [[Java Localization APIs]], [[JavaScript Localization Functions]] | |||
==== Fully Define Cases Object during Application Construction ==== | |||
:When creating a Dynamic Case Management application, both singular and plural labels can be specified for the [[Cases object]]. Additional fields can be also be defined, and the labels of the subject and description field can be changed. (Previously, those modifications could be made only after the application was created.) | |||
:''Learn more:'' [[Application Construction Wizard]] | |||
==== Specify Plural and Singular Object Labels when Creating an Object ==== | |||
:When defining an object (when creating an application or afterward), both singular and plural labels can be specified. (Previously, labels could be modified only after the object was created.) | |||
:''Learn more:'' [[Object Construction Wizard]] | |||
==== More Intuitive Names for Lookup Fields ==== | |||
:When defining an object relationship, the generated field name is now the singular version of the object name. When displayed in a Form, the field is more readily recognized by users. | |||
:For example, when a Lookup field targets the Customers object, the default label is <tt>Customer</tt> and the field name is <tt>customer_record</tt>. (Previously, the field name was <tt>related_to_customers</tt>.) | |||
==== More Readable Object Relationships ==== | |||
:The table that displays object relationships is more clear, making it easier to tell which object is on the "one" side of a One-to-Many relationship, and which is on the "many" side. That change, combined with added Help text, makes it as straight-forward as possible to manage object relationships. | |||
:''Learn more:'' [[Object Relationships#Reading the Relationship Grid]] | |||
====Include Web Forms in an Application Package==== | |||
:When an object is included in a [[Package]], any [[Web Forms]] defined for the object are automatically included. | |||
</blockquote> | |||
===4 Oct 2013=== | |||
<blockquote> | |||
==== Mobile Enhancements (beta) ==== | |||
:Mobile access to the platform has been further enhanced with a newer, localized interface, object tabs, the ability to complete process tasks, and the ability to search for records. To use the mobile interface, visit this URL in your browser or mobile device: <tt>{{mobileURL}}</tt> | |||
:''Learn more:'' [[Mobile Access]] | |||
==== Web Service Enhancements (beta) ==== | |||
The integration of [[Web Services]] into [[Process Models]] comes closer to production status with these enhancements: | |||
:* '''Use Authenticated Services''' | |||
:: Web Services protected by basic username/password authentication can be utilized. (Username and password fields that are set when configuring a Web Service are used automatically.) | |||
:* '''Download WSDLs''' | |||
:: WSDLs can be downloaded from the web, as well as uploaded from the file system. | |||
::''Learn more:'' [[Web Services Integration#Creating a Web Service]] | |||
:* '''Process Model Variables''' | |||
:: Information gathered from a Web Service can be stored in one or more Process Variables, and used later when invoking another Web Service or in a Decision Switch. | |||
::''Learn more:'' [[Process Variables]] | |||
==== Additional Process Modeling Enhancements ==== | |||
:* When a process model needs to invoke a Rule Set that doesn't yet exist, an empty Rule Set can be created right on the spot, without leaving the process-modeler window. You can then add Rules to the Rule Set after you finish modeling the process. | |||
: | |||
:* Similarly, in a Send Email step, you create a new Template by specifying a couple of fields. The template is created using reasonable defaults, so it works right away. You can then refine it later, after you finish. | |||
: | |||
: ''Learn more:'' [[Process Models#Process Tasks and Flow Control]] | |||
==== Greater Convenience when Adding Objects ==== | |||
:After adding objects to an application, the platform now stays in the design view so you can begin to customize them immediately. | |||
:''Learn more:'' [[Objects#Add a New Object]] | |||
==== Programmatic Access to Files, Attachments, Notes, and Tasks ==== | |||
:Guidelines for programmatically adding and accessing files, attachments, and private notes, as well as tasks that are related to a record have been added. | |||
:''Learn more:'' | |||
::* [[System Objects#Related System Objects]] | |||
::* [[Java Code Samples#Manage Files]] | |||
::* [[Java Code Samples#Add and Access Notes]] | |||
</blockquote> | |||
===13 Sep 2013=== | |||
<blockquote> | |||
==== Web Services Integration (beta) ==== | |||
:The {{EnterpriseBrand}} can be configured to use a wide variety of web services, allowing for sophisticated interchange of data without any platform programming. (The {{^WebMethods}} integration server is recommended.) In addition, an IT admin can make the Web Service interface as simple as possible for the application designer to use. | |||
:''Learn more:'' [[Web Services Integration]] | |||
====Task-Completion Forms==== | |||
:The standard dialog that completes a task lets the user add an optional comment. With this enhancement, a Process Model step can require a comment, and it can include a Form for the record the Task is attached to, allowing the user to modify that data, as well. (For example, when completing a Task attached to a Case, the case data can be adjusted.) | |||
:''Learn more:'' [[Process Models#Process Tasks and Flow Control| Process Model '''User Tasks''' and '''Approval Steps''']] | |||
==== Loop Variables Easier to Use in Templates ==== | |||
:When defining a template, related records (records that have a [[Lookup]] to the current record) need to be processed in a loop, because multiple records in the related object could be pointing to the current record. Such variables are easier to spot, because related objects are listed at the end of the Template Variables category list, under the heading "Related". And they're easier to use, because they include the entire loop syntax. The entire line of code can then be pasted into the template or, if a loop is already in place, you can paste only the part that is needed. | |||
:''Learn more:'' [[Processing Related Records in a Template]] | |||
==== Initial Class Template and Debugging Tips==== | |||
:An initial class template has been added to the wiki, to make it easier to code your next Java class. An additional snippet shows how to list incoming parameters. A page with debugging tips has also been added. | |||
:''Learn more:'' | |||
::* [[Class Template]] | |||
::* [[Java Debugging Tips]] | |||
</blockquote> | |||
===23 Aug 2013=== | |||
<blockquote> | <blockquote> | ||
==== Menu Reorganization ==== | ==== Menu Reorganization ==== | ||
:The gear menu changes to create a clearer separation between administration and customization activities. | :The gear menu changes to create a clearer separation between administration and customization activities. | ||
:''Learn more:'' [[Using the Agent Portal]] | |||
==== ''Localized Formats for Numbers and Currencies'' ==== | ==== ''Localized Formats for Numbers and Currencies'' ==== | ||
:As part of a large, multi-national organization, AgileApps Live has taken a significant step forward in its support for international standards. | :As part of a large, multi-national organization, AgileApps Live has taken a significant step forward in its support for international standards. | ||
:As in the past, a company can specify the default format for dates and times. Users can choose the format they are most comfortable with. The platform then does the | :As in the past, a company can specify the default format for dates and times. Users can choose the format they are most comfortable with. The platform then does the formatting, allowing reports, records, and database views to present data in the most readable way possible. | ||
:Now, though, a company can do even more: | :Now, though, a company can do even more: | ||
:* The company can specify the default format for numbers, allowing users to choose the format they're familiar with. As with dates, | ::* The company can specify the default format for numbers, allowing users to choose the format they're familiar with. As with dates, formatting is performed automatically by the program. | ||
:* Perhaps even more importantly for a wide variety of applications, the company can specify the currency format, so that data entry and | ::* Perhaps even more importantly for a wide variety of applications, the company can specify the currency format, so that data entry forms and reports use the format appropriate to the company's locale. | ||
:''Learn more:'' [[Localization]] | |||
==== Specify "Reply above this line" Text==== | ==== Specify "Reply above this line" Text==== | ||
:When a message goes out, recipients are instructed to type their message at the top of the reply. The text that tells them to do so can be customized by designers. | :When a message goes out, recipients are instructed to type their message at the top of the reply. The text that tells them to do so can be customized by designers. | ||
:''Learn more:'' [[Email Channel#Email Handling|End of Message Marker]] | |||
==== | ==== "Global" Email Templates Relocated ==== | ||
: | :Rather than having two different locations where an Email template ''might'' be found, all email templates are now found in the object they apply to -- so the templates formerly known as "Global" are now found in the Dynamic Case Management application's [[Cases object]]. | ||
</blockquote> | </blockquote> | ||
===Aug | ===3 Aug 2013=== | ||
<blockquote> | <blockquote> | ||
==== Selectively Trigger Rules during Record Updates ==== | ==== Selectively Trigger Rules during Record Updates ==== | ||
:It is now possible to trigger rules when updating records, as well as when adding them. The default when adding is to trigger any rules that exist, since that behavior is typically desired. But when updating a record, it is entirely possible to create a vicious circle of updates that does not end. For that reason, triggering of rules is disabled by default for updates. But | :It is now possible to trigger rules when updating records, as well as when adding them. The default when adding is to trigger any rules that exist, since that behavior is typically desired. But when updating a record, it is entirely possible to create a vicious circle of updates that does not end. For that reason, triggering of rules is disabled by default for updates. But the behavior can be enabled, as needed. | ||
:''Learn more:'' [[Rules#Actions to Perform|Rule Actions]] | :''Learn more:'' [[Rules#Actions to Perform|Rule Actions]] | ||
Line 45: | Line 199: | ||
:It is now possible to create a link in a JSP page (for example) and--assuming the user has a platform login--open a data entry [[Form]] that has one or more fields pre-filled when the user clicks on that link. That makes it possible to set up several links that "do the right thing", depending on which one the user clicks. | :It is now possible to create a link in a JSP page (for example) and--assuming the user has a platform login--open a data entry [[Form]] that has one or more fields pre-filled when the user clicks on that link. That makes it possible to set up several links that "do the right thing", depending on which one the user clicks. | ||
:''Learn more:'' [[Prefill Form Fields]] | :''Learn more:'' [[Prefill Form Fields]] | ||
</blockquote> | </blockquote> | ||
===July | ===July 2013=== | ||
<blockquote> | <blockquote> | ||
====Ability to Create New Dynamic Case Management Applications==== | ====Ability to Create New Dynamic Case Management Applications==== | ||
Line 61: | Line 209: | ||
====Global Email Templates==== | ====Global Email Templates==== | ||
:Previously, email templates were created for each object (for example, the Cases object). That capability still exists but now, global email templates can be created. Those templates can be used when sending a message from any record in the system (for example, from records in the [[Contacts]] or [[Tasks]] objects. | :Previously, email templates were created for each object (for example, the Cases object). That capability still exists but now, global email templates can be created. Those templates can be used when sending a message from any record in the system (for example, from records in the [[Contacts]] or [[Tasks]] objects. | ||
</blockquote> | </blockquote> | ||
===May | ===May 2013 === | ||
<blockquote> | <blockquote> | ||
====Multi Step Tasks==== | ====Multi Step Tasks==== | ||
Line 93: | Line 238: | ||
<noinclude> | <noinclude> | ||
[[Category:Release Notes]] | [[Category:Platform Release Notes]] | ||
</noinclude> | </noinclude> |
Latest revision as of 10:58, 4 July 2019
See also:
20 Dec 2013
Enhancements to Web Services
- Fields in SOAP headers are available for mapping
- A service that publishes a REST API can be configured, as well as one that uses SOAP
- Web Services can be added when creating a Package
- Learn more: Web Services
Accessibility Compliance
- AgileApps has basic compliance to accessibility standards like 508, WCAG 2.0, ISO 9241-171, and ISO 9126-1. However, to maintain a generic support for accessibility across NA and EU regions, AgileApps has chosen not to be certified with any of these standards explicitly.
- Any issues experienced by the users are resolved as per the support request raised on https://empower.softwareag.com.
- Learn more: Accessibility Mode
Unification of Processes and Process Models
- When creating a new Process, the process model editor is automatically launched. When the model is saved, the Process is created. Thereafter, the Process record contains a link to the model--so the model is intimately tied to the Process. (In the UI, "Process Models" is removed from the sidebar. To modify a model, you start by visiting the Process that wraps it.)
- Learn more: Processes
15 Nov 2013
Mobile Interface is Production-Ready!
- The mobile interface has emerged from it's beta period, and has been declared ready for production use.
Enhanced Parameter-access for Web Services (beta)
- Web Services are closing in on production status. In this enhancement, the full hierarchy of Web Service parameters is exposed, allowing any data element to be selected.
- Learn more: Web Services
Process Models allow Step Assignments, Case Forms, and Compound Conditions
- Process model enhancements include:
- Task step assignments can be designated by Role, as well as by Team.
- Task steps can include a Case form that allows the task worker to see and modify data.
- Decision switches can test for multiple conditions using and/or logic
- Learn more: Process Models#Process Steps and Flow Control
User Rules can Process Login Events
- Rules can be created that fire when a User logs in.
- Learn more: User Rules
SQL Browser
- Developers can test their SQL statements interactively before adding them to their code.
- Learn more: SQL Browser
Auto Copy Scheduled Reports to Managers
- Automatically deliver copies of scheduled reports to each recipient's manager, or to both their immediate management and second-level management.
- Learn more: Report Schedules
Dates and Times Exported in User Format
- The user's date format and time zone are used when exporting date/time data, allowing backup data exported by a user to be re-imported by the same user, without requiring a data conversion.
- Learn more: Export Data#Data Formats
25 Oct 2013
Mobile Enhancement: Geolocation Fields (beta)
- A Geolocation field stores current latitude and longitude at the click of a button. Another button allows the viewer of a record to see the location on a map.
- Learn more: Field Display Types
Scheduled Reports
- Schedule reports for a future date, and run them at regular intervals.
- Learn more: Report Schedules
Drill Down to Underlying Report from Dashboard
- Click to go from a Dashboard widget to the report that created it, then take advantage of Quick Filters and other filtering options to customize the report.
- Learn more: Dashboard Widget Types#Report, Quick Filters
Localized Time Formats
- Users can select the time format appropriate for their locale, in either 12 or 24 hour format.
- New Java and JavaScript APIs can be used to manage Time and DateTime values.
- Learn more: Dates and Times, Java Localization APIs, JavaScript Localization Functions
Fully Define Cases Object during Application Construction
- When creating a Dynamic Case Management application, both singular and plural labels can be specified for the Cases object. Additional fields can be also be defined, and the labels of the subject and description field can be changed. (Previously, those modifications could be made only after the application was created.)
- Learn more: Application Construction Wizard
Specify Plural and Singular Object Labels when Creating an Object
- When defining an object (when creating an application or afterward), both singular and plural labels can be specified. (Previously, labels could be modified only after the object was created.)
- Learn more: Object Construction Wizard
More Intuitive Names for Lookup Fields
- When defining an object relationship, the generated field name is now the singular version of the object name. When displayed in a Form, the field is more readily recognized by users.
- For example, when a Lookup field targets the Customers object, the default label is Customer and the field name is customer_record. (Previously, the field name was related_to_customers.)
More Readable Object Relationships
- The table that displays object relationships is more clear, making it easier to tell which object is on the "one" side of a One-to-Many relationship, and which is on the "many" side. That change, combined with added Help text, makes it as straight-forward as possible to manage object relationships.
- Learn more: Object Relationships#Reading the Relationship Grid
Include Web Forms in an Application Package
4 Oct 2013
Mobile Enhancements (beta)
- Mobile access to the platform has been further enhanced with a newer, localized interface, object tabs, the ability to complete process tasks, and the ability to search for records. To use the mobile interface, visit this URL in your browser or mobile device: https://{yourDomain}/m
- Learn more: Mobile Access
Web Service Enhancements (beta)
The integration of Web Services into Process Models comes closer to production status with these enhancements:
- Use Authenticated Services
- Web Services protected by basic username/password authentication can be utilized. (Username and password fields that are set when configuring a Web Service are used automatically.)
- Download WSDLs
- WSDLs can be downloaded from the web, as well as uploaded from the file system.
- Learn more: Web Services Integration#Creating a Web Service
- Process Model Variables
- Information gathered from a Web Service can be stored in one or more Process Variables, and used later when invoking another Web Service or in a Decision Switch.
- Learn more: Process Variables
Additional Process Modeling Enhancements
- When a process model needs to invoke a Rule Set that doesn't yet exist, an empty Rule Set can be created right on the spot, without leaving the process-modeler window. You can then add Rules to the Rule Set after you finish modeling the process.
- Similarly, in a Send Email step, you create a new Template by specifying a couple of fields. The template is created using reasonable defaults, so it works right away. You can then refine it later, after you finish.
- Learn more: Process Models#Process Tasks and Flow Control
Greater Convenience when Adding Objects
- After adding objects to an application, the platform now stays in the design view so you can begin to customize them immediately.
- Learn more: Objects#Add a New Object
Programmatic Access to Files, Attachments, Notes, and Tasks
- Guidelines for programmatically adding and accessing files, attachments, and private notes, as well as tasks that are related to a record have been added.
- Learn more:
13 Sep 2013
Web Services Integration (beta)
- The AgileApps Cloud platform can be configured to use a wide variety of web services, allowing for sophisticated interchange of data without any platform programming. (The WebMethods integration server is recommended.) In addition, an IT admin can make the Web Service interface as simple as possible for the application designer to use.
- Learn more: Web Services Integration
Task-Completion Forms
- The standard dialog that completes a task lets the user add an optional comment. With this enhancement, a Process Model step can require a comment, and it can include a Form for the record the Task is attached to, allowing the user to modify that data, as well. (For example, when completing a Task attached to a Case, the case data can be adjusted.)
- Learn more: Process Model User Tasks and Approval Steps
Loop Variables Easier to Use in Templates
- When defining a template, related records (records that have a Lookup to the current record) need to be processed in a loop, because multiple records in the related object could be pointing to the current record. Such variables are easier to spot, because related objects are listed at the end of the Template Variables category list, under the heading "Related". And they're easier to use, because they include the entire loop syntax. The entire line of code can then be pasted into the template or, if a loop is already in place, you can paste only the part that is needed.
- Learn more: Processing Related Records in a Template
Initial Class Template and Debugging Tips
- An initial class template has been added to the wiki, to make it easier to code your next Java class. An additional snippet shows how to list incoming parameters. A page with debugging tips has also been added.
- Learn more:
23 Aug 2013
Menu Reorganization
- The gear menu changes to create a clearer separation between administration and customization activities.
- Learn more: Using the Agent Portal
Localized Formats for Numbers and Currencies
- As part of a large, multi-national organization, AgileApps Live has taken a significant step forward in its support for international standards.
- As in the past, a company can specify the default format for dates and times. Users can choose the format they are most comfortable with. The platform then does the formatting, allowing reports, records, and database views to present data in the most readable way possible.
- Now, though, a company can do even more:
- The company can specify the default format for numbers, allowing users to choose the format they're familiar with. As with dates, formatting is performed automatically by the program.
- Perhaps even more importantly for a wide variety of applications, the company can specify the currency format, so that data entry forms and reports use the format appropriate to the company's locale.
- Learn more: Localization
Specify "Reply above this line" Text
- When a message goes out, recipients are instructed to type their message at the top of the reply. The text that tells them to do so can be customized by designers.
- Learn more: End of Message Marker
"Global" Email Templates Relocated
- Rather than having two different locations where an Email template might be found, all email templates are now found in the object they apply to -- so the templates formerly known as "Global" are now found in the Dynamic Case Management application's Cases object.
3 Aug 2013
Selectively Trigger Rules during Record Updates
- It is now possible to trigger rules when updating records, as well as when adding them. The default when adding is to trigger any rules that exist, since that behavior is typically desired. But when updating a record, it is entirely possible to create a vicious circle of updates that does not end. For that reason, triggering of rules is disabled by default for updates. But the behavior can be enabled, as needed.
- Learn more: Rule Actions
Trigger Rules Before of After a Record is Imported
- Previously, it was possible to trigger a rule before a record was imported, but not after. It is not possible to do both.
- Learn more: Event Rules
Selectively Disable Quick Text Entries
- By default, Quick Text entries are available for use. But it is now possible to disable them, so they are not visible to users. For example, you might do that when creating entries for use in the future.
Prefill Form Data using Simple URLs
- It is now possible to create a link in a JSP page (for example) and--assuming the user has a platform login--open a data entry Form that has one or more fields pre-filled when the user clicks on that link. That makes it possible to set up several links that "do the right thing", depending on which one the user clicks.
- Learn more: Prefill Form Fields
July 2013
Ability to Create New Dynamic Case Management Applications
- You now have two ways to create a new Dynamic Case Management (DCM) application. The first is to customize the (one and only) ServiceDesk application. That lets you take advantage of special ServiceDesk Features for customer interactions, but you can only have one such application installed at any given time. For other kinds of cases, you can create a new Dynamic Case Management Application, and have as many of those as you like.
- Learn more: Application Construction Wizard
Global Email Templates
- Previously, email templates were created for each object (for example, the Cases object). That capability still exists but now, global email templates can be created. Those templates can be used when sending a message from any record in the system (for example, from records in the Contacts or Tasks objects.
May 2013
Multi Step Tasks
- Case Agents can now create an "ad hoc" process while managing a case, by creating a Multi Step task.
- Learn more: Multi Step Tasks
Role-based Process Control
- The ability to start and stop a given process can now be determined by a user's Role.
- Learn more: Process Settings
Custom Form Actions in Case Forms
- Action buttons can now be added to Case Forms, and to Forms created for records in other objects.
- Learn more: Custom Form Actions
Rules for Import Events
- It is now possible to trigger rules when records are imported. Rules can be triggered by individual records, or by the import process as a whole.
- Learn more: Event Rules
Print Cases and Other Records
- When you're viewing a record and you open the list of Actions in the sidebar, you now have a Print option. You can choose the Form or Document Template to use for printing, choose Portrait or Landscape mode, and choose whether to save the document or view it online.
- Learn more: Use a Template to Print a Record
Customizable Auto Completion
- It is now possible to determine how Auto Completion works. You can specify which fields are searched for the text the user types, and which fields are displayed to help the user determine which record to select.
- Learn more: Auto Completion