Found 154 results for "ui version-control"
The search executed in 0.001218909 seconds. That's fast.
Gitana / 4.0 / Developers / User Interface Customization / 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.2616348
|
|
My UI modules aren't deploying. What should I check?If you're running an on-premise installation of Cloud CMS and are unable to deploy UI modules via the main user interface, here are a few tips and pointers. Things to consider: 1. When you click on the "Deploy Module" option, your a URL connection is made from the UI server back to the API server. Specifically, it invokes a POST to the route: /oneteam/modules/deploy Check your API side logs or any firewalls or proxies along the way to make sure that an API server receives this call. For example,
Score: 2.2356706
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / platform-manage-contextplatform-manage-context [ { "evaluator": "context-platform", "config": { "platform-manage-context": { "items": [ { "key": "platform/manage/header", "title": "Manage Platform", "header": true, "order": 10000, "allowAuthority": [ "owner", "manager", "admin" ], "items": [ { "key": "platform/settings",
Score: 2.1814852
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / platform-manage-contextplatform-manage-context [ { "evaluator": "context-platform", "config": { "platform-manage-context": { "items": [ { "key": "platform/manage/header", "title": "Manage Platform", "header": true, "order": 10000, "allowAuthority": [ "owner", "manager", "admin" ], "items": [ { "key": "platform/settings",
Score: 2.1814852
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / SamplesSamples In this section, we've collected sample configurations that customers and our support team refer to frequently when guiding developers down the path of building out UI extensions. To understand what is provided here, we recommend first reading up on the following: Configuration Service UI Views UI Modules The samples provided here can be included in custom modules and can also be plugged into UI Views. The following samples are provided: Developer Menu Items Releases Menu Item
Score: 2.1722505
|
|
Gitana / 4.0 / Developers / User Interface Customization / SamplesSamples In this section, we've collected sample configurations that customers and our support team refer to frequently when guiding developers down the path of building out UI extensions. To understand what is provided here, we recommend first reading up on the following: Configuration Service UI Views UI Modules The samples provided here can be included in custom modules and can also be plugged into UI Views. The following samples are provided: Developer Menu Items Releases Menu Item
Score: 2.1722505
|
|
Gitana / 3.2 / Guide / Guide / Docker / Kits / QuickstartQuickstart The Quickstart kit defines the following services: ui api mongodb elasticsearch These are connected like this: Running Use the following commands: docker-compose build --force-rm docker-compose up And then open a browser to: http://localhost To access the API directly: https://localhost:8080 docker-compose.yml version: "2" services: ui: build: ./ui networks: - cloudcms depends_on: - api env_file: - ./ui/ui.env ports: - "80:80" api:
Score: 2.1446466
|
|
Gitana / 4.0 / Self Managed / Kits / QuickstartQuickstart The Quickstart kit defines the following services: ui api mongodb elasticsearch These are connected like this: Running Use the following commands: docker-compose build --force-rm docker-compose up And then open a browser to: http://localhost To access the API directly: https://localhost:8080 docker-compose.yml version: "2" services: ui: build: ./ui networks: - cloudcms depends_on: - api env_file: - ./ui/ui.env ports: - "80:80" api:
Score: 2.1446466
|
|
Gitana / 4.0 / Self Managed / UI Extensions / OverviewUI Extensions The Docker-based Cloud CMS UI provides additional extension patterns beyond the AMD-driven mechanism for user interface components and screens. Since Docker allows you to run on-premise, you can use these extension patterns to influence more foundational changes to the way the application works. Environment Variables When the Cloud CMS user interface starts up, it looks to environment variables to tell it whether there are any extensions available to be loaded. Extensions are store
Score: 2.0879831
|
|
Gitana / 3.2 / Guide / Guide / Docker / Kits / API ClusterAPI Cluster The api-cluster kit defines the following services: ui api1 api2 apilb mongodb elasticsearch This kit differs from the quickstart in how it handles API requests. Requests are sent to the apilb container which runs a load balancer, distributing work between api1 and api2. It is worth reviewing the cluster settings for both of your api servers in order for them to correctly communicate. Running Use the following commands: docker-compose build --force-rm docker-compose up And then open
Score: 2.0409074
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Actions / change-passwordchange-password ID: change-password This action brings up a modal that provides a logged in user with a means to change their own password. Sample Code var UI = require("ui"); var actionContext = {}; actionContext.user = observableHolder.observable("user").get(); UI.startAction(observableHolder, "change-password", actionContext, function(err) { // all done });
Score: 2.017838
|
|
Gitana / 4.0 / Developers / User Interface Customization / Actions / change-passwordchange-password ID: change-password This action brings up a modal that provides a logged in user with a means to change their own password. Sample Code var UI = require("ui"); var actionContext = {}; actionContext.user = observableHolder.observable("user").get(); UI.startAction(observableHolder, "change-password", actionContext, function(err) { // all done });
Score: 2.017838
|
|
Gitana / 3.2 / Guide / Guide / Content Modeling / Content Model Builder / Create A New Content TypeCreate A New Content Type In the Content Model Builder, you can create a new Content Type. Click button "Create Content Type" near the top left: Then give your content type a name in the pop up modal: Hit "Create" and the new content model will open in the Content Model Builder: As you can see there are two tabs -- "UI" and "JSON". Cloud CMS provides you with two ways to build in the content type builder. If you are an editor and fancy building it with simple actions like drag and drop, UI build
Score: 2.0148833
|
|
Gitana / 4.0 / Data Engine / Content Models / Content Model Builder / Create A New Content TypeCreate A New Content Type In the Content Model Builder, you can create a new Content Type. Click button "Create Content Type" near the top left: Then give your content type a name in the pop up modal: Hit "Create" and the new content model will open in the Content Model Builder: As you can see there are two tabs -- "UI" and "JSON". Cloud CMS provides you with two ways to build in the content type builder. If you are an editor and fancy building it with simple actions like drag and drop, UI build
Score: 2.0148833
|
|
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: 2.0130856
|
|
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.0041456
|
|
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.0041456
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Actions / assign_access_policyassign_access_policy ID: assign_access_policy Brings up a popup modal that lets the user select an access policy using an Access Policy Picker. The selected access policy is handed back on the callback. Sample Code var UI = require("ui"); var actionContext = {}; actionContext.ref = node.ref(); // "node://platformId/repositoryId/branchId/nodeId"; UI.startAction(observableHolder, "assign_access_policy", actionContext, function(err) { // if something went wrong, err will contain the error
Score: 1.9906378
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Actions / create_access_policycreate_access_policy ID: create_access_policy Brings up a multi-step wizard that guides a user through the process of creating an Access Policy. The resulting access policy is handed back in the callback. Sample Code var UI = require("ui"); var actionContext = {}; UI.startAction(observableHolder, "create_access_policy", actionContext, function(err, accessPolicyId) { // if something went wrong, err will contain the error // otherwise, success // the created access policy ID is hand
Score: 1.9906378
|
|
Gitana / 4.0 / Developers / User Interface Customization / Actions / assign_access_policyassign_access_policy ID: assign_access_policy Brings up a popup modal that lets the user select an access policy using an Access Policy Picker. The selected access policy is handed back on the callback. Sample Code var UI = require("ui"); var actionContext = {}; actionContext.ref = node.ref(); // "node://platformId/repositoryId/branchId/nodeId"; UI.startAction(observableHolder, "assign_access_policy", actionContext, function(err) { // if something went wrong, err will contain the error
Score: 1.9906378
|
|
Gitana / 4.0 / Developers / User Interface Customization / Actions / create_access_policycreate_access_policy ID: create_access_policy Brings up a multi-step wizard that guides a user through the process of creating an Access Policy. The resulting access policy is handed back in the callback. Sample Code var UI = require("ui"); var actionContext = {}; UI.startAction(observableHolder, "create_access_policy", actionContext, function(err, accessPolicyId) { // if something went wrong, err will contain the error // otherwise, success // the created access policy ID is hand
Score: 1.9906378
|
|
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: 1.9839518
|
|
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: 1.9839518
|
|
API Max Heap recommendationWhat is the recommended Xmx value for running the API service? The 2GB setting on the On-Premise "quickstart" distribution is a default for development usage. In production, we recommend putting as much memory as you can. Essentially, the API should use as much memory as is allocated to the API docker container. We usually ask customers to consider an M class large instance type (something on the order of 7.5GB of RAM per API). The UI can use considerably less. For the UI, a 2GB allocation is fi
Score: 1.9511849
|
|
Gitana / 3.2 / Guide / Guide / Docker / Maintenance / Health Check / Load BalancersHealth Check / Load Balancers In a production configuration of Cloud CMS, you will want to have a load balancer (LB) in front of both your API and UI clusters. You should have one load balancer for the API cluster and one load balancer for the UI cluster. Each load balancer is responsible for receiving requests from the outside world and efficiently distributing those requests to the N servers that make up each cluster. Load balancers use a number of strategies to try to determine which servers
Score: 1.9106088
|