软件功能提示信息撰写

以下为“表单构建器组件”的标准化提示信息清单，涵盖按钮文案、工具提示、校验提示与空状态说明。文案采用简洁、行动导向的风格，支持在不同界面模块中复用。占位符以花括号表示，如 {fieldLabel}、{min}、{max}。

一、按钮文案
- 全局与项目
  - 新建表单
  - 保存草稿
  - 发布
  - 更新发布
  - 预览
  - 分享
  - 复制链接
  - 关闭预览
- 画布与字段
  - 添加字段
  - 插入分组
  - 排序
  - 对齐
  - 多选
  - 复制字段
  - 删除字段（危险操作）
  - 隐藏字段
  - 显示字段
  - 锁定位置
  - 解锁位置
- 侧边栏与设置
  - 字段设置
  - 表单设置
  - 校验规则
  - 条件逻辑
  - 外观主题
  - 集成
- 协作与版本
  - 撤销
  - 重做
  - 版本历史
  - 预览此版本
  - 还原此版本（危险操作）
- 导入导出与数据
  - 导入
  - 导出
  - 下载模板
  - 清空数据（危险操作）
  - 重置为默认
  - 应用
  - 取消
  - 确认
- 流程导航
  - 上一步
  - 下一步
  - 完成
- 表单填写端（预览/运行时）
  - 提交
  - 保存进度
  - 继续填写
  - 返回

二、工具提示（Tooltips）
- 画布与布局
  - 拖拽以添加字段到画布
  - 按住 Shift 可多选元素
  - 与参考线对齐以获得一致的间距
  - 锁定后不可移动或编辑
- 字段项
  - 标记为必填后，用户需填写此字段
  - 字段键用于数据集成与导出，需唯一且稳定
  - 复制字段将复制当前配置与校验
  - 隐藏字段在填写端不可见，可用于逻辑或预填
- 条件逻辑
  - 条件从上至下匹配，命中后不再检查后续条件
  - 避免循环依赖：字段不可依赖自身或相互依赖
  - 拖拽以调整条件优先级
- 校验规则
  - 正则表达式需包含有效语法
  - 范围校验同时设置最小值与最大值时需保证最小值小于最大值
  - 选项上限应大于或等于选项下限
- 发布与分享
  - 发布后更改将对外可见
  - 更新发布会覆盖线上版本
  - 复制链接以分享给填写者
- 导入导出
  - 导入前请使用模板格式以减少错误
  - 导出包含字段结构与校验配置
- 协作与权限
  - 有人正在编辑此区域，稍后再试
  - 无编辑权限，仅可查看
- 无障碍与可用性
  - 为每个字段提供清晰的标签与描述
  - 占位符不应替代标签

三、校验提示（Validation）
A. 构建器配置校验
- 表单级
  - 表单标题不能为空
  - 存在未保存更改，是否离开
  - 仅拥有查看权限，无法保存或发布
- 字段属性
  - 请输入字段标签
  - 字段键不能为空
  - 字段键已存在：{fieldKey}
  - 字段键格式无效：仅允许字母、数字和下划线，且以字母开头
  - 超出最大长度：最多 {max} 个字符
  - 超出最小长度：至少 {min} 个字符
  - 最小值需小于最大值
  - 小数位数超出限制：最多 {max} 位
  - 选项不能为空
  - 选项重复：{option}
  - 至少保留 {min} 个选项
  - 文件大小超出限制：最大 {maxSize}
  - 不支持的文件类型：{type}
  - 日期范围无效：开始日期需早于结束日期
  - 正则无效：{error}
  - 循环依赖检测到：{fieldA} 与 {fieldB}
- 条件逻辑
  - 条件不完整：请选择字段、运算符与值
  - 条件冲突：存在重复或互斥条件
  - 无命中分支：请设置默认分支或补充条件
- 导入导出与集成
  - 导入失败：格式不符合模板
  - 导入失败：字段键冲突 {fieldKey}
  - 导出失败：请稍后重试
  - 集成未配置凭据
  - 集成测试失败：{error}
- 发布与版本
  - 发布失败：网络异常，请重试
  - 更新发布失败：存在未通过的校验
  - 还原失败：无权限或版本不存在

B. 表单填写端校验（预览/运行时）
- 必填项：请填写{fieldLabel}
- 格式错误：请输入有效的{fieldLabel}
- 邮箱格式不正确
- 手机号格式不正确
- URL 格式不正确
- 超出最大长度：最多 {max} 个字符
- 未达最小长度：至少 {min} 个字符
- 超出最大值：最大为 {max}
- 未达最小值：最小为 {min}
- 选择数量超出限制：最多选择 {max} 项
- 选择数量不足：至少选择 {min} 项
- 文件过大：最大 {maxSize}
- 文件数量超出限制：最多 {maxCount} 个文件
- 不支持的文件类型：{type}
- 日期无效：请选择有效日期
- 时间无效：请选择有效时间
- 正则校验未通过
- 应大于或等于 {otherField}
- 请勾选同意条款后继续
- 提交失败：请检查网络或稍后重试
- 请勿重复提交

四、空状态说明（Empty States）
说明包含标题、描述与建议操作（CTA）。

- 画布无字段
  - 标题：尚无字段
  - 描述：从左侧添加字段开始构建表单
  - CTA：添加字段
- 字段库搜索无结果
  - 标题：未找到匹配字段
  - 描述：调整关键词或筛选条件后重试
  - CTA：清除筛选
- 条件逻辑为空
  - 标题：尚未创建条件
  - 描述：根据用户输入设置显示、跳转或赋值规则
  - CTA：新建条件
- 校验规则为空
  - 标题：尚未配置校验
  - 描述：添加必填、长度、范围等规则以提升数据质量
  - CTA：添加校验
- 外观主题为空
  - 标题：尚未应用主题
  - 描述：选择配色与字体以保持品牌一致
  - CTA：选择主题
- 集成未配置
  - 标题：未连接任何集成
  - 描述：连接第三方以同步数据或发送通知
  - CTA：添加集成
- 版本历史为空
  - 标题：暂无历史版本
  - 描述：保存后可在此查看并还原版本
  - CTA：保存草稿
- 提交数据为空（分析页）
  - 标题：暂无提交
  - 描述：分享表单以开始收集数据
  - CTA：复制链接
- 权限成员为空
  - 标题：尚未添加协作者
  - 描述：邀请成员共同编辑或查看
  - CTA：邀请协作者
- 分享未生成
  - 标题：尚未发布
  - 描述：发布后生成可分享的访问链接
  - CTA：发布
- 回收站为空
  - 标题：回收站为空
  - 描述：删除的内容将显示于此，30 天后自动清理
  - CTA：返回

五、可复用占位与辅助文案（可选）
- 占位符
  - 输入字段标签
  - 输入描述（可选）
  - 输入字段键（如 customer_email）
  - 搜索字段或设置
- 辅助文本
  - 字段键一旦用于集成不建议更改
  - 描述用于向填写者提供额外说明
  - 正则示例：^\\d{6}$ 表示 6 位数字

六、文案一致性原则（实现与验证用）
- 按钮不加句号，使用动词开头，优先 2–4 字
- 工具提示不超过 120 字，说明单一要点
- 错误信息优先指出问题与修复路径，必要时包含限制值
- 危险操作按钮以“删除”“清空”“还原此版本”等明确风险词开头

如需按具体产品信息架构或字符长度限制进一步定制，可提供界面截图或字数要求以细化版本。

Purpose
Provide end-user assistance content for the Permission Change Center, including a Help card, FAQs, embedded in-product guidance (microcopy, tooltips, validation, banners), and quick-resolution steps for high-frequency errors.

Help Card (Need Help)
Title: Need help with permission changes?

What you can do here:
- Request new access or modify existing permissions
- Set a start and end date for temporary access
- Track request status and see required approvals
- Revoke or downgrade access you no longer need

Before you start:
- Confirm the resource name or ID (e.g., project, repository, application)
- Select the exact role or permission set you need
- Prepare a clear business justification
- If requesting on behalf of a user or team, ensure you have delegation rights

Approvals and timing:
- Most requests require owner or manager approval
- Sensitive roles (admin, write, production) may require additional approvals
- Processing times vary by resource and policy; you will be notified of updates

Security and compliance:
- Changes are logged for audit
- Temporary access is recommended for elevated permissions
- Your justification is visible to approvers and auditors

Need more help?
- Review the FAQs below
- Contact support with your request ID

FAQ
1) What is a permission change?
A request to add, remove, or modify a user’s access to a resource (e.g., assigning a role, granting a permission set, or changing access duration).

2) Who can submit a request?
Any authenticated user can request access for themselves. Requests on behalf of others may require delegation or admin rights, depending on policy.

3) Can I request temporary access?
Yes. Select a start and end date. Temporary access is recommended for elevated roles.

4) Why do I need to provide a justification?
Approvers and auditors use it to verify business need and ensure least-privilege access.

5) How long will my request take?
It depends on required approvals and provider processing. You will receive notifications at each stage.

6) What if my request is denied?
You will see the denial reason in the request details. You can edit and resubmit, or contact the approver for guidance.

7) Can I request access for a team or group?
If enabled by policy. Otherwise, submit individual requests or contact your admin.

8) What if I cannot find my resource?
Use the resource ID if available. If still missing, choose “Resource not listed” and provide details, or contact the resource owner.

9) What is the difference between role and permission set?
A role is a predefined collection of permissions. A permission set may be a more granular group. Choose the smallest set that meets your need.

10) Can I change or cancel a submitted request?
Yes, while it is pending. Open the request and select Cancel or Edit.

11) How do I track my request?
Go to My Requests. Use filters for status, resource, or date. Select a request to view approval steps and activity.

12) What happens when temporary access expires?
Access is automatically removed. You will be notified before expiration and can request an extension if needed.

13) Will this cause downtime?
Permission changes typically do not cause downtime. Some systems may require a short propagation window.

14) Are changes audited?
Yes. All changes, approvals, and revocations are recorded and searchable by authorized users.

15) How are conflicts handled (e.g., multiple roles)?
The most restrictive policy applies unless explicitly allowed. Conflicts are shown during review with recommended actions.

Embedded In-Product Guidance (Microcopy)
Page titles and summaries:
- Permission Change Center: Request, track, and manage access changes
- New Request: Specify resource, role, justification, and duration

Primary actions:
- Request access
- Modify access
- Revoke access
- Submit for approval
- Save as draft
- Cancel request

Field labels and help text:
- Resource: Search by name or ID. Example: “billing-api-prod” or “PRJ-12345”
- Role/Permission set: Choose the least-privilege option that meets your need
- Assignee: User who will receive the access. Default is you
- Duration: For temporary access, set start and end. Permanent access requires justification
- Justification: Explain business need, scope, and impact. Avoid sensitive data
- Approver (optional): Suggest an approver if known. Final routing follows policy

Tooltips and info banners:
- “Sensitive role”: This role grants elevated privileges and requires additional approval
- “Conflicting roles”: Selected role overlaps with existing permissions. Consider removing redundant access
- “Policy hint”: Your organization recommends temporary access for write/admin roles

Validation messages:
- Resource is required
- Role is required
- Assignee is required
- Start date must be today or later
- End date must be after start date
- Duration exceeds policy limit of {X days}
- Justification must be at least {N} characters
- You have a pending request for this resource and role. Edit the existing request instead

Empty states:
- No requests yet: Submit your first access change to get started
- No matches found: Adjust your search or enter the resource ID
- No approvals required: This request will be auto-processed based on policy

Status and toasts:
- Submitted: Your request {REQ-ID} was submitted and routed for approval
- Approved: Your request was approved. Applying changes now
- Changes applied: Access granted. Propagation may take up to {X minutes}
- Denied: Your request was denied by {Approver}. View details
- Revoked: Access removed as requested
- Auto-expired: Temporary access expired on {date}. Re-request if needed

Confirmation dialogs:
- Confirm revoke: Removing this access immediately. Continue?
- Confirm cancel: This will withdraw the request. Continue?
- Confirm overwrite: You already have a similar role. Replace with the new role?

Inline review cues for approvers:
- Risk summary: Elevated scope, temporary access requested, justification length
- Impact preview: Resources affected, groups changed, potential conflicts
- Decision options: Approve, Deny, Request changes. Add a comment for audit

High-Frequency Error Resolution Steps
1) Error: “Insufficient privileges to request this change”
- Likely cause: You lack delegation or requestor rights for the assignee or resource
- Fix (requestor): Submit for yourself, or ask a manager/owner to submit. If you need delegation, request it from the admin
- Fix (admin): Grant request-on-behalf permission or adjust policy for the user’s group

2) Error: “Resource not found”
- Likely cause: Typo, wrong environment (dev/prod), or the resource is not onboarded
- Fix (requestor): Verify the exact name/ID; switch environment filter; try the ID if name fails
- Fix (owner/admin): Onboard the resource to the directory or sync metadata; confirm visibility settings

3) Error: “Role/permission set unavailable”
- Likely cause: Role is deprecated, renamed, or restricted by policy
- Fix (requestor): Select an alternative role or submit with “Cannot find role” notes
- Fix (admin): Restore or map deprecated roles; update catalog; add migration guidance

4) Error: “Duration exceeds policy limit”
- Likely cause: Requested end date beyond allowed maximum
- Fix (requestor): Shorten the duration or request permanent access with stronger justification
- Fix (admin): If business-justified, update policy or add an exception workflow

5) Error: “Pending duplicate request”
- Likely cause: Existing open request for same resource/role/assignee
- Fix (requestor): Edit the existing request to change dates or justification; cancel if no longer needed
- Fix (admin): Merge or close duplicates; communicate consolidation to requestor

6) Error: “Approval routing failed”
- Likely cause: Missing resource owner, invalid approver configuration, or directory sync delay
- Fix (requestor): Provide a suggested approver and resubmit later if prompted
- Fix (admin): Assign a fallback owner; repair approver groups; trigger a directory sync and requeue

7) Error: “Policy conflict detected (role overlap or assignment cap)”
- Likely cause: New role conflicts with existing roles or exceeds assignment limits
- Fix (requestor): Remove redundant access or select a non-conflicting role
- Fix (admin): Update conflict rules; define allowed combinations; raise caps if compliant

8) Error: “MFA required to approve or apply change”
- Likely cause: Sensitive change requires step-up authentication
- Fix (requestor/approver): Complete MFA and retry the action
- Fix (admin): Verify MFA policy enforcement and ensure the user’s MFA enrollment is active

9) Error: “Provisioning failed at provider”
- Likely cause: External system error, rate limit, or invalid mapping
- Fix (requestor): Wait and retry if prompted; check status for details
- Fix (admin): Review provider logs; verify role-to-group mappings; retry with backoff; open a ticket with the provider if persistent

10) Error: “License or seat unavailable”
- Likely cause: No available license for the requested role/application
- Fix (requestor): Choose a different role or request a license via the designated process
- Fix (admin): Allocate additional licenses or define a waitlist; notify the requestor

11) Error: “Session expired”
- Likely cause: Inactivity or token expiry
- Fix (requestor/approver): Sign in again and resume from My Drafts or My Requests

12) Error: “Invalid justification”
- Likely cause: Too short or contains restricted content
- Fix (requestor): Provide specific business purpose, scope, and timeframe. Do not include secrets or personal data
- Fix (admin): Adjust minimum length or content rules if needed

Operational tips (for admins/owners):
- Keep the resource catalog and role mappings current to reduce “not found” and “unavailable” errors
- Define fallback approvers and escalation paths
- Enforce least privilege by favoring temporary elevated access with clear maximum durations
- Monitor audit logs and provisioning failure rates to identify systemic issues

Style and Tone Guidance (for product copy)
- Use concise, action-oriented language
- Prefer concrete labels over jargon (e.g., “Role” instead of “Entitlement artifact”)
- Surface policy constraints early (e.g., duration limits) to prevent rework
- Provide next steps in every error message
- Avoid blame; suggest user and admin paths to resolve

This content is designed to be pasted into your product UI and documentation with minimal modification. Replace placeholders such as {REQ-ID}, {X minutes}, and {N} with runtime values or policy settings.