https://community.rws.com/product-groups/timearc-user-community/en-USTelligent Community 12 Non-Productionhttps://community.rws.com/product-groups/timearc-user-community/product-updates/b/product-update-s/posts/timearc-v4-19-is-now-liveThu, 16 Apr 2026 09:21:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:ff9f681b-40f4-4981-a727-c43cbe5423ccJustin HarrisonPublishing UI - Part 2 1. Preview Publication Table of Contents When content is selected for publishing and the user advances to the Review page, the selected items are displayed alongside a preview of the table of contents for each resulting Publication in the Portal. This enables users to understand the impact of their publishing choices before any updates are applied, giving them the opportunity to refine their selections or proceed with confidence. For Collections published that have multiple Publication Filters, the Review page presents a separate preview for each resulting Publication. Users can review how each Publication’s table of contents will appear in the Portal prior to publishing, ensuring that the output aligns with their expectations. Note: The functionality will be released in a separate patch to the 4.19.0 release and will include more detailed release notes. 2. Publishing UI – Filtering Selections When partially publishing a Collection, users can now refine their selection using enhanced filters. In addition to filtering by document name or folder name, users can filter content by attributes such as change type, last published date, and other relevant metadata. These expanded filtering options are particularly beneficial for Collections with a high volume of documents and files, helping ensure that the appropriate content is accurately identified and selected for publishing. Note: The functionality will be released in a separate patch to the 4.19.0 release and will include more detailed release notes. Projects - The next phase of Editorial Projects 1. Editorial Projects in Primary Navigation In the 4.19 release, Editorial Projects has been elevated from a table of contents accordion item to a dedicated primary navigation item, now named Projects . This change reflects the growing role of project-based workflows in the CCMS and addresses usability challenges that came with its previous placement. What's changed? Renamed: ‘Editorial Projects’ has been renamed to "Projects" in the CCMS. Promoted to primary navigation : Projects is now accessible as a primary navigation item, replacing its previous location as a TOC accordion. Search : Editors can now search for both projects and amendments directly within the Projects view. Empty state handling: Collections with no projects will display an appropriate empty state within the Projects view. What's unchanged? All existing amendment creation and merge workflows remain the same. Projects and amendments created prior to this release are fully accessible within the new ‘Projects’ view. No data migration or editor action is required. 2. Archive Projects Editors can now archive amendments and editorial projects directly within the CCMS, replacing the previous process of raising a development support ticket. Archived amendments are accessible from the ‘Archive’ tab within ‘Projects’, providing a separation from active work. What's new? Archive an amendment : Editors can archive individual amendments from within a project. Archive a project : Editors can archive an entire project’s folder Retrieve archived items : Archived amendments and projects can be restored by editors without development involvement. Retrieving a project restores all its child amendments. Retrieving an amendment restores that amendment and its parent project. Archived items are read-only : Content within archived amendments cannot be edited. Clear visual distinction : Archived amendments and projects are clearly separated from active ones in the Projects view. What's unchanged Amendment creation, merging, and document editing workflows are unaffected. Permanent deletion and bulk archiving are not supported as a part of this feature. 3. Refine Component Search Results by its Parent’s Metadata Values The CCMS search experience has been enhanced to allow editors to refine search results by the metadata values of its parent items. This release also introduces the ability to refine search results by metadata text fields, a capability previously unavailable in refine results. What's new Filter by metadata text fields : Users can now refine search results using metadata text values. Grouped metadata types : Configured metadata values are displayed in a single categorized view, grouped by Components, Documents, and Folders. Cross-level component filtering : Component search results can now be refined by the metadata of their parent documents and folders, not just the component itself. Combined selections apply as cumulative filters. A component must satisfy all selected criteria to appear in results. What's unchanged Existing search behavior, document-to-component linking, and search architecture are unaffected Video Webinar www.youtube.com/watch Resolved Bugs TIM-1717 Linked copy components background not rendered in Portal as per CCMS TIM-2156 Failing Metadata update to Documents created from Templates TIM-2146 Published file versions not updated in Portal TIM-1996 Bi-directional relationship links ("Related From") field shows duplicate links when Linked-Copy-Documents exist TIM-2084 Handle components without draft EN-746 Cross reference links present within published documents where there should be bookmarks EN-665 Alignment of some components in the output document is not matching CCMShttps://community.rws.com/product-groups/timearc-user-community/product-updates/b/product-update-s/posts/timearc-ai-pluginThu, 12 Mar 2026 14:40:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:314fb160-574c-484a-abe9-167db93f32a1Justin HarrisonThe TimeArc Ai Plugin is a way to supercharge your document search with an Ai driven search, quick links and more!! Keep an eye out for this feature release in May '26 Integrated directly into your Research Portal, giving you Ai Powered search results Integrate into your internal web-based tooling. This will allow you have your content in other appropriate tooling. Create specific quick links to search result allowing you to create powerful FAQs and other information links. https://youtu.be/tjloP6l_NV8https://community.rws.com/product-groups/timearc-user-community/product-updates/b/product-update-s/posts/welcome-to-version-4-18-1626364475Tue, 03 Mar 2026 12:00:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:add09002-db93-4ede-b74d-72751337cad5Justin HarrisonMajor features in Version 4.18 The New Publishing Workflow: Publishing content within a Collection has been improved to deliver a more intuitive, user-friendly experience guiding your publishing team a step-by-step workflow aimed at greater flexibility and reduced errors. We have also introduced new functionality to support Publication Replace and Withdraw. Find out more: The New Publication Workflow Now you can Withdraw or Replace a Publication: Whether you have published in error, or you need to create a publication prior to an already existing publication, TimerArc Version 4.18 has you covered with our latest publication management tools, Publication Withdraw, and Publication Replace. These features are part of our continued drive to enable you self-manage your system and content. Find out more: Publication Withdraw | Publication Replace Editorial Projects: UI Improvement to Merge Amendment Dialog: The 4.18 release introduces enhancements to the user experience of Editorial Projects. We have enhanced the ‘Update Amendment from Source dialog’ within Editorial Projects to make the merge process clearer and more efficient for editors. Automatic Deletion of Amendments where Source Document is deleted: Improvements have been made to maintain a cleaner and more predictable editorial workspace within the CCMS when source documents are removed. Find out More: Watch a full end to end demo of Editorial Projects Include file metadata in your publication filters: Prior to TimeArc Version 4.18 you could not target the supplementary files you wished to publish. Now you can! Adding file metadata to publication filters means you can now publish only the relevant supplementary files for that specific publication variant. Webinar Video https://youtu.be/v2_LB8vq558 Performance Improvements Area Before After Key Improvements Create Amendment Requests could take over 7 minutes and occasionally returned errors Requests now complete in approximately 1–2 seconds Merge Amendment ~12 seconds to load ~1 second View Amendment Document Up to 25 seconds to load large amendment documents ~1 second Bulk Edit Section / Document Open Word Document (Bulk Checkout) ~3 minutes ~2 minutes (up to 40% faster) Save Chnages back to the CCMS 2–5 minutes, with occasional timeouts 1–2 minutes Bulk Check-in 25+ seconds Less than 2 seconds Resolved Bugs TIM-1699 User unable to create new release TIM-1813 Numbering in bullet lists in the published word output document is incorrect TIM-1894 Publishes with future effective dates failing TIM-1850 Publish failing due to broken schema versions TIM-1594 Fix for Document compare error which builds comparison list from hierarchy rather that all changes in a publication TIM-2033 Publishes failing due to underlying numbering issue TIM-2049 Adjust effective date to match creation date TIM-776 Incorrect performance and functionality on the CCMS portal TIM-2022 Slow execution of Gen Preview reportshttps://community.rws.com/product-groups/timearc-user-community/product-updates/b/product-update-s/posts/editorial-projects-an-end-to-end-demoTue, 03 Mar 2026 11:09:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:04368a8b-4ce9-4e64-90d0-8b32e762b72dJustin HarrisonEnd to End Demo https://youtu.be/qOI-fzow9uM Some of the latest feature, included in TimeArc Version 4.18 UI Improvements to the Merge Dialog The 4.18 release introduces enhancements to the user experience of Editorial Projects. We have enhanced the ‘Update Amendment from Source dialog’ within Editorial Projects to make the merge process clearer and more efficient for editors. What’s new? Decision indicator icons added: Editors can now easily see which source updates have been accepted, rejected, or remain undecided directly within the source updates list. Accepted updates display a green checkmark Rejected updates display a grey “x” Undecided updates display no icon Improved navigation: While reviewing a source update, editors can now move directly to the next component update without returning to the source updates list. Benefits of these Improvements The improvements introduced as part of the 4.18 release provide the following benefits to editors within the CCMS: Faster and more intuitive merge workflow Clear visibility into decision progress across all components Reduced manual navigation when reviewing large numbers of updates Automatic Deletion of Amendments of a Deleted Source Document Improvements have been made to maintain a cleaner and more predictable editorial workspace within the CCMS when source documents are removed. What’s new? Automatic amendment deletion: When a source document is deleted, all associated amendments are now automatically deleted. Clear deletion messaging: A confirmation message is displayed when deleting a source document, informing users that related amendments will also be removed. Complete cleanup: All related metadata, references, and system links tied to deleted amendments are fully removed as part of the deletion process. TOC updates: When all amendments within a collection are deleted, the related Editorial Projects entry is removed from the table of contents. Benefits of these improvement The automatic deletion of amendments when the source document has been deleted provides the following benefits: Prevents orphaned amendments with no valid source document Reduces clutter and confusion in the editorial workspace Eliminates the need for manual cleanup by support or engineering Maintains a clean and consistent CCMS table of contenthttps://community.rws.com/product-groups/timearc-user-community/product-updates/b/product-update-s/posts/replacing-a-publicationTue, 03 Mar 2026 10:55:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:8ba85a32-2682-4ce2-9206-1daace8e81a9Justin HarrisonWhen publishing content to the Live publication on the Portal, the user may select any effective date, whether in the future or the past. In certain scenarios, later versions of the selected content may already exist, and as part of the publishing process, these versions may be replaced. Publishing with Past and Future Effective Dates When the user chooses to publish either the entire Collection or selected documents and files with an effective date set in the past or future, the CCMS evaluates each item to determine whether any versions exist that are dated later than the selected effective date. If a document or file has one or more later dated versions, an alert is displayed on both the Select Content page and the Review Content page to highlight this. Select Content A general alert is displayed at the top of the page to inform users that the Collection contains documents or files with later dated versions and therefore may be replaced if selected. In addition, an alert indicator is shown beside each individual document or file that has one or more later dated versions. When the user hovers over the alert, a tooltip provides further detail, indicating that later dated versions exist. Review Content When reviewing the selected content, whether for a partial publish or a full Collection publish, the Review Content page displays both the general alert indicating the presence of later‑dated versions and the individual alerts shown beside each document or file that has one or more later versions. Publish with Replaced Versions On proceeding to publish documents or files that have later versions, a modal will be displayed further warning the user that versions of the selected documents and files may be replaced. On proceeding with the publish, the Manage Releases page for a full Collection publish will mark the publish as “Archived”. Replaced Versions in the Portal When one or more versions of a document or file are replaced in the Portal, the version timeline for that item is updated to remove the replaced versions. Any associated content alerts on the Subscriptions Dashboard , as well as entries on the Publications & Announcements dashboard that relate to those replaced versions, are also removed. In scenarios where the first published version of a document or file is replaced, the item is removed from the Portal publication until it is published again. Replaced versions cannot be reinstated. As versions on Draft Publications are not associated with an effective date, the replacement functionality does not apply to Publication Flows that update the Draft Publication on the Portal.https://community.rws.com/product-groups/timearc-user-community/product-updates/b/product-update-s/posts/publication-withdrawTue, 03 Mar 2026 10:42:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:b0df5ac7-3cff-43f9-b2fa-e392e5ee98ddJustin HarrisonThe Portal version timeline reflects each version of a document or file that has been published from the CCMS. In certain cases, a version may have been published to the Portal in error and should no longer be accessible to Portal users. The editorial team can now withdraw any previously executed publish for a Collection when the associated document and file versions must be removed from the Portal. From the Manage Releases page, a “Withdraw Publish” option is displayed against each live and preview publish (full and partial). Withdraw a Publish On selecting the Withdraw Publish option against any existing Publishes for the Collection, a warning message is displayed indicating that all document and file versions associated with this publish action will be removed. On proceeding with the withdrawal of the publish, no other publish can be initiated nor another publish withdrawn until the current withdrawal is complete. An email is generated when the publish is withdrawn and the Publish is displayed with an Output Type of “Withdrawn” on the Manage Releases page. Portal Impacts When a Publish is withdrawn, the version timeline for the documents and files that was created for that publish is removed from the timeline. Any associated content alerts on the Subscriptions Dashboard , as well as entries on the Publications & Announcements dashboard that relate to withdrawn versions, are also removed. On withdrawing a Publish that included versions associated with Editorial Project Amendments, these versions will also be removed from the timeline of the source document. When the final remaining version of a document or file is withdrawn from a Live Publication —across all Releases within that Collection—the corresponding Publication(s) will no longer appear on the Portal Homepage, as there are no longer any published versions of the associated content. For a Draft Publication , when the final remaining version of a document or file is withdrawn for a specific Release, the Draft Publication(s) for that Release will also be removed from the Portal Homepage, as no published versions of any documents remain within that Release.https://community.rws.com/product-groups/timearc-user-community/product-updates/b/product-update-s/posts/the-new-publication-workflowMon, 02 Mar 2026 17:25:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:a305656e-b9f5-4251-8461-76d17e0c2d1fJustin HarrisonPublishing your content has changed for the better. From the Manage Releases page there are now two actions; Publish to Portal and Generate: Publish to Portal allows you publish your content to the portal for both Live publication(s) and Draft publication(s). Generate displays choices for generating DOCX preview files, as well as any other configured generation options available to your organization (such as the ISQM report). Today we will focus on the Publish to Portal workflow, which has changed significantly in Version 4.18 from it current format. Select Full\Partial Publish: On selecting a publishing action, the user chooses whether to publish all documents and files within a Collection or publish a selection of documents and files. The option to publish the full collection is selected by default. Select Date & Time: Upon selecting Next on the Choose Publish Type page, the user is taken to the Select Date & Time page, where they can specify the effective date for the versions that will be published. The current date and time are shown by default, but the user may choose any past or future date as needed. When a future date is selected the checkbox titled “Make visible on Portal before effective date” becomes enabled. If selected, the future effective version will be visible to Portal users as soon as the publish has successfully completed. If unselected (default), the future effective version will only become visible to Portal users once the specified future effective date and time is reached. Select Content to Publish: The Select Content page displays all folders, documents, and files within the Collection. To proceed with publishing, the user must select one or more documents or files. T he content is shown in a hierarchical view, though the user may switch to a list view if preferred. A Find Content option is available to help users search for specific folders, documents, or files to refine the list. The Change Type column indicates what has changed since the Collection was last published to the Live publication. The Last Published Date reflects the date on which the Collection was most recently published to the Live publication on the Portal. The Alerts Message and Alerts column notify the user if there are any checked out components, or if a file or document will have versions replaced as part of the publish. Note: Partial Publish Known Issue: Changes to a Collection’s Table of Contents, such as renaming a folder, must not be published with an effective date that is earlier than any existing future effective versions of documents or files within the Collection. If future effective versions exist with dates later than the ToC change, those versions must first be withdrawn and then republished with an effective date that is equal to or later than the effective date of the ToC update. This issue will be resolved in a future release, as the user will be notified that the versions dated later than the ToC changes will be replaced . Review Publish Selections: The Review page displays all documents and files selected for publishing, whether the user has chosen to perform a full publish or to publish only selected content. It gives the user the opportunity to review their publishing selections before the publish is initiated. The user may review their publishing selections and, if necessary, return to either the Select Date & Time page or the Select Content page. Alternatively, they may proceed directly with the publish. Note: Deleted Documents\Files : Where a document\file has been deleted it will appear in the Select Content page with a Change Type of “Deleted”. The document or file will be deleted from the Portal if one or more other files from the Collection are selected for publish. Publish Progress: Selecting the Publish option initiates the publishing process, and the Progress page displays real time updates on its status. While the publish is underway, the user may return to the Manage Releases page and continue performing other CCMS activities by selecting the Back to manage releases option. Once the publish has been successfully completed, the total number of folders, documents and files that were published is displayed. On returning to the Manage Releases page, the publish will be listed. https://youtu.be/uw1Z7bSdEJAhttps://community.rws.com/product-groups/timearc-user-community/product-updates/Thu, 12 Feb 2026 10:32:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:63e1639c-f33e-478a-a338-9bb0c8a5321aTest testhttps://community.rws.com/product-groups/timearc-user-community/i/ideas/copy-linked-sectionTue, 03 Feb 2026 14:40:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:bf0071d2-5b4e-40df-bf06-683e788e179aJustin Harrison--- Please Note, this idea was on behalf of a customer --- This is a request for a new feature called “ Linked Copy Section ” in CCMS. This will allow editors to copy, link, and reuse entire sections (i.e., groups of components within a defined document structure), similar to current Linked Copy Component functionality but applied at section level. The goal is to improve efficiency, eliminate repetitive manual copying, reduce errors, and maintain consistency across documents that share common structured sections. Problem Statement Currently, CCMS supports: Linked Copy Component - good for single granular components Linked Copy Document - appropriate for full document reuse However, there is no middle layer. Editors often need to copy entire sections of a document where: A section is a structured grouping of multiple components and is currently used across many ePR documents. These sections recur across multiple documents and teams currently spend considerable time replicating these sections manually. Manual copy and paste introduces ordering errors, version drift, and inconsistencies. Copying components one‑by‑one is time consuming and prone to mistakes. This significantly affects accuracy and slows down workflows. Request A Linked Copy Section feature would complement the existing two reuse tools and fill a core gap in CCMS functionality. The feature will mirror existing linked copy component, applied at section level. Copy Section Link - Editors should be able to copy a link representing the entire section (all child components in the defined structure). Paste Section Link (Insert Linked Section) - Editors can insert the linked section into another document or location. - Inserted section displays as a linked instance , not a static copy. Edit Once → Updates Everywhere - Editing a section in one location should update all linked copies, unless deliberately unlinked. Unlink Section - Editors must be able to “unlink” a linked section instance to create a standalone editable section. Maintain Structure - The section should preserve component order, hierarchy, and nested structures. - This eliminates manual re‑ordering and reduces errors. Compatibility with existing functionalities - The feature must work with current CCMS drafting, editing and publishing workflows.Linked CopyEditorialhttps://community.rws.com/product-groups/timearc-user-community/i/ideas/release-versions-as-well-as-release-datesTue, 03 Feb 2026 14:27:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:6a813cd4-edc9-403c-8529-4aec92241f5dJustin Harrison-- Please note, this request is submitted on behalf of a customer -- Due to the timing an nature of our publishing practice, we would like to release in Versions. Currently the model where you release and it creates a new timeline entry, does not help our users understand the latest version. A timeline entry might only have a couple of minor changes, but is considered of equal importance to a release where whole section are fully re-written. We need a way to support major and minor versions, that will also allow us compare the versions. Thank you.releasepublishingVersioningTimeline Entryhttps://community.rws.com/product-groups/timearc-user-community/b/blogs/posts/structuring_2d00_audit_2d00_tax_2d00_guidance_2d00_for_2d00_the_2d00_ai_2d00_eraWed, 28 Jan 2026 16:51:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:3d98939c-1369-491e-957e-b08adea50b60Anushka ChughEvolving technology is everywhere As the professional services landscape evolves, artificial intelligence is rapidly becoming a key intermediary in how professionals discover, interpret, and apply technical guidance. Audit and tax methodology professionals face a unique challenge: ensuring that firm guidance remains authoritative, usable, and discoverable for human practitioners, and for AI-driven knowledge systems that increasingly shape how information is accessed and applied. The New Reality of Methodology Design In every firm today, the way we write and store guidance is changing. AI-driven tools are now helping auditors and tax professionals find answers faster, but only if the guidance itself is structured clearly and logically . If your firm’s methodology is written only for human interpretation, this can cause you to fall behind as new technology becomes available. The challenge isn’t just clarity anymore, it’s ensuring that both people and machines can interpret your guidance consistently and correctly. This post provides a practical framework for organizing audit and tax methodology so it remains authoritative, easy to use, and ready for an AI-enabled future. 1. Start with a Purpose-Driven Framework Every piece of methodology should have a reason to exist. Ask yourself: What professional judgment or compliance requirement does this address? What confusion or inconsistency is this meant to resolve? Then build from the top down: Main topic (H1) – e.g., Audit of Revenue Recognition Subtopics (H2) – e.g., Identifying Performance Obligations Supporting procedures or examples (H3) Consistency in headings and numbering may sound like a formatting exercise, but it’s not. It’s what allows both professionals and AI systems to recognize the logical flow of your guidance. 2. Craft an Informative, Contextual Introduction Start each section by grounding the reader. A short, informative introduction works wonders for both humans and machines. It should cover: What the topic is and why it matters Whether it applies to audit, tax, or another service line What practitioners should be able to conclude The relevant authoritative sources (ISA, IFRS, IRC, etc.) We’ve all seen guidance that jumps straight into the technical details without context. That’s the fastest way to lose both the reader and the search engine. This up-front framing allows AI systems and practitioners alike to categorize and retrieve guidance efficiently. 3. Structure Guidance for Clarity and Scanability Audit and tax professionals are busy. When someone searches internal guidance, they’re often trying to confirm one specific point before a client meeting. Make that process painless. Use specific, searchable headings (“How Audit Documentation Supports Risk Assessment” rather than “Documentation”) Keep paragraphs short—2 to 4 sentences each Start with the main idea, not the background Use bullets, tables, and definition boxes to organize details This kind of formatting isn’t just about style, it directly improves how AI tools extract and rank your content. 4. Provide Direct, Answer-First Guidance Audit and tax professionals -and AI systems- value direct, unambiguous answers. Use an answer-first structure for each question or subtopic: State the key principle or required conclusion in the first sentence. Follow with supporting explanation or rationale. End with examples, exceptions, or documentation guidance. For example: Q: When should control be considered transferred in an audit of revenue recognition? A: Control is typically transferred when the client has the ability to direct the use of, and obtain substantially all the benefits from, the asset. Evidence may include legal title transfer, physical possession, or acceptance of performance. (See IFRS 15.31–38 for further indicators.) This format provides immediate clarity while preserving professional depth. 5. Build for AI and Search Visibility AI tools—and increasingly, your firm’s internal knowledge platforms—rely on consistent metadata to make sense of your content. Some approaches to building for machines and human readability include: Apply semantic structure Use consistent heading levels and standardized numbering (e.g., 1.1, 1.1.1) Group related procedures and definitions under labeled sections (e.g., “Objective,” “Procedures,” “Documentation”) Implement tagging or schema where possible “HowTo” or “Procedure” schemas can signal process-oriented content. For internal systems, metadata fields (topic, process, related standard, risk type) improve AI-based retrieval accuracy. These elements make your guidance machine-readable and contextually intelligent. 6. End Each Section with Actionable Takeaways Summaries shouldn’t just restate—they should guide. Before concluding on revenue cut-off, confirm whether all performance obligations were met as of period end. If not, refer to Section 3.2 for guidance on extended testing procedures. This gives your guidance a sense of closure and direction—something humans and AI indexing systems both benefit from. 7. Keep It Accurate, Consistent, and Readable Nothing undermines credibility faster than inconsistency. Check that: References to standards are current Terminology is uniform (e.g., don’t alternate between “materiality threshold” and “significance threshold”) Quantitative data and examples are correct The language remains clear and straightforward Have a peer reviewer test whether the guidance is easy to interpret. If they have to read it twice, it probably needs refining. Bringing It All Together Designing audit and tax methodology for an AI-driven world isn’t about sounding technical—it’s about communicating structure and intent clearly enough that both people and AI systems can use your guidance without confusion. As AI becomes embedded in audit tools, risk assessment engines, and tax research systems, guidance that is logically organized and explicitly defined will become the gold standard for usability and reliability. By combining clear structure, authoritative sourcing, and consistent formatting, you future-proof your guidance, ensuring it remains discoverable and trusted in both human and machine-driven workflows.AuditMethodologyTaxTechComplianceAutomationOperationalExcellenceAISovereigntyhttps://community.rws.com/product-groups/timearc-user-community/b/blogs/posts/aligning-product-strategy-with-real-world-customer-operations-why-we-prioritize-face-to-face-interactionWed, 28 Jan 2026 16:44:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:5f1e158c-a2c9-437b-8bb9-ba0e6c403d20Anushka ChughThe value of in-person touchpoints Recently, our Customer Success and Product teams spent time on-site with customers working in verticals such as auditing and accounting, and standardization. As hybrid and remote work have become a central part of global working life, our team took the opportunity to meet our clients face to face and workshop key learnings, accelerate project understanding and set the stage for our ongoing productive partnerships. First-hand understanding of real-world challenges During these client sessions, a core goal was to better understand current systems so we can gain deeper clarity on specifics and processes, which is difficult to achieve from reading documentation. As a result, our team grew their understanding of the bigger picture, answering questions like how data is being prepared and where it goes after it passes through our systems. This directly leads to identifying areas where we can adjust for greater efficiency. The in-person discussion also allowed our team to identify key bottlenecks as we partner to make our technology solutions better for our clients. Having these details allows us to propose tangible solutions that can accelerate outcomes. Facilitating real-time feedback and roadmap discussions Meeting in person enables Propylon’s product team to collaborate with greater clarity, speed, and alignment. Face-to-face sessions create space for real-time feedback, where ideas can be explored, challenged, and refined without the delays or misunderstandings that can arise in virtual settings. These collaborative discussions also strengthen roadmap planning by bringing diverse perspectives into the same room, allowing the team to quickly prioritize features, address dependencies, and make informed decisions together. The result is a more cohesive strategy, stronger team cohesion, and a shared understanding that accelerates product momentum. Opportunities for future growth In-person meetings are a great forum for exploring long-term growth and alignment. We have come to understand the processes and systems used in developing standards, policies and guidance that are outside of their current usage of our system. This allows us to partner on areas for further growth and custom integration. While virtual tools keep projects moving, there is no stand-in for the rich communication opportunities and trust-building of dedicated in-person time with clients. If you’re interested in a face-to-face, reach out to your Customer Success Manager.Operational alignmentCustomer operationsFace-to-face interactionCustomer-centric designProduct ManagementProduct strategyEnterprise softwareOperational ExcellenceBusiness operationsCustomer engagementhttps://community.rws.com/product-groups/timearc-user-community/b/blogs/posts/publication_2d00_api_2d00_digital_2d00_knowledge_2d00_delivery_2d00_ai_2d00_eraTue, 27 Jan 2026 14:32:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:31d955fb-520e-45ff-b0df-5fdaa9eb5af9Anushka ChughFor the rule-makers and rule-takers operating in regulated industries, the challenge of staying compliant with legislation, regulation and standards is more complex than ever. For rule-takers such as audit firms, fund managers, pharma companies, utilities companies, etc., the goal is to ensure that staff guidance materials adhere with the latest updates and are readily available. The intricate regulatory ecosystem underpinning the work that regulated SMEs performs currently being reshaped by two connected forces: evolving expectations for content search and navigation, and the increasing importance of AI-based modes of interacting with knowledge. The need for seamless knowledge integration Traditional approaches to managing company knowledge represent a key hurdle. Teams face a constant need to switch tasks, jumping from their core work applications into separate knowledge repositories to find crucial guidance information. This is not only inefficient, causing loss of focus, but it also creates a hurdle to accessing this critical knowledge and keeping up to date as it changes. Many knowledge management systems based on SharePoint deployments, for example, often exacerbate this problem. Due to the organic way these systems have grown over time, they can be confusing to navigate and difficult to manage for purposes such as reporting on changes. The content itself may also lag behind the pace of regulatory change due to cumbersome or delayed publishing processes. Publication API: integrated, traceable guidance The solution lies in integrating single source of truth knowledge directly into the tools and workflows that employees use every day. Publication APIs allow regulatory knowledge to flow seamlessly into business systems such as Audit Software, PLMs, CAD tools, QMS tools etc. At the same time, it is important to allow for the knowledge to be tracked across its lifecycle. Particularly in relation to the publishing of standards and regulatory information, enabling consumers of such information to track at a micro level which parts of the standards or regulations have changed and require a review of impacts caused in operational systems. By creating direct Publication API linkage between the single source of truth for guidance and the business systems downstream, knowledge management teams don’t have to work hard to get the up-to-date guidance they need as timeliness is baked in to the design from the outset. Looking ahead: AI-optimized knowledge flows As more advanced AI capabilities start to become more embedded into businesses across the board, organizations are strategically integrating AI into their systems to change how employees access and interact with company knowledge. For example, in our Innovators interview series, Gert-Jan Gerrits speaks about Forvis Mazars’ GAIA global AI assistant that teams can utilize to ask questions . Crucially, the effectiveness of burgeoning Gen AI applications hinges on the quality and structure of the underlying knowledge. For AI systems to provide accurate, reliable outputs – a critical need in regulated industries -the source knowledge itself must be AI-ready. This means structuring data in a way that AI can easily understand, process, and retrieve, ensuring that the ‘ground truth’ presented to the AI aligns with your organizational truth – the validated, up-to-date guidance material. By investing in robust knowledge integration through live APIs and by structuring existing knowledge for AI, businesses are building a trustworthy foundation that is ready for the new digital future of work that is emerging rapidly.Enterprise technologyartificial intelligencePublication APIAI governanceDigital knowledgeKnowledge DeliveryData trustAI-enabled publishingAIContent automationhttps://community.rws.com/product-groups/timearc-user-community/product-updates/b/product-update-s/posts/welcome-to-version-4-12Mon, 26 Jan 2026 16:49:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:3ef1409e-04f7-4bc5-a4df-531cefacfba5Justin HarrisonIn this release introduced: Document Template Management: Document Templates serve as a foundational feature in any content management systems to streamline the creation of structured documents. Up until now, the absence of template creation functionality in TimeArc CCMS presents significant challenges for users. Improved Table of Contents Usability (Portal and CCMS): The Table of Contents (ToC) plays a critical role in simplifying navigation within documents, particularly on the CCMS (Component Content Management System) and Portal platforms. In this release we have introduced new feature to streamline and simplify the users experience. Document Template Management Document Templates serve as a foundational feature in content management systems to streamline the creation of structured documents. By automating repetitive and pattern-based tasks, templates reduce the likelihood of human error, improve efficiency, and enhance user satisfaction. Up until now, the absence of template creation functionality in TimeArc CCMS presents significant challenges for users. The reliance on manual processes to create strawman documents exacerbates frustrations and inefficiencies, as users are burdened with repetitive tasks prone to errors. Introducing robust template functionality within TimeArc is the first step to address these challenges and improving the overall authoring experience. Template Library The Template Library is accessible through a new "Templates" tab in primary navigation. It enables users to create, manage, and organize templates efficiently. Features: Template list with filtering by Name/Type, detailed view for each template, and allow access to workflows to create, edit, and delete templates. Sample Template: Users can download a sample template to assist in template creation. These enhancements aim to improve efficiency, usability, and user productivity through streamlined and centralized template management. Create a Template The Create Template feature enables users to create templates within TimeArc CCMS by transforming Word documents with headers, sub-headers, and text into structured templates stored in the system. It enhances usability and consistency in document management. Users initiate template creation in the Template Library via a dialog window. Prepare a Word document with headers and text. Transform the document into a template. Save the completed template in the system. Key data Point are: Document Type: Category of the document. Document Name: Unique identifier for the template. Document Schema: Structural template derived from the Word document. Please note: The following functionality is not available in this release: Viewing templates within the CCMS. Editing template content directly in the CCMS. Using a Template when authoring a Document This feature focuses on enabling users to seamlessly utilize a pre-made template when creating a new document within the current workflow. By introducing the option to select a relevant template, we aim to enhance efficiency while ensuring minimal user burden during the file creation process. Template Selection Workflow When you select Add Document the Add Document dialog appears. The user can select a template from a populated list in the “New Document” section The User us required to select a Template Type and then a Template. Selecting the template type, will filter the template options available. Default Behavior If "no template" is set as the default option, users can start a document without selecting a template If no templates exist in the system, the template selection control will be hidden, ensuring a clutter-free user interface. Table of Contents: Usability Improvements The Table of Contents (ToC) plays a critical role in simplifying navigation within documents, particularly on the CCMS (Component Content Management System) and Portal platforms. Its current functionality requires additional functionality to meet user expectations and provide a simple navigation experience. This initiative aims to enhance the ToC experience both in terms of navigation and editing. CCMS ToC Changes: In this release addresses two key issues: Simplicity in filtering the ToC: The hierarchical nature of the ToC often makes it challenging for users to locate specific sections, especially in documents with deeply layered content trees. To address this, we have included the ability to refine the ToC based on keyword searches. Viewing the Folder in the content body : It is often difficult for users to traverse the ToC and negate through folders. In addition, when you select a folder, the content body is empty. In this release we have used the content body to provide quicker access to the content of a folder when you click on it Portal ToC Changes: Refine Table of Contents: On viewing content, you can refine the entries in the Table of Contents based on a full or partial keyword. On adding text into the "Refine table of contents" field, the Table of Contents will immediately be refined to display headings\subheadings that match that text. The search text is highlighted for each Table of Contents entry that matches and the Table of Contents expands to the entry. Viewing the Folder in the content body : As with the CCMS, Portal users also struggle to navigate the ToC at times. The solution applied tot he CCMS has also been applied to the Portal, providing a consistent experience across both platforms and help all users locate the content they wish to access Improved Keyword Search Functionality: CCMS TimeArc currently provides keyword search functionality, complemented by metadata filters, to help users locate rules or standards across collections, folders, and files. While these features enable users to find relevant content, the current state of the search functionality falls short of user expectations in two key areas: Lack of Keyword Highlighting: In the CCMS, search results currently do not highlight the matching keywords within documents or files. This omission forces users to spend additional time and effort identifying the specific section of the content that relates to their query. The absence of visual cues leads to a suboptimal user experience and increases cognitive overhead. Misspelling Handling: TimeArc's search does not account for user misspellings. Misspelled keywords are treated as correct entries, leading to failed searches and frustration when users cannot locate the desired content. Despite being a user error, modern search systems mitigate this issue by offering autocorrect or "Did you mean?" suggestions, reducing the impact of spelling mistakes on search outcomes. To address the identified challenges and improve the user experience, Release 4.12 now include the following two features: Keyword Highlighting in Results Introduce visual keyword highlighting in search results to draw attention to the sections of documents or files that match the user's query. This feature will streamline the search process by making it easier for users to pinpoint relevant content within seconds. Misspelling Handling and Suggestions Incorporate functionality to detect common misspellings and provide suggestions for alternative terms. Features such as autocorrect or "Did you mean?" prompts will empower users to locate content despite minor input errors, aligning the search experience more closely with modern standards. Issue Log Prevent/Automatically resolve nonsequential ordering data issue Critical publication issue resolving non-sequential ordering issue. Accessibility Accessibility updates to the User Interface UI Improvement Search Results Link Icon - anchored to far right of All Search Results page Search Keystroke Usability Improvement Pressing the enter key does not open the full results page during quick search results Content Visuals Improvement Include line breaks on Supporting Comment of a Change Proposalhttps://community.rws.com/product-groups/timearc-user-community/product-updates/b/product-update-s/posts/timearc-version-4-11Fri, 16 Jan 2026 16:34:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:94498a7c-457e-47d1-81d9-2e6840f37318Justin HarrisonIn this release we have focused on two main problems: Keyword Searching: When performing a keyword search in the CCMS and Portal, the searched keyword is highlighted in the search results, but when using this search result to navigate to the content view, the keyword is not highlighted. Finding the text related to your keyword search is both time consuming tedious. Managing Content and tracking changes: To date, it has been difficult to identify content where changes have been made, changes need to be made or content needs to be grouped to help you understand and work with your content. In this release we have improved how you can mange this in the CCMS with the Content Dashboard. Keyword Searching The Portal search feature is one of the most important features within the platform. It allows the user search across all publications within the organization or within an individually selected publication without needing to know the location of a particular keyword, phrase, component, section, or chapter in the selected collection. On performing a search from either the Instant Search pane or the All Results page, you can navigate directly to the matched results. When navigating to the match term on the content view, the search term\keyword is not highlighted and you have lost the context that was available in the search results preview. On the content view, you need to manually scan the content, which can be troublesome in a large component, or use the browser find feature to locate terms. The Solution In the release we have altered the search term functionality to highlight the first match on the search Keyword\Term found. A Next\Previous option will be provided that will allow the user to navigate through matches found within the documents of the selected Publication. A search that includes multiple keywords or phases where the AND operator is assumed will include the next\previous for each of the terms. The highlighting ok the critical search terms will allow user to easily find the sentence in the content view that directly related to their search without having to read the full content of the document. As you can see from the image above, the keyword or search term is now highlighted in blue, making it immediately recognizable by the user and directly them to the relevant text based on their search. Please note the following: A search that was not initiated via a keyword or phrase such as based on metadata values and\or a last change date parameter will not highlight any search matches on the Content view. A search that is initiate using the NOT, OR or Boolean operators (*\&) will not highlight any search matches on the Content view. The Content Dashboard The Content Dashboard is a centralized report for CCMS users to track changes in components, documents, and folders over a specific timeframe. It also provides visibility into content relationships (external components and related content) to ensure content stays up to date with recent publications. To date, it has been challenging to manage content through this dashboard without multiple repetitive tasks and several pain points for users. The Solution: In the release we have introduced functionality to allow users to view, sort, and filter information for each component, document, and folder within a Collection release. They can also customize displayed columns, with preferences retained for future visits. In addition we have extended the information available to include system information (e.g., date updated, component type, task status) and metadata. Users can also export this data for external processing. Finally, this release, includes changes to the UI, filtering, and sorting to enhance dashboard usability. Saved Filters Improved Sorting Other Update(s) Change Proposal Improvements A filter was added to the list view to make finding specific Change Proposals easier The following columns have been added to the Change Proposal list - Conflicts - Modifications - Document You can now sort and filter on the Proposal Number column Filter by submitter was not working as expected and the related issue has now been resolved Publishing Stability Improvements Prevent the creation of a duplicate Document Version with the same ID Resolve issue created when forking a release and related content links are not updated Publications were failing when no style was found when adding a component. This has now been resolved, and all sub-headings will default to a standard style if one is not recognised. Draft components were causing an issue when forking a release. In this release, draft components will be deleted on check in, avoiding any related forking issues. Cookie Notice A cookie notice has been introduced that will allow users set their initial specific preferences and subsequently edit them if required. Unauthenticated Access to Specific Content It is possible to make specific Collections available to users who are not registered Portal users. Please Note: This must be configured by Propylon, please contact your customer service representative if you require more information. Issue Log The last publication filter should not be deleted. User should not be able to delete all publication filters. CCMS Logout through Cognito was not working SAML and OIDC logout workflows have been fixed and texted Publication duplicate email User email displayed as duplicated on the manage releases page when user kicks off new publish. Fixed and tested Unlink icon not displayed on metadata fields Permissions Issue. Tested and Fixed.https://community.rws.com/product-groups/timearc-user-community/product-updates/b/product-update-s/posts/version-4_2d00_10Tue, 13 Jan 2026 09:47:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:fbe0a5c1-333c-4d9c-903a-e039d651abeeJustin HarrisonVersion 4.10 introduced a number of fundamental changes to the the CCMS which are designed to support a better user experience throughout the system. Specifically, we've introduced "Partial Publishing" the first step in a more flexible publishing paradigm. We have completed essential work our Change Proposals functionality which supports authors in the full Change Proposal lifecycle. Finally, we've enable users to easily reference supplementary files within components with our new "Copy File Link" feature. For all this and more read on! Support Folder structure changes in partial publications In TimeArc, users can publish or publish preview of the content organized within a folder hierarchy. This flexible system allows users to publish either the entire hierarchy or select specific documents within the structure. Once published, the folder structure is replicated on the TimeArc Portal and displayed as the Table of Contents (TOC) for the relevant collection, making it easy for viewers to navigate the content. One of the limitations of this was the need to publish the entire content set each time. With this update, the user can publish an already published document without having to publish the entire hierarchy or content set. This is TimeArc's first version of Partial Publishing. which we hope you will enjoy, there is much more to come in this area! Please Note the following restrictions: The user is required to publish the full hierarchy when there are changes to the Table of Contents structure due to the actions mentioned below: Adding a new document/folder/supplementary file Replacing a File Moving document/folder/supplementary file Deleting document/folder/supplementary file Rename of folder/supplementary file Additionally, a full hierarchy publish is required for the first publish of a new release. When there are changes made to the collection’s structure, the user is displayed a notification on the Publish modal and badges are displayed on the document/folder/supplementary file which requires a full hierarchy publish (see Figure 3). To initiate Part Publishing, select the relevant documents and folders you wish to publish as shown in the image below. Warning will appear if you are publishing content which requires a full publication or contravene the partial publication business rules. Change Proposals: Life Cycle Completion. Merge Change Proposals The Merge Change Proposals feature streamlines collaboration between Portal users and CMS users, enabling efficient review and integration of user feedback into the content editorial process. In TimeArc, end users interact with drafted content in the Portal, where they can suggest edits or improvements via Change Proposals. These proposals represent potential updates to the draft version of a content set. Proposed changes are submitted to the CCMS, where content creators and managers can: Review the suggestions via the Change Proposals Dashboard Accept (merge) them using the Merge Change Proposals feature. Once the Change Proposal is submitted on Portal, it is made available in the CCMS via the Change Proposal Dashboard. When the proposal number is selected from the dashboard, the user is displayed the Merge modal where the user can review the proposed changes component by component. The merge dialog presents the Change Proposal status on the right side. Once the proposed changes are reviewed, the user can merge the changes into the content in CCMS using the Merge Selected CP option. When a proposed change is merged, the components with changes are checked-in and a version history is recorded for this change. Please note the following: Components that have no change are not updated and no version history is recorded. O Once a change proposal is merged, it cannot be merged again Managing Conflicts When a component has multiple change proposals submitted, a table is displayed to notify the user of the numbers of conflicting change proposals available on the component user is reviewing. When a change proposal with a conflict is merged, the conflicting change proposals become stale since the component with multiple change proposals has a new checked-in version in CCMS compared to draft version on which the change is propose. The stale CP cannot be merged due to this reason and user will need to manually make the changes to each component. Similarly, when a component that is part of a change proposal and the component is in-edit and is locked by another user, the change proposal cannot be merged. When a component is an external component and is proposed with a change as part of the change proposal, the change proposal cannot be merged as external components cannot be edited in a collection. Modified Change Proposals When you navigate to change proposal that includes modifications you now can toggle between the original change proposal and the modification(s) as highlighted in the screen below. Other Update(s) ISQM1 Report - Publish details In this update, the ISQM1 report generation functionality has been enhanced to include Publish details fields, providing users with details on when a version of the component was published, publisher name and date. This expanded functionality maintains the same easy-to-use report generation process, now with richer data for an improved user experience. Copy File Link The new Copy File Link functionality enables users to easily reference files within CCMS content. With this feature, users can generate a direct link to a file stored in the CCMS and insert it as a reference within component content or related content metadata. This is particularly useful for creating quick, accessible references to files without re-uploading or duplicating them. How to Use the Copy File Link Function: Locate the File : Navigate to the desired file within the CCMS collection. Copy the Link : Select the Copy File Link option from the contextual menu of the file, which will copy the file's URL to your clipboard. Figure 1. Copy File Link option Insert the Link : Paste the link directly into the component content or within the related content metadata fields. Support for Macro enabled Office Files This update introduces expanded file type support in the CCMS, allowing users to upload additional office file types that include macros. With this enhancement, users can now import and add .docm (Word files with macros), .xlsm (Excel files with macros), .dotm (Word templates with macros) and .pptm (PowerPoint with macros) as supplementary files. Previously, CCMS restricted uploads to only certain file types, including .doc, .docx, .ppt, .pptx, .xls, .xlsx, and .pdf. Now, the user can also add a .txt file. This added support for macro-enabled files and .txt file enhances the system’s flexibility, enabling users to include files with advanced functionality within their content. Download File This update introduces a new option to download a file in its original format while viewing the supplementary file in CCMS. The file is downloaded locally. Issue Log Publish and Generate Preview are failing and produce "Publish Error" in the outputs table When numbering has been removed, the numbering is still displayed on the component User cannot edit a publication filter Intermittently, Check-In or Edit Content for multi-component editing does not work via the options button or checkboxes. Performance and stability improvements for multi-component editing. Content Dashboard filters and buttons are not well aligned Section headings being treated as additions in Merge CP modal Publications Filter that are not defined in publication filters page are being displayed on publish in CCMS and Portal ‘View Metadata’ toggle was not displaying metadata values in content view Cannot publish a parent release where a child release has a published draft preview Disable component editing while reorder in progress User who initiated job name now available on Jobs page Formatting only edits saved to components Version 4.10 Patch Releases 4.10.1 System Update System update for staging workflow 4.10.2 Bug Ensure folder path changes are reflected in cache 4.10.3 System Update System update to AVRO regeneration script 4.10.4 Bug Improved Error handing to conflict counts. System Update Updates to DocumentContainer initiated cache paths System Update Update to Propylon testing configuration file (YAML) System Update Update of AVRO export to support sample export request. 4.10.5 System Update Additional logging added the cache sync system to identify content humbling. Bug Resolve HTML difference failure System Update Adding cache worker docker image to propylon testing System Updates YAML updates 4.10.6 Bug Resolved issue with empty heading content causing HTML diff code to fail and affecting related change proposals. Bug Fix cache system ordering error caused by adjacent content updates Bug Increase timeout on portal ingest to support improved publication stability. Timeout increased from 2 hours to 2 days.https://community.rws.com/product-groups/timearc-user-community/product-updates/b/product-update-sFri, 19 Dec 2025 10:53:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:aa5146e2-57d3-42e9-a652-7a6eb4d5d65eRelease notes and product updateshttps://community.rws.com/product-groups/timearc-user-community/f/forums-faqWed, 10 Dec 2025 13:30:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:072e8ef1-40e4-4738-9ddb-fba4dc7078a2https://community.rws.com/product-groups/timearc-user-community/b/blogsWed, 10 Dec 2025 13:29:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:ec9a810e-8c06-47f0-a102-f3de51c55e75https://community.rws.com/product-groups/timearc-user-community/i/ideasWed, 10 Dec 2025 13:27:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:9b334c0e-2498-470d-9426-4a4b047ab23e