Found 166 results for "resources publishing"
The search executed in 0.002039908 seconds. That's fast.
|
Gitana / 3.2 / Guide / Guide / Deployment / Deployment StrategyDeployment 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: 3.6045268
|
|
|
Gitana / 3.2 / Guide / Guide / Deployment / Deployment MappingsDeployment Mappings The following Deployment Handlers supports the deployment of resources from Cloud CMS to files or file system equivalents: S3 Deployment Handler File System Deployment Handler FTP Deployment Handler These Deployment Handlers all have the common function. They must work with content from Cloud CMS, consisting of Nodes, Associations, binary attachments and a potentially complex content graph of relationships. They must take that content and then map it down into a file system c
Score: 3.5479264
|
|
|
Gitana / 3.2 / Guide / Guide / Publishing / PublicationsPublications Publications tell the system whenever content on the "master" branch goes into the "live" state, it should be pushed out to the deployment target. Once you Add a Publication to the Project, the content from the Selected Branch will be published to the Selected Deployment Target and its Lifecycle State will change to Live. To Add Publication: Go to Manage Project Publication Settings Click on Publications Click on Add a Publication Select the Branch whose content you wish to deploy t
Score: 3.5349655
|
|
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: 3.5092487
|
|
|
Gitana / 4.0 / Developers / API / Resources / accessPolicy / List the assigned targetsList the assigned targets Finds all of the resources that are assigned targets of this access policy. The targets are returned as references which identify resources that are bestowed the grants and revokes indicated by the policy. The targets are generally Users, Groups or Teams. This method supports pagination.
Score: 2.8501453
|
|
|
Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Web HookWeb Hook Type: webhook This handler makes an HTTP(S) POST to a remote web service. It automatically passes along any relevant information about the workflow, task or transition so that your web service can get to work. The config for this handler looks like this: { "url": "http://myserver:port/controller" } In addition, you can supply username and password properties in support of Basic authentication to your listener endpoint: { "url": "http://myserver:port/controller", "username":
Score: 2.8193312
|
|
|
Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Web HookWeb Hook Type: webhook This handler makes an HTTP(S) POST to a remote web service. It automatically passes along any relevant information about the workflow, task or transition so that your web service can get to work. The config for this handler looks like this: { "url": "http://myserver:port/controller" } In addition, you can supply username and password properties in support of Basic authentication to your listener endpoint: { "url": "http://myserver:port/controller", "username":
Score: 2.8193312
|
|
|
Gitana / 3.2 / Guide / Guide / Publishing / Preview ServersPreview Servers Before your changes go to Live website i.e. on the Production mode, to discover problems and fix them right away you can set up the Preview Servers and review the content changes instantly. You can look at the default Preview Servers under Manage Project : The default servers are Authoring and Production and are setup to a sample URL which can be modified with your website URL or some API or an Application. To add your Custom Server, you can click on Add Preview Server and set-up
Score: 2.8041325
|
|
Assessing the CMS cost options?The risks and costs associated with CMSs can be frightening. Many organizations have entered a CMS project, and are still to come out. Frustrated by the on-going costs of getting the CMS to work and then the costs of keeping it working. Partly this is due to unrealistic expectations but the primary reason is not looking at all the costs upfront and assessing the resources available to support a complex IT initiative. A basic for assessing your immediate and ongoing costs for any application is w
Score: 2.7373004
|
|
|
Gitana / 3.2 / Guide / Guide / User Interface / WorkflowWorkflow Cloud CMS provides an enterprise workflow engine that lets teams work together via coordinated tasks. A workflow is a customizable business process that you define and describes a series of steps and activities to be performed by your team members. Workflows are generally used to control the lifecycle state (approval and rejection) of one or more content items or documents. With workflow in place, documents are routed from user to user. Users optionally receive notifications via email a
Score: 2.6012971
|
|
|
Gitana / 4.0 / User Interface / Workflow / OverviewWorkflow Cloud CMS provides an enterprise workflow engine that lets teams work together via coordinated tasks. A workflow is a customizable business process that you define and describes a series of steps and activities to be performed by your team members. Workflows are generally used to control the lifecycle state (approval and rejection) of one or more content items or documents. With workflow in place, documents are routed from user to user. Users optionally receive notifications via email a
Score: 2.6012971
|
|
|
Use Case: Healthcare - GitanaUse Case: Healthcare - 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 a
Score: 2.5560985
|
|
|
Gitana / 3.2 / Guide / Guide / Publishing / WorkflowWorkflow Cloud CMS lets you define your own Workflows and choose them for the Publish and Unpublish activities. Each activity like Publish and Unpublish will have a Workflow Model which will have a set of instructions on how the contents should be routed during each activity. The default Workflow models we use for the Publish activity is Simple Publish and for the Unpublish activity is Simple Unpublish. You can add your own Workflows and customize your publish and unpublish activities.
Score: 2.517066
|
|
|
Requirements for CMS PublishingWhat does "publish" mean? In a CMS, publishing means moving content from a draft state to a published version. It will update the content on the published target(s) with the changes made since the last publish date. This sounds simple enough but the requirements for publishing are usually far more complex and interesting. What Publishing must do Publish must work Seems like this is stating the obvious but it is critical. Must be able to confidently publish desired content to the right place and
Score: 2.468206
|
|
|
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.4228783
|
|
|
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.36617
|
|
|
Return On Investment (ROI) with Cloud CMSROI and Content Management Systems (CMS) are rarely used in the same sentence due to the uncomfortable pricing models from all legacy CMS vendors - as well as the spiraling costs of implementing them. Often so much investment has been made in the CMS that changing is not a realistic consideration. This negativity only increases when you start using the term Enterprise Content Management (ECM), where suddenly vendors start seeing dollar signs, but offer no additional functionality e.g., Alfresco,
Score: 2.3553648
|
|
|
Gitana / 4.0 / Getting Started / Publishing / OverviewPublishing Cloud CMS brings together several power components to offer publishing of content to your live web sites and applications: Workspaces allow individuals and teams to work together without stepping on each other's toes Workflow provides managers with the tools to review and approve content Instant Preview allows reviewers to see how content changes would impact their live site Completed and approved content can be published to release snapshots or can be copied to target projects on eit
Score: 2.2922537
|
|
How to unpublish contentCloud CMS provides a range of options for making content available to your presentation tier. The most common scenarios are: 1) Use the Publishing setup within Cloud CMS; Workflow, Lifecycle states, deployment configurations. https://www.cloudcms.com/documentation/welcome/publishing.html With Publishing Enabled for a project, there are 2 simple workflows: `simple publish` and `simple unpublish`. See the Publishing example for further details: https://www.cloudcms.com/documentation/publishing/exa
Score: 2.28426
|
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / project-contextproject-context [ { "evaluator": "context-project", "config": { "project-context": { "items": [ { "key": "project/developers/heading", "title": "Developers", "order": 10000, "header": true, "allowAuthority": [ "manager" ], "items": [ { "key": "project/developers/query", "title": "Query", "uri": "#/project
Score: 2.2643647
|
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / project-contextproject-context [ { "evaluator": "context-project", "config": { "project-context": { "items": [ { "key": "project/developers/heading", "title": "Developers", "order": 10000, "header": true, "allowAuthority": [ "manager" ], "items": [ { "key": "project/developers/query", "title": "Query", "uri": "#/project
Score: 2.2643647
|
|
|
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: 2.2446847
|
|
|
Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / Local Deployment HandlerLocal Deployment Handler Handles the deployment of one or more Deployment Packages to a local Deployment Receiver. The deployment receiver must exist on the same Cloud CMS platform. It is identified by the receiverId property. The Deployment Packages will be handed to the Deployment Receiver and then processed from there. The Deployment Receiver may elect to pass those Deployment Packages down to its own configured targets or process them through additional rules priority to delivery. Configurat
Score: 2.2374444
|
|
|
Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / Local Deployment HandlerLocal Deployment Handler Handles the deployment of one or more Deployment Packages to a local Deployment Receiver. The deployment receiver must exist on the same Cloud CMS platform. It is identified by the receiverId property. The Deployment Packages will be handed to the Deployment Receiver and then processed from there. The Deployment Receiver may elect to pass those Deployment Packages down to its own configured targets or process them through additional rules priority to delivery. Configurat
Score: 2.2374444
|
|
|
Gitana / 3.2 / Guide / Guide / User Interface / Workflow / How to Start a WorkflowHow to Start a Workflow Note: 1. A Workflow model is defined at Platform level and is available within all projects 2. See workflow video: https://gitana.io/resources/introduction-to-workflow.html Example There are a number ways to start a workflow. Here is just one: open a document Click 'Workflows' and then ‘+Start Workflow’ This will bring up the Start Workflow Form. Complete the fields in the form. Notes: In our example, the Adhoc Workflow, you will need another person/member in the project
Score: 2.1987376
|