If a programming interface is changed, e.g. a modified signature to a method, added or removed table/view columns, etc., it might have influence on the customized code or the configurations set up inside the applications. To analyze this, a list of all interface changes is delivered with every update of IFS Applications. The content of this list is matched with all customized code and all extracted configurations and if the tool finds any use of a modified interface is reported as and Interface Impact.
After the analysis is complete, the impact on the files are showed in the column Interface Impact in the main grid. More information will be shown in Interface Impact Info column. To see the usage of modified interfaces and further information about each file, select Interface Reference Report Viewer in the context menu.
Note: If a file exists in the Modifications path, and if it’s a core file with layered support (instead of extension or customization file), then the file will be excluded when analyzing the interface reference report. This situation typically occurs when you have single patched a CORE file which has layered support.
The Interface Impact affect from issues from the Interface Reference report are listed below.
| Impact | Shown in Interface Impact Info column | |
|---|---|---|
| There are added objects into an APF | No Impact | No |
| There are removed objects in an APF | Unknown | Yes |
| Table or view is added | No Impact | No |
| Table or view is removed | High Impact | Yes |
| Mandatory column(s) added, column(s) removed or modified in a table or view | High Impact | Yes |
| Mandatory column(s) added, column(s) removed or modified in a table or view (unless it is a mandatory column added or removed/modified column names are not referred) | Low Impact | Yes |
| Column is added into a table or view (unless it is a mandatory column added to a table) | No Impact | No |
| Index is added to a table | No Impact | No |
| Index is removed from a table | Low Impact | Yes |
| Index is modified | Low Impact | Yes |
| Stored plsql method is added | No Impact | No |
| Stored plsql method is removed | High Impact | Yes |
| Stored plsql method is deprecated | Low Impact | Yes |
| Argument to a stored plsql method is added, removed or modified | High Impact | Yes |
| Record type is removed | High Impact | Yes |
| Attribute is added to a record type | No Impact | No |
| Attribute is removed from, or modified in a record type | High Impact | Yes |
| Collection of a record type is added | No Impact | No |
| Collection of a record type is removed | High Impact | Yes |
| Projection is added | No Impact | No |
| Projection is removed | High Impact | Yes |
| Projection item is added | No Impact | No |
| Projection item is removed or modified | High Impact | Yes |
| Fragment is added | No Impact | No |
| Fragment is removed | High Impact | Yes |
| Fragment item is added | No Impact | No |
| Fragment item is removed or modified | High Impact | Yes |
| Enumeration is added | No Impact | No |
| Enumeration is removed | High Impact | Yes |
| Enumeration value is added | No Impact | No |
| Enumeration value is removed | High Impact | Yes |
| Enumeration subset is added | No Impact | No |
| Enumeration subset is removed | High Impact | Yes |
| Entity is added | No Impact | No |
| Entity is removed | High Impact | Yes |
| Entity attribute is added | No Impact | No |
| Entity attribute is removed or modified | High Impact | Yes |
| Client is added | No Impact | No |
| Client is removed | Unknown | Yes |
| Client item is added | No Impact | No |
| Client item is removed or modified | Unknown | Yes |
| Offline utility procedure is added | No Impact | No |
| Offline utility procedure is removed | High Impact | Yes |
| Parameter to a offline utility procedure is added, removed or modified | High Impact | Yes |
Inside Update Analyzer, files containing extracted configurations are considered to be in the layer Configuration. However, there is no such layer defined when developing, it is only a fictive layer used in Update Analyzer. These files are only analyzed for impacts caused by the interface reference report. Because of this, they might only get an Interface Impact and never a Layer Impact.