Release Date: January 21, 2013
Chat with the analysts, designers, software developers or whoever in your team directly inside Agilian, right in a diagram. PostMania, a private social networking platform designed for software development team. It enables team members to post and reply discussions specifically to a diagram or a shape.
Represent enterprise level business rules or company policies using decision table diagram. To facilitate decision making, the decision table diagram allows you to record possible conditions, their combinations with respect to the action to take upon. For example, an airline can use the decision table to represent their discount policy, by recording the various situations as conditions (Frequent flyers? Early purchase? A package deal?), and showing the amount of discount available for different combination of conditions.
Good news for users who use the feature of project reference intensively. The time you need to open project file has been reduced significantly. The effect is more obvious when there are a large amount of referenced project files.
Creating, editing, deleting shapes, etc. Performance has been improved for most of the general editing actions you can perform in the diagram editor.
Perform enterprise architecture modeling with ArchiMate. The fixes, corrections and improvements issued in ArchiMate 2.0 have all been supported. The most important changes are the support of the Motivation extension and the Implementation and Migration extension.
The "Status" field in the Teamwork Client window is used to tell you whether the local project has been modified, when comparing to the server copy. We have re-developed the way "Status" is evaluated, which speed up the loading of content presented in Teamwork Client.
Another demanding feature of team collaboration - You can now commit and update multiple project files at a time, through the Teamwork Client window. This enhancement is particularly useful if you are working with a large amount of referenced projects. From now on, you can save time by having all of them updated at once, instead of updating each of them individually and manually.
The improvement is mainly about the appearance of grid. The ultimate goal is to make the separation of rows and columns more noticeable.
Similar to the improvement made in chart and matrix, as described above. We again tried to improve the appearance of grid content to make the separation of rows and columns more noticeable.
In the past, despite having the same font size set for a shape and its documentation, the visual appearance are different - with the documentation text looks slightly bigger than shape. Starting from this version, they are made consistent with each other.
You can select the type of content to present in the documentation editor - HTML/HTML Source/Plain Text. This was controlled by a drop down menu at the top left of editor. But from now on, it is controlled by the popup menu that appears when you right click in the documentation editor.
When editing documentation, it is possible to add a link that points to another model element. From now on, this function is extended to cover diagram. In other words, you can add a model element link as well as diagram link.
The Find feature is no longer limited to project-based searching. Starting from this version, you can use the "Find" feature right inside the documentation editor.
A direct pasting from external source to documentation often bring along hidden characters that affects the stability of document or the quality of generated report. From now on, you can use the "Paste without formats" function to paste by getting rid of the formatting attributes that bring along the copied content.
We have corrected some of the inconsistency about the look and feel of UI components.
The sub-diagram popup menu is re-designed to make it easier to navigate. Preview of sub-diagram is presented when you are approaching a menu of sub-diagram.
Stereotype can be used to represent that a model element a-kind-of something, and that "something" is what we called a stereotype. An <<API>> (<< and >> is the textual representation of stereotype) class represents an API class, while a <<critical>> use case stands for a use case that require immediate attention. Starting from this version, you can define your own stereotypes and apply them on components in User Interface diagram.
You can explain or elaborate a model element by adding relevant diagrams to it as references. From now on, you can open in diagram the shape that references it, through accessing the quick link at the top left corner of diagram. This allows you to instantly jump between the source and target of reference.
The method getFrom() available for connector was unable to retrieve the correct element when the from end is a connector. From this version onwards, we have made it able to retrieve the connector by calling getFrom().
In addition to the standard appearance of notations (e.g. stickman for actor, box for class, oval for use case, etc), here you have one more option - the primitive option. The primitive option enables you to present any kind of shape as simple rectangle/oval/rounded rectangle shape. You can specify custom text to such "primitive shape", which is particular useful for modeling for general-purposes. A sample use would be to present an actor that represents a computer as a rectangle, and then describe its role with custom text and have it presented on diagram.
You can write Report Composer templates for attribute and operation of class, and column of entity. And of course, you can form and export reports with your own templates.
To ensure that the header and image are shown in the same page in PDF report exported from Report Composer, you can edit the template that shows the image by adding the attribute keepWithPreviousInPDF="true" in the ElementImage element.