Version 4.1.0 (Polaris) - Release notes

Release Date	End of AMP(*)	End of Life
2026-10-19	2029-10-19	2030-10-19

(*) Active Maintenance Period

The present document contains information regarding product enhancements, fixed issues and known issues related to AnswerModules Module Suite version 4.1.0 (Polaris).

This guide

The information presented in the on-line guide are mostly non-version specific. AnswerModules team does its best to ensure that, where necessary, is made clear that the information presented is only applicable to specific versions, however if you are looking for this version-specific documentation, you can find it here

No Warranties and Limitation of Liability

Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However, AnswerModules accepts no responsibility and offer no warranty whether expressed or implied, for the accuracy of this publication.

Module Suite Compatibility Matrix

OpenText Content Server	MS 3.6.0	MS 3.7.0	MS 3.8.0	MS 3.9.0	MS 4.0.0	MS 4.1.0
Content Suite 22.1	X	X	X	X	X
Content Suite 22.2	X	X	X	X	X
Content Suite 22.3	X	X	X	X	X
Content Suite 22.4	X	X	X	X	X
Content Suite 23.1	X	X	X	X	X
Content Suite 23.2	X	X	X	X	X	X
Content Suite 23.3	X	X	X	X	X	X
Content Suite 23.4	X	X	X	X	X	X
Content Suite 24.1	X[1]	X	X	X	X	X
Content Suite 24.2		X	X	X	X	X
Content Suite 24.3		X[2]	X	X	X	X
Content Suite 24.4			X	X	X	X
Content Suite 25.1			X[3]	X	X	X
Content Suite 25.2			X[4]	X	X	X
Content Suite 25.3				X	X	X
Content Suite 25.4				X[5]	X	X
Content Suite 26.1					X	X
Content Suite 26.2					X[6]	X

[1] Requires hotfix hotFix_ANS_360_009 to be installed

[2] Requires hotfix hotFix_ANS_370_003 to be installed

[3] Requires hotfix hotFix_ANS_380_007 to be installed

[4] Requires hotfix hotFix_ANS_380_013 to be installed

[5] Requires hotfix hotFix_ANS_390_004 to be installed

[6] Requires hotfixes hotFix_ANS_400_007 and hotFix_ANS_400_008 to be installed

Module Suite 4.1.0 supports Content Suite 23.2 through 26.2. No hotfix is required on these versions.

Major Changes in version 4.1.0

Supported platforms

Module Suite 4.1.0 (Polaris) supports OpenText Content Suite 23.2 through 26.2. No Module Suite hotfix is required on these versions. Content Suite 22.1, 22.2, 22.3, 22.4, and 23.1 are no longer supported. Customers on those versions are advised to remain on the 4.0.x line until they upgrade Content Suite. See the Module Suite Compatibility Matrix above.

AI-assisted authoring

The AI Form Builder, the Component AI Builder, CARL, and Application Builder send each Generation run to Aether. Configure Aether before you use these editors. See Aether and Generation runs in Module Suite 4.1.0.

Module Suite 4.1.0 (Polaris) brings AI-assisted authoring to Content Server and to Module Suite Runtime. A developer can generate a form or a page component from a natural-language request, review it, and store it as a version that the platform serves like any other artifact. The release also adds a new runtime for Smart Pages, a portal on Module Suite Runtime, and a set of Content Script, editor, and extension improvements.

• AI Form Builder: generate an AI View from a Beautiful WebForms view, preview it, and store it as a view version. AI Views render with the V16 runtime, on desktop, small, and touch screens
• Shell Pages and Shell Components: a new Smart Page type that mounts independently versioned components in regions. Shell Pages coexist with Classic Smart Pages in the same perspective
• Component AI Builder: generate, preview, and deploy a Shell Component, with localized strings, Smart View widgets, and a shared Design Profile
• Design Profiles: one visual language for AI forms and Shell components (jato, studio, and portal), with one default for Content Server and one for the Module Suite Runtime portal
• Module Suite Runtime (MSR): supersedes the discontinued Script Console. The MSR portal hosts Shell Pages, Shell Components, and AI forms outside Content Server. Sign-on is delegated to OTDS with OAuth 2.0
• Aether: per-generation model selection, conversation continuity, host-supplied Content Server API dictionary, readable generation traces, and token use counted per tenant
• AI agents: the new AMAgentController behaviour turns a Content Script into an AI agent. An agent is also an Application Builder artifact, and it can call tools on files the user has attached and on MCP servers
• Smart View perspectives from Content Script: build, read, update, enable, and disable perspectives with layouts, rules, and widgets through the amsui service
• xECM Business Workspace Types: create, read, update, and delete business workspace types and templates from Content Script
• Transport service: work with Transport Warehouse workbenches, items, dependencies, and packages from Content Script
• MCP server definition DSL: define an MCP server in Content Script with a manifest, remote tools, and virtual resource folders on Content Server
• Content Script editor: one editor on Content Server and on Module Suite Runtime, with more languages, better completion, and new shortcuts
• Docbuilder (docx) API: read numbering, tracked changes, comment anchors, and fields; edit tracked changes at word level
• Platform: support for Content Suite 23.2 through 26.2 with no hotfix

AI Form Builder

The AI Form Builder is a new editor for Beautiful WebForms. It replaces manual layout with a natural-language request, and it stores the result as a regular view version that you can review, download, and move between platforms.

• Open from a view: the AI Form Builder opens from a Beautiful WebForms view. Each successful Generation run is stored as a new version of that view, addressed by the view id and the version id
• V16 runtime: an AI View renders with the V16 runtime. A V16 view works on a desktop, a small screen, and a touch screen. The V16 buttons submit the form and save it
• Delivery platform: choose Content Server or Module Suite Runtime for each view. The choice is stored on the view as targetHost and is sent with every Generation run. To use a version on the other platform, download it from History and upload it on the other host
• Design Profiles: the Design language select chooses the profile for a run. The resolved profile is pinned on the view after a successful run, so a later change of the administrator default does not change a pinned view. The administrator defaults are design.profile.content_server and design.profile.portal
• Smart View pickers: mark a field as a node picker or a member picker. The form stores ids only. Where the picker opens depends on the host: an AI View page on Content Server, a Shell Page region, a portal region on Module Suite Runtime, or the builder preview
• Scripts and validation: a Shell-mounted AI View runs its OnLoad script, and the changes from that script are kept after an action roundtrip. Validation names the field that failed. An omitted fieldset field produces a warning and does not block a recompile
• Styles: the builder stores and shows the authored CSS only. A later Generation run keeps that CSS. Saving the view sets the widget library and the runtime version
• Submit: a submit keeps the folder path, including an anonymous submit from a public folder
• Cluster delivery: each cluster node serves the script and the styles of an AI View from {cgi}/amwf/aiv/{viewId}/{versionNum}/bundle.js and styles.css. When a node does not have the files, it checks that the user can read the view and rebuilds them from the stored version
• Remote forms: an AI form can run on Module Suite Runtime as a remote form, mounted in a region of a portal Shell Page
• AI View definition API: forms.getAiViewDefinition() returns the fields, sections, repeating groups, and choice labels of the AI View version that Content Server renders. describe(record) turns a stored form record into labelled answers grouped as in the view, for reports, notifications, exports, and agents. See Reading an AI View definition from a script
• For detailed information, see AI Form Builder

Shell Pages and Shell Components

A Shell Page is a new kind of Smart Page. The page is assembled from Shell Components that you develop, version, and publish on their own. Classic Smart Pages keep their current behavior, and both kinds of content can sit in the same perspective.

• New page types: the Smart Page editor can create a Classic page, a Shell Page, or a Shell Component
• Regions and layout: the page controller draws one styled region when its Region ID is set. Layout replaces Row and Column. Further regions are Region widgets in the layout. Each region mounts one component at a time and can carry initial properties and a policy
• Component communication: components coordinate through shared page state, events, and requests to change a region. The Shell checks the dirty state before a region is replaced
• Component AI Builder: generate a Shell Component, review its key, input properties, capabilities, and required permissions, then preview, compile, and deploy it. The builder can read the runtime source and the Module Suite Runtime REST catalog
• Smart View widgets: a Shell Component can embed the Nodes table, Document overview, Metadata, and Related workspaces widgets. The node picker and the member picker open as host dialogs above a modal overlay
• Localized strings: a component owns its strings and reads them with useI18n(). The Shell resolves the language once, when the component mounts. A key with no text in the default language blocks compile and deploy
• Design Profile: a component uses the same Design Profiles as the AI Form Builder, resolved from the request, the stored profile, and the host default
• Debug panel and Shell trace: enable the panel with the amshelldebug query parameter, the amshell.debug browser value, or the tile option, and open it with Ctrl+Alt+Shift+D. The panel shows regions, mounted components, shared state, events, and REST traffic. A Shell trace exports one debug session as Markdown, with secrets redacted. shell.inspect() returns the same data in the browser console
• Cleanup: when a component is removed, its markup and its styles are removed with it
• OData writes: an OData write accepts the parameters documented for that write
• For detailed information, see Shell pages and Shell components and the Shell Page reference

Module Suite Runtime (MSR)

Script Console is superseded by Module Suite Runtime

Script Console is discontinued. Starting with Module Suite 4.1.0, Module Suite Runtime (MSR) supersedes it. Move Script Console workloads to MSR.

Module Suite Runtime is the containerized runtime introduced with Module Suite 4.0. It supersedes the discontinued Script Console. In 4.1.0, MSR adds a portal that serves Shell Pages and Shell Components, runs AI forms as remote forms, and calls Content Server as the signed-in user.

• Portal: the portal hosts Shell Pages and Shell Components. System components can be edited in the Component AI Builder
• Component versions: a deploy from the Component AI Builder stores the component as a new version. One version is active. Activating or restoring a version selects the version the portal serves
• Access lists: pages and components carry access lists that decide where a component is mounted. Content Server remains the authority for its own data
• Forms: a form on MSR does not require the OpenText script-value library used on Content Server. List endpoints return stable page JSON, and classic form templates can use $forms. A default remote-form action refreshes the form
• Delegated authentication: sign-on uses OTDS OAuth 2.0. A bearer token is accepted only from a trusted issuer and a trusted client. After sign-on, the browser returns to the requested page
• Content Server from the browser: REST calls and Smart View widgets go from the browser to Content Server with the user's delegated token
• Submission sync: a Content Server script can list, download, and delete MSR remote-form submissions and their attachments with the msr service, and store them as Beautiful WebForms form records. Choose import-then-delete or a cursor on submittedAt. On MSR, scheduled scripts process and clean up submissions with csforms. Deleting a submission also deletes its files. See Syncing submissions to Content Server
• Public assets: files in the MSR asset store are served anonymously at /static/<path> for logos, CSS, and fonts on public pages and emails. Sub-folders inherit the nearest folder headers, responses carry a sandbox Content-Security-Policy, and the Asset Manager can copy the public URL of a file. See Public assets
• Deployment: MSR can be deployed with Docker Compose, on AWS ECS, or on Kubernetes. See Deployment
• Error responses: a public error response does not expose an internal failure
• For detailed information, see Module Suite Runtime

Aether

Aether is a SaaS service

Aether is delivered as a SaaS service. An on-premises deployment of Aether might be available in a future release.

Aether runs every Generation run for the AI editors. In 4.1.0, Aether configuration is separate from the Content Script API, and a run gets more context about the Content Server it writes code for.

• Model selection: an editor can select a model for each Generation run, or leave the selection on Auto. Content Server can narrow the models an editor shows with amcs.aether.allowedModels. An unknown or unavailable model makes the editor resend the request once on Auto
• Conversation continuity: a run can continue the previous conversation. A change of provider or model starts a new provider conversation
• Content Server API dictionary: the host supplies the Content Script API of its Content Server for a run. Every node in a cluster shares the same dictionary. The model can read the API of a returned object before it writes a call
• Traces and token use: a generation trace can be read after the run. Token use is counted for the tenant that started the run
• Client tool approval: CARL and Application Builder ask the user to approve a client tool before the tool runs
• Environment context cards: on Content Server, the Content Script editor, the AI Form Builder, and the Component AI Builder can attach up to four selected Content Server objects (a node, a user or group, or a table) as context for a run
• Knowledge corpus: the corpus that a run consults now includes category attribute type codes and a document-categorization agent
• Reasoning models: tool calls work when the selected model is a reasoning model
• PDF attachments: a PDF attachment can be read during a run without a browser export
• For detailed information, see Aether and Generation runs in Module Suite 4.1.0

AI Agents

• The new AMAgentController behaviour turns a Content Script into an AI agent. Install it with BehaviourHelper.addBeahaviours(this, AMAgentController.getBehaviours()) and return start()
• The agent answers on /otcs/cs/runcs/<agentNodeId> with the actions chat, chat_poll, chat_stop, chat_attach, chat_detach, chat_new, and chat_session. Any other path is routed to AMRestController
• A script can call an agent synchronously with docman.runContentScript(agentId, [agentInput: [message: "..."]])
• The optional agentLimits variable sets maxIterations, maxRunSeconds, maxAttachments, maxAttachmentBytes, and embedTypes
• An AI agent is now an Application Builder artifact. It is a Content Script stored under agents/ and declared with the agentRequest hook
• The hook runs once per model call and returns the profile, the request, the tools, any MCP profiles, and the tools that have side effects
• Each tool call runs on the Content Server request thread, where the tool can use the Content Server API
• The agent can call tools on files the user has attached. A conversation holds at most 50 files. A tool opens an attached file with turn.file(nodeId)
• An optional chat UI is a Shell Component on a Shell Page that references the agent
• For detailed information, see AI agents

LLM Extension

• The LLM service and the OpenAI service accept OAuth 2 credentials
• An Azure OpenAI call completes. Also in a 4.0 hotfix
• Detached stream jobs: startDetachedResponseStream and startDetachedChatCompletionStream run a stream in the background. Read the job with getStreamJob, listStreamJobs, and cancelStreamJob
• Response stream events: CSOpenAIResponseEvent tells text deltas, final text, completion, and errors apart
• Response compaction: compactResponse summarizes a conversation so it can continue with fewer tokens
• Error propagation: chat completion request builders accept propagateErrors
• Deprecations: CSOllamaChatModelBuilder.format is replaced by responseFormat. carl.getSmartCompletions is deprecated
• For detailed information, see LLM services and API additions in Module Suite 4.1.0

Model Context Protocol (MCP)

• MCP server definition DSL: define an MCP server in Content Script. The definition builds a manifest that records the tools, resources, and prompts the server exposes
• Remote tools: a remote tool runs the closure of the same name in a Content Server REST script, as the caller. The same definition can run a script on Module Suite Runtime instead
• Virtual resource folders: a server can expose virtual resource folders on Content Server, listed under the permissions of the caller
• AMMcpController behaviour: a Content Server REST script that serves remote tools uses the new AMMcpController behaviour. It defines one closure per tool and answers with an ok or error envelope
• Builders: mcpserver.newDefinitionBuilder(), mcpserver.newToolBuilder(), mcpserver.newResource(), mcpserver.newPrompt(), and mcpserver.newResourceFolder(name)
• Delegated profiles: isDelegatedProfile(profileId) on the remote Content Server REST services tells whether a profile authenticates as the current caller
• For detailed information, see MCP server definition

Content Script IDE

• One Content Script editor is used on Content Server and on Module Suite Runtime
• Labels are available in more than one language
• The snippet library can be changed while the editor is open
• Override builder methods appear in completion, with a description
• Brackets inside an inline comment no longer stop code completion
• users.CURRENTUSER() properties are no longer reported as unknown types
• The editor reports a diagnostic severity on calls to the Content Script API interfaces
• API help (Ctrl+H) opens the full help page. Also in a 4.0 hotfix
• Alt+Shift+F formats the script

Content Script

• Extension package interfaces: an extension package can call the Content Script API through its interfaces
• xECM: xECM service methods accept the parameters of the current request. users.CURRENTUSER() works when the script runs as an xECM scheduled bot (also in a 4.0 hotfix), and a new schedule bot can be created
• Impersonation: users.impersonateUser() honors the impersonation privilege. A script can create a Business Workspace while it impersonates an administrator. Also in a 4.0 hotfix
• Node paths: a node path is not cut when the node is in a Business Workspace, and pathIds returns that path. docman.getNode().path returns the same path length as previous versions
• Document content: docman.getContentAsRawText() works on a CSNode, and reports a failure when Document Conversion Server is down
• Categories: a script can set a category nickname and read the readOnly and searchable flags of a category attribute. getValidValues() does not write a trace for a Table Key Lookup attribute. isCategory does not use the node type as its only test
• Nodes and versions: a script can update node properties. addVersion lists each version of the node once. Lowering node rights does not set Add Major Version. An unnumbered version is named by its position, and the audit record keeps one actor
• REST: executeRestAPI accepts list parameters
• Rendition: rendition works on Content Server 26 and later. Also in a 4.0 hotfix
• New API members: docman.getApplicationVolume(), node.fullPath, version.findCategory(), version.listCategories(), forms.getTableName(), a safe mode for html.markdownToHtml(), and pdf.createBarcodeImage(), forms.getAiViewDefinition(), and forms.mapToForm(map, form, exactNames), which keeps field names as given. docman.getAttributeForSearch() and version.getFileName() are deprecated. See API additions in Module Suite 4.1.0
• Smart View actions: a Content Script command that runs in classic mode can be started from a Smart View search page. After a script action, the folder name and the context menu show the new values

Smart View Perspectives

• The amsui service can create, read, update, enable, and disable Smart View perspectives: newPerspectiveRequest, createPerspective, updatePerspective, getPerspectives, getPerspective, enablePerspective, disablePerspective, and saveAllPerspectives
• Layouts: generic, flow, and left-center-right
• Rules decide where a perspective applies
• Widget factories for Content Script tiles (Content Script, nodes table, chart, tree, links, link tiles, news, Shell content) and for Smart View widgets (nodes table, metadata, permissions, document overview, version overview, HTML editor, shortcuts, custom search, and preset widgets)
• amsui.overrides(overrides) with the new OverrideBuilder sets Smart View columns and commands for a node or a subtype
• For detailed information, see Smart View Perspectives and Smart View Overrides

xECM Business Workspace Types

• xecm.listWorkspaceTypes, getWorkspaceType, createWorkspaceType, updateWorkspaceType, and deleteWorkspaceType manage business workspace types
• xecm.newWorkspaceTypeRequest builds a type with names, descriptions, name generation, creation settings, locations, external document storage, search, indexing, widget icon, and relations
• xecm.newWorkspaceTemplateRequest and createWorkspaceTemplate create a business workspace template for a type
• For detailed information, see Extended ECM (xECM) service

Workflow

• CSWorkflowMap exposes its activities as CSWorkflowMapActivity and its links as CSWorkflowTransitionLink, so a script can read the steps of a map and how they connect
• For detailed information, see Workflow map activities and links

Transport

• Transport includes Beautiful WebForms view dependencies. Also in a 4.0 hotfix
• A script can call the transport service to use the transport operations
• A transport update of a Content Script keeps the schedules of the target script
• The transport service works with workbenches (CSWorkbench), transport items, dependencies and global dependency mappings, packages, and add results
• For detailed information, see Transport service

Office Documents (docx)

• docx.loadWordDoc accepts a CSResource
• The docx API can read numbering, tracked changes, comment anchors, and fields
• The docx API can edit tracked changes at word level, and removeComments() removes the comment text
• updateNamedShapes, setNamedShapesVisible, and writeNamedRegion are part of the docx API
• Cloning a table row keeps the row structure
• MERGEFIELD formatting is applied to MERGEFIELD results only
• Word documents can list paragraphs, bookmarks, and fields, enable track changes, accept or reject revisions, add comments, and remove personal information
• For detailed information, see Office documents (docx) service

Beautiful WebForms

• FormService.getFromRequest() and Form.updateValues() ignore request parameters that are not form fields
• View Form Data opens when the view template is SmartUI
• A Smart View V4 form can scroll, and a title set in the view parameters is kept
• New Tree Page widget
• A Kanban view can virtualize a long list
• The DataTable widget works in SAP GUI. Also in a 4.0 hotfix
• The V4 Drop area can be used from the keyboard. Also in a 4.0 hotfix
• The V4 Text Area popover shows its content
• The V4 Smart DropDown DB Lookup can open above the field and can load values saved in a SQL table. Also in a 4.0 hotfix

DocuSign, eSign, and Blazon

• DocuSign and eSign: both services accept a request again
• DocuSign webhook: DocuSign can send a webhook for envelope events
• Blazon: a Blazon profile has a trustAllCertificates property. A second conversion in the same script completes. Also in a 4.0 hotfix
• For detailed information on DocuSign integration, see DocuSign Extension Guide

Administration

• Base configuration shows the profiles of a service in one place
• Base configuration validates the license object. A missing license check does not write a trace file
• The mail service reads the SMTP user name from the service profile. Also in a 4.0 hotfix

Security

• On Module Suite Runtime, a bearer token is accepted only from a trusted issuer and a trusted client

Documentation changes in version 4.1.0

The following pages of this guide are new or have new sections for Module Suite 4.1.0. Start from these pages to learn the new features and APIs.

New pages

Page	Section of the guide	What it documents
AI Form Builder	Beautiful WebForms	AI Views, the V16 runtime, Design Profiles, Smart View pickers, cluster delivery, remote forms, and the AI View definition API
Shell pages and Shell components	Smart Pages	Shell Pages, regions and layout, the Component AI Builder, localization, the debug panel, and the Shell trace
Shell Page reference	Smart Pages	Every field, default, policy, capability, composable, and event of Shell Pages and Shell Components, with worked examples, troubleshooting, and the debug panel
Smart View Perspectives	Smart Pages	Building perspectives, layouts, rules, and widgets with the amsui service
Working with Module Suite Runtime	Module Suite Runtime	The portal, component versions, access lists, public assets, forms and submission sync, delegated authentication, and deployment with Docker Compose, AWS ECS, or Kubernetes
Aether	Content Script, Extension: AI (LLM)	What Aether is, how the editors use it, tenants, the model catalog, Generation runs, and the knowledge corpus
AI agents	Content Script, Extension: AI (LLM)	The AMAgentController behaviour, the agentRequest hook, the turn object, tools, and headless calls
Extended ECM (xECM) service	Content Script	The xecm service and the Business Workspace Type and template API
Transport service	Content Script	Workbenches, transport items, dependencies, packages, and add results
Office documents (docx) service	Content Script	Word, Excel, and PowerPoint documents, tracked changes, comments, fields, named regions, and named shapes

Updated pages

Page	New section	What it documents
LLM services	Generation runs in Module Suite 4.1.0	Aether configuration, the API dictionary, model selection, traces, client tool approval, AI agents, environment context cards, and limits
OpenAI APIs	API additions in Module Suite 4.1.0	Detached stream jobs, response stream events, response compaction, error propagation, and deprecations
MCP	MCP server definition	The mcpserver service, the definition and tool builders, the AMMcpController behaviour, resources, prompts, and permissions
Writing and executing scripts	API additions in Module Suite 4.1.0	New docman, node, version, forms (including getAiViewDefinition and mapToForm with exact names), html, and pdf members, and deprecations
Working with workflows	Workflow map activities and links	CSWorkflowMapActivity and CSWorkflowTransitionLink
Working with Script Console	Notice at the top of the page	Script Console is discontinued and superseded by Module Suite Runtime
Installing Script Console	Notice at the top of the page	Script Console is discontinued and superseded by Module Suite Runtime
Smart View Overrides	Since 4.1.0	amsui.overrides() and the OverrideBuilder

All Enhancements in version 4.1.0

ID	Scope	Description
#8	Beautiful WebForms	The AI Form Builder opens from a view and stores the generated form as a view version.
#47	Module Suite	Transport includes Beautiful WebForms view dependencies. Also in a 4.0 hotfix.
#49	Module Suite	A script can call the transport service.
#70	Content Script	Override builder methods appear in completion, with a description.
#72	Content Script	One Content Script editor is used on Content Server and on Module Suite Runtime.
#93	Smart Pages	The Smart Page editor can create a Classic page, a Shell Page, or a Shell Component.
#97	Content Script	xECM service methods accept the parameters of the current request.
#98	Content Script	An extension package can call the Content Script API through its interfaces.
#99	Extension - Docbuilder	The docx API includes updateNamedShapes, setNamedShapesVisible, and writeNamedRegion.
#105	Extension - LLM	Aether configuration is separate from the Content Script API.
#119	Extension - LLM	CARL and Application Builder ask the user to approve a client tool before the tool runs.
#123	Content Script	The Content Script editor shows labels in more than one language.
#125	Beautiful WebForms	Saving an AI View sets the widget library and the runtime version.
#127	Smart Pages	A Shell component can embed a Smart View widget.
#128	Module Suite	Base configuration shows the profiles of a service in one place.
#129	Smart Pages	A Shell component can use localized strings.
#138	Smart Pages	A Shell page can show a debug panel and a Shell trace.
#141	Extension - MSR	Module Suite Runtime can sign in to OpenText with OTDS OAuth 2.0.
#146	Module Suite	An unnumbered version is named by its position, and the audit record keeps one actor.
#147	Content Script	The snippet library can be changed while the editor is open.
#148	Extension - MSR	The Module Suite Runtime portal hosts Shell pages and Shell components.
#156	Extension - Rendition	A Blazon profile has a trustAllCertificates property.
#157	Beautiful WebForms	An AI form can run on Module Suite Runtime as a remote form.
#158	Extension - MSR	A form on Module Suite Runtime does not require the OpenText script-value library.
#159	Extension - MSR	List endpoints return stable page JSON. Classic form templates can use $forms.
#171	Extension - MSR	A bearer token is accepted only from a trusted issuer and a trusted client.
#195	Beautiful WebForms	An AI View version is published with the view id and the version id.
#196	Beautiful WebForms	An AI View version and a Shell Component version are stored as a non-zip artifact.
#199	Extension - LLM	Token use is counted for the tenant that started the generation run.
#201	Extension - LLM	A generation run can continue the previous conversation.
#204	Extension - LLM	The host supplies the Content Server API dictionary for a generation run.
#214	Extension - LLM	An editor can select a model for a generation, or leave the selection on Auto.
#220	Extension - MSR	A system component can be edited in the Component Builder.
#222	Extension - Docbuilder	The docx API can read numbering, tracked changes, comment anchors, and fields.
#229	Extension - Docbuilder	The docx API can edit tracked changes at word level. removeComments() removes the comment text.
#233	Smart Pages	A Shell controller draws one styled region. Layout replaces Row and Column.
#235	Smart Pages	The Component AI Builder can read the runtime source and the Module Suite Runtime REST catalog.
#236	Smart Pages	A Shell component can use a Design Profile.
#237	Extension - LLM	An AI agent is an Application Builder artifact.
#239	Extension - LLM	An AI agent can call tools on attached files.
#241	Beautiful WebForms	A V16 AI View works on a small screen and on a touch screen.
#251	Beautiful WebForms	Design Profiles are shared by AI forms and Shell components.
#253	Beautiful WebForms	A developer can mark Smart View pickers on an AI form.
#254	Beautiful WebForms	AI form files and Shell component files use one delivery model.
#256	Extension - LLM	The MCP server definition DSL builds a manifest, calls remote tools, and exposes virtual resource folders.
#260	Extension - LLM	Environment context cards pass selected Content Server objects into a chat editor.
#273	Extension - LLM	The knowledge corpus includes category attribute type codes and a document-categorization agent.
#274	Extension - MSR	Files in the asset store are served publicly at /static/, with inherited folder headers, a sandbox Content-Security-Policy, and a Copy public URL action.
#275	Extension - MSR	A Content Server script can sync remote-form submissions and their attachments from MSR, and MSR scripts can process and clean up submissions.
#278	Beautiful WebForms	forms.getAiViewDefinition() reads an AI View definition, and describe(record) turns a form record into labelled, grouped answers.
#2496	Extension - LLM	The LLM service and the OpenAI service accept OAuth 2 credentials.

Issues Resolved in version 4.1.0

ID	Scope	Description
#51	Beautiful WebForms	The DataTable widget works in SAP GUI. Also in a 4.0 hotfix.
#53	Content Script	docman.getContentAsRawText() works on a CSNode.
#59	Content Script	API help opens the full help page. Also in a 4.0 hotfix.
#63	Content Script	users.impersonateUser() honors the impersonation privilege.
#64	Module Suite	Base configuration validates the license object. A missing license check does not write a trace file.
#65	Beautiful WebForms	The V4 Text Area popover shows its content.
#67	Smart Pages	A Content Script command that runs in classic mode can be started from a Smart View search page.
#68	Extension - LLM	An Azure OpenAI call completes. Also in a 4.0 hotfix.
#69	Smart Pages	After a script action, the folder name and the context menu show the new values.
#76	Extension - Rendition	A second Blazon conversion in the same script completes. Also in a 4.0 hotfix.
#77	Content Script	A node path is not cut when the node is in a Business Workspace.
#78	Content Script	A script can set a nickname on a category.
#79	Content Script	CARL runs a request to completion.
#94	Extension - Rendition	Rendition works on Content Server 26 and later. Also in a 4.0 hotfix.
#96	Content Script	A script can create a Business Workspace while it impersonates an administrator. Also in a 4.0 hotfix.
#100	Content Script	users.CURRENTUSER() works when the script runs as an xECM scheduled bot. Also in a 4.0 hotfix.
#101	Content Script	A new xECM schedule bot can be created.
#102	Beautiful WebForms	AI View validation names the field that failed.
#109	Beautiful WebForms	The V16 AI View buttons submit the form and save it.
#111	Beautiful WebForms	An omitted fieldset field produces a warning and does not block a recompile.
#112	Smart Pages	A published Shell page controller contains its region and its component registry.
#113	Beautiful WebForms	A Shell-mounted AI View runs its OnLoad script.
#114	Beautiful WebForms	An action roundtrip keeps the changes made by the OnLoad script.
#118	Beautiful WebForms	View Form Data opens when the view template is SmartUI.
#120	Smart Pages	A Shell AI form returns to the list after submit or discard.
#122	Beautiful WebForms	The V4 Drop area can be used from the keyboard. Also in a 4.0 hotfix.
#130	Smart Pages	A Smart View form keeps its Content Server URL after the page loads.
#133	Content Script	getValidValues() does not write a trace for a Table Key Lookup attribute.
#137	Smart Pages	A Smart View script action completes and refreshes the view.
#153	Content Script	A script can update node properties.
#155	Extension - Docbuilder	MERGEFIELD formatting is applied to MERGEFIELD results only.
#160	Extension - MSR	A default remote-form action refreshes the form.
#165	Content Script	pathIds returns the path of a node in a Business Workspace.
#168	Content Script	docman.getNode().path returns the same path length as previous versions.
#169	Content Script	docman.getContentAsRawText() reports a failure when Document Conversion Server is down.
#170	Extension - DocuSign	DocuSign and eSign accept a request again.
#172	Extension - MSR	After sign-on, the browser returns to the requested page.
#175	Content Script	Brackets inside an inline comment do not stop code completion.
#179	Content Script	users.CURRENTUSER() properties are not reported as unknown types.
#194	Content Script	executeRestAPI accepts list parameters.
#202	Beautiful WebForms	A later AI Form Builder generation keeps the authored CSS.
#206	Extension - LLM	Tool calls work when the selected model is a reasoning model.
#210	Beautiful WebForms	FormService.getFromRequest() and Form.updateValues() ignore request parameters that are not form fields.
#211	Beautiful WebForms	The AI Form Builder stores and shows the authored CSS only.
#212	Beautiful WebForms	An AI View submit keeps the folder path, including an anonymous submit from a public folder.
#215	Content Script	Alt+Shift+F formats the script in the editor.
#227	Content Script	addVersion lists each version of the node once.
#228	Smart Pages	When a Shell component is removed, its markup and its styles are removed with it.
#234	Extension - MSR	A deploy from the Component AI Builder on Module Suite Runtime stores the new component.
#252	Beautiful WebForms	Each cluster node can serve the AI form files for that node.
#261	Content Script	A script can read the readOnly and searchable flags of a category attribute.