Contents
New and Updated Features
Invoice Accrual SmartFlow Skill
- Prescheduled runs on a monthly basis: one can now configure Invoice Accrual SmartFlow Skill to automatically run every month, starting before the end of the month (configurable number of days) and finishing after a configurable number of days.
- Internal contacts: one can specify who needs to be contacted to inquire about potential accruals, outside of the vendor contacts listed in the ERP.
- Journal Entry customizations: the fields of a Journal Entry can now be customized at the Vendor level (e.g. with different Accounts, Departments, Locations).
Fixed bugs
Integration with Oracle NetSuite
- Connection failures to certain Oracle NetSuite instances, related to the use of Oracle NetSuite REST API, have been solved.
Customer Collection Status and Follow-up SmartFlow Skills
- Better accuracy in detecting Unknown Contacts: the Bot verifies all known contacts for a Customer, as entered in the ERP, upon receiving emails.
New known bugs
Customer Collection Status and Follow-up SmartFlow Skills
Multi-intent emails received might not get labelled accurately
Symptom: When the Bot processes incoming emails from customer contacts, for long emails, if specific intents are appearing towards the end of the message, the Bot will not be able to identify them.
Impact: Bot will not process correctly (label, and act upon) long email messages coming from customer contacts. Emails with more than 6 sentences will need to be read and processed by a human in order to insure full processing.
Workaround: None.
System Settings
ERP system cards - Number of SmartFlow Skills is incorrect
Symptom: The number of SmartFlow Skills that use a certain ERP, reported on the ERP card in System Settings, can be incorrect at times.
Impact: When an ERP instance card shows a count of zero SmartFlows using it, the "Remove" button is active and one can mistakenly delete the ERP. This will impact on-going automation.
Workaround: Verify whether there are SmartFlow Skills using the particular ERP instance by checking the SmartFlow Management page, instead of relying solely on the count on the card.