{"id":594,"date":"2015-03-27T13:05:25","date_gmt":"2015-03-27T20:05:25","guid":{"rendered":"https:\/\/blogs.plm.automation.siemens.com\/t5\/Polarion-Blog\/Introducing-Polarion-2015-What-39-s-New-and-Noteworthy\/ba-p\/380955"},"modified":"2026-03-26T05:28:57","modified_gmt":"2026-03-26T09:28:57","slug":"introducing-polarion-2015-whats-new-and-noteworthy","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/polarion\/introducing-polarion-2015-whats-new-and-noteworthy\/","title":{"rendered":"Introducing Polarion 2015: What's New and Noteworthy"},"content":{"rendered":"

This is the last addition to our Polarion 2015 release cycle. As you might be aware, Polarion R&D follows the principles of enterprise agile methodology, which enables us to release frequently, faster, and with better customer satisfaction.<\/p>\n

We have a “service release” (SR) each quarter, and as the name suggests, it contains issue fixes and feature enhancements. But service releases also include complete new features if they are fully implemented, tested, and documented, and they do not significantly change the way people have been trained to use the last Polarion major version.<\/p>\n

All the new features released in the SRs roll up into our next major version, which when released, also includes new features and functionality. So what you will see here are the enhancements published since our last service release Polarion 2014 SR3<\/A>.<\/p>\n

If you want to get a quick overview about our brand new release, check out my release announcement post: Polarion 2015 Delivers Visual Reporting, Variant Management, Enhanced Security and More<\/A>.<\/p>\n

So now let’s go through the final additions to Polarion 2015…
\n
\n

Visual Live Reporting<\/H2>
\nUntil now, Polarion\u2019s robust reporting has been primarily the domain of programmers. We felt that it is time to innovate in the reporting component and provide a solution that is as flexible as current Wiki-based reporting, but also very easy for non-programmers to design reports visually. You can now truly design reports without coding. Just drop Live Report \u201cwidgets\u201d into a LiveReport page and visually set options and parameters to bring in the data you want, displayed the way you want it. (We haven’t forgotten the coders. There are special scripting widgets that let them bring their skills to bear.)<\/p>\n

\"report\"<\/A><\/p>\n

You can learn more about our Live Reporting on our Polarion 2015<\/A> micro-site.
\n

Hyperlinks<\/H3>
\nThe linking artifacts is a core feature of a Wiki, and as part of our work on LiveReports 2015, we have completely redesigned the way you add hyperlinks… not only to Reports, but also to LiveDoc documents and Work Items. Adding hyperlinks is now consistent across all rich text editors. Use the Link tool from the toolbar, or simply paste the URL into the content and select the preferred rendering (or just continue typing if you are fine with the default option).<\/p>\n

\"hyperlinks\"<\/A>
\n

Gantt Chart<\/H3>
\nEach Plan is a project that a team is working on. There might be hundreds of projects that your “team of teams” is working with. To help you meet the project schedule for a complex landscape of projects, it is important to quickly get the overview of the full break-down structure of all projects, with live status information. A Gantt Chart has always been a good tool for this.<\/p>\n

\"Screenshot\"<\/p>\n

Gantt is a nice example of the extensibility of the new Reporting component in Polarion 2015. We have released Gantt widget as a reference widget implementation, so you cannot only fully leverage the new visual LiveReport technology, but also extend the widget any way you like.<\/p>\n

\"gantt-widget\"<\/A>
\n

Cross Project Planning<\/H2>
\nIf we speak about planning, it was one of the most requested enhancements to the Polarion 2014 feature set, to allow teams to include items from other projects into Plans.<\/p>\n

One good practice that our customers like is to separate the component development into dedicated projects. Each component is fully specified (requirements, user stories, test cases, tasks) in a dedicated project.<\/p>\n

But a single team is often responsible for implementation, engineering of multiple components. If this is needed, you no longer need to create proxy work packages in the team projects, or have a team working on multiple disconnected plans in parallel. In their team project – or in their team of teams project – the team Plans can now include items from all the component projects the coordinating team is responsible for.<\/p>\n

\"\"
\n

Document Status Change Signatures<\/H2>
\nYou can now set up the Document workflow configuration to require one or more user signatures, indicating agreement with the current state of the Document and its content. This prevents transition to a different status (e.g. from \u201cIn Review\u201d to \u201cApproved\u201d) until the specified person or persons have taken action to sign off, indicating their agreement to allow transition to the next process step in the workflow.<\/p>\n

\"\"<\/p>\n

You can learn more about our Document Workflow and Signatures on our Polarion 2015 micro-site<\/A>.
\n

Workflow Condition Messages<\/H3>
\nWhen workflow conditions block users from executing a workflow transition, clear messages explain why the action is not available. While implementing this for Document workflow, we also extended it to Work Item workflow.<\/p>\n

\"workflow-conditions\"<\/A><\/p>\n

 
\n

LiveDoc Enhancements<\/H2>
\nPolarion’s exclusive LiveDoc documents are still unparalleled in the ALM solutions market. But we are never content to “rest on our laurels.” As one of our most used features, we keep looking for ways to improve LiveDocs.
\n

Continuous Numbered Lists<\/H3>
\nIt is now possible to continue the numbering of ordered lists when there are paragraphs or another list between the list items.<\/p>\n

\"continue-numbering\"<\/A>
\n

Change Work Item Type<\/H3>
\nSometimes you needto change the type (or presentation) of a Work Item contained in a Document.It is super easy now – just select the option you need:<\/p>\n

\"change-type\"<\/A>
\n

Work Item Field-based Permissions<\/H2>
\nIt is often not enough to control the core artifact lifecycle (create, read, modify, delete). Sometimes it\u2019s necessary to limit access to individual Work Item attributes. For example:
\n

    \n\t
  1. You want customers to access requirements, tasks, test cases online in Polarion, but you want to be sure they do not see how much time it was spent on the individual tasks, and\/or what was the estimated effort.<\/LI>
    \n\t
  2. You want to ensure that after Business Value is set for change requests, it cannot be modified except by the product owners.<\/LI>
    \n<\/OL>
    \nThere are literally tons of such scenarios, and that\u2019s why we now make it highly flexible and enable you to grant or deny permissions for any Work Item attribute (i.e. field, including Custom Fields):<\/p>\n

    \"\"
    \n

    License Management<\/H2>
    \nWe know how important is it for you to have Polarion running 24×7. It is now possible to renew the license (if the product license was updated) or if you had to reinstall the server, without server restart… even without contacting Polarion. You can now enter a License Key and activate Polarion online:<\/p>\n

    \"activate\"<\/A>
    \n

    Performance and Core Enhancements:<\/H2>
    \n