Difference between revisions of "Version 10.2 Platform"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 14: | Line 14: | ||
<blockquote> | <blockquote> | ||
==== Community Marketplace Enhancements ==== | ==== Community Marketplace Enhancements ==== | ||
: A new button allows you to determine exactly when a package is submitted. An existing catalog entry remains unchanged until a new version is submitted approved. Once approved, the new version replaces the old. That arrangement has two significant benefits. First, it allows developers to publish a new package version for testing or backup, and save catalog information for that version, without affecting the existing catalog entry. Second, it means that the package contents and descriptive information provided for it are always exactly what the Service Provider approved. | : A new button allows you to determine exactly when a package is submitted. An existing catalog entry remains unchanged until a new version is submitted and approved. Once approved, the new version replaces the old. That arrangement has two significant benefits. First, it allows developers to publish a new package version for testing or backup, and save catalog information for that version, without affecting the existing catalog entry. Second, it means that the package contents and descriptive information provided for it are always exactly what the Service Provider approved. | ||
:''Learn more:'' | :''Learn more:'' | ||
::* [[Catalog Information]] | ::* [[Catalog Information]] | ||
Revision as of 01:00, 30 April 2014
See also:
- Version 10.1 Platform (previous release)
- All Release Notes
Next Release
Community Marketplace Enhancements
- A new button allows you to determine exactly when a package is submitted. An existing catalog entry remains unchanged until a new version is submitted and approved. Once approved, the new version replaces the old. That arrangement has two significant benefits. First, it allows developers to publish a new package version for testing or backup, and save catalog information for that version, without affecting the existing catalog entry. Second, it means that the package contents and descriptive information provided for it are always exactly what the Service Provider approved.
- Learn more:
Use a Rule Set to Make a Process Decision
- A Rule Set invoked in a Process can return a value that can be tested in a Process decision switch, allowing the process branch to be determined by the Rules executed in the Rule Set.
- Learn more: Process_Model#Decision_Switch
Group Report Records by Quarter
- Report grouping options include the ability to group records by quarter.
- Learn more: Report Group#Date Groupings
Web Service Logging
- When a Web Service fails, details of the invocation and subsequent results are recorded in the Audit Log, allowing for diagnosis and repair.
- In addition, a Debug flag can be set for a Web Service. That setting records invocation details and results for every execution of the service, allowing for a detailed examination of the call that was made, the data that was sent, and the data that came back.
- Learn more: Web Services Integration#Web Service Execution History
Interactive Search Option for Web Services (15 Apr ISV Release)
- A web service can return multiple records, and users can interactively choose which record to reference.
- Learn more: External Lookups
New in the Docs
- New Pages:
- Articles:
- Building a Dynamic Case Management Application in the AgileApps Cloud (pdf)
Simplified to make it easier to get started. Discussion of Web Services added,- Building an Advanced Two-Phase Case Management System in the AgileApps Cloud
Advanced rules and processes for a two-phase Dynamic Case Management application.