Business object constants

Following are the business object constants unique to Active Workspace: Awb0AvailableFor Lists the business object types for which a feature should be made available. The values are comma separated. This constant honors type hierarchy. When this constant is used with the Ase0ArchitectureFeature business object, the constant controls visibility of the Architecture tab for business object types. The Architecture tab is made visible for all listed business object types and their all subtypes. The types should be those that represent the top line in structures. This constant supports comma-delimited values of business object types, for example: Functionality Fnd0LogicalBlock RequirementSpec Requirement Paragraph Fnd0SystemModel Note The Architecture tab is not visible for custom business objects. Determine the business object types that require the Architecture tab. From these types, determine those that are the top line in structures. Add only those types to the value of the Awb0AvailableFor business object constant on the Ase0ArchitectureFeature business object. You can edit the display name configured for the Ase0ArchitectureFeature business object in Business Modeler IDE to suit your business processes. By default, the display name of the tab is Architecture. Awb0BOMArchetypeToOccurrence Determines the instance of which particular subtype of the Awb0Element business object is created. This business object constant is a comma-separated list of item revision or GDE subtypes. Using such a list avoids the need to create a separate Awb0Element business object for each item revision type. Awp0SearchIsIndexed Indicates that the business object will be indexed for searching when this constant is set to true. This information is propagated through the business object hierarchy. For example, if ItemRevision is selected for indexing, all business objects under ItemRevision (such as Part Revision and DocumentRevision) are also indexed. Note Do not set this constant to true for the WorkspaceObject business object. This results in indexing errors. Awp0SearchIsIndexedExt Indicates that external business objects are indexed for searching. By default, the value of this constant is false, meaning that external objects are not indexed. The scope for this constant is the Awp0AWCExternalSystemObject business object, which designates objects originating in systems external to Teamcenter. To change the value to true, open the Awp0AWCExternalSystemObject business object and select the Awp0SearchIsIndexedExt business object constant on the Business Object Constants tab. Then click Edit and select the Value check box. Awp0SearchClassifySearchEnabled Enables the searching and filtering of classification data. Awp0SearchIsClassifyDataIndexed For the specified business object type and below, specifies that classification data be indexed for searching and filtering. Awp0SearchDatasetIndexingBehavior Defines the behavior of inline indexing for dataset file contents. The scope for this constant is WorkspaceObject types and their subtypes. Specify one of the following: Inline Dataset content is indexed inline with the parent business object. When a search matches dataset content, the search results return the parent business object instead of the dataset. The datasets are defined using Awp0DatasetTypeToBeIndexedInline. Relation Dataset content is indexed as part of the dataset but it maintains the reference to the parent business object. When a search matches dataset content, the search results return the dataset as well as the parent business object. The default value is Inline except for DocumentRevision, where the default is Relation. Awp0DatasetTypeToBeIndexedInline Identifies the datasets to be indexed along with the business object. The scope for this constant is WorkspaceObject types and their subtypes. Set this property only for types that are also marked for indexing and Awp0SearchDatasetIndexingBehavior is set to Inline. The format is: Copy <INHERIT | NO_INHERIT>:RelationName:DatasetTypes The keyword specifies the behavior to apply to the rule: INHERIT Applies the rule to the specified type and all its subtypes. For example, index PDX dataset content related to TC_Attaches for ItemRevision and its subtypes: INHERIT:TC_Attaches:PDF NO_INHERIT Applies the rule only to the type where the rule is defined. A rule applied to a parent is not inherited by child types. Specifying NO_INHERIT can help improve performance. NO_INHERIT:IMAN_Specification:Text You can specify one-to-many relationships between RelationName and DatasetTypes. RelationName is a relation name or the wildcard character *. Specify one or more clauses separated by commas. INHERIT: TC_Attaches: PDF, INHERIT: IMAN_Specifiation: Text INHERIT: *: PDF DatasetTypes is a dataset type. Specify one or more values separated by a tilde . INHERIT:TC_Attaches: PDFMSWordX Specifying only wildcards is not valid (for example, do not specify INHERIT: : * ). No default value is specified with the exception that SpecElementRevision is set to INHERIT: : FullText. As a best practice, do not specify all relations () for inline indexing and then subsequently try to limit inheritance by setting a subtype clause to index only a specific relation to a specific type. You can avoid inheritance by: Using NO_INHERIT to limit the scope of indexing for a specific type. For example, if all ItemRevision PDFs for any relation are being indexed inline, do not write a qualifying INHERIT rule for a subtype. For example: If an INHERIT rule for ItemRevision is defined as INHERIT::PDF, And, an INHERIT rule for an ItemRevision subtype indexes only PDFs associated with the TC_Attaches relation, Then the indexing behavior at the subtype level might not behave as expected, because you already specified all ItemRevision subtypes to index all PDFs, Configuring the subtype to override the parent. For example, to index PDX content for all the relations of the subtype, set INHERIT: *: PDX . Setting Awp0DatasetTypeToBeIndexedInline to an empty string for the subtype avoids all inheritance from the parent type. Setting Awp0SearchIsIndexed to false to turn off indexing for the type. By default, the indexing of FullText datasets is not enabled because they are indexed inline for SpecElementRevision and its subtypes. If you choose to enable indexing of FullText datasets, users see FullText and SpecElementRevision objects in search results.