Found 218 results for "policies association"
The search executed in 0.002380584 seconds. That's fast.
Gitana / 4.0 / Data Engine / Behaviors / Policies / Data List PoliciesData List Policies Data List policies provide places where you can hook in behaviors that trigger when items within a data list are operated upon. When items are added to a data list, removed from a data list or updated, these policies trigger and may fire into your custom handlers. The following policies are available: Policy QName Description p:beforeAddListItem Raised before an item is added to a list p:afterAddListItem Raised after an item is added to a list p:beforeUpdateListItem Raised bef
Score: 6.162222
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Evaluators / context-document-is-associationcontext-document-is-association If a Document is currently being observed and is an Association. { "evaluator": "context-document-is-association" }
Score: 5.287627
|
|
Gitana / 4.0 / Developers / User Interface Customization / Evaluators / context-document-is-associationcontext-document-is-association If a Document is currently being observed and is an Association. { "evaluator": "context-document-is-association" }
Score: 5.287627
|
|
Gitana / 3.2 / Guide / Guide / Content Modeling / BehaviorsBehaviors 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: 4.4063663
|
|
Gitana / 4.0 / Data Engine / Content Models / BehaviorsBehaviors 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: 4.4063663
|
|
How do I run custom validation before something is deleted?Cloud CMS provides several ways to run validation ahead of deletion. There are many use cases where this employed - such as: Preventing an Image from being deleted when it is being referenced by a live Web Page Preventing a required sub-object from being deleted Preventing something from deleted when one or more other things are referencing it or depend on it in some way Here are a few approaches which are commonly used: ## Content Model Dependencies We implement link validation via the graph. S
Score: 3.816185
|
|
How does security work in Cloud CMS?Cloud CMS provides two ways to describe access rights to things: Object-level / role-based authorities Team / role-based authorities With object-level / role-based authorities, you assign a principal (either a user or a group) a role against something. For example, you might give Joe the CONSUMER role against a content node. When Joe then interacts with the content node in the future, he will do so with the CONSUMER role which will allow him to "read" the node. With team / role-based authorities
Score: 3.7748914
|
|
Gitana / 3.2 / Guide / Guide / SecuritySecurity 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: 3.733366
|
|
Gitana / 4.0 / Data Engine / Security / OverviewSecurity 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: 3.733366
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / ConditionsConditions This section describes features that are coming in 4.0 Access Policy Conditions And Branch Changeset Data Store Feature ID Locale Not Or Path Project Property Reference Type Type QName
Score: 3.19694
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / SamplesSamples This section describes features that are coming in 4.0 Access Policy Samples Consumer of all Content Editor of all Content in Spanish Manager of all Content in a Folder
Score: 3.19694
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / ConditionsConditions This section describes features that are coming in 4.0 Access Policy Conditions And Branch Changeset Data Store Feature ID Locale Not Or Path Project Property Reference Type Type QName
Score: 3.19694
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / SamplesSamples This section describes features that are coming in 4.0 Access Policy Samples Consumer of all Content Editor of all Content in Spanish Manager of all Content in a Folder
Score: 3.19694
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / team-subcontextteam-subcontext [ { "evaluator": "context-team", "config": { "team-subcontext": { "items": [ { "key": "team", "title": "Team", "order": 1000, "header": true, "items": [ { "key": "team/view", "title": "Overview", "uri": "#/projects/{projectId}/teams/{teamId}", "order": 1000 }, { "key"
Score: 2.6768146
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / team-subcontextteam-subcontext [ { "evaluator": "context-team", "config": { "team-subcontext": { "items": [ { "key": "team", "title": "Team", "order": 1000, "header": true, "items": [ { "key": "team/view", "title": "Overview", "uri": "#/projects/{projectId}/teams/{teamId}", "order": 1000 }, { "key"
Score: 2.6768146
|
|
Enterprise Access Policies in Gitana 4.0 (Part 1)In this article, we'll take a look at Access Policies -- a powerful, new feature in Gitana 4.0 that allows organizations to set up and guarantee compliance with complex, enterprise-wide security requirements. Access Policies build upon the existing access control facilities provided which include per-object ACLs and broader, team-based ACLs. They extend those capabilities by allowing administrators to express access rights in a broad sweeping and prescriptive manner -- one that allows for custom
Score: 2.636972
|
|
Enterprise Access Policies in Gitana 4.0 (Part 2)In this article, we'll continue our series on Access Policies within Gitana. We'll take a few interesting and more complex examples of how Access Policies may be used to guarantee compliance witih enterprise security requirements. In the previous article, we left off looking at how you can grant access to content using Access Policies that are defined at either a Platform or Project-level. Platform-scoped policies can be written once and applied across all of your Projects. In this way, you can
Score: 2.5957365
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Actions / delete_access_policiesdelete_access_policies ID: delete_access_policies This pops up a modal to ask the user if they'd like to delete the specified Access Policies. Upon confirmation, the Access Policies are deleted. Sample Code var UI = require("ui"); var actionContext = {}; actionContext.data = [policyId1, policyId2]; UI.startAction(observableHolder, "delete_access_policies", actionContext, function(err) { // if something went wrong, err will contain the error // otherwise, success });
Score: 2.55385
|
|
Gitana / 4.0 / Developers / User Interface Customization / Actions / delete_access_policiesdelete_access_policies ID: delete_access_policies This pops up a modal to ask the user if they'd like to delete the specified Access Policies. Upon confirmation, the Access Policies are deleted. Sample Code var UI = require("ui"); var actionContext = {}; actionContext.data = [policyId1, policyId2]; UI.startAction(observableHolder, "delete_access_policies", actionContext, function(err) { // if something went wrong, err will contain the error // otherwise, success });
Score: 2.55385
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Actions / unassign_access_policyunassign_access_policy ID: unassign_access_policy This pops up a modal to ask the user if they'd like to unassign the specified Access Policies. Upon confirmation, the Access Policies are unassigned from the target (specified by ref). Sample Code var UI = require("ui"); var actionContext = {}; actionContext.data = [policyId1]; actionContext.ref = node.ref(); // "node://platformId/repositoryId/branchId/nodeId"; UI.startAction(observableHolder, "unassign_access_policy", actionContext, function(er
Score: 2.5281174
|
|
Gitana / 4.0 / Developers / User Interface Customization / Actions / unassign_access_policyunassign_access_policy ID: unassign_access_policy This pops up a modal to ask the user if they'd like to unassign the specified Access Policies. Upon confirmation, the Access Policies are unassigned from the target (specified by ref). Sample Code var UI = require("ui"); var actionContext = {}; actionContext.data = [policyId1]; actionContext.ref = node.ref(); // "node://platformId/repositoryId/branchId/nodeId"; UI.startAction(observableHolder, "unassign_access_policy", actionContext, function(er
Score: 2.5281174
|
|
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.5112486
|
|
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: 2.4772549
|
|
Gitana / 4.0 / Data Engine / Behaviors / Overview_page Actions Conditions Policies Rules
Score: 2.349626
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / rule-subcontextrule-subcontext [ { "config": { "rule-subcontext": { "items": [ { "key": "rule", "header": true, "title": "Rule", "items": [ { "key": "properties", "title": "Properties", "uri": "{projectUri}/rules/{documentId}", "order": 1000 }, { "key": "binding", "title": "Policies",
Score: 2.179538
|