webMethods 10.2 | Service Development Help | Working with Elements | Renaming Elements
 
Renaming Elements
When renaming elements, keep the following points in mind:
*You can rename any elements for which you have Write access to the element and its parent folder. When renaming a folder, you must also have Write access to all elements within the folder. For more information about Write access and ACLs assigned to elements, see Assigning and Managing Permissions for Elements.
*When you rename a folder, Designer automatically renames all of the elements in that folder (that is, changes their fully qualified names).
*If the folder you want to rename contains elements with unsaved changes, you must save the changes before you can rename the folder.
*Element names must be unique across all packages. If you try to rename an element using a name that already exists, Designer reverts the element back to its original name.
*When you rename an adapter notification, Designer also renames its associated publishable document type and prompts you to indicate whether to rename the associated Broker document type.
*You cannot rename a listener or connection element.
*When you rename a publishable document type, Designer checks for dependents such as triggers and services that use the publishable document type. (Designer performs dependency checking only if you select the Prompt before updating dependents when renaming/moving preference.) If Designer finds elements that use the publishable document type, Designer gives you the option of updating the publishable document type name in each of these elements. If you do not update the references, all of the references to the publishable document type will be broken.
Important: You must manually update any services that invoke the pub.publish services and specify this publishable document type in the documentTypeName or the receivedDocumentTypeName parameter.
* To rename an element
1. In Package Navigator view, select the element that you want to rename. Right-click the element and click Rename.
2. If the element you want to rename contains unsaved changes, Designer alerts you that the element cannot be renamed until you save the changes. Click OK to close the alert dialog box. Then, save the changes and repeat the rename action.
3. Edit the name and press ENTER.
If an element already exists with that name at the same level, Designer displays a message alerting you that the rename action could not be completed. Click OK to close the message dialog box and repeat the rename action.
4. If you selected the Prompt before updating dependents when renaming/moving check box in the Package Navigator preferences and any dependent elements on the current server contain unsaved changes, Designer alerts you to save the elements that will be affected by the rename action. Select the elements and click OK to save the changes or Cancel to cancel the entire rename action.
5. If the Move and Rename Dependencies dialog box appears, do one of the following:
To...
Click...
Rename the selected element in Package Navigator view and update references to dependent elements
Update Usages.
Rename the selected element without updating references to dependent elements
Ignore Usages.
Cancel the entire rename action
Cancel.
For more information about dependency safeguards, see Configuring Dependency Checking for Elements.

Copyright © 2017-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release