In this Page
Live on November 22, 2014
You need to clear your browser cache before you log into the latest SnapLogic Elastic Integration Platform.
See the appropriate documentation for your browser:
Support user password forget/renew. When creating a new user, the password is now generated by the server. The org admin can no longer define the password. In addition, the login screen now has an option for handling a forgotten password.
When Single Sign-on is enabled, SnapLogic's native login can be disabled for all users except Admin users.
Enhanced Account Encryption. In Groundplex configurations, account data is now encrypted before it is stored in SnapLogic. This is only supported on Google Chrome, version 37 and above.
Support for Kerberos (Beta)
Designer
You can now turn off the auto validate that occurs on a pipeline save from the User Preferences and Settings dialog in Designer.
The panels within the Mapper Snap table are now resizable.
Snap Behavior Changes
Unique Snap Names. Now when a Snap is dragged onto the canvas, it is given a unique label name. This makes it easily identifiable in the execution log without you having to rename each Snap, though you can still do so.
Ctrl/Command+click to select multiple Snaps, Ctrl/Command+click to deselect a selected Snap
Right-click on a Snap to access a context menu where you can delete, copy/paste, or edit Snaps.
The ability to copy and paste configured Snaps.
Dashboard: "Time Updated" has been relabeled to "Time Started". When used in conjunction with Duration, this data provides more useful information.
Pipeline Documentation: Print or download a document that describes your pipeline, listing the Snaps and pipeline properties.
Note: This feature requires configuration by a SnapLogic Administrator as each phase will need its own Snaplex. It you wish to unsubscribe from this feature, you will need to work with a SnapLogic Administrator to reconfigure your environment. Existing customers should test this feature before applying it to their existing environment. |
This is a significant change in behavior. Previously, certain error types would cause the pipeline to fail, regardless of output view configuration. Review your existing pipelines for any impacts this may have. |