You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dyn/documentai_v1.projects.locations.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -130,7 +130,7 @@ <h3>Method Details</h3>
130
130
"allowCreation": True or False, # Whether the processor type allows creation. If true, users can create a processor of this processor type. Otherwise, users need to request access.
131
131
"availableLocations": [ # The locations in which this processor is available.
132
132
{ # The location information about where the processor is available.
133
-
"locationId": "A String", # The location id, refer to [regional and multi-regional support](/document-ai/docs/regions) for supported locations.
133
+
"locationId": "A String", # The location ID. For supported locations, refer to [regional and multi-regional support](/document-ai/docs/regions).
134
134
},
135
135
],
136
136
"category": "A String", # The processor category, used by UI to group processor types.
Copy file name to clipboardExpand all lines: docs/dyn/documentai_v1.projects.locations.processorTypes.html
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -110,7 +110,7 @@ <h3>Method Details</h3>
110
110
"allowCreation": True or False, # Whether the processor type allows creation. If true, users can create a processor of this processor type. Otherwise, users need to request access.
111
111
"availableLocations": [ # The locations in which this processor is available.
112
112
{ # The location information about where the processor is available.
113
-
"locationId": "A String", # The location id, refer to [regional and multi-regional support](/document-ai/docs/regions) for supported locations.
113
+
"locationId": "A String", # The location ID. For supported locations, refer to [regional and multi-regional support](/document-ai/docs/regions).
114
114
},
115
115
],
116
116
"category": "A String", # The processor category, used by UI to group processor types.
@@ -146,7 +146,7 @@ <h3>Method Details</h3>
146
146
"allowCreation": True or False, # Whether the processor type allows creation. If true, users can create a processor of this processor type. Otherwise, users need to request access.
147
147
"availableLocations": [ # The locations in which this processor is available.
148
148
{ # The location information about where the processor is available.
149
-
"locationId": "A String", # The location id, refer to [regional and multi-regional support](/document-ai/docs/regions) for supported locations.
149
+
"locationId": "A String", # The location ID. For supported locations, refer to [regional and multi-regional support](/document-ai/docs/regions).
150
150
},
151
151
],
152
152
"category": "A String", # The processor category, used by UI to group processor types.
Copy file name to clipboardExpand all lines: docs/dyn/documentai_v1beta3.projects.locations.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -130,7 +130,7 @@ <h3>Method Details</h3>
130
130
"allowCreation": True or False, # Whether the processor type allows creation. If true, users can create a processor of this processor type. Otherwise, users need to request access.
131
131
"availableLocations": [ # The locations in which this processor is available.
132
132
{ # The location information about where the processor is available.
133
-
"locationId": "A String", # The location id, refer to [regional and multi-regional support](/document-ai/docs/regions) for supported locations.
133
+
"locationId": "A String", # The location ID. For supported locations, refer to [regional and multi-regional support](/document-ai/docs/regions).
134
134
},
135
135
],
136
136
"category": "A String", # The processor category, used by UI to group processor types.
Copy file name to clipboardExpand all lines: docs/dyn/documentai_v1beta3.projects.locations.processorTypes.html
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -110,7 +110,7 @@ <h3>Method Details</h3>
110
110
"allowCreation": True or False, # Whether the processor type allows creation. If true, users can create a processor of this processor type. Otherwise, users need to request access.
111
111
"availableLocations": [ # The locations in which this processor is available.
112
112
{ # The location information about where the processor is available.
113
-
"locationId": "A String", # The location id, refer to [regional and multi-regional support](/document-ai/docs/regions) for supported locations.
113
+
"locationId": "A String", # The location ID. For supported locations, refer to [regional and multi-regional support](/document-ai/docs/regions).
114
114
},
115
115
],
116
116
"category": "A String", # The processor category, used by UI to group processor types.
@@ -146,7 +146,7 @@ <h3>Method Details</h3>
146
146
"allowCreation": True or False, # Whether the processor type allows creation. If true, users can create a processor of this processor type. Otherwise, users need to request access.
147
147
"availableLocations": [ # The locations in which this processor is available.
148
148
{ # The location information about where the processor is available.
149
-
"locationId": "A String", # The location id, refer to [regional and multi-regional support](/document-ai/docs/regions) for supported locations.
149
+
"locationId": "A String", # The location ID. For supported locations, refer to [regional and multi-regional support](/document-ai/docs/regions).
150
150
},
151
151
],
152
152
"category": "A String", # The processor category, used by UI to group processor types.
"displayName": "A String", # User defined name for the type.
117
117
"entityTypeMetadata": { # Metadata about an entity type. # Metadata for the entity type.
118
-
"inactive": True or False, # Whether the entity type should be considered as "inactive".
118
+
"inactive": True or False, # Whether the entity type should be considered inactive.
119
119
},
120
120
"enumValues": { # Defines the a list of enum values. # If specified, lists all the possible values for this entity. This should not be more than a handful of values. If the number of values is >10 or could change frequently use the `EntityType.value_ontology` field and specify a list of all possible values in a value ontology file.
121
121
"values": [ # The individual values that this enum values type can include.
122
122
"A String",
123
123
],
124
124
},
125
-
"name": "A String", # Name of the type. It must be unique within the schema file and cannot be a "Common Type". The following naming conventions are used: - Use `snake_casing` - Name matching is case-sensitive - Maximum 64 characters. - Must start with a letter. - Allowed characters: ASCII letters `[a-z0-9_-]`. (For backward compatibility internal infrastructure and tooling can handle any ascii character) - The `/` is sometimes used to denote a property of a type. For example `line_item/amount`. This convention is deprecated, but will still be honored for backward compatibility.
125
+
"name": "A String", # Name of the type. It must be unique within the schema file and cannot be a "Common Type". The following naming conventions are used: - Use `snake_casing`. - Name matching is case-sensitive. - Maximum 64 characters. - Must start with a letter. - Allowed characters: ASCII letters `[a-z0-9_-]`. (For backward compatibility internal infrastructure and tooling can handle any ascii character.) - The `/` is sometimes used to denote a property of a type. For example `line_item/amount`. This convention is deprecated, but will still be honored for backward compatibility.
126
126
"properties": [ # Description the nested structure, or composition of an entity.
127
127
{ # Defines properties that can be part of the entity type.
128
128
"name": "A String", # The name of the property. Follows the same guidelines as the EntityType name.
"displayName": "A String", # User defined name for the type.
168
168
"entityTypeMetadata": { # Metadata about an entity type. # Metadata for the entity type.
169
-
"inactive": True or False, # Whether the entity type should be considered as "inactive".
169
+
"inactive": True or False, # Whether the entity type should be considered inactive.
170
170
},
171
171
"enumValues": { # Defines the a list of enum values. # If specified, lists all the possible values for this entity. This should not be more than a handful of values. If the number of values is >10 or could change frequently use the `EntityType.value_ontology` field and specify a list of all possible values in a value ontology file.
172
172
"values": [ # The individual values that this enum values type can include.
173
173
"A String",
174
174
],
175
175
},
176
-
"name": "A String", # Name of the type. It must be unique within the schema file and cannot be a "Common Type". The following naming conventions are used: - Use `snake_casing` - Name matching is case-sensitive - Maximum 64 characters. - Must start with a letter. - Allowed characters: ASCII letters `[a-z0-9_-]`. (For backward compatibility internal infrastructure and tooling can handle any ascii character) - The `/` is sometimes used to denote a property of a type. For example `line_item/amount`. This convention is deprecated, but will still be honored for backward compatibility.
176
+
"name": "A String", # Name of the type. It must be unique within the schema file and cannot be a "Common Type". The following naming conventions are used: - Use `snake_casing`. - Name matching is case-sensitive. - Maximum 64 characters. - Must start with a letter. - Allowed characters: ASCII letters `[a-z0-9_-]`. (For backward compatibility internal infrastructure and tooling can handle any ascii character.) - The `/` is sometimes used to denote a property of a type. For example `line_item/amount`. This convention is deprecated, but will still be honored for backward compatibility.
177
177
"properties": [ # Description the nested structure, or composition of an entity.
178
178
{ # Defines properties that can be part of the entity type.
179
179
"name": "A String", # The name of the property. Follows the same guidelines as the EntityType name.
@@ -216,14 +216,14 @@ <h3>Method Details</h3>
216
216
],
217
217
"displayName": "A String", # User defined name for the type.
218
218
"entityTypeMetadata": { # Metadata about an entity type. # Metadata for the entity type.
219
-
"inactive": True or False, # Whether the entity type should be considered as "inactive".
219
+
"inactive": True or False, # Whether the entity type should be considered inactive.
220
220
},
221
221
"enumValues": { # Defines the a list of enum values. # If specified, lists all the possible values for this entity. This should not be more than a handful of values. If the number of values is >10 or could change frequently use the `EntityType.value_ontology` field and specify a list of all possible values in a value ontology file.
222
222
"values": [ # The individual values that this enum values type can include.
223
223
"A String",
224
224
],
225
225
},
226
-
"name": "A String", # Name of the type. It must be unique within the schema file and cannot be a "Common Type". The following naming conventions are used: - Use `snake_casing` - Name matching is case-sensitive - Maximum 64 characters. - Must start with a letter. - Allowed characters: ASCII letters `[a-z0-9_-]`. (For backward compatibility internal infrastructure and tooling can handle any ascii character) - The `/` is sometimes used to denote a property of a type. For example `line_item/amount`. This convention is deprecated, but will still be honored for backward compatibility.
226
+
"name": "A String", # Name of the type. It must be unique within the schema file and cannot be a "Common Type". The following naming conventions are used: - Use `snake_casing`. - Name matching is case-sensitive. - Maximum 64 characters. - Must start with a letter. - Allowed characters: ASCII letters `[a-z0-9_-]`. (For backward compatibility internal infrastructure and tooling can handle any ascii character.) - The `/` is sometimes used to denote a property of a type. For example `line_item/amount`. This convention is deprecated, but will still be honored for backward compatibility.
227
227
"properties": [ # Description the nested structure, or composition of an entity.
228
228
{ # Defines properties that can be part of the entity type.
229
229
"name": "A String", # The name of the property. Follows the same guidelines as the EntityType name.
0 commit comments