{"id":3940,"date":"2022-04-21T04:52:07","date_gmt":"2022-04-21T08:52:07","guid":{"rendered":"https:\/\/blogs.sw.siemens.com\/polarion\/?p=3940"},"modified":"2026-03-26T05:43:52","modified_gmt":"2026-03-26T09:43:52","slug":"polarion-alm-22-r1-whats-new-and-noteworthy","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/polarion\/polarion-alm-22-r1-whats-new-and-noteworthy\/","title":{"rendered":"Polarion ALM 22 R1 \u2013 What\u2019s New and Noteworthy"},"content":{"rendered":"\n<p>Another major version of Polarion is now available &#8211; <strong>Polarion ALM 22 R1<\/strong><\/p>\n\n\n\n<p>In this release, we deliver greatly improved source code traceability, as well as several productivity improvements, based on the feedback from our customers who use our solutions every day.<\/p>\n\n\n\n<p>Significant enhancements were done to the following:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>Commit Traceability&nbsp;<\/strong>\u2013 New scalable architecture of source code change traceability allows you to link changes from thousands of branches to Polarion Work Items with minimal network utilization.<\/li><li><strong>Simulink Connector<\/strong>&nbsp;\u2013 A brand new Simulink connector provides a superb user experience with the embedded Polarion UI within the Simulink and an advanced feature set.<\/li><li><strong>Productivity Improvements<\/strong>&nbsp;\u2013 Easy on the user with type-specific custom fields for Live Documents, or retaining the Work Item selection when switching the Live Document filter.<\/li><\/ul>\n\n\n\n<p>Let\u2019s take a deep dive into all improvements the new release brings.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Improved Commit Traceability<\/h2>\n\n\n\n<p>We rethought how Polarion connects to external repositories and tracks the changes made to your code.<\/p>\n\n\n\n<p>The new Commit Traceability feature uses&nbsp;<strong>Apache Kafka<\/strong>&nbsp;as an intermediary Data Exchange Tool to locally store all metadata for the commits made to the connected repositories. Each Polarion cluster node then uses the data from Kafka to build the index and get new changes \u2013 making the whole process&nbsp;<strong>10% to 60% faster<\/strong>&nbsp;than the original solution.<br><\/p>\n\n\n\n<figure id=\"polarion_wiki macro name=table;params=bold=1|valign=middle|width=100%|uid=1\" class=\"wp-block-table\"><table><tbody><tr><th>Repository<\/th><th>New Solution<br>Fetch<br><\/th><th>New Solution<br>(Index and Reindex)<br><\/th><th>Original Solution<br>(Fetch + Re\/Index)<br><\/th><th>\u2206<\/th><\/tr><tr><td>100x local Git, 500K revisions<\/td><td>2 min<\/td><td>6 min<\/td><td>20 min<\/td><td><strong>60%<\/strong><\/td><\/tr><tr><td>GitHub, 300K revisions<\/td><td>40 min<\/td><td>3 min<\/td><td>60 min<\/td><td><strong>&nbsp;28%<\/strong><\/td><\/tr><tr><td>GitHub, 1000K revisions<\/td><td>190 min<\/td><td>27 min<\/td><td>not possible to process<\/td><td>&#8211;<\/td><\/tr><tr><td>4x SVN, 2000K revisions<\/td><td>48 s<\/td><td>42 min<\/td><td>50 min<\/td><td><strong>14%<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>We introduced a new,&nbsp;&nbsp;<strong>External Repository Aggregator<\/strong>&nbsp;(ERA) service to manage external repository connections. The ERA service acts as a single point of contact, supports thousands of repositories for a single Polarion instance, and supports the most popular repository providers (<strong>SVN<\/strong>,&nbsp;<strong>Git<\/strong>,&nbsp;<strong>GitHub<\/strong>,&nbsp;<strong>GitLab<\/strong>, and&nbsp;<strong>Bitbucket)&nbsp;<\/strong>in all their versions and flavors.<\/p>\n\n\n\n<p>With ERA as the&nbsp;<strong>single point of contact<\/strong>,&nbsp;the whole system is much more efficient, decreasing the network load because there are no longer multiple Polarion nodes trying to communicate with each external repository at once.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"760\" height=\"785\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/kafka_1-2.png\" alt=\"Health Polling in Polarion with Kafka\" class=\"wp-image-3986\" srcset=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/kafka_1-2.png 760w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/kafka_1-2-581x600.png 581w\" sizes=\"auto, (max-width: 760px) 100vw, 760px\" \/><figcaption>Health Polling<\/figcaption><\/figure>\n\n\n\n<p>The big feature of ERA is the support for <strong>Hooks\/GitHooks\/WebHooks<\/strong> together with <strong>Health Polling<\/strong>.<\/p>\n\n\n\n<p>Up until now, every Polarion node polled all connected external repositories for updates every 5 seconds. For example, with 100 connected repositories and 7 nodes in a Polarion cluster, this totaled over 12 million requests per day.<\/p>\n\n\n\n<p>The hooks are configured on the external repository side and are used to let ERA know that there has been a change.&nbsp;This allows us to not use periodic polling as the primary source for getting information about new updates. Instead, we can increase the polling period from 5 seconds to hours and use it as a &#8220;health&#8221; feature that occasionally checks for changes missed due to network issues or system outages.<\/p>\n\n\n\n<p>Using hooks with health polling set to 1 hour with 100 connected repositories and 7 Polarion nodes in the cluster totals 4900 requests per day. (The system makes almost 2500x fewer requests, just 0,04% of the original amount.)<\/p>\n\n\n\n<figure id=\"polarion_wiki macro name=table;params=bold=1|valign=middle|width=100%|uid=107\" class=\"wp-block-table\"><table><tbody><tr><th><\/th><th>Repo<br>count<\/th><th>Commits<br>per day<\/th><th>Health polls per day<br>(60 min interval)<\/th><th>Polls per day &#8211; hooks<br>(repos * commits)<\/th><th>New polls per day<br>(health + hooks)<\/th><th>Old solution polls<br>per day (7 nodes)<\/th><th>\u2206<\/th><\/tr><tr><td>Heavy<\/td><td>50<\/td><td>100<\/td><td>1 200<\/td><td>5 000<\/td><td>6 200<\/td><td>6 048 000<\/td><td><strong>975x<\/strong><\/td><\/tr><tr><td>Mid<\/td><td>100<\/td><td>25<\/td><td>2 400<\/td><td>2 500<\/td><td>4 900<\/td><td>12 096 000<\/td><td><strong>2468x<\/strong><\/td><\/tr><tr><td>Light<\/td><td>450<\/td><td>1<\/td><td>10 800<\/td><td>450<\/td><td>11 250<\/td><td>54 432 000<\/td><td><strong>4838x<\/strong><\/td><\/tr><tr><td>Total<\/td><td>600<\/td><td>126<\/td><td>14 400<\/td><td>7950<\/td><td>22 350<\/td><td>72 576 000<\/td><td><strong>3230x<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>ERA also supports simultaneous connections to&nbsp;<strong>multiple branches<\/strong>&nbsp;of each connected repository. This avoids the need for local clones of specific remote repository branches. (A requirement up until now.)<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"720\" height=\"271\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/kafka_2-2-2.png\" alt=\"\" class=\"wp-image-4094\" srcset=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/kafka_2-2-2.png 720w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/kafka_2-2-2-600x226.png 600w\" sizes=\"auto, (max-width: 720px) 100vw, 720px\" \/><\/figure>\n\n\n\n<p>The tracked branches can be specified as a<strong>&nbsp;static list<\/strong>&nbsp;or&nbsp;<strong>dynamically loaded<\/strong>&nbsp;by ERA based on a regular expression (RegEx) that defines a pattern of branch IDs that should be automatically picked up.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"869\" height=\"525\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/kafka_3-1-2.png\" alt=\"\" class=\"wp-image-4095\" srcset=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/kafka_3-1-2.png 869w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/kafka_3-1-2-600x362.png 600w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/kafka_3-1-2-768x464.png 768w\" sizes=\"auto, (max-width: 869px) 100vw, 869px\" \/><\/figure>\n\n\n\n<p>This dramatically improves the usability of the Commit Traceability feature for use cases like working in feature branches when developing your new functionality. All commits for all features can now be visible in Polarion even if the work on a feature is still in progress and it&#8217;s done seamlessly without any administrative overhaul.<\/p>\n\n\n\n<p>Tracking multiple branches from the same repository only increases the number of processed external revisions by the commits unique to the tracked branches. Once a commit is merged to the master, it no longer appears for other branches. This allows us to effectively track multiple branches from the same repository without negatively impacting scalability and performance.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Productivity Improvements<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Type-specific custom fields for LiveDocs<\/h3>\n\n\n\n<p>The new version allows you to configure different custom fields for specific Document types so that only relevant custom fields are available for each Document. It is possible to configure custom fields for &#8220;All Types\u201c, which are then configured for all Document types on top of the type-specific ones.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"702\" height=\"388\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/document_custom_fields2.png\" alt=\"Define custom fields per LiveDoc type\" class=\"wp-image-4005\" srcset=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/document_custom_fields2.png 702w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/document_custom_fields2-600x332.png 600w\" sizes=\"auto, (max-width: 702px) 100vw, 702px\" \/><figcaption>You can now define custom fields per LiveDoc type<\/figcaption><\/figure>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"760\" height=\"348\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/polarion_document_custom_fields-2.png\" alt=\"\" class=\"wp-image-4096\" srcset=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/polarion_document_custom_fields-2.png 760w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/polarion_document_custom_fields-2-600x275.png 600w\" sizes=\"auto, (max-width: 760px) 100vw, 760px\" \/><figcaption>Custom fields for the System Requirements Document type \/ Custom Fields for the Software Requirements Document type<\/figcaption><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Keep Work Item selection when switching Document Filter<\/h3>\n\n\n\n<p>Live Documents have been enhanced so that you can keep your working context by retaining the Work Item selection when switching between filtered read-only and full edit mode of a Live Document.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Navigation via Linked Work Items in Document Editor<\/h3>\n\n\n\n<p>We unified the rendering of Linked Work Items in the Work Item Presentation layout in the Document, with the existing behavior of Linked Work Items in the Work Item Properties sidebar.<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Clicking on a Linked Work Item that is sitting in the same Document will select the target Work Item and scroll it into the view.<\/li><li>Clicking on a Linked Work Item that is sitting in a different Document will open that Document, select the target Work Item and scroll it into the view.<\/li><li>Clicking on a Linked Work Item that is not in a Document will open the Work Item details in a new browser tab.<\/li><\/ul>\n\n\n\n<p>This functionality makes the navigation via trace links easy from within the Document context, without the necessity to navigate via the Work Item Properties sidebar.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Other Enhancements<\/h3>\n\n\n\n<ul class=\"wp-block-list\"><li>The &#8220;Stay logged in&#8221; functionality can be optionally disabled via a polarion property if administrators want to force their end-users to always use their credentials for login for increased security. &#8220;Stay logged in&#8221; only applies to authentication via the local users file, or LDAP. Not via the single sign-on authentication using SAML, or OAuth 2.<\/li><li>Adding a custom logo to the login screen now replaces the Siemens logo instead of displaying both logos.<\/li><li>The custom field type <strong>Duration <\/strong>is available in Collection and Test Record Custom Field administration.<\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Enhanced Ecosystem<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Open Services for Lifecycle Collaboration (OSLC) Support<\/h3>\n\n\n\n<p>When you hover over an OSLC link in the Work Item Properties sidebar, a rich text supported window from the remote system&#8217;s UI appears.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"766\" height=\"398\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/oslc_object_preview.png\" alt=\"OSLC link from a remote system previewed in the Work Item Properties sidebar\" class=\"wp-image-4015\" srcset=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/oslc_object_preview.png 766w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/oslc_object_preview-600x312.png 600w\" sizes=\"auto, (max-width: 766px) 100vw, 766px\" \/><figcaption>OSLC link from a remote system previewed in the Work Item Properties sidebar.<\/figcaption><\/figure>\n\n\n\n<p>We also made it possible to create OSLC links between LiveDocs located on two different Polarion instances or a container of requirements (like a module) on another remote system.<br><\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"850\" height=\"600\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/system_requirement_specification.png\" alt=\"\" class=\"wp-image-4021\" srcset=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/system_requirement_specification.png 850w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/system_requirement_specification-600x424.png 600w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/system_requirement_specification-768x542.png 768w\" sizes=\"auto, (max-width: 850px) 100vw, 850px\" \/><figcaption>OSLC linking to other requirement collections in the Document Properties sidebar<\/figcaption><\/figure>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"860\" height=\"311\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/software_requirements.png\" alt=\"\" class=\"wp-image-4022\" srcset=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/software_requirements.png 860w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/software_requirements-600x217.png 600w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/software_requirements-768x278.png 768w\" sizes=\"auto, (max-width: 860px) 100vw, 860px\" \/><figcaption>LiveDoc Properties sidebar now displays a rich text preview of OSLC links to other LiveDocs<\/figcaption><\/figure>\n\n\n\n<p>We made the following usability and compatibility improvements to Polarion&#8217;s OSLC support:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>The <strong>Selection <\/strong>and <strong>Creation <\/strong>dialogs from an OSLC provider are now resizable within Polarion.<\/li><li>Polarion 22R1 was updated to use the latest OSLC libraries to ensure maximum compatibility with remote systems.<\/li><li>OSLC links now display the Teamcenter <strong>Item ID<\/strong>, <strong>Rev ID<\/strong>, and <strong>Name <\/strong>when using the Teamcenter\/Polarion linked data integration. (Instead of just the <strong>Name<\/strong>.)<\/li><\/ul>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"574\" height=\"104\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/oslc_links_displayed_with_Rev_id.png\" alt=\"\" class=\"wp-image-4025\"\/><figcaption>Teamcenter OSLC links displayed with Rev ID, Item ID and Name<\/figcaption><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Personal Access Tokens for authentication in the Webservices API<\/h3>\n\n\n\n<p>Personal Access Tokens allow you to authenticate users or service accounts via the Webservices API (and later in the REST API) securely, by avoiding the storage of usernames and passwords in external tools. Users can create their own Personal Access Tokens with specific expiration dates, or revoke the tokens manually.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"535\" height=\"474\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/PATs.png\" alt=\"\" class=\"wp-image-4059\"\/><figcaption>Personal Access Tokens administration<\/figcaption><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">License monitoring via Java Management Extensions<\/h3>\n\n\n\n<p>Polarion license utilization can be easily monitored via the new License statistics MBean that exposes license usage information via the Java Management Extensions API, or so-called JMX. The JMX is a standard Java technology that enables the easy plugging of these statistics into enterprise monitoring&nbsp;tools like Zabbix, or Kibana, or allows viewing these statistics with tools such as Java Management Console.<\/p>\n\n\n\n<figure class=\"wp-block-image size-medium\"><img loading=\"lazy\" decoding=\"async\" width=\"600\" height=\"292\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/License-monitoring-600x292.png\" alt=\"\" class=\"wp-image-4060\" srcset=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/License-monitoring-600x292.png 600w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/License-monitoring-768x374.png 768w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/License-monitoring-900x438.png 900w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/License-monitoring.png 908w\" sizes=\"auto, (max-width: 600px) 100vw, 600px\" \/><figcaption>License Statistics can be easily monitored in the favorite tool of your DevOps team<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"polarion_wiki macro name=module-workitem;params=id=DPP-232981|copy=1|document_revision=1622986\">Active Load Balancing in the Cloud<\/h2>\n\n\n\n<p>Active load balancing ensures the correct balancing of users across the Polarion application nodes in a cluster. Users need to be re-balanced especially when Polarion application nodes in the cluster are added, removed, or restarted.<\/p>\n\n\n\n<p>Active load balancing requires that the user&#8217;s login session is shared across all the nodes in the cluster. Previously, the technical implementation of this functionality relied on Multicast technology, which was not available with many cloud providers, so we updated the session replication implementation to unlock active load balancing in the Polarion clusters deployed in the cloud. We highly recommend setting up active load balancing for any Polarion cluster.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"polarion_wiki macro name=module-workitem;params=id=DPP-230538|copy=1|document_revision=1622986\">Performance and Scalability<\/h2>\n\n\n\n<p>The most notable improvement is related to the loading of objects that use custom fields of type object enumeration, i.e., Fields that list Polarion objects. All the object enumerations are now lazy-loaded into the editor, which significantly reduces the load time of affected objects.<\/p>\n\n\n\n<p>Additionally, the algorithm for constructing a tree of Work Items has been enhanced&nbsp;to avoid deduplication of tree nodes when a certain tree size is reached in order to limit system resource utilization. The deduplication removes redundant root Work Items if the same Work Item is displayed in the lower levels of the tree.<\/p>\n\n\n\n<p>Finally, the calculation and indexing of outline numbers in Document history has been switched off by default, in order to speed up historical indexing and reduce index size. Outline numbers in Document history can be enabled by a polarion property.<\/p>\n\n\n\n<figure id=\"polarion_wiki macro name=table;params=width=84.88%|uid=1\" class=\"wp-block-table\"><table><tbody><tr><th>Use Case<\/th><th>21 R2 [s]<\/th><th>22 R1 [s]<\/th><th>\u2206<\/th><\/tr><tr><td>Load Test Run No Cache<\/td><td>168<\/td><td>1<\/td><td>99,40%<\/td><\/tr><tr><td>Load Test Run Cache<\/td><td>14<\/td><td>0,6<\/td><td>95,70%<\/td><\/tr><tr><td>TreeCreatorPerformanceTests.testCreateTree* (Median)<\/td><td>0,44<\/td><td>0,21<\/td><td>51,90%<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Technology update<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Graal JavaScript engine<\/h3>\n\n\n\n<p>Polarion workflow script functions, conditions, and script jobs are currently executed by the Nashhorn JavaScript engine that is part of Java. Due to the upcoming removal of the Nashorn JavaScript engine in the future Java 17, we included the next-generation <strong>Graal JavaScript<\/strong> engine into Polarion. For now, the usage of the Graal engine can be enabled by a Polarion property.<\/p>\n\n\n\n<p>From Polarion 22 R2, we will support only Java 17 for runtime, so the Graal engine will be used by Polarion by default.<\/p>\n\n\n\n<p>The scripts are not fully compatible between the different engines, so we suggest you start validating and updating your scripts early.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Updates to Supported 3rd Party Systems and Components<\/h3>\n\n\n\n<ul class=\"wp-block-list\"><li>Added Debian 11 support <\/li><li>Added support of PostgreSQL 13.4 which is now bundled in the Windows distribution<\/li><li>Firefox support limited to ESR versions<\/li><\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">New Documentation Guides<\/h3>\n\n\n\n<p>In order to make Polarion scripting easier, a new <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/product\/230235217\/doc\/PL20210812782182305.guide\/pdf\/\" target=\"_blank\" rel=\"noreferrer noopener\"><strong>SDK Scripting Guide<\/strong><\/a> was introduced and provided in the Polarion distribution. <\/p>\n\n\n\n<p>Since Polarion needs to be maintained&nbsp;long-term, we need to update the technology continuously&nbsp;and occasionally deprecate and remove old features. To keep our customers in the loop, we created a new <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/product\/230235217\/doc\/PL20210812782182305.xid2056109\/html\/xid2056111\" target=\"_blank\" rel=\"noreferrer noopener\">Deprecation and Removal<\/a> plan that lists all the depreciations and removals for the current release as well as a roadmap for the following Polarion release.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"polarion_wiki macro name=module-workitem;params=id=DPP-232987|copy=1|document_revision=1622986\">Notable Issue Fixes<\/h3>\n\n\n\n<p>A number of important issues have been addressed in this release. For example, the search in the historical Work Items table has been fixed to execute the search against the historical index to produce an accurate query result. Here are some further notable issue fixes:<\/p>\n\n\n\n<p>DPP-225317 &#8211; Easy Linking: Memory leakage reported<br>DPP-224397 &#8211; White Label Error Page when activating Collaboration Feature using AWS LB<br>DPP-223026 &#8211; Coordinator runs out of memory because of multiplied login requests<br>DPP-223012 &#8211; Regression in 3.21.1 SAML: Polarion does not convert anchor links before they are sent to IdP<br>DPP-214163 &#8211; Regression in SVN 1.10+: History view of some documents fails with SVN exception &#8220;chunked stream ended unexpectedly\u201e&nbsp;<br>DPP-203009 &#8211; Any changes in UI-data classes breaks the deserialization of already serialized objects<br>DPP-164731 &#8211; Cannot execute workflow action via drag&amp;drop in Kanban board if the action requires description<br>DPP-122146 &#8211; unable to attach *.gz file to work item<br>DPP-96084 &#8211; NPE when selecting Work Item for bulk edit with insufficient permission<br>DPP-94261 &#8211; Rows in old table component are stuck in Loading&#8230; State<br>DPP-92597 &#8211; Filter is applied on head revision when viewing Document history<br>DPP-91617 &#8211; Table with no border in editor displays border in PDF Export<br>View the complete <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/product\/230235217\/doc\/PL20210812782182305.xid1919185\/html\/xid2060821\" target=\"_blank\" rel=\"noreferrer noopener\">resolved issues list<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">One last thing &#8230; New Polarion Connector for Mathworks Simulink<\/h2>\n\n\n\n<p>In the last &#8220;W<em>hat&#8217;s new blog post for Polarion&#8221;<\/em>, we mentioned that we were working on a new Polarion connector for Mathworks Simulink. Now, in time for this new Polarion 22 R1 release, we are pleased to announce that <a href=\"https:\/\/blogs.sw.siemens.com\/polarion\/the-new-polarion-connector-for-simulink-is-now-available-for-download\/\" target=\"_blank\" rel=\"noreferrer noopener\"><strong>the new Polarion connector for Simulink is here<\/strong><\/a> in a dedicated blog post. For the first time, Polarion itself has been directly embedded into the Simulink desktop client to support a larger set of customer use cases and reduce inconvenient app context switching.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"960\" height=\"525\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/polarion_simulink_connector.png\" alt=\"\" class=\"wp-image-4028\" srcset=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/polarion_simulink_connector.png 960w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/polarion_simulink_connector-600x328.png 600w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/polarion_simulink_connector-768x420.png 768w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/polarion_simulink_connector-900x492.png 900w\" sizes=\"auto, (max-width: 960px) 100vw, 960px\" \/><figcaption>Polarion embedded inside of Simulink<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Update Information<\/h2>\n\n\n\n<p>Version 22 R1 is a free update to all customers with a current maintenance subscription. You can download the update distribution at&nbsp;<a href=\"https:\/\/support.sw.siemens.com\/en-US\/product\/230235217\/download\/PL20210812782182305\" target=\"_blank\" rel=\"noreferrer noopener\">Support Center<\/a>. Instructions for installing it are in&nbsp;the HOW_TO_INSTALL_THIS_UPDATE.txt file, bundled in the update distribution package. Please also review the Configuration.txt file, which describes changes that can affect existing Polarion installations.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Evaluation<\/h2>\n\n\n\n<p>If you would like to evaluate this release before updating your production installation, simply visit&nbsp;<a href=\"https:\/\/www.plm.automation.siemens.com\/store\/en-us\/trial\/polarion-alm-download.html#\/ACTION=3856996352\" target=\"_blank\" rel=\"noreferrer noopener\">Polarion Trial Download<\/a>, download the product, install it, and use the built-in 30-day evaluation license.<\/p>\n\n\n\n<p>If you have any questions or comments, please don\u2019t hesitate to contact us on the&nbsp;<a href=\"https:\/\/community.sw.siemens.com\/s\/topic\/0TO4O000000MihxWAC\/polarion\" target=\"_blank\" rel=\"noreferrer noopener\"><strong>Polarion Community<\/strong><\/a>&nbsp;portal&nbsp;or through your Polarion technical support contact.&nbsp;On behalf of our entire team, thank you for using Polarion ALM.<\/p>\n\n\n\n<p>Regards,<br>Radek Krotil,<br>Polarion ALM Product Management<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Polarion ALM 22 R1 deliver greatly improved source code traceability, as well as several productivity improvements. Learn more in our blog!<\/p>\n","protected":false},"author":52296,"featured_media":4070,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[54,1,109],"tags":[389,529,481,29,459],"industry":[62,86,103,102],"product":[285],"coauthors":[479],"class_list":["post-3940","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-featured","category-news","category-product-updates","tag-collaboration","tag-polarion-22-r1","tag-release","tag-requirements-management","tag-software","industry-automotive-transportation","industry-industrial-machinery-heavy-equipment","industry-small-medium-business","industry-software-development","product-polarion"],"featured_image_url":"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2022\/04\/polarion-release-22-R1.png","_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/3940","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/users\/52296"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/comments?post=3940"}],"version-history":[{"count":5,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/3940\/revisions"}],"predecessor-version":[{"id":4111,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/3940\/revisions\/4111"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/media\/4070"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/media?parent=3940"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/categories?post=3940"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/tags?post=3940"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/industry?post=3940"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/product?post=3940"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/coauthors?post=3940"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}