Show / Hide Table of Contents

# Class ServerProjectResourceAssignmentForResourceType

Represents assignments of light resources of a specific resource type to a server project.

##### Inheritance

Object
ServerProjectResourceAssignmentForResourceType

##### Syntax

    public class ServerProjectResourceAssignmentForResourceType

### Fields

#### ResourceType

The type of the resource.

##### Declaration

    public ResourceType ResourceType

##### Type

ResourceType

#### ServerProjectResourceAssignment

An array of ServerProjectResourceAssignment objects, each representing the assignment of a single resource to the involved server project. All existing assignments for resource type identified by the ResourceType member are deleted before applying the new set. Each resource has to identify a resource of type defined by the ResourceType member. The rules for different resource types are the following:

- AutoCorrect, FilterConfigs, KeyboardShortcuts: can not be assigned to server projects.
- AutoTrans: 0..N can be assigned to each target language of a server project (independently). The ObjectId has to have the three+(two) letter code of the project target language to which the specific resource is to be assigned to.
- NonTrans: 0..N can be assigned to a server project (shared for all target languages of the project. ObjectId has to be null for the assignment. If there is at least one assigned, one of them has to be marked as primary.
- IgnoreLists: 0..N can be assigned independently to each target language of a server project. The ObjectId has to be the three+(two) letter code of the project target language to which the specific resource is to be assigned to. Only IgnoreList resources with language exact matching the target language (ObjectId) of the assignment can be assigned (e.g. no resource with lang "eng" can be assigned to target lang "eng-US"). If there is at least one assigned to a target language, one of them has to be marked as primary (one for each target lang).
- SegRules: There are two options here (the first one is only for backward compatibility, the second one is the recommended):

1. Exactly one has to be assigned to a project, which defines the segmentation rules for the source language of the project. ObjectId has to be null for the assignment. In this case the deployed default segmentation rule resources will be assigned to the target languages of the project.
2. Exactly one has to be assigned to each language (source and target as well) of the project. ObjectId has to be the language code for the assignment. Only SegRule resources with language exact matching the languages of the project can be assigned (e.g. no resource with lang "eng" can be assigned to project where the lang "eng" is not the source lang of the project and "eng" is not in the target languages of the project). The default segmentation rule deployed with memoQ is automatically assigned to the server project when the project is created. To reset the assignment to this deployed default later on (if it has been changed) use an empty (full zero) guid resource ID.

- TMSettings: Exactly one has to be assigned to a project, which defines the default TM settings for the project. The ObjectId for this project default assignment has to be null. Optionally one TMSettings resource can be assigned for each TM assigned to the project (can be different for each one), that overrides the project default for the specific TM. The ObjectId has to the the guid of the TM for which the setting is to be applied. The default TMSetting resource deployed with memoQ is automatically assigned to the server project to define the project default TM settings when the project is created. To reset the assignment to this deployed default later on (if it has been changed) use an empty (full zero) guid resource ID. To remove the override setting for a specific TM simply do not provide any ServerProjectResourceAssignment object for the specific TM when setting the new assignment for resource type TMSettings.
- PathRules: Exactly two have to be assigned to a project: one defining file export path rule, and another one defining the folder export path rule. Assigning the file export use ObjectId "File", assigning the folder rule use ObjectId "Folder". The default file and folder rule deployed with memoQ are automatically assigned to the server project when the project is created. To reset the assignment to these deployed defaults later on (if it has been changed) use an empty (full zero) guid resource ID.
- QASettings: Exactly one has to be assigned to each target language of the project (independently). The ObjectId has to be the three+(two) be the letter code of the project target language to which the specific resource is to be assigned to. The default QASettings resource deployed with memoQ is automatically assigned to each target language of the server project when the project is created. To reset the assignment to this deployed default later on (if it has been changed) use an empty (full zero) guid resource ID.
- LiveDocsSettings: Exactly one has to be assigned to a project, which defines the default LiveDocs settings for the project. The ObjectId for this project default assignment has to be null. Optionally one LiveDocsSettings resource can be assigned for each LiveDocs assigned to the project (can be different for each one), that overrides the project default for the specific LiveDocs corpus. The ObjectId has to the the guid of the LiveDocs corpus for which the setting is to be applied. The default LiveDocsSettings resource deployed with memoQ is automatically assigned to the server project to define the project default LiveDocs settings when the project is created. To reset the assignment to this deployed default later on (if it has been changed) use an empty (full zero) guid resource ID. To remove the override setting for a specific LiveDocs corpus simply do not provide any ServerProjectResourceAssignment object for the specific LiveDocs corpus when setting the new assignment for resource type LiveDocsSettings.
- LQA: a single one can be assigned to a server project (shared for all target languages of the project. ObjectId has to be null for the assignment.
- MTSettings: Exactly one can be assigned to each target language of the project (independently). The ObjectId has to be the three+(two) letter code of the project target language to which the specific resource is to be assigned to.

##### Declaration

    public ServerProjectResourceAssignment[] ServerProjectResourceAssignment

##### Type

ServerProjectResourceAssignment[]