|
New semantic for agent relationship in inheritance hierarchies
Now, an agent class inherits the visibility of its ascendant agent classes. Descendant agent classes can add elements to an interface, which have not been added in the interface of its ascendant class, in order to extend the visibility over a server class.
It will not be possible to remove permissions on elements that have been added in the interface of its ascendant class.
In addition, Horizontal Visibility formulas can be redefined by means of the new “Redefinition” mark. If the “Redefinition” mark is checked and the Horizontal Visibility formula is redefined to empty, then no restriction is applied over the population of the server class, regardless of the Horizontal Visibility formula defined in ascendant classes over the same server class. If the Horizontal Visibility formula is not redefined then the ascendant class Horizontal Visibility formula is applied.

Figure 1: Agents tab for a class with ascendant agent classes
Selection of agents in inheritance hierarchies for Views
Analysts can select the interfaces of the agents that will be able to log in to the final application for that view. Besides, if the agent belongs to an inheritance net, the Analyst can choose if this agent can log in or not, independently if its ascendant class have been included or not in “Selected agents” list of that view.
Agents that do not have inheritance relationships are always in the selected agents list and cannot be removed from it.

Figure 2 Selected agents in a view
For more information about this feature:
Download Feature Overview Inheritance of Agents permissions at runtime >>
Log audit info
Now on, Business Logic Transformation Engine can include code to generate audit info (who did what when) to log files. A default implementation is provided which can be easily customized so as to define the name and location of the log files and to define for which users performing what operations audit info is to be logged. Please refer to the corresponding “How-to” document to learn how to perform the customization.
In order to activate this feature, a new option in the OLIVANOVA STAR Client profile for this transformation engine has been provided. This new option is called “Generate audit logs” and its value is set by default to “No”. Changing it to “Yes” will add this feature to the generated code.

Figure 3 Generate audit logs option in OLIVANOVA STAR Client tool
For more information about this feature:
Download Feature Overview Audit and Log file>>
User Interface Transformation Engines generate only the application code accessible from the selected model View
Now on, the application code generated from any User Interface Transformation Engine will be only the code accessible from the model View selected in the “View” option of the OLIVANOVA STAR Client tool.

Figure 4 View option in OLIVANOVA STAR Client tool
For more information about this feature:
Download Feature Overview Restict to View >>
Reset password functionality
Now, a “SetPassword” event is added to agent classes. In inheritance hierarchies, this “SetPassword” event is only added to the most ascendant agent class. With this event, it is possible to initialize the password of Users, in the final application.
|