Skip to main content

Set repository policies

Decide how a repository numbers versions, when diagram Describes relationships reach the enterprise model, where comments are mandatory, who owns new objects, and which root folders are visible.

Prerequisites​

  • The Manage Repository Configuration repository permission — see Assigning Security Roles.
  • The Data Retention tab appears only when an administrator has enabled the Data Retention Early Access feature, and additionally requires the Manage Retention Policies and Archive repository permission — see Data retention and archiving.

Steps​

In the Repository area, select Policies. The settings are spread over the Version Policies, Security Policies, and Hidden Root Objects tabs, and save as you change them.

Set the version numbering​

Items build a version history through check-out and check-in. Under Version Numbering:

  • Number of parts in version numbers — one (1), two (1.0), or three (1.0.0).
  • Default incremented part during check-in — which part a check-in increments by default.

The Version Policies tab with the version numbering, modeling, comments, owner, and digital signature sections.

Control Describes relationships​

Shapes in a diagram can Describe repository objects. The Modeling section controls how those relationships behave:

  • Always show live described object data for latest visible versions of Diagrams. — every checked-in diagram version freezes a snapshot of its described object data, and readers without the See Unapproved permission normally see the frozen snapshot. Check this to show live data instead. See Described Object Changes in Diagrams.
  • Require a Creator to accept diagram-based Describes relationships in web-based diagrams before creating them — with this checked, Describes relationships to existing objects need explicit acceptance, not only relationships to newly proposed objects. On repositories using the Architect license model, the option reads "Require an Architect to accept …".
  • Create diagram-based Describes relationships and approve described objects when — at Checking in a Diagram, or only when the Diagram is made the Current Approved version. The second option keeps work-in-progress diagrams from changing the enterprise model.
  • Proposed Object Requirements — click Choose Requirements to pick the requirements shown to users when they propose objects.

Require comments​

Under Comments, check each situation where users must enter a comment: adding IGX documents and external files, checking in objects, reviewing, endorsing, canceling an in-progress cycle, or pausing and resuming an acknowledgement cycle. For approvals, choose Never required, Always required, or Only required when voting "No".

Set the default administrative owner​

Every object has an administrative owner, which automatically grants the Set Any Item Permission right on that object. Under Default Administrative Owner, keep New objects are owned by the creator of the object, or choose New objects are owned by a specific user and pick a user — for example a system account, so creators keep only their role permissions.

iGrafx stores the owner as a username. If that account doesn't exist — a name entered here that never matched a user, or an owner whose account is deleted later — the username stays recorded as the administrative owner, so nobody who can sign in holds administrative-owner rights on those objects. The objects remain reachable through normal role permissions. This applies to any deleted owner, however you set this policy, and it's visible on the object: an owner with no account shows as the stored username rather than a display name.

Require digital signatures​

The Digital Signatures section applies to cycles performed through the iGrafx desktop client:

  • Require Digital Signatures when Reviewing / Approving / Endorsing — acknowledgement cycles do not support digital signatures.
  • Require Windows Password when Digitally Signing — signers must also enter their Windows credentials.
  • Signing Statement — the wording shown in the client's signing dialog. %SIGNER% and %VOTE% are placeholders the product fills in; keep them in the text. Reset to Default restores the original wording.

Set the security policy​

On the Security Policies tab, Allow Windows Clients to remember connection passwords lets desktop client users store their connection password after entering it once.

Hide unused root folders​

On the Hidden Root Objects tab, check the root folders your organization doesn't use — for example Journeys or Work Products — and click Confirm. Hidden folders disappear from the repository tree. Deselect All clears the selection; Reset returns to the saved state.

The Hidden Root Objects tab with the checkbox list of root folders.

Limitations​

  • Hiding a root folder only removes it from the repository tree; it doesn't disable its object types. Hide the Risk Catalog, for example, and the Risks already in it keep working: they stay attached to the objects they apply to, still appear in reports, and the REST API can still create more.