In some situations, function packages or some of their functions cannot be resolved at run time. In other words, a model contains references to specific function packages and/ or functions but the required plug-ins defining those functions are not available (or the IDs have changed).
Depending on where the model is loaded from, AWM handles this situation in the following ways:
AWM loads everything from the model that can be resolved, and ignores unresolved function package references. It depends on the kind of unresolved features and the model itself as to whether the application is still fully functional. e.g. if a missing function package only provided new icons, all elements and actions referencing those icons can still be used (but their icon will be missing).
If a function package contains functions, fundamental functions like new tool types can be missing intentionally (e.g. a function package intended for certain users only), the model can be designed to still work without it. e.g. actions containing missing tool types can have enabled conditions testing, such as for a static application property (see Master Configuration) which should be set according to the function package availability.
AWM will gather all IDs of missing features that have been detected in the model and display a warning message containing these IDs (see figure below). The model administrator can click “Remove Features…” which will open up the model editor with all those features removed (after a confirmation dialog). The model file itself will not be altered at this point: only changing the model and saving the editor will cause those features to be permanently removed from the model.
If the dialog is simply confirmed by clicking OK, all those features will remain in the model but will not be visible in the editor. Even references to those features will be invisible (e.g. action descriptor has references to an unresolved tool type).
