Static code analysis for fragment files

The result of the analysis shows directly in the editor as hints. The static code analysis can also be started as a separate job from the project node.

Defines a code-resuable fragment of for both projection and client models.

Performance

• Multiple server calls one after the other

Maintainability

• Duplicate 'include fragment' statement.
• Entity array needed from master
• Method argument ${object name} is not used.
• Shape of Gantt item
• SnapTime values of Gantt chart.
• Unused ${rule name} ${object name}.
• Usage of deprecated property/setting

Functionality

• 'Java' implementation to be used with Stream
• Both Available and Selected Items labels must use together.
• Commands that require bulk execution
• Component name must match the folder name.
• Default datasources should be used
• Emphasis cannot be used within iconset
• enableonallfiltered can be used only with commands making use of stringify.
• Entity is mandatory for every node except root node.
• EntitySet name should be different from the Entity name.
• Freeinput and Wildcards cannot be used simultaneously
• Grouby and ranking cannot be used together.
• Identifier needed for overrides/overtakes
• Method overtakes should be avoided
• Model name must be the same as the file name.
• Name already exists in database
• Non-editable computedfield
• Not allowed to prefix DB calls with IFSAPP
• Query must have LU attribute
• Record is a Reserved Keyword
• Selected is enabled only for generic messagebox
• String literals with non-US-ASCII characters
• Syntax error. Offline projections require additional syntax entries.
• The content type can only be set once.
• The Type definition for attribute 'Objstate' expects to be a valid Enumeration.
• Type in assignments must be compatible.
• Unsupported create command
• Unsupported structure content
• Warning. Offline projections require additional syntax entries.
• Wildcard syntax to be used in dynamiclov fields only.
• Wrong usage of inline saving property

Usability

• Some values for height cannot be use with some components

This page is generated from IFS Developer Studio at 2025-05-28 19:49.