Find out more about new features and improvements in the Fabasoft app.ducx 2017 June Release.
In expressions a new way of (re)declaring variables is possible using the keyword assume. The app.ducx compiler does not create a declaration for these variables in the resulting kernel expression, but it creates a few assertions regarding the presence and the dynamic value of the variable.
Redefine a variable
assume can be used to redefine the type of already available variables or parameters.
Example |
usecase OnUserAndGroup(any memberof) { expression { if (cooobj.HasAttribute(cootx, #usersurname)) { assume User coooobj; assume Group memberof; } } } |
Define a variable
Sometimes it is necessary to access variables which are available in a given scope but the app.ducx compiler does not know about them. This is very often the case in application implementations.
These can be declared by writing something like an inline parameter declaration using the keyword assume.
Example |
usecase SetReturnURL() { application { expression { assume in string sys_branchvalue; assume out ::ru; … } } } |
The address range drop-down field in the properties dialog now shows the free addresses per file.
As there are more and more keywords for complex constructs like ACLs and doc properties, the edit/synchronize functionality has been reworked and is currently only available in a very basic form. Features will be added to this functionality in the future.
Importing projects from COO files is no longer supported (as files and from the server).