Hi Pim, this can already be done by adding the keyword PERSISTED to the end of the calculated field query. [img]https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/b8e6dd63-577b-42be-8b76-8dcda560f737.png[/img] Keep in mind there are some limitations when using persisted computed columns, they must be deterministic.
When you compare it to 2018.2, 'None' might seem a bit weird. However, all types have been renamed in 2018.3 to better reflect the type of logic that is used in this task. [img]https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/6bbb79a8-c082-4f92-bb0e-7838ac18b08b.png[/img] This is why it's called 'None'.
Since the language for a user cannot be set per application, the user preferences menu shows all known languages in IAM, not just the active application. However, German and Chinese should not be present on a clean installation as default languages. We have found the root cause, this has been resolved for future versions. A hotfix has been released for 2018.3 to remove these languages (provided they are not in use by another application).
The extended property does seem to be configured correctly. However, I'm fairly certain this property only works when using IAM as meta, not SF. Can you try to sync the model to IAM and see if it works when you boot and quit the GUI on IAM?
[h3]What about drag-drop of nodes in a tree?[/h3]Similar code can be used when re-positioning nodes in a [b]hierarchical tree[/b]. When the node is dropped on a node with a different parent, the user probably wants the dragged node to be positioned under the dropped node. When the node is dropped within the same parent, only re-positioning is required. If you want users to only re-position nodes within the same parent, you can map the parent_id at the task and the drag-drop link to make the GUI check for equality. See below for the re-position task code: [code]-- Check if we didn't drop to self if @drag_tree_id = @drop_tree_id return -- Find the current order_no and parent_id of the dragged node declare @current_order_no order_no declare @current_parent_id tree_id select @current_order_no = order_no, @current_parent_id = parent_id from tree where tree_id = @drag_tree_id -- Find the desired order_no and parent_id of the dragged node declare @desired_orde
[h3]What about drag-drop [i]before[/i],[i] after[/i] and [i]between[/i] rows?[/h3]At first glance, it looks like this drag-drop is not suitable for re-positioning rows in a list. One would think this requires you to be able to drag-drop [i]before[/i], [i]after[/i] and [i]between[/i] rows. But this is not the case, depending on the source index and target index you can make a very fine guess of how the rows should be ordered after the drag-drop operation. The following code example can be used in the drag-drop task when the source- and target variant are the same. The parameters sent to the task are the following: [list] [*][b]sales_invoice_id[/b] – The sales invoice, mapped by the bound task and the drag drop link. Equality required! [*][b]drag_invoice_line_id[/b] – The dragged line, mapped by the drag drop link. [*][b]drop_invoice_line_id[/b] – The line on which the dragged line is dropped, mapped by the bound task. [/list]The task code should re-position all lines between the
Hello Florian, Version 2018.1 of the Thinkwise Platform has revised the authorisation of administrators in the Intelligent Application Manager. [url=https://office.thinkwisesoftware.com/docs/docs/iam/administrators.html]This[/url] list provides an overview of the different types of administrators and their capabilities. In your particular case, several Application owners should be configured. An Application owner cannot configure users (including him- or herself) to be Application owner for an application. Only Application administrators and Main administrators can do this. Does this answer your question?
We've added an execute-as option for SQL Server procedures, functions, CLR procedures and CLR functions in version [url=https://office.thinkwisesoftware.com/docs/blog/2018/10/07/2018_3.html#execute-as-option]2018.3[/url].
Two new connector process actions have been added: Copy file and copy folder.
Unique indexes can now be configured to exclude null values.
It is now possible to mark a stored procedure task or stored procedure subroutine to execute as an atomic transaction for SQL Server and DB2. This will affect the generated code for this stored procedure.
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.