{"id":361,"date":"2025-12-11T12:57:35","date_gmt":"2025-12-11T11:57:35","guid":{"rendered":"https:\/\/www.covalgo.at\/blog\/?p=361"},"modified":"2025-12-11T12:59:13","modified_gmt":"2025-12-11T11:59:13","slug":"polarion-polarion-alm-2512-ist-verfuegbar","status":"publish","type":"post","link":"https:\/\/www.covalgo.at\/blog\/2025\/12\/11\/polarion-polarion-alm-2512-ist-verfuegbar\/","title":{"rendered":"Polarion: Polarion ALM 2512 ist verf\u00fcgbar"},"content":{"rendered":"\n<p>Das neue Polarion ALM 2512 ist verf\u00fcgbar und steht zum Update\/Download bereit. Eine Zusammenfassung der neuen Highlights gibt es hier &#8211; <a href=\"https:\/\/blogs.sw.siemens.com\/polarion\/polarion-alm-2512-whats-new-and-noteworthy\/\" target=\"_blank\" rel=\"noreferrer noopener\">Polarion Blog von Siemens<\/a><\/p>\n\n\n\n<p>Neuigkeiten:<\/p>\n\n\n\n<p><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Introduced new AI features with Polarion Copilot.<\/li>\n\n\n\n<li>Added support for Test Management in Collections.<\/li>\n\n\n\n<li>Boosted productivity with Mentions and Multiple sidebars.<\/li>\n\n\n\n<li>Helped our Administrators implement new options for managing Attachments, Import and Export Projects, and&nbsp;centralized the management of reporting Widgets.<\/li>\n<\/ul>\n\n\n\n<p><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Bringing the power of Artificial Intelligence to Polarion<\/strong>\n<ul class=\"wp-block-list\">\n<li>\u2018Similarity Analysis\u2019 to locate duplicate Work Items<\/li>\n\n\n\n<li>Detecting contradictions with Consistency Check<\/li>\n\n\n\n<li>Content Validation for the INCOSE standard<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Test Management comes to Collections<\/li>\n\n\n\n<li>Related Collection enhancements<\/li>\n\n\n\n<li>Boosting your productivity\n<ul class=\"wp-block-list\">\n<li><strong>Bring anyone into a conversation with @Mentions<\/strong><\/li>\n\n\n\n<li>See more with Multi-sidebar support in Documents<\/li>\n\n\n\n<li>Merge links automatically between Branched and Master Documents<\/li>\n\n\n\n<li>Flexible Test Run creation from a Document at any Revision<\/li>\n\n\n\n<li><strong>Quicker Document Approvals with signature notifications<\/strong><\/li>\n\n\n\n<li><strong>Your own support agent with Polarion Help AI Chatbot<\/strong><\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Helping our administrators\n<ul class=\"wp-block-list\">\n<li>Manage repository size by storing Attachments externally<\/li>\n\n\n\n<li>Automatic antivirus scanning for Attachments<\/li>\n\n\n\n<li><strong>Import and export Projects across Polarion instances<\/strong><\/li>\n\n\n\n<li>Managing Velocity Widgets<\/li>\n\n\n\n<li>Search for deactivated users<\/li>\n\n\n\n<li>Check for duplicated Project prefixes<\/li>\n\n\n\n<li>Execute Scheduled Scripts on-demand<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Enhanced Integration Capabilities\n<ul class=\"wp-block-list\">\n<li>OSLC now supports Revision-based linking<\/li>\n\n\n\n<li>Third-party cookies support OSLC<\/li>\n\n\n\n<li>Documents from the same Space and Simplified Export for ReqIF<\/li>\n\n\n\n<li>Improved ReqIF compatibility with IBM DOORS<\/li>\n\n\n\n<li>Support of rich text Comments with JIRA integration<\/li>\n\n\n\n<li>Personal Access Token support for sync pair configuration<\/li>\n\n\n\n<li><strong>Expanded Polarion REST API capabilities<\/strong><\/li>\n\n\n\n<li>Configuration Management and branching with the MathWorks Simulink Connector<\/li>\n\n\n\n<li>Domain validation for the Rhapsody Connector<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Security updates\n<ul class=\"wp-block-list\">\n<li>Refined Monitor topic and Job management permissions<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Performance and scalability\n<ul class=\"wp-block-list\">\n<li>Scalability white paper<\/li>\n\n\n\n<li>Performance improvements<\/li>\n\n\n\n<li>Location Index (early adoption)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-large is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"710\" src=\"https:\/\/www.covalgo.at\/blog\/wp-content\/uploads\/2025\/12\/000_Titel-1024x710.png\" alt=\"\" class=\"wp-image-398\" style=\"width:500px\" srcset=\"https:\/\/www.covalgo.at\/blog\/wp-content\/uploads\/2025\/12\/000_Titel-1024x710.png 1024w, https:\/\/www.covalgo.at\/blog\/wp-content\/uploads\/2025\/12\/000_Titel-300x208.png 300w, https:\/\/www.covalgo.at\/blog\/wp-content\/uploads\/2025\/12\/000_Titel-768x533.png 768w, https:\/\/www.covalgo.at\/blog\/wp-content\/uploads\/2025\/12\/000_Titel.png 1400w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Bringing the power of Artificial Intelligence to Polarion<\/h2>\n\n\n\n<p>Siemens is uniquely positioned to drive Industrial AI and help our customers bridge the gap between generic AI model-based agentic use cases and engineering processes adhering to strict regulations and factual results. Polarion plays a pivotal role in this strategy in the Software-defined lifecycle sphere.<\/p>\n\n\n\n<p>Siemens envisions an end-to-end multi-layer AI stack from underlying engineering Foundational models specifically trained for various domains on real engineering data, through a flexible AI Fabric linking Siemens Xcelerator applications, including Polarion, as well as third-party apps, into unified ontologies empowering Digital Thread Agents executing actions across the integrated applications. Specific in-app AI features are also encompassed for rapid adoption by end users of various Siemens applications.<\/p>\n\n\n\n<p>Polarion 2512 introduces <strong>Polarion Copilot<\/strong>, a new paid add-on that delivers in-app AI features as a collection of three AI-powered tools, all accessible via a new icon on the top right of the Polarion UI.<\/p>\n\n\n\n<figure class=\"wp-block-image is-resized\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/select_AI_icon-1.png\" alt=\"The new AI tools are accessible via a new icon on the top right of the Polarion UI.\" class=\"wp-image-7344\" style=\"width:200px\"\/><\/figure>\n\n\n\n<p><a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/zho4125043893753\" target=\"_blank\" rel=\"noreferrer noopener\">Polarion Copilot<\/a> lets you leverage your own Azure-hosted OpenAI LLM and use it with Polarion. It can be purchased for on-premise Polarion installations using Hybrid SaaS-type licenses.\u00a0<br>Let\u2019s review the three AI features included with Polarion Copilot in this release:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>\u2018Similarity Analysis\u2019 to locate duplicate Work Items<\/h3>\n\n\n\n<p>Managing a large number of <strong>Work Items<\/strong> can sometimes lead to duplicates or make it challenging to group related items for comprehensive planning and testing. Our new <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/jrs5877144730233\" target=\"_blank\" rel=\"noreferrer noopener\">Similarity Analysis<\/a> feature harnesses AI to help identify <strong>Work Items<\/strong> that are similar to one that you select.<\/p>\n\n\n\n<p><strong>Similarity Analysis<\/strong> goes beyond simple keyword matching by understanding the underlying meaning of the text. It helps in identifying semantically similar <strong>Work Items<\/strong>, even if they are phrased differently, which can prevent redundant entries and streamline related tasks.<\/p>\n\n\n\n<p>Let\u2019s say you are a product owner or a test lead, and you are looking at a \u201c<em>System Administrator must be able to set the user roles<\/em>\u201d <strong>User Story<\/strong>. Your goal is to identify all related stories to consider while planning tests for this functionality.<\/p>\n\n\n\n<p>Manually searching for related stories across a large backlog can be time-consuming, and you might miss stories that are conceptually linked but use different terminology.<\/p>\n\n\n\n<p>Now you can select the <strong>User Story<\/strong>, and use <strong>Similarity Analysis<\/strong> to search a defined scope for similar <strong>Work Items<\/strong>.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/Polarion_similarity_analysis_1.png\" alt=\"Similarity Analysis executes on the selected Work Item against\u00a0work items returned by the query.\" class=\"wp-image-7357\" title=\"Similarity Analysis executes on the selected Work Item against Work Items returned by the query\"\/><\/figure>\n\n\n\n<p><strong>Similarity Analysis<\/strong> scans the defined scope and lists the <strong>Work Items<\/strong> it finds that are highly similar or conceptually related based on their descriptions.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/similarity_analysis_result.png\" alt=\"The Similarity score is calculated for all Work Items returned by the query.\" class=\"wp-image-7362\" title=\"The Similarity score is calculated for all Work Items returned by the query\"\/><\/figure>\n\n\n\n<p>Only the most similar <strong>Work Items<\/strong> are listed, giving you a great starting point for comparison. Administrators can define how many results are listed and set a similarity score in the <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/xid1551538\" target=\"_blank\" rel=\"noreferrer noopener\">Configuration Properties<\/a> in <strong>Global Administration<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Detecting contradictions with Consistency Check<\/h3>\n\n\n\n<p>The last thing any company needs is to have safety issues caused by contradicting requirements. Imagine one requirement states the input voltage for a computer board is 5V, while a second requirement states that the output voltage of a power supply is 24V. To help prevent such problems, we created <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/kxg9897259476610\" target=\"_blank\" rel=\"noreferrer noopener\">Consistency Check<\/a>.<\/p>\n\n\n\n<p>Simply select the <strong>Requirement <\/strong>and run <strong>Consistency Check<\/strong>.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/Polarion_consistency_check.png\" alt=\"The Consistency Check traverses all linked Work Items as per the selected Role and Depth.\" class=\"wp-image-7373\" title=\"The Consistency Check traverses all linked Work Items as per the selected role and depth\"\/><\/figure>\n\n\n\n<p><strong>Consistency Check<\/strong> traverses all linked <strong>Work Items<\/strong>, depending on the <strong>Role <\/strong>and <strong>Level Depth<\/strong> configuration, and detects any inconsistencies in their <strong>Descriptions<\/strong>, their <strong>Types<\/strong>, and their linked <strong>Work Items<\/strong>.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/polarion_consistency_check_result.png\" alt=\"A consistency summary is generated for every issue found with any linked Work Item.\" class=\"wp-image-7376\" title=\"A consistency summary is generated for every issue found with any linked Work Item.\"\/><\/figure>\n\n\n\n<p>There might be multiple inconsistencies listed with links leading to all involved <strong>Work Items<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Content Validation for the INCOSE standard<\/h3>\n\n\n\n<p>Vague <strong>Requirements <\/strong>with open questions or overcomplicated language can also be a safety risk.<br>To help ensure your engineers craft <strong>Requirements <\/strong>and <strong>Specification Documents<\/strong> that are compliant with industry standards, we created <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/acx8712348698235\" target=\"_blank\" rel=\"noreferrer noopener\">Content Validation<\/a>.<\/p>\n\n\n\n<p>This feature allows you to compare <strong>Requirement <\/strong>descriptions directly against the rigorous standards developed by the <strong>IN<\/strong>ternational <strong>CO<\/strong>uncil on <strong>S<\/strong>ystems <strong>E<\/strong>ngineering (<a href=\"https:\/\/www.incose.org\/\" target=\"_blank\" rel=\"noreferrer noopener\">INCOSE<\/a>).<\/p>\n\n\n\n<p>Just select a <strong>Requirement <\/strong>and run <strong>Content Validation<\/strong>.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/Polarion_content_violation_validate.png\" alt=\"Just select a Requirement and run Content Validation.\" class=\"wp-image-7385\" title=\"Content Validation is executed on the selected Work Item\"\/><\/figure>\n\n\n\n<p><strong>Content Validation<\/strong> reports which rules were not met, what was wrong, and how you can make the <strong>Requirements <\/strong>INCOSE compliant. (See the\u00a0<a href=\"https:\/\/www.incose.org\/docs\/default-source\/working-groups\/requirements-wg\/guidetowritingrequirements\/incose_rwg_gtwr_v4_summary_sheet.pdf\" target=\"_blank\" rel=\"noreferrer noopener\">INCOSE website<\/a> for a complete list of rules.)<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/content_validation_results.png\" alt=\"Content Validation reports which rules were not met, what was wrong, and how you can make the Requirements INCOSE compliant. \" class=\"wp-image-7390\" title=\"Content Validation reports which rules were not met, what was wrong, and how you can make the Requirements INCOSE compliant.\u00a0\"\/><\/figure>\n\n\n\n<p>You can then often copy the suggested text to your clipboard and use it to replace the original text.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><a><\/a>Test Management comes to Collections<\/h2>\n\n\n\n<p>Continuing our work from recent releases on <strong>Collections<\/strong>, we introduced the ability to create and manage <strong>Test Runs<\/strong> directly <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/els7628035072445\" target=\"_blank\" rel=\"noreferrer noopener\">within the context of a Collection<\/a>. This makes test execution more aligned, consistent, and aware of the exact <strong>Document <\/strong>set you are validating.<\/p>\n\n\n\n<p>Now a <strong>Collection <\/strong>contains a specific set of <strong>Documents<\/strong>, the <strong>Test Runs<\/strong> that validate those <strong>Documents, <\/strong>and their <strong>Test Results<\/strong> all in a single, convenient place.<\/p>\n\n\n\n<p><strong>Collections <\/strong>now offer a dedicated <strong>Test Runs<\/strong> view filtered to the scope of the <strong>Collection<\/strong>, ensuring that only the <strong>Documents <\/strong>referenced within it are available for test execution. You can create new <strong>Test Runs<\/strong> without ever leaving the <strong>Collection <\/strong>view, allowing you to initiate campaigns that remain tightly linked to the baseline versions and artifacts defined by the <strong>Collection<\/strong>. This context-aware approach gives teams a unified place to track test progress, view relevant <strong>Test Runs<\/strong>, and maintain full oversight across all related <strong>Documents <\/strong>for more accurate coordination and higher confidence in validation outcomes.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/collection_full_2.png\" alt=\"Collections now offer a dedicated Test Runs view filtered to the scope of the Collection.\" class=\"wp-image-7416\" title=\"Collections now offer a dedicated Test Runs view filtered to the scope of the Collection.\"\/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><a><\/a>Related Collection enhancements<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>We enhanced several of our report <strong>Widgets <\/strong>so that <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/xrs8026334400992\" target=\"_blank\" rel=\"noreferrer noopener\">they can be used within the scope of a Collection<\/a>. To make it easier to find and use these enhanced <strong>Widgets,\u00a0<\/strong>we added a new <strong>Collections <\/strong>category. Several <strong>Widgets <\/strong>are supported for the 2512 release, and this complements the <strong>Collection<\/strong>-aware reporting with the <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/bot1724137049240\" target=\"_blank\" rel=\"noreferrer noopener\">scripting capability<\/a> we added in the 2506 release earlier this year.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/collection_widgets_for_polarion.png\" alt=\"To make it easier to find and use these enhanced Widgets,\u00a0we added a new Collections category.\" class=\"wp-image-7408\" title=\"To make it easier to find and use these enhanced Widgets, we added a new Collections category.\"\/><\/figure>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Report <strong>Widgets <\/strong>now offer greater flexibility in handling <strong>Collection <\/strong>contexts. When a <strong>Widget <\/strong>is configured for the <strong>Current Collection Context<\/strong>, it automatically adapts to the <strong>Collection <\/strong>and scope where the report is viewed, enabling easy reuse across various <strong>Collections<\/strong>. Alternatively, you can explicitly assign a <strong>Widget <\/strong>to a specific <strong>Collection <\/strong>and baseline, ensuring it always displays that fixed context, regardless of where the report is opened.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/select_current_collection_context.png\" alt=\"The new scope option set to Collections for the table widget.\" class=\"wp-image-7487\" title=\"The new scope option set to Collections for the table widget\"\/><\/figure>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OSLC linking is now fully supported for <strong>Collections<\/strong>, introducing a new <strong>Remote Links<\/strong> option within the <strong>Collection <\/strong>form. This lets you link a <strong>Collection\u00a0<\/strong>to other OSLC resources, such as <strong>Work Items<\/strong>, <strong>Documents<\/strong>, or even other <strong>Collections<\/strong>, and simultaneously displays any incoming OSLC backlinks. For a seamless experience, rich hover provides convenient previews of linked items, and clicking a link navigates you directly to the associated resource.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/oslc_remote_links.png\" alt=\"OSLC linking is now fully supported for  Collections, introducing a new Remote Links option within the Collection form.\" class=\"wp-image-7494\" title=\"OSLC linking is now fully supported for\u00a0Collections, introducing a new Remote Links option within the Collection form\"\/><\/figure>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OSLC revision resource linking has also been extended to include <strong>Collections<\/strong>. For more information, see the OSLC now supports Revision-based linking section of this blog.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><a><\/a>Boosting your productivity<\/h2>\n\n\n\n<p>We always value our conversations with customers. Your insights are invaluable in helping us continually enhance your Polarion experience. With this release, we focused on improving your productivity. We\u2019ve listened to your needs, and it\u2019s with great excitement that we announce a suite of enhancements designed to make your work even more effective and collaborative!<\/p>\n\n\n\n<p>Driven directly by your input, we\u2019re proud to share that this release incorporates a total of 32 functional enhancements requested directly by customers, successfully closing almost 202 customer Enhancement Requests (ERs)! These targeted improvements are all about making your daily tasks in Polarion more efficient and straightforward, helping you accomplish more with less effort.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Bring anyone into a conversation with @Mentions<\/h3>\n\n\n\n<p>We introduced user <strong>@Mentions <\/strong>to Polarion to improve team collaboration and boost productivity.<\/p>\n\n\n\n<p>Now, when you type <em>@<\/em> in <strong>Work Item<\/strong>, <strong>Document<\/strong>, or <strong>Page <\/strong>comments, a dynamic pop-up appears with a list of relevant <strong>Project <\/strong>users configurable by role. This lets you give and receive timely feedback, to and from the right people, easily and efficiently.<\/p>\n\n\n\n<p>To enable this feature, we upgraded all comments to rich text, so you can also use rich text formatting within your<strong> Work Item<\/strong>, <strong>Document<\/strong>, and <strong>Page <\/strong>comments to highlight important statements and increase clarity.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/add_mention_to_comment.png\" alt=\"We upgraded all comments to Rich Text, so you can also use Rich Text formatting within your Work Item, Document, and Page comments.\" class=\"wp-image-7457\" title=\"We upgraded all comments to Rich Text, so you can also use Rich Text formatting within your Work Item, Document, and Page comments.\"\/><\/figure>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/comments_mention.png\" alt=\"Mentions let you tag other users in a comment for better collaboration.\" class=\"wp-image-7498\" title=\"Mentions let you tag other users in a comment for better collaboration.\"\/><\/figure>\n\n\n\n<p>But we didn\u2019t stop with comments. We extended the&nbsp;<strong>Mention <\/strong>feature across all of Polarion\u2019s rich text fields.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">You can Mention team members in:<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Work Item<\/strong> <strong>Descriptions <\/strong>and rich text <strong>Custom Fields<\/strong>.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/mentions_in_work_item_description_fields.png\" alt=\"\" class=\"wp-image-7183\" title=\"Mentions can be used in Work Item Description and Rich Text Custom Fields\"\/><\/figure>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Throughout <strong>Documents<\/strong>.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/livedoc_mentions_2.png\" alt=\"\" class=\"wp-image-7502\" title=\"Mentions can be used directly in LiveDocs\"\/><\/figure>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Within <strong>Pages<\/strong>.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/page_region_mention.png\" alt=\"\" class=\"wp-image-7192\" title=\"Mentions can be used in Pages in Edit Mode\"\/><\/figure>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Even in <strong>Test Run<\/strong> rich text <strong>Custom Fields<\/strong>.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/testrun_custom_field.png\" alt=\"\" class=\"wp-image-7193\" title=\"Mentions can be used in Test Run rich text custom fields\"\/><\/figure>\n\n\n\n<p>See <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/kul5609862962846\" target=\"_blank\" rel=\"noreferrer noopener\">Mentions, Notifications, and Watchers<\/a> in Polarion Help for a table listing all the places you can use our new <strong>Mention <\/strong>feature.<\/p>\n\n\n\n<p>When a user is mentioned in a comment or rich text field, an email is immediately sent with a preview of the comment or the rich text that they are mentioned in. If multiple users are mentioned within the same comment, each of them receive a single notification for that comment.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/mention_email_notification.png\" alt=\"\" class=\"wp-image-7191\" title=\"Email generated from a mention used in a LiveDoc\"\/><\/figure>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/mention_email_notification_2_update.png\" alt=\"\" class=\"wp-image-7436\" title=\"Email generated from a mention used in a Work Item Description\"\/><\/figure>\n\n\n\n<p>By default, when you mention someone in <strong>Work Item<\/strong> or <strong>Page <\/strong>comments, they are also added as a<br><strong>Watcher<\/strong>. Administrators can disable this by setting the following property to <code>false<\/code>:<\/p>\n\n\n\n<p><code>mentionedUser.addWatcher.enabled<\/code><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>See more with Multi-sidebar support in Documents<\/h3>\n\n\n\n<p>Continuing our focus on boosting your productivity, we\u2019re thrilled to unveil <a href=\"https:\/\/docs.sw.siemens.com\/docs\/PL20250606201928474\/polarion_help_sc.xid1465510\/html\/xid1483374#yff1683231275400__section_rqw_gjn_qfc\" target=\"_blank\" rel=\"noreferrer noopener\">Multi-sidebar support<\/a> in <strong>Documents<\/strong>! To enhance overall usability and provide a more comprehensive view of your <strong>Document\u2019s<\/strong> content, you can now select and display multiple sidebars simultaneously. Imagine having your <strong>Document Outline <\/strong>sidebar open for quick navigation while concurrently viewing the detailed <strong>Work Item Properties<\/strong> sidebar. This combination means you no longer need to manually switch between essential views, which can cause you to lose focus.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/multi_sidebar.png\" alt=\"It's now possible to have multiple sidebars displayed for a Document.\" class=\"wp-image-7510\" title=\"It's now possible to have multiple sidebars displayed for a Document\"\/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Merge links automatically between Branched and Master Documents<\/h3>\n\n\n\n<p>In an effort to improve and speed up dealing with changes between <strong>Master <\/strong>and <strong>Branched Documents<\/strong>, we are happy to announce that both <strong>Automatic <\/strong>and <strong>Manual <\/strong>merge (using the <strong>Compare<\/strong>\/<strong>Merge <\/strong>action) have been enhanced to include the <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/rer4609400603850\" target=\"_blank\" rel=\"noreferrer noopener\">merging of Work Item links<\/a>. The removal or update of links pointing to other <strong>Work Items<\/strong> also now happens automatically when merging all fields. Links relative to the <strong>Document <\/strong>are automatically converted.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/push_to_master_document_3-1.png\" alt=\"The preview now shows if links will be merged.\" class=\"wp-image-7579\" title=\"The preview now shows if Links will be merged\"\/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Flexible Test Run creation from a Document at any Revision<\/h3>\n\n\n\n<p>We didn\u2019t forget about improving the productivity of our quality engineers and testers.\u00a0You can now generate <strong>Test Runs<\/strong> <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/xid1519920\" target=\"_blank\" rel=\"noreferrer noopener\">directly from your Documents<\/a> by selecting a specific <strong>Document<\/strong>, <strong>Revision<\/strong>, or even a <strong>Baseline <\/strong>during the creation process. This means no more editing or maintaining <strong>Test Run<\/strong> templates just to target a particular <strong>Document <\/strong>and version. Polarion intelligently prepares the <strong>Test Run<\/strong> with the correct <strong>Test Cases<\/strong> based on your chosen <strong>Document <\/strong>and its version, supporting both the \u2018<code>From LiveDoc on Create<\/code>\u2018 and \u2018<code>From LiveDoc on Execute<\/code>\u2018 strategies.<\/p>\n\n\n\n<p>An intuitive new <strong>Document and Revision<\/strong> picker makes this process flexible. While <strong>Document <\/strong>and <strong>Revision <\/strong>settings can be pre-populated from your templates, you retain full control to adjust them on the fly. This enhancement directly addresses a key customer request, allowing you to initiate <strong>Test Runs<\/strong> precisely from the right <strong>Document <\/strong>version, without extra overhead, keeping your test planning focused, efficient, and aligned with your <strong>Project\u2019s<\/strong> evolving context.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/flexible_test_run_creation-1024x491.png\" alt=\"\" class=\"wp-image-7464\" title=\"Using the Create Test Run Dialog, Test run template can be configured for letting users create test run directly from a document at any revision\"\/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Quicker Document Approvals with signature notifications<\/h3>\n\n\n\n<p>To accelerate your <strong>Document Approval<\/strong> process, we added <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/xid1554071\" target=\"_blank\" rel=\"noreferrer noopener\">signature notifications<\/a>.&nbsp;Say goodbye to delays and manual follow-ups, as Polarion now automatically alerts users when their signature is required on a <strong>Document<\/strong>. This means instant email notifications with direct links, allowing you to jump straight to the <strong>Document <\/strong>and take action without delay. You\u2019ll also receive real-time updates, not just when you\u2019re invited to sign, but also when others sign or decline, keeping everyone in the loop and significantly reducing approval cycle times.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/document_approval.png\" alt=\"\" class=\"wp-image-7516\" title=\"New notification events can be configured by administration for document signatures\"\/><\/figure>\n\n\n\n<p>For administrators, a new notification event in <img loading=\"lazy\" decoding=\"async\" width=\"16\" height=\"16\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/notification_sm.png\" alt=\"\"> <strong>Notifications Administration<\/strong> provides full control and visibility over these alerts, ensuring your approval processes are as efficient and transparent as possible.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Your own support agent with Polarion Help AI Chatbot<\/h3>\n\n\n\n<p>And finally, to conclude on the productivity boosters, we\u2019re introducing the <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/hlc6166590804976\" target=\"_blank\" rel=\"noreferrer noopener\">Polarion Help AI Chatbot<\/a>. This intelligent, AI-powered documentation assistant is designed to be a readily accessible resource, available directly from anywhere within Polarion. You can ask your questions, and it will provide clear, digestible help, serving as a quick reference without needing to search through extensive documentation, basically acting as your own support agent.<\/p>\n\n\n\n<p>Trained on Polarion\u2019s entire documentation set, it delivers structured answers with direct links to the source material for further details. This tool is conveniently located via the same new icon on the top right of the Polarion UI that you use for Polarion Copilot.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/12\/polarion_help_sidebar-1024x689.png\" alt=\"\" class=\"wp-image-7603\" title=\"The new Polarion Help AI Chatbot via its dedicated sidebar\"\/><\/figure>\n\n\n\n<p>Polarion Help runs on Siemens infrastructure. It is available for free&nbsp;for on-premise Polarion installations using Hybrid SaaS-type licenses. It can be enabled upon request \u2013 the process is described in <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/vuc7804978723657\" target=\"_blank\" rel=\"noreferrer noopener\">Polarion\u2019s Help Documentation<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><a><\/a>Helping our administrators<\/h2>\n\n\n\n<p>Polarion Administrators are essential. They support their Polarion users by mapping workflows, configuring <strong>Projects<\/strong>, and managing who can access what in Polarion. Many of these administrators are also responsible for additional infrastructure tasks, such as server maintenance and support. In Polarion 2512, we added the following features to make their lives easier:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Manage repository size by storing Attachments externally<\/h3>\n\n\n\n<p>As teams upload more screenshots, binaries, logs, and PDFs\u2014especially during test execution\u2014the Subversion repository can grow quickly. This can lead to increased repository size on the server, potentially impacting its maintenance.<\/p>\n\n\n\n<p>To address this, Polarion now offers <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/eam8960341332768\" target=\"_blank\" rel=\"noreferrer noopener\">new Attachment storage options<\/a> for storing files outside Subversion. This feature lets you attach files without inflating the repository or exceeding size limits. Storing these files externally helps keep the repository manageable, making backups and maintenance faster and more predictable.<\/p>\n\n\n\n<p><strong>Note<\/strong>: <em>This feature is optional, so you can continue storing Attachments directly in Subversion if preferred.<\/em><\/p>\n\n\n\n<p>When enabled, Polarion can store files in external systems such as AWS S3, Azure Blob Storage, Google Cloud Storage, or NFS, while preserving the same user experience and retaining full traceability.<br>Attachments remain accessible and secure, with real-time MIME type checks, file extension validation, and optional antivirus scanning on upload. This gives teams a cleaner and more scalable way to handle files \u2013 without changing the way they work.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Automatic antivirus scanning for Attachments<\/h3>\n\n\n\n<p>To help organizations maintain robust security around file uploads and meet compliance requirements, Polarion now supports <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/iew1593275664872\" target=\"_blank\" rel=\"noreferrer noopener\">antivirus scanning for all Attachments<\/a>.<br>This new configurable scanning feature allows administrators to connect their preferred antivirus solution. Every uploaded file is checked before it\u2019s stored. If the scanner reports a problem, the upload is blocked, and the uploader is notified. This provides a straightforward way to enhance security without disrupting existing workflows.<\/p>\n\n\n\n<p>Note<em>: The feature is optional; if no scanner is configured, Attachment upload will continue to work as it does today.<\/em><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Import and export Projects across Polarion instances<\/h3>\n\n\n\n<p>Transferring <strong>Projects <\/strong>between different Polarion instances, bootstrapping new environments, or sharing standardized <strong>Project <\/strong>configurations have often required manual steps, reliance on Subversion tools, or workarounds.<\/p>\n\n\n\n<p>To simplify these processes, we created a new <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/dnb4163891779805\" target=\"_blank\" rel=\"noreferrer noopener\">Export\/Import Project<\/a> feature. You can now export an existing project as a simple .zip archive. You can then use that file to create a brand-new <strong>Project <\/strong>instantly.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/import_export_projects.png\" alt=\"New Import\/Export Project options in the Project topic in Administration.\" class=\"wp-image-7210\" title=\"New Import\/Export Project options in the Project topic in Administration.\"\/><\/figure>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/Polarion_import_project_dialog.png\" alt=\"The new &quot;Import Project&quot; dialog.\" class=\"wp-image-7212\" title=\"The new &quot;Import Project&quot; dialog.\"\/><\/figure>\n\n\n\n<p>This eliminates the need for Subversion tools, manual checkouts, or template workarounds, making cross-instance <strong>Project <\/strong>mobility far more accessible. Teams can easily transfer <strong>Projects<\/strong>, quickly set up new instances, or share standardized setups across organizations. Imported <strong>Projects <\/strong>get created cleanly, without a version history, providing you with a lightweight, consistent starting point.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Managing Velocity Widgets<\/h3>\n\n\n\n<p>Velocity <strong>Widgets <\/strong>are a popular customization option in Polarion that extends <strong>Page <\/strong>content by rendering dynamic reports.<\/p>\n\n\n\n<p>In 2512, we added a new <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/ezy8953247485207\" target=\"_blank\" rel=\"noreferrer noopener\">Administration topic<\/a> in Polarion\u2019s UI, making it easier than ever to manage Velocity <strong>Widgets<\/strong> and eliminating the need for external tools like the Repository Browser.<\/p>\n\n\n\n<p>(<strong>Administration<\/strong> <img loading=\"lazy\" decoding=\"async\" width=\"28\" height=\"14\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/black_arrow.png\" alt=\"\"> <strong>Documents and Pages<\/strong> <img loading=\"lazy\" decoding=\"async\" width=\"28\" height=\"14\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/black_arrow.png\" alt=\"\"><strong>Velocity Widgets<\/strong> )<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/velocity_widget_administration_in_Polarion.png\" alt=\"You can Upload, Download, or Delete widgets from the new Administration topic.\" class=\"wp-image-7216\" title=\"You can Upload, Download, or Delete widgets from the new Velocity Widget Administration\u00a0topic.\"\/><\/figure>\n\n\n\n<p>The <strong>Velocity Widgets<\/strong> topic is available on both the <strong>Global <\/strong>and <strong>Project <\/strong>levels.<\/p>\n\n\n\n<p>There, you can easily <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/ngb6614936538326\" target=\"_blank\" rel=\"noreferrer noopener\">Upload<\/a>, <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/lmk3224961701027\" target=\"_blank\" rel=\"noreferrer noopener\">Download<\/a>, or <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/oex2718098076686\" target=\"_blank\" rel=\"noreferrer noopener\">Delete<\/a><strong> Widgets<\/strong> from the Polarion repository.<\/p>\n\n\n\n<p><em><strong>Looking to update an existing Velocity Widget?<\/strong><\/em><br>Just name the folder in your update archive to the same name as the existing <strong>Widget\u2019s <\/strong>folder and <strong>Upload <\/strong>it.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Search for deactivated users<\/h3>\n\n\n\n<p>Administrators can now search for deactivated users in <strong>User Management<\/strong> &#8211; <strong>Users<\/strong>, making user license management easier and more transparent. They can easily unassign licenses from users who are no longer active by selecting the new \u201c<strong>Show only Disabled Users<\/strong>\u201d filter at the top, then unassigning licenses from the users that appear in the list to help keep team license usage optimized and up to date.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/delete_disabled_users_in_polarion.png\" alt=\"Delete disabled users in Polarion\" class=\"wp-image-7239\" title=\"New option in User Administration topic to search for deactivated users\"\/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Check for duplicated Project prefixes<\/h3>\n\n\n\n<p>When <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/xid1484304\" target=\"_blank\" rel=\"noreferrer noopener\">creating a new<\/a> <strong>Project<\/strong>, Polarion now automatically checks for existing <strong>Work Item<\/strong> prefixes.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/12\/polarion_prefix_warning.png\" alt=\"\" class=\"wp-image-7608\"\/><\/figure>\n\n\n\n<p>If a selected prefix is already in use, administrators receive a warning to help ensure unique prefixes across all <strong>Projects<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Execute Scheduled Scripts on-demand<\/h3>\n\n\n\n<p>Building on the <strong>Scheduled Scripts<\/strong> feature introduced in our last release, you can now <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/zrh5186003774487\" target=\"_blank\" rel=\"noreferrer noopener\">execute any configured scheduled script on-demand<\/a> directly from Polarion <strong>Administration<\/strong>.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/trigger_polarion_scheduled_script.png\" alt=\"Execute any configured scheduled script on-demand.\" class=\"wp-image-7246\" title=\"Execute any configured scheduled script on-demand.\"\/><\/figure>\n\n\n\n<p>No more waiting for the next scheduled run. This capability allows you to instantly trigger scripts for immediate testing, troubleshooting, or urgent tasks, even those currently disabled from their regular schedule. Plus, for complete transparency, the script log will indicate whether a script was run by a schedule or manually via the <strong>Administration <\/strong>UI, giving you complete visibility and control over your automation processes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><a><\/a>Enhanced Integration Capabilities<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"OSLC_revision_based_linking\"><a><\/a>OSLC now supports Revision-based linking<\/h3>\n\n\n\n<p>OSLC (Open Services for Lifecycle Collaboration) is an open standard for integrating tools across the software development lifecycle, enabling applications to share data, link related artifacts, and maintain traceability. In 2512, this integration offers a new level of precision, letting you create OSLC links that <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/xid1551487\" target=\"_blank\" rel=\"noreferrer noopener\">point directly to specific revisions<\/a> of your Polarion <strong>Work Items<\/strong>, <strong>Documents<\/strong>, and <strong>Collections<\/strong>.<\/p>\n\n\n\n<p>The Polarion delegated OSLC resource picker provides the flexibility to select and link to any particular revision you need, ensuring your OSLC connections accurately reflect the exact state of your artifacts at a given point in time, rather than just the latest version.<\/p>\n\n\n\n<p>So, for example, if you use JIRA with a JIRA OSLC plugin that\u2019s configured to work with Polarion, when you attempt to link from a JIRA item to a Polarion <strong>Work Item<\/strong>, the Polarion delegated OSLC picker lets you select not just the <strong>Work Item<\/strong>, but also its <strong>Revision <\/strong>(or <strong>Baseline<\/strong>).<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/oslc_revision.png\" alt=\"The OSLC picker now allows you to select a work-item revision to link.\" class=\"wp-image-7250\" title=\"The OSLC picker now allows you to select a work-item revision to link\"\/><\/figure>\n\n\n\n<p>To further help and simplify linking to the correct <strong>Work Item<\/strong> <strong>Revision<\/strong>, the OSLC resource picker was enhanced so that you can filter the list of <strong>Work Items<\/strong> by either a <strong>Collection <\/strong>baseline <em>and <\/em><strong>Document <\/strong>Baseline, <em>or <\/em>just the <strong>Document <\/strong>(baseline), and Polarion will then show the corresponding <strong>Work Item<\/strong> (revisions) that are valid for the filter. This makes it easier to find and link to the correct <strong>Work Items<\/strong> and their <strong>Revisions<\/strong>.&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/olsc_select_revision2.png\" alt=\"To improve productivity, the OSLC picker allows you to select Work Items by Collection and\/or Document revision.\" class=\"wp-image-7253\" title=\"To improve productivity, the OSLC picker allows you to select Work Items by Collection and\/or Document revision.\"\/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Third-party cookies support OSLC<\/h3>\n\n\n\n<p>To maintain the compatibility of our OSLC feature set with modern browsers, we have updated our approach for <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/xid2210121\" target=\"_blank\" rel=\"noreferrer noopener\">handling third-party cookies<\/a>. This ensures that OSLC remains functional and consistent as you integrate your tools.<\/p>\n\n\n\n<figure class=\"wp-block-image is-resized\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/important_callout.png\" alt=\"\" class=\"wp-image-7258\" style=\"width:200px\"\/><\/figure>\n\n\n\n<p>Because this is security-related, this is a great opportunity to review your security settings! For details, please review the bundled config changes text (<code>5_Required_Config_changes.txt<\/code>).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Documents from the same Space and Simplified Export for ReqIF<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>We added the ability to <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/xid1489773\" target=\"_blank\" rel=\"noreferrer noopener\">add several Documents from the same Space<\/a> to an existing ReqIF file to the UI.\u00a0 This can be useful when leveraging the <strong>Spaces <\/strong>for classifying your <strong>Requirements <\/strong>specifications.\u00a0<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/add_to_reqif_document-1.png\" alt=\"It's now easy to add documents to an existing ReqIF package.\" class=\"wp-image-7262\" title=\"It's now easy to add documents to an existing ReqIF package directly from the Space Index\"\/><\/figure>\n\n\n\n<ul class=\"wp-block-list\">\n<li>To help you keep your ReqIF files up-to-date, we\u2019ve introduced a new \u2018<strong>ReqIF Export<\/strong>\u2018 option, conveniently located under the \u2018<strong>CREATE<\/strong>\u2018 button in the <strong>Navigation <\/strong>header. This opens a new dialog listing all ReqIF files in your current <strong>Project<\/strong>. From there, you can easily export them, ensuring they reflect their most recent data with just a single click. This feature is particularly useful for quickly updating ReqIF files that were previously exported from Polarion.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/quick_create_export_reqif.png\" alt=\"Import or Export ReqIF documents from the Quick Create menu.\" class=\"wp-image-7265\" title=\"New ReqIF\u00a0Export documents option from the Quick Create menu.\"\/><\/figure>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/export_polarion_LiveDoc_Document.png\" alt=\"Ability to quickly export an existing ReqIF package.\" class=\"wp-image-7269\" title=\"Ability to quickly export an existing ReqIF package\"\/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Improved ReqIF compatibility with IBM DOORS<\/h3>\n\n\n\n<p>We <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/xid2205294\" target=\"_blank\" rel=\"noreferrer noopener\">revised the way<\/a> Polarion treats ReqIF files that only contain a single item type. Previously, for all of these files, we showed two \u201cvirtual\u201d item types: <strong>Heading <\/strong>and <strong>Requirement<\/strong>. This led to confusion and customers wondering where the second item type comes from. We resolved this by now only having \u201cvirtual\u201d item types for ReqIF files that come from DOORS and adapted the terminology of virtual types in the UI to indicate DOORS connections.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/updated_doors_ui.png\" alt=\"Revised mapping for DOORS objects.\" class=\"wp-image-7272\" title=\"Revised mapping for DOORS objects\"\/><\/figure>\n\n\n\n<p><strong>Note:<\/strong> You can revert to the old behavior by adding the following Configuration Polarion property:<br><code>reqif.import.virtualTypesForNonDoors.enabled=true<\/code><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Support of rich text Comments with JIRA integration<\/h3>\n\n\n\n<p>As mentioned earlier, user <strong>Mentions <\/strong>are now fully supported within the now <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/kul5609862962846\" target=\"_blank\" rel=\"noreferrer noopener\">rich text-capable comment fields<\/a>. Building on this, our JIRA Connector was updated to support bi-directional synchronization of rich text formatting and user <strong>Mentions<\/strong>, complete with correct user mapping across applications. This means your conversations and critical information stay aligned, no matter which tool your team uses.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Personal Access Token support for sync pair configuration<\/h3>\n\n\n\n<p>Personal Access Tokens (PATs) are a widely adopted alternative to password authentication when integrating third-party applications. In this release, we extended the <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/rph6605313032762\" target=\"_blank\" rel=\"noreferrer noopener\">use of PATs in sync pair configurations<\/a> when connecting to Polarion (the left side of the configuration) with the JIRA, Azure DevOps and HP ALM integrations.<\/p>\n\n\n\n<p>PATs are securely stored in your <strong>User Account Vault<\/strong>, providing a more robust and secure authentication method than traditional credentials. They allow you to set expiration dates and can be <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/xid2210303\" target=\"_blank\" rel=\"noreferrer noopener\">revoked at any time<\/a>, giving you more control over your integrations.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Expanded Polarion REST API capabilities<\/h3>\n\n\n\n<p>We have significantly enhanced our REST API capabilities by introducing new endpoints that provide comprehensive control and flexibility across key areas.<\/p>\n\n\n\n<p>For detailed information, see our REST API documentation in the <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.sdk\" target=\"_blank\" rel=\"noreferrer noopener\">SDK<\/a> and the <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid2134849\/xid2134871\" target=\"_blank\" rel=\"noreferrer noopener\">REST API User Guide<\/a>, but here\u2019s a brief summary:<\/p>\n\n\n\n<p><strong>Collections<\/strong><\/p>\n\n\n\n<p>We expanded the <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid2134849\/aur1729187940150\" target=\"_blank\" rel=\"noreferrer noopener\">Collection<\/a> endpoints to support <strong>Document<\/strong> and <strong>Page <\/strong>retrievals from Polarion<br><strong>Collections<\/strong>. We also implemented an action endpoint to reuse an existing <strong>Collection<\/strong>.<\/p>\n\n\n\n<p><strong>Custom fields<\/strong><\/p>\n\n\n\n<p>You can now administer <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid2134849\/fsj8692626963886\" target=\"_blank\" rel=\"noreferrer noopener\">Custom fields<\/a> through our REST API. You can use new custom field endpoints to read and change the configuration for Polarion artifact types like <strong>Work Items<\/strong> and <strong>Documents<\/strong> and their subtypes (<strong>Tasks<\/strong>, <strong>Defects<\/strong>, <strong>User Stories<\/strong>, and so on).<\/p>\n\n\n\n<p><strong>Documents<\/strong><\/p>\n\n\n\n<p>It is now possible to search for <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid2134849\/xid2213343\" target=\"_blank\" rel=\"noreferrer noopener\">Documents<\/a> on both the <strong>Project <\/strong>and <strong>Global <\/strong>levels and filter the results with a Lucene query.<br>With improved <code>POST<\/code> and <code>PATCH <\/code>endpoints, <strong>Document Parts<\/strong> can now be placed and moved within a <strong>Document<\/strong>, and their indentation can be updated to set the level of their parent-child relation, along with their children in the <strong>Document <\/strong>structure.<br><strong>Headings <\/strong>are now considered a standard <strong>Document Part<\/strong>, and their handling is no longer impeded.<\/p>\n\n\n\n<p><strong>Enumerations<\/strong><\/p>\n\n\n\n<p>New endpoints allow the listing of all existing <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid2134849\/xid2213332\" target=\"_blank\" rel=\"noreferrer noopener\">Enumerations<\/a> on a given level (<strong>Project <\/strong>or <strong>Global<\/strong>), including those that are inherited, for all Polarion object types that support them.<\/p>\n\n\n\n<p><strong>Fields metadata<\/strong><\/p>\n\n\n\n<p>The new <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid2134849\/hgy8534384709252\" target=\"_blank\" rel=\"noreferrer noopener\">Fields metadata<\/a> endpoints let you retrieve the complete field schema of <strong>Work Items<\/strong>, <strong>Documents<\/strong>, <strong>Test Runs<\/strong>, and <strong>Plans<\/strong>. You receive a list of all attributes and relationships, including both built-in and custom fields, that are currently configured for a given object or are inherited from a higher-level custom field definition.<\/p>\n\n\n\n<p><strong>Jobs<\/strong><\/p>\n\n\n\n<p>It is now possible to search for <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid2134849\/eco7621051713221\" target=\"_blank\" rel=\"noreferrer noopener\">Jobs<\/a>on both the <strong>Project <\/strong>and <strong>Global <\/strong>levels and filter the results with a Lucene query. Retrieved <strong>Jobs <\/strong>now provide access to the <strong>Job logs<\/strong>, ensuring complete visibility into <strong>Job <\/strong>execution details. A new endpoint also allows users to execute a specific <strong>Job <\/strong>directly.<\/p>\n\n\n\n<p><strong>Licensing<\/strong><\/p>\n\n\n\n<p>The newly introduced endpoints extensively cover <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid2134849\/fml0519405292065\" target=\"_blank\" rel=\"noreferrer noopener\">Licensing<\/a>.<br>Admins can configure the default <strong>Base <\/strong>and <strong>Add-on<\/strong> type Licenses and manage <strong>License Groups<\/strong> and <strong>Slots<\/strong>. They can also assign Licenses to specific Users and display an overview of <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid2134849\/lai0330868511951\" target=\"_blank\" rel=\"noreferrer noopener\">assigned Slots<\/a> for all available License types.<\/p>\n\n\n\n<p>Polarion now provides <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/xid1568232\" target=\"_blank\" rel=\"noreferrer noopener\">License Usage Statistic<\/a> reporting, including detailed usage information and usage limits.<\/p>\n\n\n\n<p>There have also been updates to the existing <strong>User Management<\/strong> endpoints that enable the display of License information that\u2019s currently assigned to a specific User. This ensures that User License data can be easily accessed alongside other User-related information, so it can be validated in external tools and ensures your users receive the appropriate licenses.<\/p>\n\n\n\n<p><strong>Metadata<\/strong><\/p>\n\n\n\n<p>This endpoint, available to all Polarion users, provides general information about the <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid2134849\/hgy8534384709252\" target=\"_blank\" rel=\"noreferrer noopener\">Polarion instance and its configuration<\/a>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Polarion Version, Build, Node, Time Zone, Logo URL<\/li>\n\n\n\n<li>REST API Properties: Default Page Size, Max Page Size, Max Relationship Size, Body Size Limit, Max Includes Size<\/li>\n<\/ul>\n\n\n\n<p><strong>Pages<\/strong><\/p>\n\n\n\n<p>It is now possible to search for <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid2134849\/vvw7114774859868\" target=\"_blank\" rel=\"noreferrer noopener\">Pages<\/a> on both the <strong>Project <\/strong>and <strong>Global <\/strong>levels and filter the results with a Lucene query.<br>The <strong>Page <\/strong>resource also supports accessing and updating the <code>HomePage Content<\/code> attribute, which contains the <strong>Page LiveReport<\/strong>, allowing users to adjust the data displayed on the <strong>Page<\/strong>.<br>We\u2019ve also expanded the <strong>LiveReport Pages<\/strong> topic with new endpoints that let users create\/delete <strong>Pages<\/strong>, get and manage <strong>Page Attachments<\/strong>, and work with <strong>Page Comments<\/strong> and <strong>Watches<\/strong>.<\/p>\n\n\n\n<p><strong>User Management<\/strong><\/p>\n\n\n\n<p>As already mentioned in the <strong>Licensing <\/strong>section, the <strong>User <\/strong>resource now contains information about the <strong>Base <\/strong>and <strong>Add-on<\/strong> Licenses currently <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid2134849\/fml0519405292065\" target=\"_blank\" rel=\"noreferrer noopener\">assigned to a specific user<\/a>.<\/p>\n\n\n\n<p>We also added a new <code>GET<\/code> user endpoint that allows any user to retrieve information about themselves. Every user has access to this endpoint, regardless of whether their Global REST API Permissions are enabled.<\/p>\n\n\n\n<p><strong>Work Items<\/strong><\/p>\n\n\n\n<p>It is now possible to <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid2134849\/shl8706510526066\" target=\"_blank\" rel=\"noreferrer noopener\">create multiple backlinked Work Items<\/a> using a single endpoint call. This reduces the number of REST API calls required to make a linked Work Item structure.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Configuration Management and branching with the MathWorks Simulink Connector<\/h3>\n\n\n\n<p>We have added many new productivity and ease-of-use improvements to our very popular <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid2045375\/xid2049626\" target=\"_blank\" rel=\"noreferrer noopener\">Mathworks Simulink Connector<\/a>. Some of the highlights of this new release include support for <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid2045375\/ftk4933109471936\" target=\"_blank\" rel=\"noreferrer noopener\">configuration managment-aware<\/a> models as well as improved support for working with <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid2045375\/pbf5696627065272\" target=\"_blank\" rel=\"noreferrer noopener\">Polarion Branched Documents<\/a>.<\/p>\n\n\n\n<p>It\u2019s not uncommon to put Simulink models under revision control using a third-party revision control system such as GitLab. We improved our <strong>Polarion Connector <\/strong>so that model surrogates contain information about the model under revision control and even provide a navigation link to the model in the revision control system. This means that you can create a global baseline in Polarion that reflects not just the Polarion artifacts (<strong>Documents<\/strong>, <strong>Requirements<\/strong>, <strong>Work Items<\/strong>, <strong>Test Cases<\/strong>, and so on) but also the model artifacts and a pointer to the revision of the model in the remote revision control system.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/simulink_configuration_management.png\" alt=\"Simulink Surrogate Work Item showing attributes (custom fields) and links associated with the Simulink model under revision control.\" class=\"wp-image-7321\" title=\"Simulink Surrogate Work Item showing attributes (custom fields) and links associated with the Simulink model under revision control.\"\/><\/figure>\n\n\n\n<p>Polarion itself has powerful reuse and branching capabilities built in. Sometimes it may be necessary to work with a branched version of a Polarion <strong>Document <\/strong>rather than the document\u2019s master version with your Simulink model \u2013&nbsp; if, for example, you need to patch an earlier version of your product\u2019s software or implementation.<\/p>\n\n\n\n<p>The <strong>Connector <\/strong>has been enhanced so that it\u2019s now easy to work with <strong>Branched Documents<\/strong>. The <strong>Connector <\/strong>will automatically recognize a <strong>Branched Document <\/strong>and ask you if you wish to replace the <strong>Master <\/strong>version of the <strong>Document<\/strong> with the newer <strong>Branched <\/strong>version. In this case, the <strong>Connector <\/strong>will automatically move any links to model elements that were linked to the <strong>Master Document<\/strong> over to the new <strong>Branched Document<\/strong>. After running the update backlinks operation, the surrogate model elements in Polarion will now automatically point to the <strong>Branched Document<\/strong>.<\/p>\n\n\n\n<p>Several additional productivity improvements have been made to the <strong>Connector<\/strong>, including:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Enabled setting the startup mode for the <strong>Connector <\/strong>(for example <strong>Requirements<\/strong> or <strong>Direct Linking modes<\/strong>).<\/li>\n\n\n\n<li>Improved the labeling of direct links for enhanced readability and to ensure they can be kept current.<\/li>\n\n\n\n<li>Added the ability to skip documents during import if they are part of a <strong>Collection<\/strong>.<\/li>\n\n\n\n<li>Improved backlinking speed by restricting backlink processing to selected model elements.<\/li>\n\n\n\n<li>Introduced the ability to define a live <strong>Document<\/strong> to contain all Simulink surrogate <strong>Work Items<\/strong>.<\/li>\n<\/ul>\n\n\n\n<p>The <a href=\"https:\/\/extensions.polarion.com\/extensions\/397-polarion-connector-for-simulink\" target=\"_blank\" rel=\"noreferrer noopener\">new<\/a> version of the Simulink <strong>Connector <\/strong>will be available from the Extension Portal shortly.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Domain validation for the Rhapsody Connector<\/h3>\n\n\n\n<p>We\u2019re always working to ensure our <strong>Connectors <\/strong>provide robust support for your specific engineering needs.&nbsp;The <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/fgb1716199418397\" target=\"_blank\" rel=\"noreferrer noopener\">Polarion Connector for Rhapsody<\/a> was tested and validated to work with the following predefined domain specific profiles:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>AUTOSAR_470<\/code><\/li>\n\n\n\n<li><code>AUTOSAR_480_R2211<\/code><\/li>\n\n\n\n<li><code>FMEA_Profile<\/code><\/li>\n\n\n\n<li><code>ISO_26262_Profile<\/code><\/li>\n\n\n\n<li><code>ModernCpp<\/code><\/li>\n\n\n\n<li><code>UAF<\/code><\/li>\n<\/ul>\n\n\n\n<p>You can now confidently use Polarion with your Rhapsody models that leverage these domain profiles, ensuring your <strong>Projects <\/strong>remain compliant and efficient.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><a><\/a>Security updates<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Refined Monitor topic and Job management permissions<\/h3>\n\n\n\n<p>In our last release, we introduced a new global permission, <code>MANAGE_JOBS<\/code>, to execute jobs and limit access to information about those that are currently running and scheduled. We had to grant this permission to the global&nbsp;user role by default to ensure continuity.<\/p>\n\n\n\n<p>With this release,\u00a0we enhanced job management permissions for more granular control over job visibility and execution. Users without <code>MANAGE_JOBS<\/code> permission can now access the <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/xid1489492\" target=\"_blank\" rel=\"noreferrer noopener\">Monitor<\/a> topic to view the status and logs of jobs they personally initiated (such as exports or merges), but they cannot execute any system jobs.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/manage_job_permission_update.png\" alt=\"\" class=\"wp-image-7336\" title=\"Warning shown in the Monitor when a user does not have the MANAGE JOBS permission\"\/><\/figure>\n\n\n\n<p>In contrast, users granted the <code>MANAGE_JOBS<\/code> permission have full visibility into all executed jobs and the ability to execute system jobs directly from the <strong>Monitor <\/strong>topic:<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2025\/11\/monitor_running_jobs_in_polarion.png\" alt=\"\" class=\"wp-image-7339\" title=\"Full Monitor view when a user has the MANAGE_JOBS permssion\"\/><\/figure>\n\n\n\n<p>On the <strong>Monitor <\/strong>page, <strong>Jobs <\/strong>are displayed and organized according to their execution context. For example, if a <strong>Job <\/strong>was triggered by an API, it will be assigned a global context, which appears as <code>system<\/code> in the <strong>Monitor<\/strong>. In the <strong>Global <\/strong>context, you will see all globally executed jobs that you have permission to view.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><a><\/a>Performance and scalability<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Scalability white paper<\/h3>\n\n\n\n<p>Performance remains one of our top priorities, and Polarion 2512 delivers continued stability even under demanding enterprise workloads. As part of this release, we executed extensive performance, scalability, and endurance tests using a 20-million\u2013work-item repository and thousands of concurrent simulated users. These tests validate not only response times but also long-running system behavior, data handling, and the impact of new security features introduced in recent versions.<br><br>To help customers understand the results and apply the same practices in their own environments, we\u2019ve published a comprehensive performance white paper. It includes detailed findings, test methodology, system configuration, tuning guidance, and a release-to-release comparison of key use cases. If you want a deeper look into the numbers, setup, scenarios, and runtime insights, the white paper provides everything end-to-end.<\/p>\n\n\n\n<p>Read the dedicated blog post <a href=\"https:\/\/blogs.sw.siemens.com\/polarion\/polarion-alm-2512-enterprise-scale-alm-validated-for-7000-concurrent-users\/\">here<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Performance improvements<\/h3>\n\n\n\n<p>With Polarion 2512, we are delivering a series of performance and scalability boosts, bringing faster response times across the platform:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Significantly faster save operations\u00a0<\/strong>when saving <strong>Work Items<\/strong> that use <a href=\"https:\/\/docs.sw.siemens.com\/en-US\/doc\/230235217\/PL20250606201928474.polarion_help_sc.xid1465510\/onl1729085397714\" target=\"_blank\" rel=\"noreferrer noopener\">Save Hook scripts<\/a> \u2014 reducing <strong>Work Item<\/strong> save times by\u00a0<strong>tens of percent<\/strong>\u00a0in real scenarios.<\/li>\n\n\n\n<li><strong>More efficient authentication<\/strong> with database-backed password handling as the new default for SVN, low-level operations, and report delivery is <strong>5 \u2013 10% faster<\/strong>.<\/li>\n\n\n\n<li><strong>Java 21 support<\/strong> brings modern JVM optimizations, resulting in <strong>overall performance gains<\/strong> \u2013 typically <strong>5\u201320%<\/strong> across different use cases like rendering formulas, loading <strong>Work Items<\/strong>, using <strong>Save Hooks<\/strong> and <strong>Word Round-trip<\/strong>, reusing\u00a0<strong>Documents<\/strong>, and so on.<\/li>\n\n\n\n<li><strong>Improved PostgreSQL caching<\/strong>, providing consistent performance enhancements across a wide range of workflows \u2013 including up to <strong>10% faster logins and up to 5% faster Document saves<\/strong>.<\/li>\n\n\n\n<li><strong>Optimized SVN access-file evaluation<\/strong>, reducing NFS and Apache overhead and improving responsiveness in Cluster and large-scale deployments. This results in a <strong>30% reduction in memory usage<\/strong> and a <strong>20% improvement in Page loading<\/strong>.<\/li>\n\n\n\n<li><strong>Up to 90% faster Project loading<\/strong> in the Project Explorer, thanks to a redesigned loading mechanism that also accelerates document-reuse workflows.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a>Location Index (early adoption)<\/h3>\n\n\n\n<p>Polarion 2512 introduces an <strong>early adoption<\/strong> release of the new <strong>Location Index<\/strong>, a foundational update to the underlying data layer, and the long-term replacement for legacy Object Maps. Built on a PostgreSQL-backed design, <strong>Location Index<\/strong> enhances robustness and system resilience. Even in this early phase, it already supports the main indexing scenarios and historical object resolution across typical operations such as moves and renames. Certain complex or less common scenarios \u2013 especially those involving repeated renaming, deletion, or reuse of old names \u2013 are still under active development and planned for completion in future releases. The database-driven design also helps alleviate several pain points seen in large deployments, including the shutdown overhead associated with legacy Object Maps.<\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Das neue Polarion ALM 2512 ist verf\u00fcgbar und steht zum Update\/Download bereit. Eine Zusammenfassung der neuen Highlights gibt es hier &#8211; Polarion Blog von Siemens Neuigkeiten: Bringing the power of Artificial Intelligence to Polarion Siemens is uniquely positioned to drive Industrial AI and help our customers bridge the gap between generic AI model-based agentic use [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1,7],"tags":[31,29,9,30,10],"class_list":["post-361","post","type-post","status-publish","format-standard","hentry","category-allgemein","category-application-life-cycle-management","tag-31","tag-ai","tag-alm","tag-ki","tag-polarion"],"_links":{"self":[{"href":"https:\/\/www.covalgo.at\/blog\/wp-json\/wp\/v2\/posts\/361","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.covalgo.at\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.covalgo.at\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.covalgo.at\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.covalgo.at\/blog\/wp-json\/wp\/v2\/comments?post=361"}],"version-history":[{"count":19,"href":"https:\/\/www.covalgo.at\/blog\/wp-json\/wp\/v2\/posts\/361\/revisions"}],"predecessor-version":[{"id":413,"href":"https:\/\/www.covalgo.at\/blog\/wp-json\/wp\/v2\/posts\/361\/revisions\/413"}],"wp:attachment":[{"href":"https:\/\/www.covalgo.at\/blog\/wp-json\/wp\/v2\/media?parent=361"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.covalgo.at\/blog\/wp-json\/wp\/v2\/categories?post=361"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.covalgo.at\/blog\/wp-json\/wp\/v2\/tags?post=361"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}