It works great. Thanks for sharing.
Original Message:
Sent: Jan 08, 2025 10:18 AM
From: Thorlund
Subject: Scripting field / area in Orchestrator
I have changed the initial example a bit. Maybe you can use it and change it for your needs. The idea and suggestion has really improved the UI for me.
The code below can be used in a single bookmarklet, which will toggle the hide/unhide of stuff in the UI. It will hide the headers, different panes, the input fields, the environment, item title etc, and the editor views will be maximized. It requires you to be on either an action or a workflow item. If not, no action is taken.
I am sure there is plenty of additions which could be made, but it takes a bit deciphering of the UI elements.
Please update the thread, if you find good stuff to add to it.
javascript: (()=>{ isHidden = document.getElementsByClassName("subnav")[0].hidden; if (!isHidden) { hide = true; schemaAreaContainerSize = "100%"; splitRightSecondPanel = "100%"; } else { hide = false; schemaAreaContainerSize = "80%"; splitRightSecondPanel = "50%"; } var url = window.location.href; if ((url.indexOf("#/action") > -1) && (url.indexOf("#/action(host") == -1)) { /* ACTION EDITOR */ document.getElementById("scriptTabBtn").click(); document.getElementsByClassName("subnav")[0].hidden = hide; document.getElementsByClassName("header-7 header ng-star-inserted")[0].hidden = hide; var scriptTabContent = document.querySelector(".script-tab-content"); var firstPanel = scriptTabContent.querySelector(".firstPanel"); var secondPanel = scriptTabContent.querySelector(".secondPanel"); var extensionTtem = scriptTabContent.querySelector(".extension-item"); secondPanel.hidden = hide; extensionTtem.hidden = hide; firstPanel.style.width = "100%"; } else if (url.indexOf("#/edit") > -1) { /* WORKFLOW EDITOR */ tab = document.getElementById("tab-edit-schema-btn"); button = document.getElementById("taskScriptingTabBtn"); if(tab.getAttribute("aria-selected") == "true" && button != null) { document.getElementById("taskScriptingTabBtn").click(); document.getElementsByClassName("subnav")[0].hidden = hide; document.getElementsByClassName("header-7 header ng-star-inserted")[0].hidden = hide; contentArea = document.querySelector(".content-area"); contentArea.style.width = "20%"; paletteContainer = contentArea.querySelector(".palette-container"); paletteContainer.hidden = hide; firstPanel = contentArea.querySelector(".firstPanel"); firstPanel.hidden = hide; expandButton = contentArea.querySelector(".collapse-element-container"); expandButton.hidden = hide; document.getElementById("parameter-pills").hidden = hide; document.getElementsByClassName("gutter gutter-horizontal ng-star-inserted")[0].hidden = hide; document.getElementsByClassName("dialog-title text-no-wrap ng-star-inserted")[0].hidden = hide; document.getElementsByClassName("actions ng-star-inserted")[0].hidden = hide; document.getElementById("workflowEditor").style.height = "100%"; document.getElementById("editorContent").style.height = "100%"; document.getElementsByClassName("schema-area-container")[0].style.width = schemaAreaContainerSize; document.getElementsByClassName("split-right secondPanel")[0].style.width = splitRightSecondPanel; } } else if (url.indexOf("#/workflow") > -1) { /* WORKFLOW VIEWER */ } else { /* ANYTHING ELSE */ }})();
Original Message:
Sent: Jan 07, 2025 04:20 AM
From: Thorlund
Subject: Scripting field / area in Orchestrator
This is really really cool. Many thanks. It should be a standard feature in the UI.
Well done!
Original Message:
Sent: Jan 06, 2025 08:36 AM
From: Thelemanu
Subject: Scripting field / area in Orchestrator
Hi, try this workaround from Krisztian. It works great. Bye.
Original Message:
Sent: Dec 13, 2024 02:53 AM
From: Thorlund
Subject: Scripting field / area in Orchestrator
Hello,
my everyday is in the Orchestrator, currently on 8.18.1. The product / editor has indeed gotten great improvements since version 8 first arrived.
But I really struggle with a development tool, where the actual development / coding is so limited. As an example, I have uploaded a picture of one of my code items. Picture is taken on a screen with resolution on 2440 x 1440 (only the right half part of the UI). The item has some input and out variables, and a monster header and footer, with pretty much no useful information, only a waste of space for the scripting area. I would consider the red areas "waste" and the green area the important stuff, which only covers 1/5 of the screen. I really lack more area to read and write code. I am so limited to this small area; I wish it could run in a separate or popped out windows, maybe even external editor.. Image there were even more variables - then I would have no option to do code..
Do any of you know how I can improve with view, or how do you do it - do you suffer with the same, or dont you see it as an issue?