9.1. Controlling Access to Objects

Engineering Knowledge Manager

User's Guide | Chapter 9: Version Control and Access Management |

Chapter 9: Version Control and Access Management |  | 9.2. Getting Exclusive Control
Prev |  | Next

## 9.1. Controlling Access to Objects

Once an object has been added to EKM, you can control access to it in different ways:

- set permissions on the object that permit (or restrict) access by users and groups.

- get exclusive control of the object, which gives you exclusive edit privileges and prevents others from modifying it. When you are done modifying the object, you can release exclusive control of it.

- place the object under version control by adding it to EKM,'s version control system. Editing objects in a “controlled check-in” environment ensures that only one user is modifying an object at any given time, and that their modifications are captured exclusively in the version they are working on.

Managing the configuration of an object under version control includes creating new versions for it and branching. Versioning creates a linear sequence of versions for an object, whereas branching creates a tree of versions. Figure 9.1: Versioning Versus Branching shows an example of an object that has been versioned and branched. Versions `1.1`, `1.2`, and `1.3` are versions of the same object. `2.1` is a branch of version `1.2` and has a new version `2.2`, spawned from it.

Figure 9.1: Versioning Versus Branching

Versioning and branching are both handled from the Versioning action menu. You can also use the Versioning action menu to revert to a previous version of the object, retrieve a copy of a stored version, remove the object from version control if it is obsolete, and view its revision history. When you revert to a previous version, the current repository copy of the file gets replaced with the contents of a selected previously stored version in the version store. For example, suppose you have a text file under version control. Let's say there are three versions of it stored in the version store; `1.1`, `1.2`, and `1.3`. Now if you revert to `1.2`, then your file will have its content replaced with the content from `1.2`. Then, if you check in the file, a new fourth version will be added to version control and labeled `1.4`.

Some sample actions from the Versioning menu are shown below for an object that has been added to version control and is checked out.

Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.

Prev | Up / Contents | Next

Release 18.2 - © ANSYS, Inc. All rights reserved.