Integration Framework

Auto Map Metadata at Run Time

You now get options to automatically map new data elements detected by a Planning Data Loader at run time. Automapping is particularly useful for tasks that run on a schedule without user interaction. Automap options exist for:

• Accounts
• Levels
• Dimensions

If you make a selection for Source Display Name Column in Data Mapping, you can automap by Source ID or Source Display Name. For Accounts, you can also automap Source ID or Display Name to Account Name or Account Code.

If you don't make a selection for Source Display Name Column you can automap by Source ID. For Accounts, you can automap by Account Name or Account Code.

New and existing Planning Data Loaders do not automap by default.

See Create a Planning Data Loader for more.

Handle Invalid Data Mappings in the Planning Data Loader

The Planning Data Loader now gives you a new mapping status of Invalid. An invalid mapping status lets you know when the Adaptive Planning Accounts, Levels, and Dimensions you mapped were deleted since your last mapping. Filter for invalid mappings in the Data Mappings tab, remap them, delete them, or download a spreadsheet to update and upload new mappings.

See Create a Planning Data Loader for more.

Export Security Audit Event Logs API

The new exportSecurityAudit API lets you request security event audit logs and filter them by a time range. The audit log records security events based on NIST 800-53, retaining only the last 30 days of activity. It records:

• Account creations
• Account disables
• Account lockouts
• Unsuccessful logins
• User logouts
• User password changes
• Session terminations due to exceptions
• Session expirations
• Credential changes
• Authentication configuration changes

See exportSecurityAudit for more.