tmp
XMPL Server & Client 3.0, together with Circle 4.7, support SecURL which offers user authentication in personalized URLs. When the recipient attempts to access a PURL, he/she is prompted to sign in and provide user authentication. This protects unauthorized users from accessing private recipient information which is stored in ADORs.
For information on implementing SecURL, see User Authentication (SecURL).
See also:
The following enhancement is relevant for developers who wish to access XMPL objects from their JavaScript code.
Versions 1.9.1 and above include two new callback functions for custom JavaScript code:
- angularComponenetsOnReady - for users who develop customized script and define a new directive, controller or a new Angular applicaton on top of the xmp.app application. This function will be be fired once Angular xmp.app modules are ready.
- xmplOnReady - for users who develop customized script. This function will be fired once xmp.app directives and controllers are ready in the browser.
Webpages written using custom JavaScript code in versions 1.8 and below should not be changed. The event $(document).ready can remain as is.
For more information and examples of these functions, see JavaScript Access
New!! Take a look at XMPL V5 Beta