English navigation · Main article content follows the Chinese edition. View Simplified Chinese version.

ChuanYun's collection of practical skills

50+ Practical skills · Best practices · Double efficiency

7General skills
Practical verification
Available now

Form design tips

Field naming uses English or Pinyin abbreviations
⭐ Basics
Field labels use English or Pinyin to facilitate subsequent formula reference and avoid poor readability of formulas caused by Chinese field names.

✓ Recommended practices

Leave days field identification: leave_days (instead of "leave days")

Formula reference: SUM(leave_days) ← Clear and easy to understand

Improve maintainability Easy to read formula
Optimize form layout using grouping and dividers
⭐ Basics
For forms with more than 10 fields, it is recommended to use the grouping function to classify related fields to improve the readability of the form.

✓ Recommended layout

  • 📋Basic information: applicant, department, application date
  • 📅 Leave information: leave type, start and end time, number of days of leave
  • 📝 Additional instructions: reasons for requesting leave and uploading attachments
Good user experience
Mobile layout single column display
⭐⭐ Advanced
The PC side can use a double-column layout to save space, but the mobile side recommends that all fields be displayed in a single column to avoid fields that are too small and difficult to operate.

✓ Setting method

Form Design → Layout Settings → Mobile Layout → Select "Single Column Display"

Mobile friendly
Reduce manual input using automatic calculations using formulas
⭐⭐ Advanced
For fields that can be calculated using formulas, do not let users fill them in manually to reduce the error rate.

✓ Examples of commonly used formulas

// Calculate the number of days of leave (working days)
NETWORKDAYS(start_date, end_date)

// Convert the amount from lower case to upper case
NUMBERSTRING(amount, 1)

// Get the current user name
CURRENTUSER()
Reduce errors Efficiency improvement
Use explicit and implicit rules to implement dynamic forms
⭐⭐⭐ Advanced
Dynamically show/hide fields based on user selections to avoid overly long forms and improve the filling experience.

✓ Application scenarios

Select "Sick Leave" → Display the "Sick Leave Certificate" upload field

Select "Personal Leave" → Hide the "Sick Leave Certificate" field

Setting method: Field properties → Show and hide rules → Add conditions

Good interactive experience

Process design skills

The approver prefers to use "supervisor" instead of the specific name.
⭐ Basics
The approver is set to "the submitter's supervisor" instead of writing down the specific name. When the personnel changes, there is no need to modify the process.

✗ Not recommended

Approver: Zhang San (if Zhang San resigns, the process will be interrupted)

✓ Recommended

Approver: Submitter’s supervisor (automatically matches organizational structure)

High maintainability
Reasonable use of conditional branches to reduce approval levels
⭐⭐ Advanced
The approval process is dynamically adjusted based on conditions such as amount and number of days to avoid complex procedures for small-amount applications.

✓ Optimization example

  • • Amount ≤ 1000 yuan: Supervisor approval → End
  • • 1000 < 金额 ≤ 5000：主管 → 部门经理 → 结束
  • • Amount > 5000: Supervisor → Department Manager → General Manager → End
Efficiency improvement Experience optimization
Enable approval timeout reminder
⭐⭐ Advanced
Set an approval timeout reminder to prevent documents from being stuck at a certain node for a long time without being processed.

✓ Recommended settings

Timeout: 24 hours

Reminder method: DingTalk message + site message

Remind: Approver + Approver supervisor

Process Monitoring
Allow approval rollback but control the number of rollbacks
⭐⭐⭐ Advanced
Allowing approval rejection can improve flexibility, but it is recommended to limit the number of rollbacks to avoid infinite loops.

✓ Recommended configuration

Allow rejection to: submitter/previous node

Maximum number of rejections: 2 times

After the number of times is exceeded: the process is automatically terminated and needs to be resubmitted.

The process is controllable

Data management skills

Make good use of filters to quickly locate data
⭐ Basics
Create filters for common query conditions and quickly view specific data with one click, avoiding manual filtering every time.

✓ Recommended filters

  • • My application: submitted by = current user
  • • Awaiting my approval: Approver = current user and status = Approval in progress
  • • Data for this month: submission date = this month
  • • Exception data: Process status = terminated
Efficiency improvement
Periodically archive historical data
⭐⭐ Advanced
It is recommended to archive historical data that exceeds 3 months to keep the amount of active data within a reasonable range and improve query speed.

✓ Archiving strategy

Archiving the previous quarter's data quarterly

Export Excel backup before archiving

Archived data can still be queried, but is not displayed by default.

Performance optimization
Back up important data regularly
⭐⭐ Advanced
Although ChuanYun has data protection, it is recommended to regularly export important data to local backup.

✓ Backup frequency recommendations

  • • Core business data: Back up once a week
  • • General data: Backup once a month
  • • Major nodes (such as the end of the year): full backup
Data Security

Performance optimization tips

Avoid using overly complex formulas
⭐⭐ Advanced
Complex formulas will affect the form loading speed. It is recommended to split them into multiple simple formulas or use automated rules instead.

✗ Not recommended (nested too deeply)

IF(AND(A>100, OR(B="X", C<50)), SUM(D*E), IF(F>200, G+H, I))

✓ Recommended (split calculation)

Field 1: conditions for judging A and B

Field 2: Condition for judging C

Field 3: Comprehensive calculation result of field 1 and field 2

Performance improvement
Reduce cross-table data association levels
⭐⭐ Advanced
It is recommended that data association does not exceed the 3 level. Too many levels will cause slow loading.

✓ Optimization plan

If you need deeply related data, consider adding redundant fields to the source table

Or use automated rules to sync data regularly

Performance optimization
The number of subform detail rows is controlled within 50 rows
⭐⭐⭐ Advanced
Too many detailed rows in a single subform will affect performance. It is recommended to control it within 50 rows, and consider splitting if it exceeds the number.

✓ Split plan

Split a large order into multiple sub-orders

Use master-child table association instead of a large number of details in a single table

Performance optimization

User experience skills

Add instructions for key fields
⭐ Basics
Add filling instructions or examples in field descriptions to reduce user filling errors.

✓ Example

Reimbursement amount: Please fill in the actual expenditure amount (accurate to the minute, such as: 198.50)

Contact number: Please fill in 11 mobile phone number (for example: 13812345678)

Reduce errors
Required fields are marked with eye-catching reminders
⭐ Basics
Required fields are added with "*" or marked in red after the field name to allow users to identify them at a glance.

✓ Identification method

ChuanYun automatically adds a red * mark to required fields

It is recommended to set core fields as required to avoid incomplete data

Good user experience
Use icons and colors to differentiate between states
⭐⭐ Advanced
In the list view, use different colors or icons to identify different states to improve readability.

✓ Status ID

  • 🟢 Passed: Green
  • 🟡Pending approval: yellow
  • 🔴Rejected: red
  • ⚪ Draft: Gray
Visual optimization

Security and Permissions Tips

Sensitive field setting data desensitization
⭐⭐ Advanced
For sensitive information such as ID number and mobile phone number, it is recommended to set desensitized display to protect privacy.

✓ Desensitization example

ID card: Displayed as 320***********1234

Mobile phone number: Displayed as 138****5678

Setting method: Field attributes → Data desensitization

Privacy Protection
Assign least privileges by role
⭐⭐ Advanced
Follow the principle of least privilege and only assign necessary permissions to users to avoid the risk of data leakage.

✓ Permission classification

  • Ordinary employees: can only view and submit their own data
  • Department manager: can view all data of the department
  • Administrator: can view all data + configure applications
Safe and controllable

Recommended practical tools

browser plug-in

ChuanYun Developer Tools - Formula Tips, Code Snippets

Excel template

Requirements documents, test cases, training manual templates

code base

Commonly used formula code snippets and front-end event examples

More practical tips: Join Knowledge Planet

New skills updated every week + skill video tutorials + expert Q&A

Join now
Return to Learning Center