System Settings Configuration - Designer Page
Description
The LogicNets system provides a settings file in which you configure basic configuration settings for the Designer. You can change this file to configure it more specifically for your company and LogicNets-based applications.
Designer Configuration
This contains settings for the following topics:
- User role in designer
- admin
- user (no access to underlying code text)
- Category scope
- [To be defined]
- Generate project meta XML file
- check this box to generate an XML output of the project during the publish process
- Code validation language
- LUA4
- LUA5
- Mixed
- Designer Profiles (Release 8.1)
- Via uploaded configuration file(s), different filters can be used to hide configuration options in the form parts and process menu, for instance to create more streamlined part editors specific to the client, use case, or role. See this article for more information.
- Also note that via the Framework, the Node Toolbox can be customized for the same purpose. See this article for more information.
- Task Management
- Tasks can be sourced locally (in the data.db) OR using JIRA.
When using JIRA, the tasks are read from Atlassian JIRA software.
This requires that the user is logged in via a JIRA IdP otherwise an error message is shown
Jira Atlassian API Base url is provided by the client's JIRA settings (This URL is different for every tenant in JIRA).
Jira Atlassian JQL filter using to retrieve issues can be copied from the URL created within JIRA's filtering tool
The default shows tasks assigned to the current JIRA user in the current Sprint, and not having status of Resolved, REJECT, Duplicate or Done. See JIRA documentation for more information on filtering of JIRA tasks.
Jira Atlassian URL to browse an issue can be copied from the JIRA installation
- Tasks can be sourced locally (in the data.db) OR using JIRA.
Further Notes on Task Management
The above configuration items and others below can be added or edited directly to the company settings.cfg file in the _designer context.
Config item |
Default value |
Description |
CURRENT_TASK_PATH |
taskspane.current_task.key |
Location in the designer context where the activated task key is stored (used by the changelog functionality to link a changelog to a task) |
CURRENT_TASK_SUMMARY_PATH |
taskspane.current_task.summary |
Location in the designer context where the activated task summary is stored (used by the changelog functionality to link a changelog to a task) |
CURRENT_TASK_SOURCE_PATH |
taskspane.current_task.source |
Location in the designer context where the activated task source (e.g., JIRA or local) is stored (used by the changelog functionality to link a changelog to a task) |
CURRENT_TASK_URL_PATH |
taskspane.current_task.url |
Location in the designer context where the activated task URL (URL to open the task details) is stored (used by the changelog functionality to link a changelog to a task) |
JIRA_API_URL |
URL of JIRA API. This URL is different for every tenant in JIRA. |
|
JIRA_BROWSE_URL |
URL of JIRA Web portal. This URL is different for every tenant in JIRA. |
|
JIRA_GET_TASKS_JQL |
Search filter URL e.g.
|
JIRA Query to select tasks that must be listed in the JIRA task pane |
STRICT_TASK_MODE |
0 |
0 = Allow editing of the projects without activating a task 1 = Requires an activated task to allow editing of the projects |