What's New

In addition to general editorial changes and corrections, this release of the documentation contains the following main changes included in the release of 2025.R2:

• Your in-app Nakisa AI Assistant is here - get instant answers about product features and how to use them, directly from any page in the application. Just click the chat icon to get started.

• To allow users to better use the product, pop-ups can now be repositioned so that information on the page can be viewed and used.
• To provide better control over access to Journal Vouchers, we have introduced dedicated security roles "Journal Voucher Admin" and "Journal Voucher Approver". Note that the roles "NLA Accountant" and "NLA Approver" can no longer create and approve journal vouchers, but they can still view them.
• To add clarity, save time, and reduce manual entries, the following enhancements have been made to all types of jobs (e.g., for reports and postings):
  • Jobs can now be copied, edited if required, and run again.
  • Users can now easily view the job input fields on previously run jobs to understand what the job was run for. 
  • When users select a profile in a job, the profile input fields are now fully visible.
  • To add clarity to the status of the posting jobs and duplicate consistency checks, the job Status field now displays "Queued" and "Finished". Task statuses are now also color coded to better highlight whenever there are issues with any of the items.
  • Scheduled jobs now generate notifications whenever the job is queued, starts running, and finishes.
• Users can now paste a list of up to 50 object IDs when creating GL Balance Report jobs (instead of searching each ID individually). Any invalid ID is shown to the user.
• In Posting Jobs, users can now download an error report to see the activation groups with failed external postings, which will allow them to better handle errors and make corrections.
• In Posting Profiles, users can now filter which documents to post based on Accounting Standards.
• Ledger transactions can now be enriched with additional information from other products before they are posted externally.
  • To fetch extra information from a product, the product integration must be configured in Enrichment Management in Financial Organization Structure.
• The Lessee ERP Field Mapping has been enhanced as follows:
  • The table better identifies which product-specific GL Table and GL Field is being mapped.
  • Additional fields such as object names can now also be sent.
  • In custom mappings, the default GL table and field are now displayed.
  • Multiple fields can be concatenated together and sent in one single SAP field.