Refactoring for Move and Rename Operations
Move and rename refactoring operations change only the structure of a project. For example, when you change a concept name, that name must change everywhere the concept is referenced in the project. If the element has its own file, the file must also be renamed.
References to the changed or moved element are handled as shown in the following table. Projects can be complex; this list covers the main cases.
Renaming this... | Updates references in these places... |
---|---|
Concept | Concepts that inherit from this one Event expiry actions Property definitions for contained or referenced concepts State models Rules and rule functions |
Event | Events that inherit from this one Event expiry actions Destination (Default Event) State models Rules and rule functions |
Property of a concept or an event | Event expiry actions State models Rules and rule functions |
Domain Model | Domain models that inherit from this one Associated properties |
Channel | Event default destination paths |
Destination | Event default destination paths |
Rule | The rule source Rules and rule functions |
Rule Function | Event expiry actions State models The rule function source Rules and rule functions |
Folder | All location that this folder is used in a path, for example path to a default destination in an event, property definitions for contained or referenced concepts, and in rules and rule functions. For folder refactoring limitations, See Refactoring Limitations . |