To access the Repository Configuration area, Polices page you must be assigned a Repository Role granting Manage Repository permission. See Assigning Security Roles for more information.
The Policies page allows you to specify for a repository:
- The number of parts in item version numbers
- Whether an Architect needs to accept diagram-based Describes relationships to existing objects
- When diagram-based Describes relationships are applied to objects
- When comments are required
- Regarding digital signatures:
- Turning the feature on or off
- Whether the Windows password is required when digitally signing
- Content of the signing statement
- Whether Windows clients will remember connection passwords
Repository items such as iGrafx documents, web diagrams, and non-iGrafx documents (e.g. Word files) are modified via check out and check in commands creating an item history. The numbering of the item versions can have one, two, or three parts.
Web and Client diagram elements can Describe repository objects. For example, a shape representing the "Advertise Product" Process or Activity can Describe the repository object named "Advertise Object". This might be done in multiple process diagrams. In this way, you can visualize the enterprise objects you have defined, and follow relationships from Described objects to other objects.
As an Administrator, you can specify whether the Describes relationships are promoted from a diagram to the enterprise model at check-in time (the historic behavior) or only after a diagram has been approved and made the current approved version (17.4 or later).
Furthermore, in 17.4 and later, for Web diagrams, the Administrator can now dictate that in addition to requiring Architect acceptance of describes relationships to newly proposed objects, that Describes relationships to existing objects also require Architect acceptance. Both of these options, give you more control over the introduction of new relationships in the repository. For example, you might not want changes to work-in-progress diagrams to affect enterprise objects.
The three check boxes under Require Comments let you specify whether comments are required for some, all, or none of the following activities:
Requires a comment when adding a document to the repository.
When Checking In
Requires a comment when checking document in to this repository.
Requires a comment when reviewing, approving, or endorsing a document in this repository.
Requiring a Digital Signature
Enable the Require Digital Signatures when Reviewing/Approving/Endorsing check box to require digital signatures when reviewing, approving, or endorsing a document in this repository. For more information on working with digital signatures and their certificates, see the "Digital Signature" topic in the iGrafx Process client Help.
If you turn on the requirement for Digital Signatures users require the desktop client to participate in cycles.
CLOUD As implied by the check box label, Acknowledgement cycles, a new feature in the iGrafx Cloud, do not support requiring digital signatures when acknowledging a document in a repository.
Requiring a Windows Password
You can require identity authentication for digital signatures by enabling the Require Windows Password when Digitally Signing check box for this repository. Users will have to provide their Windows username and password when digitally signing their review, approval, or endorsement of a document in this repository.
Changing the Signing Statement
If your organization requires specific wording to be present in the signing statement that appears in the iGrafx client's Digitally Sign dialog box, you can add or change text accordingly in the Signing Statement box. Your edits are saved automatically. If you need to return to the original wording, click the Reset to Default link.
The text elements %SIGNER% and %VOTE% are dynamic text placeholders. Do not change or delete them. If you inadvertently do so, click the Reset to Default link to restore the original signing statement text.
Enabling Connection Password Memory
iGrafx can permit Windows clients to remember the Windows username and password of reviewers, approvers, and endorsers, if required, after the first time they are provided.
To allow this:
- Choose the Security Policies tab
- Check Allow Windows clients to remember connection passwords