Found 937 results for "conditions or"

The search executed in 0.00215462 seconds. That's fast.

Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Type QName

Type 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: 2.4891653

Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Branch

Branch This section describes features that are coming in 4.0 The branch condition allows you to constrain a policy statement so that it applies to nodes and/or associations that are on a matching branch. The branch can be matched using its ID (_doc), title or alias. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a branch by ID: { "type": "branch", "config": { "id": "{value regex}

Score: 2.4572816

Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Branch

Branch This section describes features that are coming in 4.0 The branch condition allows you to constrain a policy statement so that it applies to nodes and/or associations that are on a matching branch. The branch can be matched using its ID (_doc), title or alias. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a branch by ID: { "type": "branch", "config": { "id": "{value regex}

Score: 2.4572816

Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Project

Project This section describes features that are coming in 4.0 The project condition allows you to constrain a policy statement so that it applies to entities that are contained with a project. The project can be matched using either its ID (_doc) or its title. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a project by ID: { "type": "project", "config": { "id": "{value regex}"

Score: 2.4430585

Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Project

Project This section describes features that are coming in 4.0 The project condition allows you to constrain a policy statement so that it applies to entities that are contained with a project. The project can be matched using either its ID (_doc) or its title. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a project by ID: { "type": "project", "config": { "id": "{value regex}"

Score: 2.4430585

Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Data Store

Data Store This section describes features that are coming in 4.0 The datastore condition allows you to constrain a policy statement so that it applies to datastores and/or objects within a datastore. The datastore can be matched using its Type, ID and/or a title. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a changeset by Type: { "type": "datastore", "config": { "typeId": "{val

Score: 2.4349174

Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Data Store

Data Store This section describes features that are coming in 4.0 The datastore condition allows you to constrain a policy statement so that it applies to datastores and/or objects within a datastore. The datastore can be matched using its Type, ID and/or a title. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a changeset by Type: { "type": "datastore", "config": { "typeId": "{val

Score: 2.4349174

Gitana / 4.0 / Data Engine / Behaviors / Overview

_page Actions Conditions Policies Rules

Score: 2.349626

Gitana / 3.2 / Guide / Guide / Projects

Projects In Cloud CMS, a Project is an isolated workspace in which your team can collaborate on the production and publication of content. You can create as many Projects as you wish. Within each Project, you can: Design your content model (types, features and associations) Build out editorial forms for easy-content entry Wire up "automagic" business logic consisting of Rules, Actions and Conditions to automatically do things like call out to web hooks, send emails or sanitize your data as edito

Score: 2.2897065

Gitana / 4.0 / Data Engine / Platform / Projects

Projects In Cloud CMS, a Project is an isolated workspace in which your team can collaborate on the production and publication of content. You can create as many Projects as you wish. Within each Project, you can: Design your content model (types, features and associations) Build out editorial forms for easy-content entry Wire up "automagic" business logic consisting of Rules, Actions and Conditions to automatically do things like call out to web hooks, send emails or sanitize your data as edito

Score: 2.2897065

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Strategy

Deployment Strategy A Deployment Strategy defines the conditions by which a Deployment Package should automatically be assembled and delivered to one or more Deployment Targets. A Deployment Strategy is a recipe that tells a listener within Cloud CMS how to identify nodes whose content has changed and should be deployed. It then describes what steps to take in terms of deploying the content. If you're using Cloud CMS Publishing, you will not need to set up a Deployment Strategy by hand. The Publ

Score: 2.1392217

Gitana / 4.0 / Data Engine / Deployment / Deployment Strategy

Deployment Strategy A Deployment Strategy defines the conditions by which a Deployment Package should automatically be assembled and delivered to one or more Deployment Targets. A Deployment Strategy is a recipe that tells a listener within Cloud CMS how to identify nodes whose content has changed and should be deployed. It then describes what steps to take in terms of deploying the content. If you're using Cloud CMS Publishing, you will not need to set up a Deployment Strategy by hand. The Publ

Score: 2.1392217

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: 2.1182039

Gitana / 3.2 / Guide / Guide / Security

Security Cloud CMS lets you define enterprise-grade access control policies across all of your content to ensure and assert that the right content is being accessed by the right people at all times. To achieve this, Cloud CMS offers a security engine that incorporates multiple levels of access provisioning. These include: A Role-based, multi-level Authorization engine that asserts Permissions on every API, service and DAO method invocation. Fine-grained, object-level access control lists for spe

Score: 2.086548

Gitana / 4.0 / Data Engine / Security / Overview

Security Cloud CMS lets you define enterprise-grade access control policies across all of your content to ensure and assert that the right content is being accessed by the right people at all times. To achieve this, Cloud CMS offers a security engine that incorporates multiple levels of access provisioning. These include: A Role-based, multi-level Authorization engine that asserts Permissions on every API, service and DAO method invocation. Fine-grained, object-level access control lists for spe

Score: 2.086548

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Evaluators

Evaluators Evaluators are used to define conditions that determine whether a block of configuration should be included in the evaluated and merged configuration document. Evaluators work on different aspects of the runtime experience, including: what is being observed who is observed it what URL is being looked at what objects are known about at the time (i.e. observables) what permissions and authorities the current user has over things that are being observed There are many types of evaluators

Score: 2.037979

Gitana / 4.0 / Developers / User Interface Customization / Evaluators

Evaluators Evaluators are used to define conditions that determine whether a block of configuration should be included in the evaluated and merged configuration document. Evaluators work on different aspects of the runtime experience, including: what is being observed who is observed it what URL is being looked at what objects are known about at the time (i.e. observables) what permissions and authorities the current user has over things that are being observed There are many types of evaluators

Score: 2.037979

Terms of Service - Gitana

Terms of Service - 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 enhance and c

Score: 1.8547785

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Configuration

Configuration The configuration service evaluates a series of conditional configuration blocks and determines which blocks to keep in composing a final configuration document for the user interface. The configuration document consists of blocks that define JSON structures that are to be merged into a final JSON configuration that powers the user interface. The configuration service executes two phases - evaluate and merge. It essentially looks like this: [block1] --> --> [config1]

Score: 1.7599087

Gitana / 4.0 / Developers / User Interface Customization / Configuration

Configuration The configuration service evaluates a series of conditional configuration blocks and determines which blocks to keep in composing a final configuration document for the user interface. The configuration document consists of blocks that define JSON structures that are to be merged into a final JSON configuration that powers the user interface. The configuration service executes two phases - evaluate and merge. It essentially looks like this: [block1] --> --> [config1]

Score: 1.7599087

Gitana / 3.2 / Guide / Guide / Content Modeling / Behaviors

Behaviors Cloud CMS lets you wire in behaviors behind your content models so that rules automatically execute when your content is touched. Content editors work with simple forms to create content that conforms to your defined content models. When that content is created, updated or deleted, it automatically triggers policies (or events) which you use to bind in custom behaviors. In this way, the developers can wire up behaviors and the editorial team never needs to know about it. Furthermore, b

Score: 1.6570385

Gitana / 4.0 / Data Engine / Content Models / Behaviors

Behaviors Cloud CMS lets you wire in behaviors behind your content models so that rules automatically execute when your content is touched. Content editors work with simple forms to create content that conforms to your defined content models. When that content is created, updated or deleted, it automatically triggers policies (or events) which you use to bind in custom behaviors. In this way, the developers can wire up behaviors and the editorial team never needs to know about it. Furthermore, b

Score: 1.6570385

Gitana / 3.2 / Guide / Guide / Single Sign On (SSO) / Azure Active Directory

Azure Active Directory Azure Active Directory is a Microsoft Azure service which provides identity and access management. Cloud CMS supports single sign on with Azure AD using SAML 2.0. Set up Azure Before configuring the Cloud CMS Single Sign-On, you’ll need to set up a few things on Microsoft Azure Active Directory: Create an Azure Account If not already present, create an Azure Account using the Azure portal. Log into the portal and go to Azure Active Directory. Register your App Click New Re

Score: 1.5613155

Gitana / 4.0 / Data Engine / Authentication / Single Sign On (SSO) / Azure Active Directory

Azure Active Directory Azure Active Directory is a Microsoft Azure service which provides identity and access management. Cloud CMS supports single sign on with Azure AD using SAML 2.0. Set up Azure Before configuring the Cloud CMS Single Sign-On, you’ll need to set up a few things on Microsoft Azure Active Directory: Create an Azure Account If not already present, create an Azure Account using the Azure portal. Log into the portal and go to Azure Active Directory. Register your App Click New Re

Score: 1.5613155

Gitana / 3.2 / Guide / Guide / UI Developers Guide

UI Developers Guide The Cloud CMS user interface is an HTML / JavaScript application that comes pre-configured with a base application that is feature-complete and out-of-the-box. It includes a ready-to-run content management and collaboration tool set for managing documents, web sites, mobile content and more. It also makes some default assumptions about page layout, placement of buttons, availability of functionality and role-based provisioning that may or may not match your desired editorial

Score: 1.4006015