Difference between revisions of "Version 10.0 Platform"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 9: Line 9:
</blockquote>
</blockquote>
-->
-->
==== At Design Time, Create New Email Templates and Rule Sets "On the Fly" ====
==== 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 can the behavior can be enabled, as needed.
:''Learn more:'' [[Rules and Rule Sets]]
 
==== Create New Email Templates and Rule Sets While Designing ====
:''The Problem:''When creating a process step that sends an email, for example, you need to specify the template to use for the message--otherwise you can't save your work. But what if no templates have been created yet? You have to stop what you're doing and start down another track to create the item you need.
:''The Problem:''When creating a process step that sends an email, for example, you need to specify the template to use for the message--otherwise you can't save your work. But what if no templates have been created yet? You have to stop what you're doing and start down another track to create the item you need.



Revision as of 18:27, 30 July 2013

See also: Previous Enhancements

Upcoming Enhancements

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 can the behavior can be enabled, as needed.
Learn more: Rules and Rule Sets

Create New Email Templates and Rule Sets While Designing

The Problem:When creating a process step that sends an email, for example, you need to specify the template to use for the message--otherwise you can't save your work. But what if no templates have been created yet? You have to stop what you're doing and start down another track to create the item you need.
The Solution: In the selection list that shows Email Templates, it is now possible to create a new template on the spot. An empty template is created with the name you specify, ready for you to customize later. In the meantime, you can continue doing what you're doing, and save your current work before starting something new.

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.

Add and update records using simple URLs

Using a URL with the right format (and assuming you are logged into the platform), you can add or update a record, just by visiting that URL in your browser. For external applications, it means that adding or updating application data has never been easier.
Learn more: Prefill Form Fields

User-Role Function

A new function can be used to see if the current user has a given Role. That function can be used in Form Layout Rules for example, to vary the appearance of the form based on the user's role.