Found 256 results for "features translation"
The search executed in 0.001792545 seconds. That's fast.
Gitana / 4.0 / Data Engine / Security / Access Policies / Samples / Editor of all Content in SpanishEditor of all Content in Spanish This section describes features that are coming in 4.0 JSON { "title": "Editor of all Content in Spanish", "statements": [{ "action": "grant", "roles": ["editor"], "conditions": [{ "conditions": [{ "type": "locale", "config": { "locale": "es" } }] }] }] }
Score: 1.4647049
|
|
Gitana / 3.2 / Guide / Guide / Features / BehaviorBehavior QName: f:behavior This features indicates that a node provides the implementation of a behavior. This feature simply tags the node as a behavior implementation. The node must be a script or a rule. Configuration Behavior Example { "title": "My JavaScript file", "_features": { "f:behavior": { } } }
Score: 1.4560632
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Samples / Manager of all Content in a FolderManager of all Content in a Folder This section describes features that are coming in 4.0 JSON { "title": "Manager of all Content in a Folder", "statements": [{ "action": "grant", "roles": ["manager"], "conditions": [{ "conditions": [{ "type": "path", "config": { "path": "^/my/folder/.*" } }] }] }] }
Score: 1.4560632
|
|
Gitana / 4.0 / Data Engine / Aspects / BehaviorBehavior QName: f:behavior This features indicates that a node provides the implementation of a behavior. This feature simply tags the node as a behavior implementation. The node must be a script or a rule. Configuration Behavior Example { "title": "My JavaScript file", "_features": { "f:behavior": { } } }
Score: 1.4560632
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Samples / Manager of all Content in a FolderManager of all Content in a Folder This section describes features that are coming in 4.0 JSON { "title": "Manager of all Content in a Folder", "statements": [{ "action": "grant", "roles": ["manager"], "conditions": [{ "conditions": [{ "type": "path", "config": { "path": "^/my/folder/.*" } }] }] }] }
Score: 1.4560632
|
|
Pricing: Self Managed Options - GitanaPricing: Self Managed Options - Gitana Status Releases Registry Blog Cloud CMS Platform Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Enterprise Data Engine Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Automate Automate your content creation and approval flows while taking advantage of AI services to
Score: 1.4451232
|
|
Customizing the Cloud CMS User InterfaceCloud CMS is incredibly powerful and feature rich. This is great except that in exposing all the powerful features the UI can easily appear cluttered and difficult to use. We recently added the ability to customize the UI to declutter, simplify, and make more familiar. Navigation The UI has been simplified to make navigation easier. The number of left-hand menu options has decreased because of the new “Manage Platform” and “Manage Project” sections. These two new sections have moved all of the a
Score: 1.4415002
|
|
The Gitana Blog - Page 1 - GitanaThe Gitana Blog - Page 1 - Gitana Status Releases Registry Blog Cloud CMS Platform Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Enterprise Data Engine Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Automate Automate your content creation and approval flows while taking advantage of AI services to enhan
Score: 1.4388231
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / document-subcontextdocument-subcontext [ { "evaluator": "context-document-is-datalist", "config": { "document-subcontext": { "items": [ { "key": "document", "items": [ { "key": "datalist/items", "title": "Data List Items", "uri": "{documentUri}/datalist/items" } ] } ] } } }, { "evaluator": "context-document", "config": { "doc
Score: 1.4229047
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / document-subcontextdocument-subcontext [ { "evaluator": "context-document-is-datalist", "config": { "document-subcontext": { "items": [ { "key": "document", "items": [ { "key": "datalist/items", "title": "Data List Items", "uri": "{documentUri}/datalist/items" } ] } ] } } }, { "evaluator": "context-document", "config": { "doc
Score: 1.4229047
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / NotNot This section describes features that are coming in 4.0 The not condition lets you perform a logical NOT operation against a sub-condition. Configuration { "type": "not", "config": { "condition": { ... } } } Sample #1 This policy document allows a principal to edit any content that is not in Spanish { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"], "conditions": [{ "typ
Score: 1.4143405
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / NotNot This section describes features that are coming in 4.0 The not condition lets you perform a logical NOT operation against a sub-condition. Configuration { "type": "not", "config": { "condition": { ... } } } Sample #1 This policy document allows a principal to edit any content that is not in Spanish { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"], "conditions": [{ "typ
Score: 1.4143405
|
|
Gitana / 3.2 / Guide / Guide / Actions / OCR Extract NodeOCR Extract Node This section describes features that are coming in 4.0 ID: ocrExtractNode Runs OCR Extraction against a node. { "title": "OCR Extract Node", "properties": { "serviceId": { "type": "string", "title": "Service ID" } } } Where: serviceId is the ID of an optional OCR Extraction Service to be used If serviceId is not provided, the default OCR Extraction Service for the project will be used (if available). Example { "serviceId":
Score: 1.4062812
|
|
Gitana / 4.0 / Data Engine / Behaviors / Actions / OCR Extract NodeOCR Extract Node This section describes features that are coming in 4.0 ID: ocrExtractNode Runs OCR Extraction against a node. { "title": "OCR Extract Node", "properties": { "serviceId": { "type": "string", "title": "Service ID" } } } Where: serviceId is the ID of an optional OCR Extraction Service to be used If serviceId is not provided, the default OCR Extraction Service for the project will be used (if available). Example { "serviceId":
Score: 1.4062812
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / OrOr This section describes features that are coming in 4.0 The or condition lets you perform a logical OR operation across multiple sub-conditions. Configuration { "type": "or", "config": { "conditions": [ ... subconditions ] } } Sample #1 This policy document allows a principal to read content from the /products and /images folders. { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"], "c
Score: 1.3983134
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / OrOr This section describes features that are coming in 4.0 The or condition lets you perform a logical OR operation across multiple sub-conditions. Configuration { "type": "or", "config": { "conditions": [ ... subconditions ] } } Sample #1 This policy document allows a principal to read content from the /products and /images folders. { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"], "c
Score: 1.3983134
|
|
Gitana / 3.2 / Guide / Guide / Overview_page Access Policies Actions Antivirus Scanning API API Keys Applications Application Server Attachments Auditing Authentication Binary Files Branches Bulk Import Command Line Conditions Content Modeling Cookbooks Deployment Docker Features Find Forms General GraphQL Integrations Multifactor Authentication Modules Narration Optical Character Recognition Platform Policies Projects Publishing Query Recognition Releases Reports Rules Scripting Search Security Single Sign On (SSO) Supported Stacks
Score: 1.3904353
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / TypeType This section describes features that are coming in 4.0 The type condition allows you to constrain a policy statement so that it applies to entities of a specific type. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "type", "config": { "type": "{type name}" } } Samples This policy document grants the Consumer role to all Projects. { "title": "My Sample Policy", "st
Score: 1.3749423
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / TypeType This section describes features that are coming in 4.0 The type condition allows you to constrain a policy statement so that it applies to entities of a specific type. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "type", "config": { "type": "{type name}" } } Samples This policy document grants the Consumer role to all Projects. { "title": "My Sample Policy", "st
Score: 1.3749423
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / IDID This section describes features that are coming in 4.0 The id condition allows you to constrain a policy statement so that it applies to entities that match a given ID. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "id", "config": { "id": "{value regex}" } } Samples This policy document grants the Consumer role to a specific piece of content with the ID 46ba5e0d79b83aac97e
Score: 1.3673247
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Type QNameType QName This section describes features that are coming in 4.0 The type-qname condition allows you to constrain a policy statement so that it applies to content nodes that have a matching QName. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "type-qname", "config": { "qname": "{value regex}" } } Sample #1 This policy document allows a principal to read content
Score: 1.3673247
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / IDID This section describes features that are coming in 4.0 The id condition allows you to constrain a policy statement so that it applies to entities that match a given ID. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "id", "config": { "id": "{value regex}" } } Samples This policy document grants the Consumer role to a specific piece of content with the ID 46ba5e0d79b83aac97e
Score: 1.3673247
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Type QNameType QName This section describes features that are coming in 4.0 The type-qname condition allows you to constrain a policy statement so that it applies to content nodes that have a matching QName. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "type-qname", "config": { "qname": "{value regex}" } } Sample #1 This policy document allows a principal to read content
Score: 1.3673247
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / PropertyProperty This section describes features that are coming in 4.0 The property condition allows you to constrain a policy statement so that it applies to entities where a specific property matches a value. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "property", "config": { "property": "{property name}", "value": "{property value or regex}" } } Samples This policy docu
Score: 1.3523397
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / PropertyProperty This section describes features that are coming in 4.0 The property condition allows you to constrain a policy statement so that it applies to entities where a specific property matches a value. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "property", "config": { "property": "{property name}", "value": "{property value or regex}" } } Samples This policy docu
Score: 1.3523397
|