Find out more about new features and improvements in the Fabasoft app.ducx 2018 September Release.
All expressions of a software component are stored in a content property of the software component from version 18.3.0 onwards. This behavior can be disabled by setting a system property for Java: -D com.fabasoft.ducx.disableexternalexpressions=true
Disable this behavior temporarily in the advanced project settings:
It is now possible to load the software component files directly without creating the XML cache files in the .references folder. The required part of the .ducxproject file looks like this:
Example |
<ns:CooPath> |
Disable this feature with <ns:Enabled>no</ns:Enabled>. <ns:CooOut> denotes a folder with component files, <ns:CooPathEntry> denotes a folder with a full Fabasoft Folio setup.
Note: For all three entries variable substitution is done, so you can use environment variables or direct values.
Audience constants are usable as part of other audience constants.
Example |
orgmodel APPDUCXSAMPLE@200.200 const audience[] OwnerAudience = [ const audience[] AdminAudience = { const audience[] ChefAudience = [ acl SampleACL { |
The business process language now supports three types of loops.
Example |
processes APPDUCXSAMPLE@200.200 { repeat reference_opt { do reference_opt { while reference_opt (whilecondition) { |
Business Processes
Coverage processing for business processes has been refined. There is no object model coverage for most properties of processes and activities any more. When a process is instantiated, the process itself and its activities are marked as covered.
Start/Stop With Expression
Start a coverage session in an expression with FSCAPPDUCX@1.1001:StartCoverage. Stop the session with FSCAPPDUCX@1.1001:StopCoverage.