When you have created / adjusted functionality and as a consequence also created a unit test, the functionality can be send to the review process. Also, you can see the (results of) the linked unit tests.At the moment, the unit test itself is not a part of the review process. To improve quality, I suggest to make unit tests be part of the review process.
When double clicking on a row in a detail, you now will open a new main document with that detail. Sometimes it is useful when this new document becomes floating, so one can check some data on this document and the original document. To help the user minimise mouse clicking, we would like the document to be floating directly.I suggest to make this option configurable in the model, so the developer can configure on a subject how the zoom action will be performed.For now it is a hard way to model this:for each detail one would like to have this functionality is needed:a task containing the primary key of the subject, add it as a table task, with double click on record “on”a process flow, with the tab task as starting point. A process action opening the document required, and a process action to filter the new document to the requested primary keyAlso, the main screen type of the subject should be the zoom screen type, in order to get the result needed. One even might have to create a va
Already have an account? Login
Enter your 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.