Cisco Crosswork Planning Design 7.2.x User Guide
Is this content helpful?
Thank you for your feedback. Your response has been recorded.
AI responses are currently only available to logged in users. Log in
Only ask questions about this document. To ask questions about this product as a whole, go to Technical Documentation .
Suggestions
Sorry, we couldn't generate a response for this query.
Cisco Crosswork Planning Design 7.2.x User Guide
Updated: August 14, 2026
Want to summarize with AI?
Log inExplains how to apply patch files to plan files to update or modify their contents as needed.
Use this task to make targeted changes or corrections to existing plan files using patch files.
You may need to update plan files with patch files to fix errors, add enhancements, or synchronize the design with new requirements.
Open the plan file in the Network Design page. For more information, refer to Open plan files.
From the toolbar, choose Actions > Tools > Patches > Apply patch.
Click Browse to browse to the location where the patch file resides. Choose from these options:
From user space: Choose this option to select the patch file saved in your user space.
From local: Choose this option to select the patch files saved in your local system. Click Browse, choose the patch file located in your local system, and click Import.
Note that the patch file is imported into the user space as well.
Specify whether to stop or continue in case of error.
To verify the patch file’s contents before applying it, click the View details link. After viewing the patch, click Close. Use the Edit patch button to edit the patch file.
Click Run in the Apply Patch page.
Need help?
(Requires a Cisco Service Contract)
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.