Overview
Applications: GSM
Focus Area: Single- and multi-select windows
Customers have identified scenarios where some users need the ability to create new specifications, but they do does not have the authority to create new issues. The scenario usually states that Sales/Marketing can create copies for new specifications and R&D/Labeling can create new issues and new specifications.
In addition, users cannot always create new issues if the specification is in a certain workflow status. As an example, an R&D user has the ability to both create a new specification and a new version of a specification. If the R&D user is performing a copy from a specification that is currently in “Draft” status the user should only have the ability to create a new specification. The goal is to avoid creating a second issue of the specification when the earlier issue is in a “Draft” status because the user should merely update the current specification.
The Basics
Create Copy and Create New Issue functionality is now securable through separate roles. The roles are:
- SPEC_COPIER]: A user with this role is able to copy specification as a starting point for a new specification.
- [SPEC_ISSUER]: A user with this role is able to create a new issue or version of a specification.
The above roles are used in combination with specification creator roles, such as [SPEC_CREATOR_(NNNN)]
In addition the validation framework can invoke custom code upon performing either of these actions.
Specification Copier
When a user clicks Create Copy from a specification the user will only be presented with the link, “Create NEW SPECIFICATION based on this one”. This user has the standard security needed to get to the specification and the user is associated to a group with the role [SPEC_COPIER].
Figure 1. Specification Copier role choices
Specification Copier & Issuer
This user has the standard security needed to get to the
specification and the user is associated to a group with the roles [SPEC_COPIER]
and [SPEC_ISSUER]. It is possible to only associate a user to the [SPEC_ISSUER]
role.
Figure 2. Specification Copier and Issuer role choices
Validation
Regarding the validation framework there are two validation events that are fired any time the Spec Copy/New Issue popup is opened. Those validation events are ‘copy’ and ‘issue’ and they are evaluated if the user has permissions to copy/create issue (governed by the two roles mentioned above).
Customers will configure validation by modifying/configuring
the new validation rules in Config/Extensions/ValidationSettings.xml file. The basic idea of the configuration is as
follows:
<rule
type="spectype" configChildKey="event">
<condition event="copy/issue"
configChildKey="type">
<if
type="SomePreExistingOrNewValidator" property="…"
propertyAlias="…" behaviorId="…" report="…" />
</condition>
</rule>
About Configuration Files:
- <DeployedLocation>\config\Core\validationRules.xml
–Pre-existing validators/validations are defined in this file. New ones go
in the ValidationSettings.xml file (see below).
- <DeployedLocation>\config\Core\validationRules.xml.usage.txt
– Documents how to configure all the properties in the validation
conditions.
- <DeployedLocation>\config\Extensions\ValidationSettings.xml – Customer specific or custom validations are written in this file.
