IF_ELSE operator:
New "IF ... ELSE ..." flow control operator available in transaction/operation formulas. The syntax of this operator is as follows:

IF ( condition )
{
  Sequence of actions
}
ELSE
{
  Sequence of actions
}

The "ELSE" part is optional.

Now, in transactions marked as "New", "Guards" are not allowed before a creation action because they do not ensure to be mutually exclusive. Using the IF_ELSE operator it is possible to ensure that one and only one alternative is fulfilled.

AGENT_ClassName:
AGENT_ClassName allows to access to the connected agent in formulas. Until now, the information of the connected agent was an implicit part in the context of a query or a service execution. From now on, in order to treat agents explicitly, words AGENT_ClassName can already be used in formulas to access to the information of the connected agent, where ClassName represents any agent class in the model. In case the connected agent is not an instance of the class ClassName the word AGENT_ClassName will be evaluated to NULL.

Figure 1: Example of new Help Dialog with Agents tab information

Navigational filtering in Hierarchical Actions Tree nodes:
Now, the Analyst can define a Navigational Filtering formula for a hierarchy node which references a Population Interaction Unit or a Master-Detail Interaction Unit, with a Population IU as master.

Figure 2 Navigational filtering in a HAT node

Visibility on outbound arguments in the Service Interaction Unit:
Now, in a Service Interaction Unit, it is possible to select which outbound arguments of the service will be shown to the user after the service is executed and in which order they will appear.

Figure 3: Example of where to define the outbound arguments visibility

• Arguments in creation events of Legacy Views: Creation (New) events defined in legacy views do not contain anymore implicit arguments from attributes or relationships. Consequently, the “Request upon creation” check has been removed from the Attributes tab, in the legacy view edit dialog. Furthermore, when a class is imported as a legacy view or a class is transformed to legacy view, all its implicit arguments are maintained but changed to explicit type, so that the Analyst can modify or delete them. Moreover, if a legacy view becomes a class, all the arguments of its creation events are removed and new arguments are generated from request upon creation attributes, class relationships, agents or class shared events.
• Arguments with the prefix “p_”: Now, it is already possible to name arguments with the prefix “p_” in local services. This prefix was previously reserved for arguments created automatically by OLIVANOVA Modeler.
• Class name in the caption of the Presentation Model dialog:Now, in the caption of the Presentation Model dialog, when an Interaction Unit or Auxiliary Pattern is selected, in addition of appearing the name of the selected Unit or Pattern, it will also appear the class where this selected element is contained. Moreover, for a selected Service IU, the name of the container service will also be displayed.
• Reorder local services: In the Services tab, in the class edit dialog, there are two new buttons (Move Up and Move Down) to allow the Analyst to reorder services. Events and transactions/operations cannot be mixed when reordering services.
• System agent classes:When the agents dialog is opened, the "System agent classes" option is activated by default.
• Warning message for events without valuations: If an event (except if it is a creation, destruction, shared, carrier or liberator event) does not have valuations then a message will appear during the model validation warning the Analyst about this situation.
• Preserve formulas which used deleted elements: When the Analyst deletes an attribute, an argument, an aggregation relationship or an inheritance relationship; valuations, transitions or triggers that use any of these elements in its formula are not deleted any more. When these formulas are validated, error messages will be displayed because they use elements that do not exist in the model.

New profiles options

• New option in User Interface Transformation Engine Web ASP.NET 2.0 (UIT_ASP2) and User Interface Transformation Engine Java Server Faces (UIT_JSF) profiles:
• Tabs in MDIUs: Defines how many details are needed in a MDIU in order to use Tabs to display its detail IUs. Its options are ‘Without Tabs’, ‘Tabs when 2 or more details’ or ‘Tabs when 3 or more details’.

Log file

• Now, it can be selected the directory to save the "Log" file in the "Options" window. If "Log directory" field is empty, the "Log" file is saved in the directory where OLIVANOVA Client is installed. Besides, the "Log" file includes more information about the request process and adds more detailed information about the produced errors.

New ACM validations

• In case the OLIVANOVA Advanced Code Manager tool is not installed in the computer or the version of OLIVANOVA Advanced Code Manager is not compatible, the "Authentication" window will appear with all its fields disabled. Also, an information message warning about this situation will be displayed in the upper area of the window. Once the "Next" button is pressed, the application will be redirected to the "Summary" window in order to complete de process.
• If the "Authentication" window is enabled, after pressing the "Next" button, some validations are made in order to ensure that the user is valid:
  1. User has visibility over non-obsolete ACM projects and versions.
  2. ACM has been registered.
• In the ACM Versions tree and grid it is shown the name of versions and projects instead of their Identifier. New icons also have been included to show the projects and versions.

New Tasks window

• This window shows the tasks to be performed, based on the data introduced in the previous windows. If the receive directory has not been introduced only the sending task will be carried out and the rest will be discarded.
  When pressing the "Send" button, the assistant shows all the processes that are currently being run.

• Formula texts format
  Compares the new property of the State verification, showing all the information about their modifications

• Navigational filtering in Hierarchical Actions Tree nodes
  The information about the hierarchy nodes navigational filtering has been included in the Views section of both the Full Model Documentation and the Hierarchical Actions View Documentation.
• Outbound arguments visibility for Service Interaction Units
  The information about the visibility of the outbound arguments has been included in the Service Interaction Unit section both in local services and in global services. This data is generated for the Full Model and Help Messages Documentation.

• Tree views
  For displaying the information in a faster and more hierarchical way, new tree views have been included in the Multilanguage application:
  • Projects in tree
  • Translations in tree (for model texts)
• Export and Import from Excel 2007
  In this new version, the translations information can be exported to Microsoft Excel 2007. In addition, a Microsoft Excel 2007 translations sheet can be also imported to OLIVANOVA Multilanguage. This is possible, both for model and fixed texts.
• Fixed texts management
  The fixed texts management has been modified in order to be more useful and comfortable for the user.
• New user interface
  The menu interface has been modified. The new design allows users to use the application in a more friendly way.
• Users management
  In this new version there are only two kinds of profiles, Administrator and User. The Manager profile will not be available from now on.
• Dumping processes
  The interface of the dumping services, Dump to XML and Dump default texts to XML, has been modified to become more friendly and easier to use.

• New options for the command line
  New options have been added to the command line in order to extend the communication between the OLIVANOVA Advanced Code Manager and the OLIVANOVA Star Client.
• Copy file and all its changes
  Now, the "New file name" field of the "Copy file and all its changes" service is initialized with the name of the selected file (original file).

• Details loading on demand in Master-Detail Interaction Units.
• Visual Studio 2008 and .NET Framework 3.5 compatibility.
• Keep the selection in a Detail Interaction Unit, after executing a service from this Detail in Master-Detail Interaction Units. This is related to the changes explained in the HowTo HT_RefreshOptions_UIT_CS2_EN.
• Store user preferences for each connected user.
• Refresh Population or Instance Interaction Units data after successful execution of services accessed through conditional navigation.

• Tabs grouping for details in Master-Detail Interaction Units.
• Details loading on demand in Master-Detail Interaction Units.
• Visual Studio 2008 and .NET Framework 3.5 compatibility.
• Microsoft Internet Explorer web browser support for version 8.
• The size of the controls which represent String type fields vary depending on its maximum length property.
• The size of the controls which represent Text type fields has been increased.

• Tabs grouping for details in Master-Detail Interaction Units.
• Details loading on demand in Master-Detail Interaction Units.
• Microsoft Internet Explorer web browser support for version 8.
• The size of controls which represent String type fields vary depending on its maximum length property.
• The size of controls which represent Text type fields has been increased.

• Horizontal Visibility is now being checked for attributes of related classes.
  When querying an instance or the population of a given class C, if the DisplaySet used in the query has items that correspond to attributes of classes related with class C, horizontal visibility constraints have to be checked on every related instance. Such items will be returned by the query only if both vertical and horizontal visibility constraints are fulfilled.
• Horizontal Visibility is now also being checked for object-valued filter variables and object-valued arguments and the SelectedObject keyword in navigational filters.
• Propagation of agent permissions in an inheritance net at runtime
  In conceptual models with agent classes related in an inheritance net (e.g. "Accountant" and "Salesman" specializing from "User" and "AccountantAdmin" specializing from "Accountant") agent permissions are defined for any given agent class are inherited by all its descendants. However, this was not taken into account at runtime.
  
  IMPORTANT NOTICE: Should you already have models with agents in inheritance nets, this new version of the transformation engine may result in modifications in the behavior of your applications.
• Support for Microsoft .NET Framework 3.5

• Horizontal Visibility is now being checked for attributes of related classes.
  When querying an instance or the population of a given class C, if the displayset used in the query has items that correspond to attributes of classes related with class C, horizontal visibility constraints have to be checked on every related instance. Such items will be returned by the query only if both vertical and horizontal visibility constraints are fulfilled.
• Horizontal Visibility is now also being checked for object-valued filter variables and object-valued arguments and the SelectedObject keyword in navigational filters.
• Propagation of agent permissions in an inheritance net at runtime.
  In conceptual models with agent classes related in an inheritance net (e.g. "Accountant" and "Salesman" specializing from "User" and "AccountantAdmin" specializing from "Accountant") agent permissions are defined for any given agent class are inherited by all its descendants. This, however, was not taken into account at runtime.
  
  IMPORTANT NOTICE: Should you already have models with agents in inheritance nets, this new version of the transformation engine may result in modifications in the behavior of your applications.