The grouped grid appearance in universal currently differs from windows/web. Grouped columns are treated as regular grid-columns, which creates an indentation in the rows under this grouped columns.It would be nice if universal appears the same as Windows and Web in this case. Universal Windows/Web
Currently i am working on a system flow that processes a mail queue with attachments. The current SMTP-connector can give the following status codes as output. It would be nice if it can also output if it fails to find an attachment. That way I can get rid of custom file exists functions. This is the message that Indicium currently gives when I provide an invalid attachment path:
Based on a question from a client, I created this idea to support resizable multiline/HTML-fields in the form component of the Web GUI. They like to be able to resize the field themselves without opening it as pop-up.See the following image for an example: See also: https://www.w3docs.com/tools/code-editor/10938
This is an Archived topic.GoalReplace all existing file links in an end product without manually writing an update script for every table. This can be used for migrating file systems or DTAP-deployment.SolutionI wrote a script that replaces all file links of domains with control ‘File link’ and ‘File upload’. The script gathers the tables that it can update from IAM and builds an update script.Use CTRL+SHIFT+M to fill the following parameters:
Currently code history will not be filled with trunk code history by creating a branch. It would be nice if this was possible. This way you can easily do a WinMerge between versions. For example in picture 2 I cannot easily do a WinMerge between 1.11 (trunk) and 1.20 (branch).While checking the code history detail, I found out that the detail only shows data of the selected (version selector) project_id. So maybe that is the reason why you cannot see this data in that screen. A possible solution is to copy the last trunk code history record as version 1.00 of the branch while creating the branch.I also found out that trunk code history will not be filled with branch code history after the merge. This is even easier to fix, because you already know to which trunk version you are going to merge. So you can fill originated in project with the trunk project_id and originated in version with the version that is going to arise after merging to trunk. Picture 1 Picture 2
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
