![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
This section explains what is done for each kind of refactoring operation. It also lists some limitations.Changes made to certain items are not refactored in this release. You must handle reference updates manually.References to moved or changed folders in strings References to changed or moved folders are not updated in strings, including CDD and XSLT strings. CDD strings are used in the Cluster Definition Descriptor editor to point to project resources using their project path. XSLT strings are used in mapper functions, which are completed using the Function Argument Mapper. (Such references are, however, updated for entity refactoring operations).Copy-paste of folders Elements inside the pasted folder are not updated.References to global variables and shared resources Refactoring does not handle changes to global variables and shared resources. You must manually update references to global variables and shared resources that you change.
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 Table 12. Projects can be complex; this list covers the main cases.
Property of a concept or an event 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.Element deletion can affect project behavior. You must take care to ensure that your project behavior is as desired after the deletion refactoring.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |