Updating the object-centric Duplicate Invoice Checker
When there’s an update for the Duplicate Invoice Checker, you’ll see an UPDATE AVAILABLE button next to the package name in the Dependencies tab in the package settings. The package settings are available from the package’s context menu (the three vertical dots by the package name).
Updates with new features are announced in the Release Notes, and all the updates for the object-centric Duplicate Invoice Checker are listed at the end of this topic. Update your app regularly to benefit from our new developments.
Important
The AI Annotation for the Duplicate Invoice Checker is independent of the app package. When you update the package through Studio, you won’t see any changes to the AI Annotation or the settings you made in it. If there are changes to the AI Annotation, we’ll push these directly to the feature.
Here’s how to update your app:
Check the change history at the end of this topic for all the releases that have happened since your current version, to see what changes were made since you last updated the app. If there’s any action you need to take, such as manually updating a KPI or reapplying some of your customizations, we’ll tell you here.
Tip
Your current app version is shown in the Dependencies tab in the package settings.
In Studio, click Publish Package to publish your current app package, so that you can revert to this in case there are any problems during the update.
In the Dependencies tab in the package settings, click the UPDATE AVAILABLE button to update the app to the latest version. The popup lists the updated assets - click Update to proceed.
In the visual editor for the app’s Knowledge Model, check that the Knowledge Model Key variable is still set to the value of the Knowledge Model key for your local app installation. If you have multiple copies of the app, the update might overwrite it. Setting the Knowledge Model Key variable for the object-centric Duplicate Invoice Checker tells you how to find the local Knowledge Model key and set the variable value.
In Studio, make any required manual updates that we’ve noted in the change history for your new app version, or for the other versions since you last updated the app.
Check all the app’s views to make sure everything works correctly, all the fields are populated, and the numbers look as you’d expect.
If there’s an issue and you’re sure you made any required manual changes correctly, see Contacting support to find how to get help.
If everything’s working, click Publish Package to publish your updated package and make it available to your users.
Change history
Version 0.1.0 : The Machine Learning Sensor has been replaced with the AI Annotations configuration interface. If you have an earlier version of the package where the ML Sensor is used, make sure to disable it by saving the Skill and publishing the package before using the AI Annotation Signal.