Type Clause for the Add Policy Command

This clause defines all of the business object types governed by the policy. Just as a policy can govern many different object types, each object type can have many different policies that govern it. An object instance can only have one policy associated at any time.

For example, assume you have an object type named Drawing. This type could be governed by two policies named “Engineering Drawing Process” and “Documentation Drawing Process.” When an object of type Drawing is created, you must decide which policy will govern the object instance. A drawing meant for documentation will have a different review and lifecycle than a drawing of a component to an engineering assembly. By associating one policy with the created object, you control the types of files that can be checked in, who will use the object, and when it is used.

The Type clause is required for a policy to be usable:

type TYPE_NAME{,TYPE_NAME}

Or:

type all
  • TYPE_NAME is a previously defined object type.

You can list one type or many types (separated by a comma or carriage return). When specifying the name of an object type, it must be of a type that already exists in the database. If it is not, an error message will display.

For example, the following two commands are valid Add Policy commands that identify object types associated with the policy:

add policy "Engineering Revision Process"
   description "Quality Control Process for Engineering Revisions"
   type Drawing,"Multipage Drawings",Schematics,Manual;
add policy "Documentation Revision Process"
   description "Quality Control Process for Documentation Revisions"
   type Manual,"Release Notes";

In the first command, the user can associate the “Engineering Revision Process” policy with object instances of four different object types: Drawing, Multi-page Drawings, Schematics, and Manual. In the second command, the user can associate the “Documentation Revision Process” policy with only two object types: Manual and Release Notes. If the user created an object named “MQL User Guide” of type Manual, could he assign a policy of “Engineering Revision Process?” The answer is yes, although the “Documentation Revision Process” policy might be more appropriate.

A variation of the Type clause uses the keyword 'all' in place of one or more type names (Type All). When this keyword is used, all existing and future business object types defined within 3DEXPERIENCE Platform are allowed by the policy-the policy governs objects of all types. The 'all' keyword is more like an option that can be turned on for the policy rather than a list of types. If a list of types is already defined for the policy and the 'all' keyword is used, the system will clear the list and turn the 'type all' option on for the policy.

Use caution when including this clause. While all of the types currently defined can apply to the policy, what happens if a new one is created that should not apply?

If you have a policy that uses most of the defined objects, you might want to assign all of the types rather than list them. Then you can use the Modify Policy command to remove the unwanted types.