Found 59 results for "introduction how-it-works workspaces"
The search executed in 9.07854E-4 seconds. That's fast.
Gitana / 3.2 / Guide / Guide / WorkspacesWorkspaces Cloud CMS offers Workspaces to provide editors with a way to create their own private and shared spaces where they can work on content without stepping on each other's toes. Workspaces are implemented using branches to provide all of those capabilities to the editorial team, including fork, merge, differencing, compare and push/pull between workspaces. Editorial users can create workspaces for any purpose they wish. Here are a few good uses of workspaces: A place to work on content th
Score: 21.110847
|
|
Gitana / 4.0 / Data Engine / Branches / WorkspacesWorkspaces Cloud CMS offers Workspaces to provide editors with a way to create their own private and shared spaces where they can work on content without stepping on each other's toes. Workspaces are implemented using branches to provide all of those capabilities to the editorial team, including fork, merge, differencing, compare and push/pull between workspaces. Editorial users can create workspaces for any purpose they wish. Here are a few good uses of workspaces: A place to work on content th
Score: 21.110847
|
|
Gitana / 3.2 / Guide / Guide / ProjectsProjects 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: 8.829912
|
|
Gitana / 4.0 / Data Engine / Platform / ProjectsProjects 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: 8.829912
|
|
Gitana / 3.2 / Guide / Guide / Getting Started / WorkspacesWorkspaces Everything you do with content is done within a workspace. When you create content or modify content definitions, it is all done inside of a workspace. Workspaces are isolated from one another so that different teams can make changes to things without stepping on each other's toes. By default, there is a master workspace where everything happens. You can create new workspaces at any time. When you create a workspace, Cloud CMS remembers the point in time when the new workspace was cre
Score: 8.755104
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / workspaces-contextworkspaces-context [ { "evaluator": "context-project", "config": { "workspaces-context": { "items": [ { "key": "project/workspaces", "title": "Workspaces", "header": true, "order": 10000, "items": [ { "key": "project/workspaces/list", "title": "List", "uri": "#/projects/{projectId}/workspaces", "iconClass": "fa fa-angle-right"
Score: 7.873457
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / workspaces-contextworkspaces-context [ { "evaluator": "context-project", "config": { "workspaces-context": { "items": [ { "key": "project/workspaces", "title": "Workspaces", "header": true, "order": 10000, "items": [ { "key": "project/workspaces/list", "title": "List", "uri": "#/projects/{projectId}/workspaces", "iconClass": "fa fa-angle-right"
Score: 7.873457
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Evaluators / project-workspaces-enabledproject-workspaces-enabled If a Project is currently being observed and has the "workspaces" feature enabled. { "evaluator": "project-workspaces-enabled" }
Score: 6.9545712
|
|
Gitana / 4.0 / Developers / User Interface Customization / Evaluators / project-workspaces-enabledproject-workspaces-enabled If a Project is currently being observed and has the "workspaces" feature enabled. { "evaluator": "project-workspaces-enabled" }
Score: 6.9545712
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / workspaces-list-item-actionsworkspaces-list-item-actions [ { "config": { "workspaces-list-item-actions": [ { "key": "switch-to-workspace", "action": "switch-to-workspace", "iconClass": "fa fa-exchange" } ] } } ]```
Score: 6.3121557
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / workspaces-list-item-actionsworkspaces-list-item-actions [ { "config": { "workspaces-list-item-actions": [ { "key": "switch-to-workspace", "action": "switch-to-workspace", "iconClass": "fa fa-exchange" } ] } } ]```
Score: 6.3121557
|
|
New reporting optionsWe’ve added some expanded reports lately: for both Workflow, as well as Logging. Since it’s introduction, workflow remains a key component of our platform. The process to define and execute various business processes in Cloud CMS is well documented. Now, you can track and analyze each step involved to streamline operations even further: Review any historical sequence of events, or those currently in-flight, to find patterns / trends / bottlenecks needing attention. Especially where system log de
Score: 3.3527837
|
|
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 Start a workflow from a ‘document’ - 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 n
Score: 3.2834063
|
|
Gitana / 4.0 / 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 Start a workflow from a ‘document’ - 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 n
Score: 3.2834063
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / workspace-subcontextworkspace-subcontext [ { "evaluator": "context-branch-is-master", "config": { "workspace-subcontext": { "items": [ { "key": "workspace/changes", "title": "Changes", "order": 20000, "header": true, "items": [ { "key": "workspace/activities", "remove": true }, { "key": "workspace/content", "remove": t
Score: 3.2692075
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / workspace-subcontextworkspace-subcontext [ { "evaluator": "context-branch-is-master", "config": { "workspace-subcontext": { "items": [ { "key": "workspace/changes", "title": "Changes", "order": 20000, "header": true, "items": [ { "key": "workspace/activities", "remove": true }, { "key": "workspace/content", "remove": t
Score: 3.2692075
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / release-subcontextrelease-subcontext [ { "evaluator": "context-workspace-has-pending-merges", "config": { "release-subcontext": { "items": [ { "key": "release/workspaces", "items": [ { "key": "release/merges", "title": "Pending Merges", "uri": "#/projects/{projectId}/releases/{releaseId}/merges", "iconClass": "fa fa-angle-right", "order": 32000 }
Score: 2.8139968
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / release-subcontextrelease-subcontext [ { "evaluator": "context-workspace-has-pending-merges", "config": { "release-subcontext": { "items": [ { "key": "release/workspaces", "items": [ { "key": "release/merges", "title": "Pending Merges", "uri": "#/projects/{projectId}/releases/{releaseId}/merges", "iconClass": "fa fa-angle-right", "order": 32000 }
Score: 2.8139968
|
|
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.8059826
|
|
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.8059826
|
|
Gitana / 3.2 / Guide / Guide / Getting Started / Instant PreviewInstant Preview All of your content changes can be instantly previewed. Cloud CMS removes the need for IT to set up additional servers or deploy changes to content. Instead, you simply work on your content and click to preview the content in real-time. The reason why this is possible is because Workspaces are layered. When you create a workspace, your new workspace is connected to a parent workspace at some point in time in the past. All of your changes are automatically layered on top of the pa
Score: 2.6553812
|
|
Gitana / 4.0 / Getting Started / Working with Content / BranchesBranches Everything you do with content is done within a workspace. When you create content or modify content definitions, it is all done inside of a workspace. Workspaces are isolated from one another so that different teams can make changes to things without stepping on each other's toes. By default, there is a master workspace where everything happens. You can create new workspaces at any time. When you create a workspace, Cloud CMS remembers the point in time when the new workspace was creat
Score: 2.6553812
|
|
Gitana / 4.0 / Getting Started / Navigating the User Interface / Instant PreviewInstant Preview All of your content changes can be instantly previewed. Cloud CMS removes the need for IT to set up additional servers or deploy changes to content. Instead, you simply work on your content and click to preview the content in real-time. The reason why this is possible is because Workspaces are layered. When you create a workspace, your new workspace is connected to a parent workspace at some point in time in the past. All of your changes are automatically layered on top of the pa
Score: 2.6553812
|
|
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.4114237
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / project-manage-contextproject-manage-context [ { "evaluator": "context-project", "config": { "project-manage-context": { "items": [ { "key": "project/manage/header", "title": "Manage", "order": 10000, "header": true, "allowAuthority": [ "collaborator", "manager" ], "items": [ { "key": "project/settings", "title": "Project Settin
Score: 2.3958652
|