Applied Parameters: None Summary
This command is used to release the current document being edited - through a direct editing session of the active managed content server Item - storing it as the next revision of that Item, closing the temporary editor, and destroying the temporary file.
Direct editing frees you of the shackles of separate version-controlled source data. You can simply edit a supported Item type using a temporary editor loaded with the latest source direct from the server itself. And once editing is complete, the entity is re-released into a subsequent planned revision of its parent Item, and the temporary editor closed. There are no files on your hard drive, no questioning whether you are working with the correct or latest source, and no having to maintain separate version control software. The managed content server handles it all, with the highest integrity, and in a manner that greatly expedites changes to your data.
While you can still create source files under your control, the freedom offered through direct editing takes this variable out of the equation, so-to-speak. The managed content server becomes both source and target for design data, allowing you to access and edit the secure (and latest!) source, without the headache of managing two sets of data
This command can be accessed by:
button, on the Standard toolbar of the temporary editor (associated with the document currently being edited). Right-clicking over the entry for the document - in the
<SourceServerName> folder on the Projects panel - and choosing the Save to Server command from the context menu. Using the
Ctrl+Alt+S keyboard shortcut.
The command is only available provided the temporary file is open in a direct editing session.
After launching the command, the
Create or Edit Revision (When Releasing) dialog will appear. The dialog allows you to add release notes and modify the name and description for the next revision of the item that is being released to the server. If desired, revisions of parent items related to (referencing) the current revision of the item being released can be updated also. Updating Components when Re-Releasing a Model Item
When you make a change to a managed domain model - be it a symbol, footprint model, or simulation model - the moment you release that change into a new revision of the model's Item, any Component Item revisions that use that model will become effectively out of date, still using the previous revision. In most cases, you will no doubt want to re-release those components, with the respective model links updated to use the latest revisions available. To streamline this process, a managed content server, in conjunction with Altium NEXUS, facilitates the ability to update related Component Item revisions - at the point of re-releasing a model Item - after having made any modifications to that model through the direct editing feature.
With the applicable temporary file used for a direct editing session, you do not have to complete the updating process in a single editing session - you can save your work and close the file if you wish. Altium NEXUS understands that this is a special file, so it retains it in the
<SourceServerName> folder in the Projects panel, so that you can re-open it when you are ready, and complete the updating and re-releasing process.