2022.08.10 version update-YIDA page link default card transfer

Background introduction

YIDA a large number of application/page links are sent in DingTalk single chat/group chat every day to improve the operation efficiency of operators and viewers, by default, links in existing YIDA high-frequency scenarios can be converted into cards according to common business conditions, thus YIDA applications have cool application capabilities of cool links by default.

Typical scenarios:

• Link sharing automatic card transfer: Beautiful
• YIDA message cardalization: Information focus

Features

Link to card universal function description:

1. Click the whole card by default to view the page details.

2. All login-free access/oIf the link of is not in the current organization, it cannot be converted to a standard card. It can only be converted to a standard card in the current organization.

3. Links shared across organizations cannot be converted into cards.

Pre-description of opening method:

1. All links at the application layer or page layer (without instances) are opened in the same way as before. The browser is opened by default.

2. The page layer (with instance data) normal form/flow chart details page. The opening method can be opened in the right drawer. Applicable to single chat or group chat scenarios.

3. All mobile addresses are still enabled in full screen.

case1Common applications/Page link (no instance data)

When users YIDA applications/Links such as forms will be converted into a card after being shared in DingTalk sessions (single chat or group chat). Users can directly display web pages without clicking on web links.The title, summary, and main map can bring a good user experience.

Share application links (open by default)

Function entry/Link name	1-before sending	2-Transfer to standard interactive card after sending (single chat/Group chat)
Custom link sharing
Application homepage link address

YIDA page link sharing (opened by default browser)

Function entry	Function link	1-Before sending	2-Transfer to standard interactive card after sending (single chat/Group chat)
Common form	Share Free
	Share within the organization
	Share custom links within an organization
Flow chart	Share Free
	Share within the organization
	Share custom links within an organization
Custom page	Share Free
	Share within the organization
	Share custom links within an organization
Generated Data Management page	Share within the organization
	Share custom links within an organization
Report page	Share within the organization
	Share custom links within an organization

case2Ordinary/Details link of flow sheet page (with instance data)--(Single chat/By default, the right drawer is open for group chat)

• When the card is sent to the group (Currently, different business fields are not supported for different people, only standard cards can be displayed);
• When the card is sent to a single chat (3 business fields +2 system fields are displayed);

• Business field display rules:Three required business fields with permissions and data from top to bottom in the preset page + two system fields: initiator/Initiation Time

• Special note: If you have changed the permission configuration, it will only take effect on the newly sent Link card.

• If there is a form instance, only the business field component types revealed in the single chat scenario are supported.Single-line text, multi-line text, numeric value, single choice, date, member, Department

Common form

When a user shares a common form link in a DingTalk session (both single chat and group chat), it will be converted into an interactive card, to solve the core problem, you can quickly view the core business fields of the current document. To view the details, you can click the button to quickly preview.

Page sample link	1-Before sending	2-Transfer to interactive card after sending (group chat)	3-Transfer to interactive card after sending (single chat)
Common form document sharing

Flow chart

After the user shares the approval document link in a DingTalk session (both single chat and group chat), it will be converted into an interactive card.The core problem is that the user can complete the approval action without jumping or losing the screen. The user's approval url link automatically generates an approval card. The user can directly click "agree" or "reject.

The status of the approval card represents the status of the process instance rather than the task status ".

Page sample link	1-Before sending	2-Transfer to interactive card after sending (group chat)	3-transfer to interactive card (single chat) after sending with quick approval action
Flow chart document sharing	Quick process approval card	[Sender perspective/Receiver perspective]]:	[Sender perspective]]: SenderShow the details of documents to be approved, and the person to be approved will approve them. View approver approval results: If the approval result has been agreed If the approval is rejected, the reason for the rejection is displayed. 3. Initiator can be revoked
			[Approver's perspective]]: Approver perspective, showingView details, if you have required fields on the current node, go to the flow chart details page for approval. After you click reject, the card status changes. After you click agree, the card status changes.