What is the correct purpose of "inferred"? First I thought it can be used to model a little bit more generic.
For example: I want to model a "Save Record" action which takes "Database Record" elements and handles Insert/Update.
The action should be reusable for any types of "Database Record" prototype, so it shouldn't have any dependencies to a concrete dataTypeId. But even though I used "inferred" on the triggers/exits, the dataTypeId property of the triggers/exits are set to a conrete dataTypeId
Is "inferred" 'just' a comfort mechanism inside the Studio? And to achieve the described model I have to use the "Anything" datatype explicit? Is this right?
Are there plans to introduce something like Interfaces, so that one could drag e.g. the datatype "Database Record" to a trigger and the trigger therefore will accept any elements of prototype "Database Record"?
ciao, kkg
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign