Skip to content

Changelog ​

Highlights ​

  1. The Semantic Center becomes Ontology: Describe business relationships in natural language to generate an ontology. Maintain logical definitions and physical mappings separately, so changes to business definitions do not require data configuration changes, and switching data sources does not require redefining business rules. Drafts and versions are managed across the space, with a redesigned interaction flow.
  2. Business Actions let Digital Workers carry out business operations: Define the scope, conditions, and permissions for critical business changes in advance, then publish them. Requests in chats and triggers from automation tasks use the same definition, keeping data changes controlled and business rules consistent.
  3. Non-text WeCom messages can now be parsed: Collection previously parsed only text. Images, voice, videos, files, and mini program messages can now be parsed individually, making quotations and demo videos shared by customers available for retrieval and Q&A.
  4. App connections add custom user credentials: For internal systems that issue individual keys without supporting OAuth, administrators define credential parameters and their request locations once. Members enter their own values, reducing configuration effort.

This Release's Focus: Business Actions Let Digital Workers Follow Your Rules ​

The new Business Actions in the Capability Center let teams define and publish operational rules in advance for Digital Workers to follow.

  • Bounded operations: Specify the business object, required information, and permitted changes.
  • Checks before execution: Verify permissions and business conditions. Request missing information first; do not submit if conditions are not met.
  • Reusable rules: Use the same published action in chats and automation tasks.

How to use Business Actions:

  1. Define the rules for marking an opportunity as won

For example, the team requires an opportunity to be approved and in the negotiation stage before it can be marked as won, with a reason provided. An administrator defines a “Mark Opportunity as Won” action with the checks, required information, and updates. Once published, everyone follows the same rules.
2. Act in a chat: state the request and confirm before changes are made

After the contract is signed, a salesperson says: “This renewal opportunity is won. The reason is that the customer confirmed the annual renewal.”

The Digital Worker matches the published action, finds the target opportunity, checks permissions, information, and conditions, then shows the proposed changes. Only after the salesperson confirms does it mark the opportunity as won. If conditions are not met, it explains why without making changes.

  • Scenario 1: Update an opportunity after a visit

After a customer visit, the salesperson confirms that the project has entered the proposal stage and the expected contract value is now RMB 800,000.

The salesperson can say: “Move this opportunity for Customer A to the proposal stage and change the expected contract value to RMB 800,000.”

Using the published “Update Opportunity” action, the Digital Worker locates an opportunity the user is allowed to operate on and checks the proposed changes and execution conditions. If several opportunities match, it asks the salesperson to identify the right one. It updates the record only after validation and confirmation.

  • Scenario 2: Mark an opportunity as won after signing

The annual renewal contract has been signed, but the CRM opportunity is still in negotiation.

The salesperson can say: “Customer A has signed the annual renewal. Mark this opportunity as won, with the reason that the customer confirmed the renewal.”

If the team has published a “Mark Opportunity as Won” action and connected the corresponding CRM tool, the Digital Worker checks the opportunity, permissions, and win conditions. It asks for missing information first. After the user confirms the change, it executes the operation in the CRM.

3. Let tasks handle routine changes using the same rules

Automation tasks can also invoke published actions. Each opportunity is still checked against the action's permissions and conditions, and the execution result is recorded. There is no need to define a separate set of rules for automated processing.

The Semantic Center Becomes Ontology: Separate Definitions and Mappings, Manage Versions Together ​

The Semantic Center is renamed Ontology. Teams can organize business objects such as customers and opportunities and their relationships more easily, while maintaining them collaboratively in one ontology space:

  • Define ontologies in natural language: Describe business objects and relationships to generate an ontology definition with system assistance. Conversational modeling replaces configuring each item individually, making it easier to get started.
  • Separate logical definitions and physical mappings: Save and maintain business definitions independently from data source mappings. Business rule changes do not affect data configuration, and data source changes do not alter business definitions.
  • Manage drafts and versions centrally: Ontology drafts and version history are shared across the entire space instead of belonging to individuals, keeping team modeling versions aligned.

Knowledge Base: More Complete WeCom Chat Collection ​

  • Expanded WeCom message parsing: WeCom collection already covered multiple message types but parsed only text. Images, voice, videos, files, and mini program messages are now parsed individually. Customer quotations, demo videos, and mini program cards shared in groups can be retrieved and cited in Q&A instead of remaining only raw collected messages.
  • Card view for the knowledge list: Switch to cards to browse image and screenshot thumbnails without opening each item.
  • Knowledge Base folder descriptions: Add a description when creating a folder. Digital Workers use it to narrow retrieval and find relevant materials more quickly and accurately.

App Connections: Custom User Credentials ​

  • The problem: Some enterprise systems issue a separate access code to each employee but do not support OAuth redirect authorization. These systems were previously difficult to use through app connections.
  • What's new: Administrators can configure which credentials members must provide and how they are submitted to the system. Administrators set shared enterprise information; members enter their individual values.
  • How members use it: After the connection is published, members enter their own access codes in App Connections. They do not have to share credentials, and can update expired credentials when prompted.
  • Example: An enterprise CRM gives each salesperson an access code. After an administrator configures the connection, each salesperson enters their code so Digital Workers can call the CRM using the appropriate credentials.

Data and Open Integration: For Developers and Platform Administrators ​

These capabilities are available to enterprise integration developers through OpenAPI and CLI.

  1. Memory management through OpenAPI / CLI: Manage memory through API calls and the command line. Enable or disable automatic memory collection and choose whether to clear existing automatic memory when disabling it. Replace or clear manual memory, and clear automatic memory by type or in full. Both personal memory and memory in a specified Collaboration Space are supported, letting you manage what Digital Workers retain from your own workspace.
  2. Collaboration Space workflows through OpenAPI / CLI: Invoke workflow capabilities through API calls and the command line to integrate workflow creation and run management into your enterprise platform.
  3. Data source support extends to MaxCompute: Define partition queries using conditions in an ontology or scan entire tables, giving more control over queries on very large tables. Extended attribute objects are not supported in this release.

Other Updates ​

  • Resource handling when members are deleted: Removing a tenant or Collaboration Space member automatically cleans up or transfers associated resources according to defined rules. Departures and role changes no longer leave unmanaged data, and collaborative content retains a clear owner without manual cleanup.

Try it: Ask an administrator to define a business action for your team's most frequent business change. Then say in a chat, “This opportunity is won because the customer confirmed the renewal,” and see the steps from request to completion.