From e413420867da8ac7d9ac2e9e046ee63d71a2f66c Mon Sep 17 00:00:00 2001 From: Albert Ma Date: Wed, 4 Mar 2026 10:03:17 +0800 Subject: [PATCH] docs: align image references across all language versions --- .../auth-oidc/examples/google.md | 2 +- .../auth-saml/examples/google.md | 2 +- .../auth-verification/auth/authenticators.md | 2 +- .../ar/auth-verification/auth/dev/index.md | 2 +- .../ar/auth-verification/auth/password.md | 6 ++-- .../associations/o2m/index.md | 2 +- .../ar/data-sources/field-encryption/index.md | 2 +- .../ar/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/ar/email-manager/usage/signature.md | 8 ++--- docs/docs/ar/email-manager/usage/template.md | 8 ++--- docs/docs/ar/flow-engine/learning-roadmap.md | 2 +- .../blocks/data-blocks/list.md | 2 +- docs/docs/ar/solution/ticket-system/design.md | 34 +++++++++---------- .../ar/users-permissions/acl/permissions.md | 2 +- docs/docs/ar/users-permissions/acl/ui.md | 4 +-- docs/docs/ar/workflow/advanced/variables.md | 2 +- docs/docs/ar/workflow/nodes/aggregate.md | 2 +- docs/docs/ar/workflow/nodes/manual.md | 2 +- docs/docs/ar/workflow/nodes/variable.md | 4 +-- docs/docs/ar/workflow/triggers/post-action.md | 2 +- docs/docs/ar/workflow/triggers/pre-action.md | 6 ++-- .../auth-oidc/examples/google.md | 2 +- .../auth-saml/examples/google.md | 2 +- .../cs/auth-verification/auth-saml/index.md | 2 +- .../auth-verification/auth/authenticators.md | 2 +- .../cs/auth-verification/auth/dev/index.md | 2 +- .../collection-expression/collection.md | 4 +-- .../associations/m2o/index.md | 2 +- .../associations/o2m/index.md | 2 +- .../associations/o2o/index.md | 4 +-- .../cs/data-sources/field-encryption/index.md | 2 +- .../cs/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/cs/email-manager/usage/signature.md | 8 ++--- docs/docs/cs/email-manager/usage/template.md | 8 ++--- docs/docs/cs/flow-engine/learning-roadmap.md | 2 +- docs/docs/cs/solution/ticket-system/design.md | 34 +++++++++---------- .../cs/users-permissions/acl/permissions.md | 2 +- docs/docs/cs/users-permissions/acl/role.md | 2 +- docs/docs/cs/users-permissions/user.md | 2 +- docs/docs/cs/workflow/nodes/aggregate.md | 2 +- docs/docs/cs/workflow/nodes/create.md | 2 +- docs/docs/cs/workflow/nodes/destroy.md | 2 +- docs/docs/cs/workflow/nodes/manual.md | 8 ++--- docs/docs/cs/workflow/nodes/parallel.md | 4 +-- .../cs/workflow/nodes/response-message.md | 2 +- docs/docs/cs/workflow/nodes/variable.md | 6 ++-- docs/docs/cs/workflow/triggers/post-action.md | 2 +- docs/docs/cs/workflow/triggers/pre-action.md | 6 ++-- .../knowledge-base/knowledge-base.md | 6 ++-- docs/docs/de/ai-employees/permission.md | 4 +-- .../de/auth-verification/api-keys/index.md | 2 +- .../auth-saml/examples/google.md | 2 +- .../de/auth-verification/auth-saml/index.md | 2 +- .../de/auth-verification/auth/dev/index.md | 2 +- .../de/data-sources/collection-fdw/index.md | 2 +- .../de/data-sources/field-encryption/index.md | 2 +- .../de/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/de/email-manager/usage/signature.md | 8 ++--- docs/docs/de/email-manager/usage/template.md | 8 ++--- docs/docs/de/flow-engine/learning-roadmap.md | 2 +- .../fields/specific/picker.md | 2 +- docs/docs/de/solution/ticket-system/design.md | 34 +++++++++---------- .../de/users-permissions/acl/permissions.md | 2 +- docs/docs/de/users-permissions/acl/role.md | 2 +- docs/docs/de/users-permissions/acl/ui.md | 2 +- docs/docs/de/users-permissions/user.md | 2 +- docs/docs/de/workflow/advanced/revisions.md | 4 +-- docs/docs/de/workflow/nodes/aggregate.md | 2 +- docs/docs/de/workflow/nodes/calculation.md | 2 +- docs/docs/de/workflow/nodes/destroy.md | 2 +- docs/docs/de/workflow/nodes/json-query.md | 2 +- docs/docs/de/workflow/nodes/manual.md | 6 ++-- docs/docs/de/workflow/nodes/request.md | 2 +- docs/docs/de/workflow/nodes/variable.md | 2 +- docs/docs/de/workflow/triggers/post-action.md | 2 +- docs/docs/de/workflow/triggers/pre-action.md | 6 ++-- .../knowledge-base/knowledge-base.md | 10 +++--- .../es/auth-verification/api-keys/index.md | 2 +- .../auth-oidc/examples/google.md | 2 +- .../es/data-sources/field-encryption/index.md | 2 +- .../es/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/es/email-manager/usage/signature.md | 8 ++--- docs/docs/es/email-manager/usage/template.md | 8 ++--- docs/docs/es/flow-engine/learning-roadmap.md | 2 +- docs/docs/es/solution/ticket-system/design.md | 34 +++++++++---------- .../es/users-permissions/acl/permissions.md | 2 +- docs/docs/es/users-permissions/acl/role.md | 2 +- docs/docs/es/users-permissions/acl/ui.md | 2 +- docs/docs/es/workflow/advanced/revisions.md | 2 +- docs/docs/es/workflow/nodes/calculation.md | 2 +- docs/docs/es/workflow/nodes/destroy.md | 2 +- docs/docs/es/workflow/nodes/manual.md | 4 +-- docs/docs/es/workflow/nodes/variable.md | 2 +- docs/docs/es/workflow/triggers/collection.md | 4 +-- docs/docs/es/workflow/triggers/post-action.md | 2 +- docs/docs/es/workflow/triggers/pre-action.md | 6 ++-- docs/docs/fr/ai-employees/permission.md | 4 +-- .../fr/auth-verification/api-keys/index.md | 2 +- .../fr/auth-verification/auth-saml/index.md | 2 +- .../auth-verification/auth/authenticators.md | 2 +- .../fr/auth-verification/auth/dev/index.md | 2 +- .../fr/auth-verification/auth/password.md | 2 +- .../fr/data-sources/collection-fdw/index.md | 2 +- .../associations/o2o/index.md | 2 +- .../fr/data-sources/field-encryption/index.md | 2 +- .../fr/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/fr/email-manager/usage/signature.md | 8 ++--- docs/docs/fr/email-manager/usage/template.md | 8 ++--- docs/docs/fr/flow-engine/learning-roadmap.md | 2 +- docs/docs/fr/solution/ticket-system/design.md | 34 +++++++++---------- .../fr/users-permissions/acl/permissions.md | 2 +- docs/docs/fr/users-permissions/acl/role.md | 2 +- docs/docs/fr/users-permissions/acl/ui.md | 2 +- .../fr/users-permissions/departments/role.md | 2 +- docs/docs/fr/users-permissions/user.md | 4 +-- docs/docs/fr/workflow/advanced/revisions.md | 2 +- docs/docs/fr/workflow/nodes/aggregate.md | 2 +- docs/docs/fr/workflow/nodes/calculation.md | 4 +-- docs/docs/fr/workflow/nodes/create.md | 2 +- docs/docs/fr/workflow/nodes/loop.md | 2 +- docs/docs/fr/workflow/nodes/manual.md | 4 +-- .../fr/workflow/nodes/response-message.md | 2 +- docs/docs/fr/workflow/nodes/variable.md | 6 ++-- docs/docs/fr/workflow/triggers/post-action.md | 2 +- docs/docs/fr/workflow/triggers/pre-action.md | 6 ++-- .../auth-oidc/examples/google.md | 2 +- .../he/auth-verification/auth-oidc/index.md | 2 +- .../auth-saml/examples/google.md | 6 ++-- .../auth-verification/auth/authenticators.md | 2 +- .../he/auth-verification/auth/password.md | 2 +- .../he/data-sources/collection-fdw/index.md | 2 +- .../associations/m2o/index.md | 2 +- .../associations/o2m/index.md | 2 +- .../he/data-sources/field-encryption/index.md | 2 +- .../he/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/he/email-manager/usage/signature.md | 8 ++--- docs/docs/he/email-manager/usage/template.md | 8 ++--- docs/docs/he/flow-engine/learning-roadmap.md | 2 +- .../interface-builder/actions/types/link.md | 2 +- docs/docs/he/solution/ticket-system/design.md | 34 +++++++++---------- docs/docs/he/users-permissions/acl/role.md | 2 +- docs/docs/he/users-permissions/acl/ui.md | 6 ++-- docs/docs/he/users-permissions/user.md | 2 +- docs/docs/he/workflow/advanced/variables.md | 2 +- docs/docs/he/workflow/nodes/aggregate.md | 2 +- docs/docs/he/workflow/nodes/calculation.md | 2 +- docs/docs/he/workflow/nodes/create.md | 2 +- docs/docs/he/workflow/nodes/destroy.md | 2 +- docs/docs/he/workflow/nodes/end.md | 2 +- docs/docs/he/workflow/nodes/manual.md | 8 ++--- docs/docs/he/workflow/nodes/parallel.md | 2 +- .../he/workflow/nodes/response-message.md | 2 +- docs/docs/he/workflow/nodes/variable.md | 8 ++--- docs/docs/he/workflow/triggers/post-action.md | 2 +- docs/docs/he/workflow/triggers/pre-action.md | 4 +-- .../hi/auth-verification/api-keys/index.md | 2 +- .../auth-saml/examples/google.md | 2 +- .../auth-verification/auth/authenticators.md | 2 +- .../associations/m2o/index.md | 2 +- .../associations/o2m/index.md | 2 +- .../associations/o2o/index.md | 2 +- .../hi/data-sources/field-encryption/index.md | 2 +- .../hi/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/hi/email-manager/usage/signature.md | 8 ++--- docs/docs/hi/email-manager/usage/template.md | 8 ++--- docs/docs/hi/flow-engine/learning-roadmap.md | 2 +- docs/docs/hi/solution/ticket-system/design.md | 34 +++++++++---------- .../hi/users-permissions/acl/permissions.md | 2 +- docs/docs/hi/users-permissions/acl/ui.md | 6 ++-- .../hi/users-permissions/departments/index.md | 2 +- .../hi/users-permissions/departments/role.md | 2 +- docs/docs/hi/users-permissions/user.md | 2 +- docs/docs/hi/workflow/advanced/variables.md | 2 +- docs/docs/hi/workflow/nodes/condition.md | 2 +- docs/docs/hi/workflow/nodes/create.md | 2 +- docs/docs/hi/workflow/nodes/loop.md | 2 +- docs/docs/hi/workflow/nodes/manual.md | 4 +-- docs/docs/hi/workflow/nodes/variable.md | 6 ++-- docs/docs/hi/workflow/triggers/collection.md | 2 +- docs/docs/hi/workflow/triggers/post-action.md | 2 +- docs/docs/hi/workflow/triggers/pre-action.md | 8 ++--- .../id/auth-verification/api-keys/index.md | 2 +- .../auth-oidc/examples/google.md | 2 +- .../auth-saml/examples/google.md | 4 +-- .../id/data-sources/collection-fdw/index.md | 2 +- .../associations/o2o/index.md | 4 +-- .../id/data-sources/field-encryption/index.md | 2 +- .../data-visualization/guide/chart-options.md | 2 +- .../id/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/id/email-manager/usage/signature.md | 8 ++--- docs/docs/id/email-manager/usage/template.md | 8 ++--- docs/docs/id/flow-engine/learning-roadmap.md | 2 +- docs/docs/id/solution/ticket-system/design.md | 34 +++++++++---------- .../id/users-permissions/acl/permissions.md | 2 +- docs/docs/id/users-permissions/acl/ui.md | 2 +- docs/docs/id/workflow/advanced/variables.md | 2 +- docs/docs/id/workflow/nodes/manual.md | 4 +-- .../id/workflow/nodes/response-message.md | 4 +-- docs/docs/id/workflow/nodes/variable.md | 4 +-- docs/docs/id/workflow/triggers/post-action.md | 2 +- docs/docs/id/workflow/triggers/pre-action.md | 2 +- docs/docs/id/workflow/triggers/schedule.md | 2 +- docs/docs/it/ai-employees/permission.md | 4 +-- .../it/auth-verification/auth-oidc/index.md | 2 +- .../auth-saml/examples/google.md | 4 +-- .../it/auth-verification/auth-saml/index.md | 2 +- .../it/auth-verification/auth/dev/index.md | 2 +- .../associations/m2o/index.md | 2 +- .../associations/o2m/index.md | 2 +- .../it/data-sources/field-encryption/index.md | 2 +- .../it/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/it/email-manager/usage/signature.md | 8 ++--- docs/docs/it/email-manager/usage/template.md | 8 ++--- docs/docs/it/flow-engine/learning-roadmap.md | 2 +- docs/docs/it/solution/ticket-system/design.md | 34 +++++++++---------- docs/docs/it/users-permissions/acl/role.md | 2 +- docs/docs/it/users-permissions/user.md | 4 +-- docs/docs/it/workflow/advanced/revisions.md | 2 +- docs/docs/it/workflow/advanced/variables.md | 2 +- docs/docs/it/workflow/nodes/destroy.md | 2 +- docs/docs/it/workflow/nodes/end.md | 2 +- docs/docs/it/workflow/nodes/manual.md | 6 ++-- docs/docs/it/workflow/nodes/request.md | 2 +- docs/docs/it/workflow/nodes/variable.md | 2 +- docs/docs/it/workflow/triggers/post-action.md | 4 +-- docs/docs/it/workflow/triggers/schedule.md | 2 +- .../ja/auth-verification/api-keys/index.md | 2 +- .../ja/auth-verification/auth-cas/index.md | 2 +- .../auth-saml/examples/google.md | 4 +-- .../ja/auth-verification/auth/dev/index.md | 2 +- .../ja/auth-verification/auth/password.md | 2 +- .../collection-expression/collection.md | 2 +- .../associations/m2o/index.md | 2 +- .../associations/o2o/index.md | 2 +- .../ja/data-sources/field-encryption/index.md | 2 +- .../ja/data-visualization/guide/data-query.md | 4 +-- .../ja/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/ja/email-manager/usage/signature.md | 8 ++--- docs/docs/ja/email-manager/usage/template.md | 8 ++--- docs/docs/ja/flow-engine/learning-roadmap.md | 2 +- docs/docs/ja/solution/ticket-system/design.md | 34 +++++++++---------- docs/docs/ja/users-permissions/acl/role.md | 2 +- docs/docs/ja/users-permissions/acl/ui.md | 6 ++-- docs/docs/ja/workflow/advanced/executions.md | 2 +- docs/docs/ja/workflow/advanced/options.md | 2 +- docs/docs/ja/workflow/nodes/create.md | 2 +- docs/docs/ja/workflow/nodes/destroy.md | 2 +- docs/docs/ja/workflow/nodes/manual.md | 4 +-- docs/docs/ja/workflow/nodes/parallel.md | 2 +- docs/docs/ja/workflow/nodes/request.md | 2 +- docs/docs/ja/workflow/nodes/variable.md | 2 +- docs/docs/ja/workflow/triggers/post-action.md | 2 +- docs/docs/ja/workflow/triggers/pre-action.md | 4 +-- docs/docs/ja/workflow/triggers/schedule.md | 2 +- docs/docs/ko/ai-employees/permission.md | 2 +- .../ko/auth-verification/api-keys/index.md | 2 +- .../ko/auth-verification/auth-oidc/index.md | 2 +- .../auth-verification/auth/authenticators.md | 2 +- .../ko/auth-verification/auth/dev/index.md | 2 +- .../ko/auth-verification/auth/password.md | 2 +- .../collection-expression/collection.md | 2 +- .../associations/o2o/index.md | 4 +-- .../ko/data-sources/field-encryption/index.md | 2 +- .../ko/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/ko/email-manager/usage/signature.md | 8 ++--- docs/docs/ko/email-manager/usage/template.md | 8 ++--- docs/docs/ko/flow-engine/learning-roadmap.md | 2 +- docs/docs/ko/integration/api-doc/index.md | 2 +- docs/docs/ko/solution/ticket-system/design.md | 34 +++++++++---------- docs/docs/ko/template-print/faq.md | 4 +-- .../ko/users-permissions/acl/permissions.md | 2 +- docs/docs/ko/users-permissions/user.md | 2 +- docs/docs/ko/workflow/advanced/revisions.md | 2 +- docs/docs/ko/workflow/nodes/condition.md | 2 +- docs/docs/ko/workflow/nodes/manual.md | 6 ++-- docs/docs/ko/workflow/nodes/parallel.md | 2 +- docs/docs/ko/workflow/nodes/request.md | 2 +- docs/docs/ko/workflow/nodes/variable.md | 4 +-- docs/docs/ko/workflow/triggers/post-action.md | 2 +- docs/docs/ko/workflow/triggers/pre-action.md | 2 +- docs/docs/ko/workflow/triggers/schedule.md | 2 +- .../knowledge-base/knowledge-base.md | 4 +-- docs/docs/nl/ai-employees/permission.md | 4 +-- .../nl/auth-verification/api-keys/index.md | 2 +- .../auth-oidc/examples/google.md | 2 +- .../auth-saml/examples/google.md | 2 +- .../nl/auth-verification/auth-saml/index.md | 2 +- .../auth-verification/auth/authenticators.md | 2 +- .../nl/auth-verification/auth/dev/index.md | 2 +- .../associations/o2o/index.md | 2 +- .../nl/data-sources/field-encryption/index.md | 2 +- .../nl/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/nl/email-manager/usage/signature.md | 8 ++--- docs/docs/nl/email-manager/usage/template.md | 8 ++--- docs/docs/nl/flow-engine/learning-roadmap.md | 2 +- docs/docs/nl/integration/api-doc/index.md | 2 +- docs/docs/nl/integration/api-keys/index.md | 2 +- docs/docs/nl/solution/ticket-system/design.md | 34 +++++++++---------- docs/docs/nl/users-permissions/acl/role.md | 2 +- docs/docs/nl/users-permissions/acl/ui.md | 4 +-- .../nl/users-permissions/departments/role.md | 2 +- docs/docs/nl/users-permissions/user.md | 2 +- docs/docs/nl/workflow/nodes/calculation.md | 4 +-- docs/docs/nl/workflow/nodes/condition.md | 2 +- docs/docs/nl/workflow/nodes/manual.md | 6 ++-- docs/docs/nl/workflow/nodes/update.md | 4 +-- docs/docs/nl/workflow/nodes/variable.md | 4 +-- docs/docs/nl/workflow/triggers/post-action.md | 2 +- docs/docs/nl/workflow/triggers/pre-action.md | 6 ++-- docs/docs/nl/workflow/triggers/schedule.md | 2 +- .../knowledge-base/knowledge-base.md | 10 +++--- .../pl/auth-verification/auth-oidc/index.md | 2 +- .../auth-saml/examples/google.md | 2 +- .../pl/auth-verification/auth-saml/index.md | 2 +- .../collection-expression/collection.md | 2 +- .../pl/data-sources/collection-fdw/index.md | 4 +-- .../associations/m2o/index.md | 2 +- .../associations/o2o/index.md | 2 +- .../pl/data-sources/field-encryption/index.md | 2 +- .../data-visualization/guide/chart-options.md | 2 +- .../pl/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/pl/email-manager/usage/signature.md | 8 ++--- docs/docs/pl/email-manager/usage/template.md | 8 ++--- docs/docs/pl/flow-engine/learning-roadmap.md | 2 +- docs/docs/pl/integration/sso/index.md | 2 +- docs/docs/pl/solution/ticket-system/design.md | 34 +++++++++---------- .../pl/users-permissions/acl/permissions.md | 2 +- docs/docs/pl/users-permissions/acl/role.md | 2 +- docs/docs/pl/users-permissions/acl/ui.md | 2 +- .../pl/users-permissions/departments/role.md | 4 +-- docs/docs/pl/workflow/nodes/calculation.md | 2 +- docs/docs/pl/workflow/nodes/destroy.md | 2 +- docs/docs/pl/workflow/nodes/manual.md | 6 ++-- docs/docs/pl/workflow/nodes/variable.md | 6 ++-- docs/docs/pl/workflow/triggers/post-action.md | 2 +- docs/docs/pl/workflow/triggers/pre-action.md | 2 +- docs/docs/pl/workflow/triggers/schedule.md | 2 +- .../pt/auth-verification/auth/password.md | 2 +- .../collection-expression/collection.md | 2 +- .../associations/o2m/index.md | 2 +- .../pt/data-sources/field-encryption/index.md | 2 +- .../data-visualization/guide/chart-options.md | 2 +- .../pt/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/pt/email-manager/usage/signature.md | 8 ++--- docs/docs/pt/email-manager/usage/template.md | 8 ++--- docs/docs/pt/flow-engine/learning-roadmap.md | 2 +- docs/docs/pt/integration/api-doc/index.md | 2 +- docs/docs/pt/solution/ticket-system/design.md | 34 +++++++++---------- docs/docs/pt/users-permissions/acl/ui.md | 4 +-- docs/docs/pt/users-permissions/user.md | 2 +- docs/docs/pt/workflow/nodes/aggregate.md | 2 +- docs/docs/pt/workflow/nodes/calculation.md | 2 +- docs/docs/pt/workflow/nodes/create.md | 2 +- docs/docs/pt/workflow/nodes/manual.md | 2 +- docs/docs/pt/workflow/nodes/request.md | 2 +- docs/docs/pt/workflow/nodes/variable.md | 4 +-- docs/docs/pt/workflow/triggers/post-action.md | 2 +- docs/docs/pt/workflow/triggers/pre-action.md | 4 +-- docs/docs/pt/workflow/triggers/schedule.md | 2 +- .../auth-saml/examples/google.md | 2 +- .../ru/auth-verification/auth-saml/index.md | 2 +- .../auth-verification/auth/authenticators.md | 2 +- .../ru/data-sources/collection-fdw/index.md | 2 +- .../associations/m2o/index.md | 2 +- .../associations/o2o/index.md | 2 +- .../ru/data-sources/field-encryption/index.md | 2 +- .../data-visualization/guide/chart-options.md | 2 +- .../ru/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/ru/email-manager/usage/signature.md | 8 ++--- docs/docs/ru/email-manager/usage/template.md | 8 ++--- docs/docs/ru/flow-engine/learning-roadmap.md | 2 +- .../fields/association-field.md | 2 +- docs/docs/ru/solution/ticket-system/design.md | 34 +++++++++---------- .../ru/users-permissions/acl/permissions.md | 2 +- docs/docs/ru/users-permissions/acl/role.md | 2 +- docs/docs/ru/users-permissions/acl/ui.md | 6 ++-- .../ru/users-permissions/departments/role.md | 2 +- docs/docs/ru/workflow/advanced/options.md | 2 +- docs/docs/ru/workflow/nodes/aggregate.md | 2 +- docs/docs/ru/workflow/nodes/calculation.md | 2 +- docs/docs/ru/workflow/nodes/create.md | 2 +- docs/docs/ru/workflow/nodes/manual.md | 4 +-- docs/docs/ru/workflow/nodes/parallel.md | 2 +- .../ru/workflow/nodes/response-message.md | 2 +- docs/docs/ru/workflow/nodes/variable.md | 6 ++-- docs/docs/ru/workflow/triggers/collection.md | 2 +- docs/docs/ru/workflow/triggers/post-action.md | 2 +- docs/docs/ru/workflow/triggers/pre-action.md | 2 +- .../knowledge-base/knowledge-base.md | 12 +++---- .../auth-oidc/examples/google.md | 4 +-- .../auth-saml/examples/google.md | 2 +- .../sv/data-sources/collection-fdw/index.md | 2 +- .../associations/m2o/index.md | 2 +- .../associations/o2o/index.md | 4 +-- .../sv/data-sources/field-encryption/index.md | 2 +- .../sv/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/sv/email-manager/usage/signature.md | 8 ++--- docs/docs/sv/email-manager/usage/template.md | 8 ++--- docs/docs/sv/flow-engine/learning-roadmap.md | 2 +- docs/docs/sv/solution/ticket-system/design.md | 34 +++++++++---------- docs/docs/sv/users-permissions/acl/ui.md | 4 +-- docs/docs/sv/workflow/nodes/aggregate.md | 4 +-- docs/docs/sv/workflow/nodes/loop.md | 2 +- docs/docs/sv/workflow/nodes/manual.md | 6 ++-- docs/docs/sv/workflow/nodes/parallel.md | 4 +-- docs/docs/sv/workflow/nodes/variable.md | 4 +-- docs/docs/sv/workflow/triggers/collection.md | 2 +- docs/docs/sv/workflow/triggers/post-action.md | 2 +- docs/docs/sv/workflow/triggers/pre-action.md | 2 +- docs/docs/sv/workflow/triggers/schedule.md | 2 +- docs/docs/th/ai-employees/permission.md | 2 +- .../auth-saml/examples/google.md | 2 +- .../auth-verification/auth/authenticators.md | 2 +- .../th/data-sources/collection-fdw/index.md | 2 +- .../associations/o2o/index.md | 2 +- .../th/data-sources/field-encryption/index.md | 2 +- .../th/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/th/email-manager/usage/signature.md | 8 ++--- docs/docs/th/email-manager/usage/template.md | 8 ++--- docs/docs/th/flow-engine/learning-roadmap.md | 2 +- docs/docs/th/solution/ticket-system/design.md | 34 +++++++++---------- docs/docs/th/users-permissions/acl/role.md | 2 +- docs/docs/th/users-permissions/acl/ui.md | 2 +- .../th/users-permissions/departments/role.md | 2 +- docs/docs/th/users-permissions/user.md | 2 +- docs/docs/th/workflow/advanced/variables.md | 2 +- docs/docs/th/workflow/nodes/calculation.md | 2 +- docs/docs/th/workflow/nodes/destroy.md | 2 +- docs/docs/th/workflow/nodes/manual.md | 6 ++-- docs/docs/th/workflow/nodes/parallel.md | 2 +- docs/docs/th/workflow/nodes/variable.md | 2 +- docs/docs/th/workflow/triggers/collection.md | 2 +- docs/docs/th/workflow/triggers/post-action.md | 2 +- docs/docs/th/workflow/triggers/pre-action.md | 4 +-- docs/docs/tr/ai-employees/permission.md | 2 +- .../tr/auth-verification/auth-oidc/index.md | 2 +- .../associations/o2m/index.md | 2 +- .../tr/data-sources/field-encryption/index.md | 2 +- .../tr/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/tr/email-manager/usage/signature.md | 8 ++--- docs/docs/tr/email-manager/usage/template.md | 8 ++--- docs/docs/tr/flow-engine/learning-roadmap.md | 2 +- docs/docs/tr/solution/ticket-system/design.md | 34 +++++++++---------- docs/docs/tr/users-permissions/acl/role.md | 2 +- .../tr/users-permissions/departments/index.md | 2 +- .../tr/users-permissions/departments/role.md | 2 +- docs/docs/tr/workflow/advanced/revisions.md | 2 +- docs/docs/tr/workflow/nodes/aggregate.md | 2 +- docs/docs/tr/workflow/nodes/destroy.md | 2 +- docs/docs/tr/workflow/nodes/json-query.md | 2 +- docs/docs/tr/workflow/nodes/manual.md | 6 ++-- docs/docs/tr/workflow/nodes/parallel.md | 2 +- .../tr/workflow/nodes/response-message.md | 2 +- docs/docs/tr/workflow/nodes/update.md | 4 +-- docs/docs/tr/workflow/nodes/variable.md | 4 +-- docs/docs/tr/workflow/triggers/collection.md | 2 +- docs/docs/tr/workflow/triggers/post-action.md | 4 +-- .../uk/auth-verification/api-keys/index.md | 2 +- .../associations/o2o/index.md | 2 +- .../uk/data-sources/field-encryption/index.md | 2 +- .../data-visualization/guide/chart-options.md | 2 +- .../uk/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/uk/email-manager/usage/signature.md | 8 ++--- docs/docs/uk/email-manager/usage/template.md | 8 ++--- docs/docs/uk/integration/sso/index.md | 2 +- docs/docs/uk/solution/ticket-system/design.md | 34 +++++++++---------- docs/docs/uk/users-permissions/acl/ui.md | 2 +- .../uk/users-permissions/departments/index.md | 2 +- .../uk/users-permissions/departments/role.md | 2 +- docs/docs/uk/users-permissions/user.md | 2 +- docs/docs/uk/workflow/advanced/executions.md | 2 +- docs/docs/uk/workflow/nodes/calculation.md | 4 +-- docs/docs/uk/workflow/nodes/json-query.md | 2 +- docs/docs/uk/workflow/nodes/loop.md | 2 +- docs/docs/uk/workflow/nodes/manual.md | 4 +-- docs/docs/uk/workflow/nodes/parallel.md | 2 +- docs/docs/uk/workflow/nodes/request.md | 2 +- docs/docs/uk/workflow/nodes/variable.md | 4 +-- docs/docs/uk/workflow/triggers/post-action.md | 2 +- docs/docs/uk/workflow/triggers/pre-action.md | 2 +- docs/docs/vi/ai-employees/permission.md | 4 +-- .../vi/auth-verification/auth-saml/index.md | 2 +- .../vi/auth-verification/auth/password.md | 2 +- .../associations/o2o/index.md | 2 +- .../vi/data-sources/data-source-main/index.md | 2 +- .../vi/data-sources/field-encryption/index.md | 2 +- .../vi/email-manager/advanced/batch-send.md | 14 ++++---- docs/docs/vi/email-manager/usage/signature.md | 8 ++--- docs/docs/vi/email-manager/usage/template.md | 8 ++--- docs/docs/vi/flow-engine/learning-roadmap.md | 2 +- docs/docs/vi/solution/ticket-system/design.md | 34 +++++++++---------- .../vi/users-permissions/acl/permissions.md | 2 +- docs/docs/vi/users-permissions/acl/ui.md | 8 ++--- .../vi/users-permissions/departments/index.md | 2 +- docs/docs/vi/users-permissions/user.md | 2 +- docs/docs/vi/workflow/advanced/variables.md | 2 +- docs/docs/vi/workflow/nodes/calculation.md | 2 +- docs/docs/vi/workflow/nodes/end.md | 2 +- docs/docs/vi/workflow/nodes/manual.md | 4 +-- docs/docs/vi/workflow/nodes/variable.md | 4 +-- docs/docs/vi/workflow/triggers/post-action.md | 2 +- docs/docs/vi/workflow/triggers/schedule.md | 2 +- 502 files changed, 1201 insertions(+), 1201 deletions(-) diff --git a/docs/docs/ar/auth-verification/auth-oidc/examples/google.md b/docs/docs/ar/auth-verification/auth-oidc/examples/google.md index f75cc566f87..882adf327bc 100644 --- a/docs/docs/ar/auth-verification/auth-oidc/examples/google.md +++ b/docs/docs/ar/auth-verification/auth-oidc/examples/google.md @@ -14,7 +14,7 @@ انتقل إلى واجهة الإعدادات واملأ عنوان URL لإعادة التوجيه المصرّح به. يمكن الحصول على عنوان URL لإعادة التوجيه عند إضافة مُصادِق جديد في NocoBase، وعادةً ما يكون `http(s)://host:port/api/oidc:redirect`. راجع قسم [دليل المستخدم - الإعدادات](../index.md#configuration). -![](https://static-docs.nocobase.com/24078bf2ec966a16334894cb3d9d126.png) +![](https://static-docs.nocobase.com/24078bf52ec966a16334894cb3d9d126.png) ## إضافة مُصادِق جديد في NocoBase diff --git a/docs/docs/ar/auth-verification/auth-saml/examples/google.md b/docs/docs/ar/auth-verification/auth-saml/examples/google.md index d14549c7f8d..59f3278f480 100644 --- a/docs/docs/ar/auth-verification/auth-saml/examples/google.md +++ b/docs/docs/ar/auth-verification/auth-saml/examples/google.md @@ -35,7 +35,7 @@ ![](https://static-docs.nocobase.com/1536268bf8df4a5ebc72384317172191.png) -![](https://static-docs.nocobase.com/c7de1f8b84df4a5ebc72384317172191.png) +![](https://static-docs.nocobase.com/c7de1f8b84c1335de110e5a7c96255c4.png) تحت قسم **تعيين السمات (Attribute Mapping)**، أضف تعيينات للسمات المقابلة. diff --git a/docs/docs/ar/auth-verification/auth/authenticators.md b/docs/docs/ar/auth-verification/auth/authenticators.md index 357c9ac85e0..a91a8b71a1a 100644 --- a/docs/docs/ar/auth-verification/auth/authenticators.md +++ b/docs/docs/ar/auth-verification/auth/authenticators.md @@ -16,7 +16,7 @@ pkg: '@nocobase/plugin-auth' ## تفعيل أدوات المصادقة -![](https://static-docs.nocobase.com/7f1bf8f8ca5de67ffc68eff0a65848f5.png) +![](https://static-docs.nocobase.com/7f1fb8f8ca5de67ffc68eff0a65848f5.png) فقط أنواع المصادقة المفعّلة هي التي ستظهر في صفحة تسجيل الدخول. diff --git a/docs/docs/ar/auth-verification/auth/dev/index.md b/docs/docs/ar/auth-verification/auth/dev/index.md index 27abb86c7fd..ab591119202 100644 --- a/docs/docs/ar/auth-verification/auth/dev/index.md +++ b/docs/docs/ar/auth-verification/auth/dev/index.md @@ -167,7 +167,7 @@ class CustomAuthPlugin extends Plugin { ### نموذج إعدادات المسؤول -![](https://static-docs.nocobase.com/f4b44b5b0f5afee5621ad4abf66b24f.png) +![](https://static-docs.nocobase.com/f4b544b5b0f5afee5621ad4abf66b24f.png) الجزء العلوي هو التكوين العام للمصادقة، والجزء السفلي هو جزء نموذج التكوين المخصص الذي يمكن تسجيله. diff --git a/docs/docs/ar/auth-verification/auth/password.md b/docs/docs/ar/auth-verification/auth/password.md index 448dbfce0c5..4b90ce28893 100644 --- a/docs/docs/ar/auth-verification/auth/password.md +++ b/docs/docs/ar/auth-verification/auth/password.md @@ -20,15 +20,15 @@ pkg: '@nocobase/plugin-auth' صفحة التسجيل -![](https://static-docs.nocobase.com/ac3c342df28cb7c6dc70b24e99e7f7.png) +![](https://static-docs.nocobase.com/ac3c3ab42df28cb7c6dc70b24e99e7f7.png) عند عدم السماح بالتسجيل، لن تعرض صفحة تسجيل الدخول رابطًا لإنشاء حساب. -![](https://static-docs.nocobase.com/8d5e3b6df9991bfc1c2e095a3745121.png) +![](https://static-docs.nocobase.com/8d5e3b6df9991bfc1c2e095a93745121.png) عند عدم السماح بالتسجيل، لا يمكن الوصول إلى صفحة التسجيل. -![](https://static-docs.nocobase.com/09325c4b07e09f84dff8430556.png) +![](https://static-docs.nocobase.com/09325c4b07e09f88f80a14dff8430556.png) ## إعدادات نموذج التسجيلv1.4.0-beta.7+ diff --git a/docs/docs/ar/data-sources/data-modeling/collection-fields/associations/o2m/index.md b/docs/docs/ar/data-sources/data-modeling/collection-fields/associations/o2m/index.md index 52548847672..e3384a67bca 100644 --- a/docs/docs/ar/data-sources/data-modeling/collection-fields/associations/o2m/index.md +++ b/docs/docs/ar/data-sources/data-modeling/collection-fields/associations/o2m/index.md @@ -12,7 +12,7 @@ تهيئة الحقل: -![alt text](https://static-docs.nocobase.com/a608ce54821172dad8e8ab760107ff4e.png) +![alt text](https://static-docs.nocobase.com/a608ce54821172dad7e8ab760107ff4e.png) ## وصف المعلمات diff --git a/docs/docs/ar/data-sources/field-encryption/index.md b/docs/docs/ar/data-sources/field-encryption/index.md index c6137940a46..47f3559ed1a 100644 --- a/docs/docs/ar/data-sources/field-encryption/index.md +++ b/docs/docs/ar/data-sources/field-encryption/index.md @@ -30,7 +30,7 @@ pkg: "@nocobase/plugin-field-encryption" تعتمد طريقة تشفير الأظرف (Envelope Encryption). -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### عملية إنشاء المفتاح 1. عند إنشاء حقل مشفر لأول مرة، ينشئ النظام تلقائيًا `مفتاح تطبيق` بحجم 32 بت، ويُحفظ بترميز Base64 في دليل التخزين الافتراضي. diff --git a/docs/docs/ar/email-manager/advanced/batch-send.md b/docs/docs/ar/email-manager/advanced/batch-send.md index 13b6d586ec7..02fdab072bd 100644 --- a/docs/docs/ar/email-manager/advanced/batch-send.md +++ b/docs/docs/ar/email-manager/advanced/batch-send.md @@ -11,27 +11,27 @@ pkg: "@nocobase/plugin-email-manager" ## نظرة عامة على الإرسال بالجملة يمكنك إرسال رسائل بريد إلكتروني إلى عدة أشخاص دفعة واحدة (سيتلقى كل مستلم رسالة بريد إلكتروني منفصلة). -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## الإرسال بالجملة عبر الجدول يمكنك أيضًا إرسال رسائل بريد إلكتروني بالجملة عبر جدول: 1. أضف زر إرسال بريد إلكتروني إلى الجدول - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. قم بتكوين حقل البريد الإلكتروني في الجدول (يُستخدم لتحليل عناوين البريد الإلكتروني بعد تحديد صفوف الجدول) - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. حدد بيانات الجدول لإرسال رسائل البريد الإلكتروني - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) إذا كنت بحاجة إلى إرسال رسائل بريد إلكتروني إلى جميع العناوين في الجدول بأكمله، فيمكنك تمكين ميزة **تحديد جميع السجلات في الجدول الحالي كمستلمين افتراضيًا**: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) بعد تحرير محتوى البريد الإلكتروني، انقر على زر الإرسال بالجملة للإرسال: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## تتبع إرسال البريد الإلكتروني يمكنك عرض وتتبع حالة إرسال البريد الإلكتروني المحددة في مركز إدارة البريد الإلكتروني: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/ar/email-manager/usage/signature.md b/docs/docs/ar/email-manager/usage/signature.md index 17cbee14ceb..f23d3d0749b 100644 --- a/docs/docs/ar/email-manager/usage/signature.md +++ b/docs/docs/ar/email-manager/usage/signature.md @@ -11,15 +11,15 @@ pkg: "@nocobase/plugin-email-manager" ## إعدادات التوقيع انتقل إلى مركز إدارة البريد الإلكتروني وانقر على زر الإعدادات: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) انتقل إلى لوحة التوقيع: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) يمكنك إدارة التوقيعات هنا. حدد الخيار الموجود قبل التوقيع لتعيينه كتوقيع افتراضي: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## استخدام التوقيعات في مربع نص رسالة البريد الإلكتروني، انقر على أيقونة التوقيع لاختيار التوقيع المطلوب: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/ar/email-manager/usage/template.md b/docs/docs/ar/email-manager/usage/template.md index f33a7193aee..e737bb3d700 100644 --- a/docs/docs/ar/email-manager/usage/template.md +++ b/docs/docs/ar/email-manager/usage/template.md @@ -11,15 +11,15 @@ pkg: "@nocobase/plugin-email-manager" ## إعدادات القوالب انتقل إلى مركز إدارة البريد الإلكتروني وانقر على زر الإعدادات: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) انتقل إلى لوحة القوالب: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) يمكنك إدارة القوالب من هنا: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## استخدام القوالب في مربع نص البريد الإلكتروني، انقر على أيقونة القالب لاختيار القالب المطلوب: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/ar/flow-engine/learning-roadmap.md b/docs/docs/ar/flow-engine/learning-roadmap.md index 34a2a177d70..d62cf833bbd 100644 --- a/docs/docs/ar/flow-engine/learning-roadmap.md +++ b/docs/docs/ar/flow-engine/learning-roadmap.md @@ -4,4 +4,4 @@ # خريطة طريق التعلم -![خريطة طريق التعلم](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![خريطة طريق التعلم](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/ar/interface-builder/blocks/data-blocks/list.md b/docs/docs/ar/interface-builder/blocks/data-blocks/list.md index d2e834f37a9..8495204f739 100644 --- a/docs/docs/ar/interface-builder/blocks/data-blocks/list.md +++ b/docs/docs/ar/interface-builder/blocks/data-blocks/list.md @@ -43,7 +43,7 @@ pkg: "@nocobase/plugin-block-list" > **ملاحظة**: يمكن عرض الحقول من المجموعات المرتبطة (حاليًا، يتم دعم العلاقات من نوع "واحد إلى واحد" فقط). -![20251023203611](https://docs.nocobase.com/20251023203611.png) +![20251023203611](https://static-docs.nocobase.com/20251023203611.png) لتهيئة حقول القائمة، راجع [حقل التفاصيل](/interface-builder/fields/generic/detail-form-item) diff --git a/docs/docs/ar/solution/ticket-system/design.md b/docs/docs/ar/solution/ticket-system/design.md index 81e6ca2112f..6ddf078aff5 100755 --- a/docs/docs/ar/solution/ticket-system/design.md +++ b/docs/docs/ar/solution/ticket-system/design.md @@ -31,7 +31,7 @@ - **الأفقي (الجدول الرئيسي)**: يغطي القدرات العامة لجميع أنواع الأعمال — رقم التذكرة، الحالة، المسؤول، اتفاقية مستوى الخدمة (SLA) وغيرها من الحقول الأساسية. - **الرأسي (جداول التوسعة)**: حقول متخصصة متعمقة في أعمال محددة — إصلاح المعدات يحتوي على الأرقام التسلسلية، والشكاوى تحتوي على خطط التعويض. -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **لماذا هذا التصميم؟** @@ -61,7 +61,7 @@ #### الفلسفة الثالثة: التدوير الذاتي للمعرفة -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) هذا يشكل حلقة مغلقة من **ترسيب المعرفة - تطبيق المعرفة**. @@ -71,7 +71,7 @@ ### 2.1 نظرة عامة على علاقات الكيانات -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 تفاصيل الجداول الأساسية @@ -296,18 +296,18 @@ **المسار الرئيسي (من اليسار إلى اليمين)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **المسارات الفرعية** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **آلة الحالة الكاملة** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 قواعد انتقال الحالات الرئيسية @@ -337,7 +337,7 @@ ### 4.2 منطق حساب SLA -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### عند إنشاء التذكرة @@ -466,7 +466,7 @@ ### 5.3 موظفو الذكاء الاصطناعي ودورة حياة التذكرة -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 أمثلة على استجابات الذكاء الاصطناعي @@ -526,12 +526,12 @@ ### 6.1 مصادر المعرفة -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 إجراء تحويل التذكرة إلى معرفة -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **أبعاد التقييم**: - **العمومية**: هل هذه مشكلة شائعة؟ @@ -576,19 +576,19 @@ #### WF-T01: إجراء إنشاء التذكرة -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: تحليل التذكرة بواسطة AI -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: ترجمة ومراجعة التعليقات -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: توليد المعرفة -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 المهام المجدولة @@ -605,11 +605,11 @@ ### 8.1 لوحة الإدارة الخلفية -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 بوابة العملاء -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 تصميم لوحة البيانات diff --git a/docs/docs/ar/users-permissions/acl/permissions.md b/docs/docs/ar/users-permissions/acl/permissions.md index b4675a9353b..2150e876d92 100644 --- a/docs/docs/ar/users-permissions/acl/permissions.md +++ b/docs/docs/ar/users-permissions/acl/permissions.md @@ -26,7 +26,7 @@ pkg: '@nocobase/plugin-acl' ## أذونات إجراءات المجموعة -![](https://static-docs.nocobase.com/6a6e0281391cecdea5b5218e6137c5d7.png) +![](https://static-docs.nocobase.com/6a6e0281391cecdea5b5218e6173c5d7.png) ![](https://static-docs.nocobase.com/9814140434ff9e1bf028a6c282a5a165.png) diff --git a/docs/docs/ar/users-permissions/acl/ui.md b/docs/docs/ar/users-permissions/acl/ui.md index 53bdb6f805a..990fc618b1e 100644 --- a/docs/docs/ar/users-permissions/acl/ui.md +++ b/docs/docs/ar/users-permissions/acl/ui.md @@ -50,7 +50,7 @@ pkg: '@nocobase/plugin-acl' عملية التكوين الكاملة هي كما يلي: -![](https://static-docs.nocobase.com/1dbe559a4579c2e052e194e50edc74a7.gif) +![](https://static-docs.nocobase.com/1dbe559a9579c2e052e194e50edc74a7.gif) - **إضافة**: يحدد ما إذا كان يمكن إضافة (إنشاء) الحقول. @@ -137,7 +137,7 @@ pkg: '@nocobase/plugin-acl' تكوين الأذونات الفردية لـ **مجموعة** الطلبات، حيث يمتلك حقل الارتباط "العميل" جميع أذونات الحقول: -![](https://static-docs.nocobase.com/3a3ab972f14a7b3a35361219d67fa40.png) +![](https://static-docs.nocobase.com/3a3ab9722f14a7b3a35361219d67fa40.png) تكوين الأذونات الفردية لـ **مجموعة** العملاء، حيث تمتلك الحقول في **مجموعة** العملاء أذونات العرض فقط: diff --git a/docs/docs/ar/workflow/advanced/variables.md b/docs/docs/ar/workflow/advanced/variables.md index 73a45d92263..4286bf7136c 100644 --- a/docs/docs/ar/workflow/advanced/variables.md +++ b/docs/docs/ar/workflow/advanced/variables.md @@ -17,7 +17,7 @@ لقد استخدمنا ميزة المتغيرات عدة مرات في [البدء السريع](../getting-started.md). على سبيل المثال، في عقدة العمليات الحسابية، يمكننا استخدام المتغيرات للإشارة إلى بيانات سياق المشغّل لإجراء العمليات الحسابية: -![عقدة العمليات الحسابية تستخدم الدوال والمتغيرات](https://static-docs.nocobase.com/837e4851a4c70a1923542caadef3431b.png) +![عقدة العمليات الحسابية تستخدم الدوال والمتغيرات](https://static-docs.nocobase.com/837e4851a4c70a1932542caadef3431b.png) في عقدة التحديث، استخدم بيانات سياق المشغّل كمتغير لشرط التصفية، وأشر إلى نتيجة عقدة العمليات الحسابية كمتغير لقيمة الحقل المراد تحديثه: diff --git a/docs/docs/ar/workflow/nodes/aggregate.md b/docs/docs/ar/workflow/nodes/aggregate.md index a1abe34c727..8813a348fbd 100644 --- a/docs/docs/ar/workflow/nodes/aggregate.md +++ b/docs/docs/ar/workflow/nodes/aggregate.md @@ -64,7 +64,7 @@ pkg: '@nocobase/plugin-workflow-aggregate' ثم، أضف عقدة استعلام تجميع وقم بتكوينها كما يلي: -![عقدة استعلام التجميع_مثال_إعدادات العقدة](https://static-docs.nocobase.com/542272e64b567373d1b37ddda78.png) +![عقدة استعلام التجميع_مثال_إعدادات العقدة](https://static-docs.nocobase.com/542272e638c6c0a567373d1b37ddda78.png) بهذه الطريقة، بعد تشغيل **سير العمل**، ستقوم عقدة استعلام التجميع بحساب عدد جميع المقالات في فئة المقال المضاف حديثًا وحفظه كنتيجة للعقدة. diff --git a/docs/docs/ar/workflow/nodes/manual.md b/docs/docs/ar/workflow/nodes/manual.md index 37f792b8f3e..db3156a2638 100644 --- a/docs/docs/ar/workflow/nodes/manual.md +++ b/docs/docs/ar/workflow/nodes/manual.md @@ -60,7 +60,7 @@ pkg: '@nocobase/plugin-workflow-manual' كتل بيانات العقدة متشابهة؛ يمكنك تحديد نتيجة البيانات من عقدة سابقة لعرضها كتفاصيل. على سبيل المثال، يمكن أن تكون نتيجة عقدة حساب سابقة بمثابة معلومات مرجعية سياقية لمهمة المسؤول "قيد الانتظار": -![عقدة يدوية_إعداد العقدة_إعداد الواجهة_كتلة البيانات_بيانات العقدة](https://static-docs.nocobase.com/a583e26e508e95b47e5ddff80d998c4.png) +![عقدة يدوية_إعداد العقدة_إعداد الواجهة_كتلة البيانات_بيانات العقدة](https://static-docs.nocobase.com/a583e26e508e954b47e5ddff80d998c4.png) :::info{title=ملاحظة} نظرًا لأن سير العمل يكون في حالة غير منفذة أثناء إعداد الواجهة، فلا يتم عرض أي بيانات محددة في كتل البيانات. لا يمكن رؤية البيانات ذات الصلة بمثيل سير عمل معين إلا في واجهة النافذة المنبثقة لمهام "قيد الانتظار" بعد تشغيل سير العمل وتنفيذه. diff --git a/docs/docs/ar/workflow/nodes/variable.md b/docs/docs/ar/workflow/nodes/variable.md index e5133b777bf..64cbef21866 100644 --- a/docs/docs/ar/workflow/nodes/variable.md +++ b/docs/docs/ar/workflow/nodes/variable.md @@ -16,7 +16,7 @@ pkg: '@nocobase/plugin-workflow-variable' في واجهة إعدادات سير العمل، انقر على زر الزائد ("+") في سير العمل لإضافة عقدة "متغير": -![إضافة عقدة متغير](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![إضافة عقدة متغير](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## إعداد العقدة @@ -41,7 +41,7 @@ pkg: '@nocobase/plugin-workflow-variable' في وضع التعريف، يعادل تعيين قيمة للمتغير إسناد قيمة أولية له. -![تعريف قيمة أولية](https://static-docs.nocobase.com/4ce2c65ad537343013758c6a4.png) +![تعريف قيمة أولية](https://static-docs.nocobase.com/4ce2c508986565ad537343013758c6a4.png) في وضع الإسناد، يعادل تعيين قيمة للمتغير تعديل قيمة المتغير الهدف المُعرّف إلى قيمة جديدة. وستحصل الاستخدامات اللاحقة على هذه القيمة الجديدة. diff --git a/docs/docs/ar/workflow/triggers/post-action.md b/docs/docs/ar/workflow/triggers/post-action.md index cdc99ead46a..38dc729108d 100644 --- a/docs/docs/ar/workflow/triggers/post-action.md +++ b/docs/docs/ar/workflow/triggers/post-action.md @@ -178,7 +178,7 @@ curl -X POST -H 'Authorization: Bearer ' -H 'X-Role: ' -d كما هو موضح في الشكل أدناه: -![ترتيب تنفيذ الإجراءات](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![ترتيب تنفيذ الإجراءات](https://static-docs.nocobase.com/20251219234806.png) ### الفرق عن حدث المجموعة diff --git a/docs/docs/ar/workflow/triggers/pre-action.md b/docs/docs/ar/workflow/triggers/pre-action.md index f03ee433b01..2fce4a34bcc 100644 --- a/docs/docs/ar/workflow/triggers/pre-action.md +++ b/docs/docs/ar/workflow/triggers/pre-action.md @@ -28,7 +28,7 @@ pkg: '@nocobase/plugin-workflow-request-interceptor' في مشغل سير عمل الاعتراض، أول ما يجب تهيئته هو المجموعة المطابقة للإجراء: -![تهيئة حدث الاعتراض_المجموعة](https://static-docs.nocobase.com/8f7122caca81959d334cf776f838d53d6.png) +![تهيئة حدث الاعتراض_المجموعة](https://static-docs.nocobase.com/8f7122caca8159d334cf776f838d53d6.png) ثم اختر وضع الاعتراض. يمكنك اختيار اعتراض زر الإجراء المرتبط بسير العمل هذا فقط، أو اعتراض جميع الإجراءات المحددة لهذه المجموعة (بغض النظر عن النموذج الذي تأتي منه، ودون الحاجة إلى ربط سير العمل المقابل): @@ -91,7 +91,7 @@ pkg: '@nocobase/plugin-workflow-request-interceptor' إذا تم تهيئة عقدة "إنهاء سير العمل" للخروج بحالة "نجاح"، فسيظل طلب الإجراء معترضًا عند تنفيذ هذه العقدة، ولكن رسالة الاستجابة المعادة ستُعرض بحالة "نجاح" (بدلاً من "خطأ"): -![رسالة استجابة بحالة نجاح](https://static-docs.nocobase.com/9559bbf5607144759451294b18c790e.png) +![رسالة استجابة بحالة نجاح](https://static-docs.nocobase.com/9559bbf56067144759451294b18c790e.png) ## مثال @@ -107,7 +107,7 @@ pkg: '@nocobase/plugin-workflow-request-interceptor' تُستخدم عقدة الشرط ضمن سير عمل التكرار لتحديد ما إذا كان مخزون كائن المنتج الحالي في التكرار كافيًا: -![مثال_الشرط في التكرار](https://static-docs.nocobase.com/4af9111293b0a04a4ce55e657c0833b.png) +![مثال_الشرط في التكرار](https://static-docs.nocobase.com/4af91112934b0a04a4ce55e657c0833b.png) التكوينات الأخرى هي نفسها المذكورة في الاستخدام الأساسي. عند تقديم الطلب أخيرًا، إذا كان مخزون أي منتج غير كافٍ، فسيتم اعتراض تقديم الطلب، وسيتم إرجاع رسالة تنبيه مطابقة. أثناء الاختبار، حاول تقديم طلب يتضمن عدة منتجات، حيث يكون مخزون أحد المنتجات غير كافٍ والآخر كافيًا. يمكنك رؤية رسالة الاستجابة المعادة: diff --git a/docs/docs/cs/auth-verification/auth-oidc/examples/google.md b/docs/docs/cs/auth-verification/auth-oidc/examples/google.md index e1f01ed77a9..412ffd24541 100644 --- a/docs/docs/cs/auth-verification/auth-oidc/examples/google.md +++ b/docs/docs/cs/auth-verification/auth-oidc/examples/google.md @@ -15,7 +15,7 @@ Přejděte do [Google Cloud Console](https://console.cloud.google.com/apis/crede Přejděte do konfiguračního rozhraní a vyplňte autorizovanou URL pro přesměrování. Tuto URL pro přesměrování získáte při přidávání autentikátoru v NocoBase; obvykle má formát `http(s)://host:port/api/oidc:redirect`. Podrobnosti naleznete v části [Uživatelská příručka - Konfigurace](../index.md#konfigurace). -![](https://static-docs.nocobase.com/24078bf52ec96616334894cb3d9d126.png) +![](https://static-docs.nocobase.com/24078bf52ec966a16334894cb3d9d126.png) ## Přidání nového autentikátoru v NocoBase diff --git a/docs/docs/cs/auth-verification/auth-saml/examples/google.md b/docs/docs/cs/auth-verification/auth-saml/examples/google.md index a2cb9de6da3..66ff28575bc 100644 --- a/docs/docs/cs/auth-verification/auth-saml/examples/google.md +++ b/docs/docs/cs/auth-verification/auth-saml/examples/google.md @@ -36,7 +36,7 @@ Vraťte se do konzole Google a na stránce **Podrobnosti o poskytovateli služeb ![](https://static-docs.nocobase.com/1536268bf8df4a5ebc72384317172191.png) -![](https://static-docs.nocobase.com/c7de1f8b84f1335de110e5a7c96255c4.png) +![](https://static-docs.nocobase.com/c7de1f8b84c1335de110e5a7c96255c4.png) V části **Mapování atributů** přidejte mapování pro odpovídající atributy. diff --git a/docs/docs/cs/auth-verification/auth-saml/index.md b/docs/docs/cs/auth-verification/auth-saml/index.md index 08ada0df3a3..76bc50bb491 100644 --- a/docs/docs/cs/auth-verification/auth-saml/index.md +++ b/docs/docs/cs/auth-verification/auth-saml/index.md @@ -58,4 +58,4 @@ Mapování uživatelských organizací a rolí v současné době není podporov Navštivte přihlašovací stránku a klikněte na tlačítko pod přihlašovacím formulářem pro zahájení přihlášení třetí stranou. -![](https://static-docs.nocobase.com/7496365c9d36a294948e6adeb5b24bc.png) \ No newline at end of file +![](https://static-docs.nocobase.com/74963865c9d36a294948e6adeb5b24bc.png) \ No newline at end of file diff --git a/docs/docs/cs/auth-verification/auth/authenticators.md b/docs/docs/cs/auth-verification/auth/authenticators.md index dbe5d34db70..e4acde14df0 100644 --- a/docs/docs/cs/auth-verification/auth/authenticators.md +++ b/docs/docs/cs/auth-verification/auth/authenticators.md @@ -15,7 +15,7 @@ Při instalaci pluginu pro uživatelskou autentizaci se automaticky inicializuje ## Aktivace autentizátorů -![](https://static-docs.nocobase.com/7f1bf8f8ca5de67ffc68eff0a65848f5.png) +![](https://static-docs.nocobase.com/7f1fb8f8ca5de67ffc68eff0a65848f5.png) Na přihlašovací stránce se zobrazí pouze aktivované typy autentizace. diff --git a/docs/docs/cs/auth-verification/auth/dev/index.md b/docs/docs/cs/auth-verification/auth/dev/index.md index 2dbf5934bad..fe3b0355d24 100644 --- a/docs/docs/cs/auth-verification/auth/dev/index.md +++ b/docs/docs/cs/auth-verification/auth/dev/index.md @@ -169,7 +169,7 @@ Pokud potřebujete přejít z přihlašovací stránky na registrační stránku ### Formulář pro správu administrace -![](https://static-docs.nocobase.com/f4b544b5b0f4afee5621ad4abf66b24f.png) +![](https://static-docs.nocobase.com/f4b544b5b0f5afee5621ad4abf66b24f.png) Nahoře je obecná konfigurace ověřovatele a dole je část formuláře pro vlastní konfiguraci, kterou lze registrovat. diff --git a/docs/docs/cs/data-sources/collection-expression/collection.md b/docs/docs/cs/data-sources/collection-expression/collection.md index 7cb482cfd1a..456565717ac 100644 --- a/docs/docs/cs/data-sources/collection-expression/collection.md +++ b/docs/docs/cs/data-sources/collection-expression/collection.md @@ -15,7 +15,7 @@ Než začnete v pracovním postupu používat uzly pro operace s dynamickými v Poté můžete nastavit blok tabulky a zadat několik záznamů vzorců do šablonové kolekce. Každý řádek v šablonové kolekci „Výraz“ lze chápat jako pravidlo výpočtu navržené pro konkrétní datový model v rámci kolekce. Můžete použít různá pole z datových modelů různých kolekcí jako proměnné a vytvářet jedinečné výrazy jako pravidla výpočtu. Kromě toho můžete podle potřeby využívat různé výpočetní enginy. -![Zadávání dat výrazů](https://static-docs.nocobase.com/761047f8daabacccbc6a24a73564093.png) +![Zadávání dat výrazů](https://static-docs.nocobase.com/761047f8daabacccbc6a924a73564093.png) :::info{title=Tip} Jakmile jsou vzorce vytvořeny, je potřeba je propojit s obchodními daty. Přímé spojování každého řádku obchodních dat s daty vzorců může být zdlouhavé, proto se běžně používá přístup, kdy se metadata kolekce, podobná klasifikační kolekci, použije k vytvoření vztahu mnoho-k-jednomu (nebo jedna-k-jednomu) s kolekcí vzorců. Následně jsou obchodní data spojena s klasifikovanými metadaty ve vztahu mnoho-k-jednomu. Tento přístup Vám umožňuje jednoduše specifikovat relevantní klasifikovaná metadata při vytváření obchodních dat, což usnadňuje nalezení a použití odpovídajících dat vzorců prostřednictvím vytvořené cesty propojení. @@ -25,4 +25,4 @@ Jakmile jsou vzorce vytvořeny, je potřeba je propojit s obchodními daty. Př Jako příklad si vezměte vytvoření pracovního postupu spouštěného událostí kolekce. Při vytvoření objednávky by měl spouštěč přednačíst související data produktů spolu s daty výrazů souvisejících s produkty: -![Událost kolekce_Konfigurace spouštěče](https://static-docs.nocobase.com/f75b10007afd5de068f3458d2e04.png) \ No newline at end of file +![Událost kolekce_Konfigurace spouštěče](https://static-docs.nocobase.com/f181f75b10007afd5de068f3458d2e04.png) \ No newline at end of file diff --git a/docs/docs/cs/data-sources/data-modeling/collection-fields/associations/m2o/index.md b/docs/docs/cs/data-sources/data-modeling/collection-fields/associations/m2o/index.md index f1be361da74..bd22bf6376f 100644 --- a/docs/docs/cs/data-sources/data-modeling/collection-fields/associations/m2o/index.md +++ b/docs/docs/cs/data-sources/data-modeling/collection-fields/associations/m2o/index.md @@ -13,7 +13,7 @@ ER diagram: Konfigurace pole: -![alt text](https://static-docs.nocobase.com/3b484ebb98d82f832f3dbf752bd84c9.png) +![alt text](https://static-docs.nocobase.com/3b4484ebb98d82f832f3dbf752bd84c9.png) ## Popis parametrů diff --git a/docs/docs/cs/data-sources/data-modeling/collection-fields/associations/o2m/index.md b/docs/docs/cs/data-sources/data-modeling/collection-fields/associations/o2m/index.md index 6684aef8786..f955fe4af3b 100644 --- a/docs/docs/cs/data-sources/data-modeling/collection-fields/associations/o2m/index.md +++ b/docs/docs/cs/data-sources/data-modeling/collection-fields/associations/o2m/index.md @@ -13,7 +13,7 @@ ER diagram: Konfigurace pole: -![alt text](https://static-docs.nocobase.com/a608ce5481172dad7e8ab760107ff4e.png) +![alt text](https://static-docs.nocobase.com/a608ce54821172dad7e8ab760107ff4e.png) ## Popis parametrů diff --git a/docs/docs/cs/data-sources/data-modeling/collection-fields/associations/o2o/index.md b/docs/docs/cs/data-sources/data-modeling/collection-fields/associations/o2o/index.md index 11eb910db06..9b012e07d08 100644 --- a/docs/docs/cs/data-sources/data-modeling/collection-fields/associations/o2o/index.md +++ b/docs/docs/cs/data-sources/data-modeling/collection-fields/associations/o2o/index.md @@ -21,7 +21,7 @@ ER Vztah Konfigurace pole -![alt text](https://static-docs.nocobase.com/7659e128936bbd7c9ff51bcff1d646dd.png) +![alt text](https://static-docs.nocobase.com/7665a87e094b4fb50c9426a108f87105.png) ## Vztah jeden k jednomu (Patří k) @@ -33,7 +33,7 @@ ER Vztah Konfigurace pole -![alt text](https://static-docs.nocobase.com/4f09eeb3c7717d61a34982da43c187c.png) +![alt text](https://static-docs.nocobase.com/4f09eeb3c7717d61a349842da43c187c.png) ## Popis parametrů diff --git a/docs/docs/cs/data-sources/field-encryption/index.md b/docs/docs/cs/data-sources/field-encryption/index.md index eb062dcdd74..8f2f9ba056e 100644 --- a/docs/docs/cs/data-sources/field-encryption/index.md +++ b/docs/docs/cs/data-sources/field-encryption/index.md @@ -29,7 +29,7 @@ Pokud je plugin povolen pro podaplikaci, klíč se ve výchozím nastavení ukl Používá se šifrování obálkou (Envelope Encryption). -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### Proces vytváření klíčů 1. Při prvním vytvoření šifrovaného pole systém automaticky vygeneruje 32bitový `aplikační klíč` a uloží jej do výchozího úložiště v kódování Base64. diff --git a/docs/docs/cs/email-manager/advanced/batch-send.md b/docs/docs/cs/email-manager/advanced/batch-send.md index b078e9bdfcf..152b6206a35 100644 --- a/docs/docs/cs/email-manager/advanced/batch-send.md +++ b/docs/docs/cs/email-manager/advanced/batch-send.md @@ -9,27 +9,27 @@ Tento dokument byl přeložen umělou inteligencí. V případě nepřesností s ## Přehled hromadného odesílání Můžete hromadně odesílat e-maily více lidem (každý příjemce obdrží samostatný e-mail). -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## Hromadné odesílání prostřednictvím tabulky E-maily můžete hromadně odesílat také prostřednictvím tabulky: 1. Přidejte do tabulky tlačítko pro odeslání e-mailu - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. Nakonfigurujte e-mailové pole v tabulce (slouží k získání e-mailových adres po výběru záznamů v tabulce). - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. Zaškrtněte data v tabulce pro odeslání e-mailů - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) Pokud potřebujete odeslat e-maily na všechny adresy v celé tabulce, můžete povolit funkci **Ve výchozím nastavení vybrat všechny záznamy v aktuální tabulce jako příjemce**: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) Po úpravě obsahu e-mailu klikněte na tlačítko pro hromadné odeslání: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## Sledování odesílání e-mailů Stav odesílání e-mailů můžete zobrazit a sledovat v Centru pro správu e-mailů: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/cs/email-manager/usage/signature.md b/docs/docs/cs/email-manager/usage/signature.md index a2f5917e479..10b7eadbd72 100644 --- a/docs/docs/cs/email-manager/usage/signature.md +++ b/docs/docs/cs/email-manager/usage/signature.md @@ -10,15 +10,15 @@ Tento dokument byl přeložen umělou inteligencí. V případě nepřesností s ## Nastavení podpisu Přejděte do Centra správy e-mailů a klikněte na tlačítko nastavení: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Přepněte se na panel podpisu: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) Zde můžete spravovat podpisy. Zaškrtnutím možnosti před podpisem jej nastavíte jako výchozí: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## Používání podpisů V textovém poli e-mailu klikněte na ikonu podpisu a vyberte požadovaný podpis: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/cs/email-manager/usage/template.md b/docs/docs/cs/email-manager/usage/template.md index add41323b28..4a9b551b634 100644 --- a/docs/docs/cs/email-manager/usage/template.md +++ b/docs/docs/cs/email-manager/usage/template.md @@ -10,15 +10,15 @@ Tento dokument byl přeložen umělou inteligencí. V případě nepřesností s ## Konfigurace šablon Přejděte do Centra správy e-mailů a klikněte na tlačítko nastavení: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Přepněte se na panel šablon: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) Zde můžete spravovat šablony: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## Používání šablon V poli pro text e-mailu klikněte na ikonu šablony a vyberte požadovanou šablonu: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/cs/flow-engine/learning-roadmap.md b/docs/docs/cs/flow-engine/learning-roadmap.md index 9a923eb4cc9..117ab58a713 100644 --- a/docs/docs/cs/flow-engine/learning-roadmap.md +++ b/docs/docs/cs/flow-engine/learning-roadmap.md @@ -5,4 +5,4 @@ Tento dokument byl přeložen umělou inteligencí. V případě nepřesností s # Mapa učení -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/cs/solution/ticket-system/design.md b/docs/docs/cs/solution/ticket-system/design.md index 90fe976e605..75c850db777 100755 --- a/docs/docs/cs/solution/ticket-system/design.md +++ b/docs/docs/cs/solution/ticket-system/design.md @@ -31,7 +31,7 @@ Vychází z konceptu "talentu typu T" — horizontální šířka + vertikální - **Horizontální (Hlavní tabulka)**: Pokrývá obecné schopnosti pro všechny typy agend — core pole jako číslo, stav, řešitel, SLA atd. - **Vertikální (Rozšiřující tabulky)**: Specifická pole pro konkrétní agendy — opravy zařízení mají sériová čísla, stížnosti mají plány kompenzací. -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **Proč tento návrh?** @@ -61,7 +61,7 @@ Nejde o "funkce AI", ale o "AI zaměstnance". Každá AI má jasnou roli, osobno #### Koncept 3: Sebecirkulace znalostí -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) Tím se vytváří uzavřená smyčka **akumulace znalostí – aplikace znalostí**. @@ -71,7 +71,7 @@ Tím se vytváří uzavřená smyčka **akumulace znalostí – aplikace znalost ### 2.1 Přehled vztahů entit -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 Detailní popis hlavních tabulek @@ -296,18 +296,18 @@ Toto je jádro systému, využívající design "široké tabulky", kde jsou vš **Hlavní proces (zleva doprava)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **Větvení procesu** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **Kompletní stavový automat** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 Klíčová pravidla přechodu stavů @@ -337,7 +337,7 @@ Toto je jádro systému, využívající design "široké tabulky", kde jsou vš ### 4.2 Logika výpočtu SLA -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### Při vytvoření tiketu @@ -466,7 +466,7 @@ Každý AI zaměstnanec má nakonfigurovány 4 konkrétní úkoly: ### 5.3 AI zaměstnanci a životní cyklus tiketu -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 Příklady odpovědí AI @@ -526,12 +526,12 @@ Audit kvality odpovědí, za který odpovídá Grace, blokuje následující pro ### 6.1 Zdroje znalostí -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 Proces převodu tiketu na znalost -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **Dimenze hodnocení**: - **Obecnost**: Jde o běžný problém? @@ -576,19 +576,19 @@ Když řešitel otevře detail tiketu, Max automaticky doporučí relevantní zn #### WF-T01: Proces vytvoření tiketu -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: AI analýza tiketu -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: Překlad a audit komentářů -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: Generování znalostí -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 Naplánované úlohy @@ -605,11 +605,11 @@ Když řešitel otevře detail tiketu, Max automaticky doporučí relevantní zn ### 8.1 Administrační rozhraní -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 Zákaznický portál -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 Návrh dashboardů diff --git a/docs/docs/cs/users-permissions/acl/permissions.md b/docs/docs/cs/users-permissions/acl/permissions.md index 8ac66dea69e..5811f7d86e9 100644 --- a/docs/docs/cs/users-permissions/acl/permissions.md +++ b/docs/docs/cs/users-permissions/acl/permissions.md @@ -25,7 +25,7 @@ Globální oprávnění k akcím platí univerzálně pro všechny **kolekce** a ## Oprávnění k akcím kolekce -![](https://static-docs.nocobase.com/6a6e028139cecdea5b5218e6173c5d7.png) +![](https://static-docs.nocobase.com/6a6e0281391cecdea5b5218e6173c5d7.png) ![](https://static-docs.nocobase.com/9814140434ff9e1bf028a6c282a5a165.png) diff --git a/docs/docs/cs/users-permissions/acl/role.md b/docs/docs/cs/users-permissions/acl/role.md index f6212171407..98a83c5ae56 100644 --- a/docs/docs/cs/users-permissions/acl/role.md +++ b/docs/docs/cs/users-permissions/acl/role.md @@ -19,7 +19,7 @@ Aplikace po úvodní instalaci obsahuje dvě předdefinované role: „Admin“ Identifikátor role (jedinečný systémový identifikátor) umožňuje přizpůsobení výchozích rolí, ale systémové výchozí role nelze smazat. -![](https://static-docs.nocobase.com/35f323b6db4f9f12f9bee4dea63302.png) +![](https://static-docs.nocobase.com/35f323b346db4f9f12f9bee4dea63302.png) ### Nastavení výchozí role diff --git a/docs/docs/cs/users-permissions/user.md b/docs/docs/cs/users-permissions/user.md index f3a69265022..8b96fa1d2b8 100644 --- a/docs/docs/cs/users-permissions/user.md +++ b/docs/docs/cs/users-permissions/user.md @@ -17,7 +17,7 @@ Tento plugin poskytuje rozhraní pro správu uživatelů v centru konfigurace. P Kromě toho můžete také přidat různé bloky kolekce Uživatelé pro správu uživatelů, například tabulkové bloky: -![](https://static-docs.nocobase.com/76b5a465f869541a9e8f18a4568a7c9.png) +![](https://static-docs.nocobase.com/76b5a4652f869541a9e8f18a4568a7c9.png) ## Přidání uživatele diff --git a/docs/docs/cs/workflow/nodes/aggregate.md b/docs/docs/cs/workflow/nodes/aggregate.md index 3d2ba16eeed..59d61b8151d 100644 --- a/docs/docs/cs/workflow/nodes/aggregate.md +++ b/docs/docs/cs/workflow/nodes/aggregate.md @@ -25,7 +25,7 @@ V rozhraní konfigurace pracovního postupu klikněte na tlačítko plus („+ ## Konfigurace uzlu -![Uzel Agregační dotaz_Konfigurace uzlu](https://static-docs.nocobase.com/57362f747b9992230567c6bb5e968fd2.png) +![Uzel Agregační dotaz_Konfigurace uzlu](https://static-docs.nocobase.com/57362f747b9992230567c6bb5e986fd2.png) ### Agregační funkce diff --git a/docs/docs/cs/workflow/nodes/create.md b/docs/docs/cs/workflow/nodes/create.md index d4b89ff220b..8808362bb53 100644 --- a/docs/docs/cs/workflow/nodes/create.md +++ b/docs/docs/cs/workflow/nodes/create.md @@ -41,6 +41,6 @@ Například, když je záznam v kolekci „Příspěvky“ vytvořen nebo aktual ![Uzel Vytvořit záznam_Příklad_Konfigurace pracovního postupu](https://static-docs.nocobase.com/dfd4820d49c145fa331883fc09c9161f.png) -![Uzel Vytvořit záznam_Příklad_Konfigurace uzlu](https://static-docs.nocobase.com/1a0972e66170be12a068da6503298868.png) +![Uzel Vytvořit záznam_Příklad_Konfigurace uzlu](https://static-docs.nocobase.com/1a0992e66170be12a068da6503298868.png) Po povolení pracovního postupu s touto konfigurací, když se změní záznam v kolekci „Příspěvky“, automaticky se vytvoří záznam „Verze příspěvků“, který zaznamená historii změn příspěvku. \ No newline at end of file diff --git a/docs/docs/cs/workflow/nodes/destroy.md b/docs/docs/cs/workflow/nodes/destroy.md index a28cd774329..bb8c8e7fd3d 100644 --- a/docs/docs/cs/workflow/nodes/destroy.md +++ b/docs/docs/cs/workflow/nodes/destroy.md @@ -17,7 +17,7 @@ V současné době uzel pro smazání dat nepodporuje mazání po jednotlivých V rozhraní konfigurace pracovního postupu klikněte na tlačítko plus („+“) v toku a přidejte uzel „Smazat data“: -![Vytvoření uzlu pro smazání dat](https://static-docs.nocobase.com/e1b6b8728251fcdbed6c7f50e5570da2.png) +![Vytvoření uzlu pro smazání dat](https://static-docs.nocobase.com/e1d6b8728251fcdbed6c7f50e5570da2.png) ## Konfigurace uzlu diff --git a/docs/docs/cs/workflow/nodes/manual.md b/docs/docs/cs/workflow/nodes/manual.md index 1041aaaf79b..b5a0e00e10b 100644 --- a/docs/docs/cs/workflow/nodes/manual.md +++ b/docs/docs/cs/workflow/nodes/manual.md @@ -31,7 +31,7 @@ Manuální uzel vyžaduje určení uživatele jako vykonavatele úkolu k vyříz Vyberte uživatele, nebo pomocí proměnné vyberte primární či cizí klíč uživatelských dat z kontextu. -![Manual Node_Configure_Assignee_Select Variable](https://static-docs.nocobase.com/22fbca3b8e21fda3a825abb4b257df909.png) +![Manual Node_Configure_Assignee_Select Variable](https://static-docs.nocobase.com/22fbca3b8e21fda3a831019037001445.png) :::info{title=Poznámka} V současné době možnost zodpovědné osoby pro manuální uzly nepodporuje zpracování více uživateli. Tato funkce bude přidána v budoucí verzi. @@ -59,7 +59,7 @@ Datové bloky mohou zobrazovat data spouštěče nebo výsledky zpracování lib Bloky dat uzlů jsou podobné; můžete vybrat datový výsledek z předchozího uzlu pro zobrazení jako podrobnosti. Například výsledek předchozího výpočetního uzlu může sloužit jako kontextová referenční informace pro úkol zodpovědné osoby. -![Manual Node_Node Configuration_Interface Configuration_Data Block_Node Data](https://static-docs.nocobase.com/a53e258a1a4f45db310a72c2d0a404c.png) +![Manual Node_Node Configuration_Interface Configuration_Data Block_Node Data](https://static-docs.nocobase.com/a583e26e508e954b47e5ddff80d998c4.png) :::info{title=Poznámka} Vzhledem k tomu, že **pracovní postup** není během konfigurace rozhraní ve spuštěném stavu, v datových blocích se nezobrazují žádná konkrétní data. Relevantní data pro konkrétní instanci **pracovního postupu** uvidíte pouze v rozhraní vyskakovacího okna úkolu k vyřízení poté, co byl **pracovní postup** spuštěn a proveden. @@ -103,11 +103,11 @@ Pro ruční zpracování je také třeba přidat na stránku seznam úkolů k vy Můžete vybrat „**Pracovní postup** k vyřízení“ z dostupných bloků na stránce a přidat tak blok seznamu úkolů k vyřízení: -![Manual Node_Add To-do Block](https://static-docs.nocobase.com/198b41754cd73b704267bf30fe5e647.png) +![Manual Node_Add To-do Block](https://static-docs.nocobase.com/198b417454cd73b704267bf30fe5e647.png) Příklad bloku seznamu úkolů k vyřízení: -![Manual Node_To-do List](https://static-docs.nocobase.com/cfefb033deebff6b3f6ef4408066e688.png) +![Manual Node_To-do List](https://static-docs.nocobase.com/cfefb0d2c6a91c5c9dfa550d6b220f34.png) ### Podrobnosti úkolu k vyřízení diff --git a/docs/docs/cs/workflow/nodes/parallel.md b/docs/docs/cs/workflow/nodes/parallel.md index 59269e0409e..74d38fbcf64 100644 --- a/docs/docs/cs/workflow/nodes/parallel.md +++ b/docs/docs/cs/workflow/nodes/parallel.md @@ -20,11 +20,11 @@ Jedná se o vestavěný plugin, který nevyžaduje instalaci. V rozhraní pro konfiguraci pracovního postupu klikněte na tlačítko plus („+“) v diagramu a přidejte uzel „Paralelní větev“: -![Přidat paralelní větev](https://static-docs.nocobase.com/9e0f3faa0b9335270647a3047759eac.png) +![Přidat paralelní větev](https://static-docs.nocobase.com/9e0f3faa0b9335270647a30477559eac.png) Po přidání uzlu paralelní větve do pracovního postupu se ve výchozím nastavení přidají dvě podvětvě. Můžete také přidat libovolný počet dalších větví kliknutím na tlačítko pro přidání větve. Do každé větve lze přidat libovolný počet uzlů. Nepotřebné větve lze odebrat kliknutím na tlačítko pro smazání na začátku větve. -![Správa paralelních větví](https://static-docs.nocobase.com/36088b8b7970c8a1771eb3ee9bc2a757.png) +![Správa paralelních větví](https://static-docs.nocobase.com/36088a8b7970c8a1771eb3ee9bc2a757.png) ## Konfigurace uzlu diff --git a/docs/docs/cs/workflow/nodes/response-message.md b/docs/docs/cs/workflow/nodes/response-message.md index 51f7df3a9c6..0ee9b960181 100644 --- a/docs/docs/cs/workflow/nodes/response-message.md +++ b/docs/docs/cs/workflow/nodes/response-message.md @@ -35,7 +35,7 @@ Když se pracovní postup provede k tomuto uzlu, šablona bude analyzována a vy Produkt „iPhone 14 pro“ není skladem ``` -![Obsah zprávy](https://static-docs.nocobase.com/06fa4b6b6ec499c853f0c39987f63a6a.png) +![Obsah zprávy](https://static-docs.nocobase.com/06bd4a6b6ec499c853f0c39987f63a6a.png) ## Konfigurace pracovního postupu diff --git a/docs/docs/cs/workflow/nodes/variable.md b/docs/docs/cs/workflow/nodes/variable.md index d48eec4600d..910aec1bb43 100644 --- a/docs/docs/cs/workflow/nodes/variable.md +++ b/docs/docs/cs/workflow/nodes/variable.md @@ -15,7 +15,7 @@ V pracovním postupu můžete deklarovat proměnné nebo přiřazovat hodnoty ji V rozhraní konfigurace pracovního postupu klikněte na tlačítko plus („+“) v pracovním postupu a přidejte uzel „Proměnná“: -![Přidat uzel proměnné](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![Přidat uzel proměnné](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## Konfigurace uzlu @@ -40,7 +40,7 @@ Hodnota proměnné může být libovolného typu. Může to být konstanta, nap V režimu deklarace je nastavení hodnoty proměnné ekvivalentní přiřazení počáteční hodnoty. -![Deklarovat počáteční hodnotu](https://static-docs.nocobase.com/4ce2c08271526ef3ee.png) +![Deklarovat počáteční hodnotu](https://static-docs.nocobase.com/4ce2c508986565ad537343013758c6a4.png) V režimu přiřazení je nastavení hodnoty proměnné ekvivalentní úpravě hodnoty deklarované cílové proměnné na novou hodnotu. Následné použití získá tuto novou hodnotu. @@ -50,7 +50,7 @@ V režimu přiřazení je nastavení hodnoty proměnné ekvivalentní úpravě h V následných uzlech po uzlu proměnné můžete použít hodnotu proměnné výběrem deklarované proměnné ze skupiny „Proměnné uzlu“. Například v uzlu dotazu použijte hodnotu proměnné jako podmínku dotazu: -![Použít hodnotu proměnné jako podmínku filtru dotazu](https://static-docs.nocobase.com/1ca91c295245999a1751499f14bc.png) +![Použít hodnotu proměnné jako podmínku filtru dotazu](https://static-docs.nocobase.com/1ca91c295254ff85999a1751499f14bc.png) ## Příklad diff --git a/docs/docs/cs/workflow/triggers/post-action.md b/docs/docs/cs/workflow/triggers/post-action.md index 3ef65f47d00..b2fc14f0dea 100644 --- a/docs/docs/cs/workflow/triggers/post-action.md +++ b/docs/docs/cs/workflow/triggers/post-action.md @@ -177,7 +177,7 @@ Pokud je událost nakonfigurována v globálním režimu, nemusíte používat p Jak je znázorněno na obrázku níže: -![Action Execution Order](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![Action Execution Order](https://static-docs.nocobase.com/20251219234806.png) ### Rozdíl oproti události kolekce diff --git a/docs/docs/cs/workflow/triggers/pre-action.md b/docs/docs/cs/workflow/triggers/pre-action.md index 861dc2a61a4..f3b4a767ba1 100644 --- a/docs/docs/cs/workflow/triggers/pre-action.md +++ b/docs/docs/cs/workflow/triggers/pre-action.md @@ -30,7 +30,7 @@ Při vytváření pracovního postupu zvolte typ „Událost před akcí“: Ve spouštěči zachycujícího pracovního postupu je nejprve nutné nakonfigurovat kolekci, ke které se akce vztahuje: -![Konfigurace zachycující události_Kolekce](https://static-docs.nocobase.com/8f7122caca59d334cf776f838d53d6.png) +![Konfigurace zachycující události_Kolekce](https://static-docs.nocobase.com/8f7122caca8159d334cf776f838d53d6.png) Poté vyberte režim zachycení. Můžete zvolit, zda se má zachytit pouze tlačítko akce vázané na tento pracovní postup, nebo zda se mají zachytit všechny vybrané akce pro tuto kolekci (bez ohledu na to, z jakého formuláře pocházejí a bez nutnosti vázat odpovídající pracovní postup): @@ -93,7 +93,7 @@ Tímto je konfigurace odpovídajícího pracovního postupu dokončena. Nyní m Pokud je uzel „Ukončit pracovní postup“ nakonfigurován tak, aby se ukončil se stavem „Úspěch“, a při provedení tohoto uzlu „Ukončit pracovní postup“ bude požadavek na akci stále zachycen, ale vrácená zpráva odpovědi se zobrazí se stavem „Úspěch“ (namísto „Chyba“): -![Zpráva odpovědi se stavem úspěch](https://static-docs.nocobase.com/9559bbf559451294b18c790e.png) +![Zpráva odpovědi se stavem úspěch](https://static-docs.nocobase.com/9559bbf56067144759451294b18c790e.png) ## Příklad @@ -113,7 +113,7 @@ Uzel podmínky v rámci cyklu se používá k určení, zda je zásoba aktuáln Ostatní konfigurace jsou stejné jako v základním použití. Když je objednávka nakonec odeslána, pokud má kterýkoli produkt nedostatečné zásoby, odeslání objednávky bude zachyceno a vrátí se odpovídající zpráva. Během testování zkuste odeslat objednávku s více produkty, kde jeden má nedostatečné zásoby a druhý dostatečné. Můžete vidět vrácenou zprávu odpovědi: -![Příklad_Zpráva odpovědi po odeslání](https://static-docs.nocobase.com/dd9e8108a237bda0241d399ac19270.png) +![Příklad_Zpráva odpovědi po odeslání](https://static-docs.nocobase.com/dd9e81084aa237bda0241d399ac19270.png) Jak můžete vidět, zpráva odpovědi neuvádí, že první produkt „iPhone 15 pro“ je vyprodán, ale pouze to, že druhý produkt „iPhone 14 pro“ má nedostatečné zásoby. Je to proto, že v cyklu má první produkt dostatečné zásoby, takže nebyl zachycen, zatímco druhý produkt měl nedostatečné zásoby, což zachytilo odeslání objednávky. diff --git a/docs/docs/de/ai-employees/knowledge-base/knowledge-base.md b/docs/docs/de/ai-employees/knowledge-base/knowledge-base.md index 9d9cd17232a..377f981b554 100644 --- a/docs/docs/de/ai-employees/knowledge-base/knowledge-base.md +++ b/docs/docs/de/ai-employees/knowledge-base/knowledge-base.md @@ -49,16 +49,16 @@ Die Wissensdatenbank unterstützt derzeit folgende Dokumenttypen: txt, pdf, doc, Eine Lokale Wissensdatenbank ist eine Wissensdatenbank, die direkt in NocoBase gespeichert wird. Sowohl die Dokumente als auch deren Vektordaten werden von NocoBase lokal gespeichert. -![20251023101620](https://static-docs.nocobase.com/2025101620.png) +![20251023101620](https://static-docs.nocobase.com/20251023101620.png) ### Nur-Lese-Wissensdatenbank Eine Nur-Lese-Wissensdatenbank ist eine schreibgeschützte Wissensdatenbank. Die Dokumente und Vektordaten werden extern verwaltet. In NocoBase wird lediglich eine Verbindung zur Vektordatenbank hergestellt (derzeit wird nur PGVector unterstützt). -![20251023101743](https://static-docs.nocobase.com/2025101743.png) +![20251023101743](https://static-docs.nocobase.com/20251023101743.png) ### Externe Wissensdatenbank Eine Externe Wissensdatenbank ist eine Wissensdatenbank, bei der Dokumente und Vektordaten extern verwaltet werden. Die Abfrage der Vektordatenbank erfordert eine Erweiterung durch Entwickler, wodurch auch Vektordatenbanken genutzt werden können, die derzeit von NocoBase nicht direkt unterstützt werden. -![20251023101949](https://static-docs.nocobase.com/2025101949.png) \ No newline at end of file +![20251023101949](https://static-docs.nocobase.com/20251023101949.png) \ No newline at end of file diff --git a/docs/docs/de/ai-employees/permission.md b/docs/docs/de/ai-employees/permission.md index d291a1177e3..5e6c568c506 100644 --- a/docs/docs/de/ai-employees/permission.md +++ b/docs/docs/de/ai-employees/permission.md @@ -73,7 +73,7 @@ Diese Tools werden typischerweise verwendet für: #### Beispiel 1: Overall Analytics (Allgemeine Geschäftsanalyse) -![05viz-configuration-2025-11-03-00-18-55](https://static-docs.nocobase.com/20251022013802.png) +![05viz-configuration-2025-11-03-00-18-55](https://static-docs.nocobase.com/05viz-configuration-2025-11-03-00-18-55.png) Im CRM-Demo ist `Overall Analytics` eine vorlagenbasierte Geschäftsanalyse-Engine: @@ -103,7 +103,7 @@ flowchart TD #### Beispiel 2: SQL Execution (Erweitertes Analysetool) -![05viz-configuration-2025-11-03-00-17-13](https://static-docs.nocobase.com/20251022013802.png) +![05viz-configuration-2025-11-03-00-17-13](https://static-docs.nocobase.com/05viz-configuration-2025-11-03-00-17-13.png) Im CRM-Demo ist `SQL Execution` ein flexibleres, aber streng kontrolliertes Tool: diff --git a/docs/docs/de/auth-verification/api-keys/index.md b/docs/docs/de/auth-verification/api-keys/index.md index b20d6f37725..9f0d1cc1939 100644 --- a/docs/docs/de/auth-verification/api-keys/index.md +++ b/docs/docs/de/auth-verification/api-keys/index.md @@ -18,7 +18,7 @@ http://localhost:13000/admin/settings/api-keys/configuration ### API-Schlüssel hinzufügen -![](https://static-docs.nocobase.com/46182fc0ad9a96fa5b14e97fcba12.png) +![](https://static-docs.nocobase.com/46141872fc0ad9a96fa5b14e97fcba12.png) **Wichtige Hinweise** diff --git a/docs/docs/de/auth-verification/auth-saml/examples/google.md b/docs/docs/de/auth-verification/auth-saml/examples/google.md index 793ed20bf37..fe51cd14859 100644 --- a/docs/docs/de/auth-verification/auth-saml/examples/google.md +++ b/docs/docs/de/auth-verification/auth-saml/examples/google.md @@ -12,7 +12,7 @@ Diese Dokumentation wurde automatisch von KI übersetzt. Nachdem Sie die App eingerichtet haben, kopieren Sie die **SSO-URL**, die **Entitäts-ID** und das **Zertifikat**. -![](https://static-docs.nocobase.com/aafd30a794730e85411c0c8f368637e0.png) +![](https://static-docs.nocobase.com/aafd20a794730e85411c0c8f368637e0.png) ## Neuen Authentifikator in NocoBase hinzufügen diff --git a/docs/docs/de/auth-verification/auth-saml/index.md b/docs/docs/de/auth-verification/auth-saml/index.md index 93534603255..995aec8b8d2 100644 --- a/docs/docs/de/auth-verification/auth-saml/index.md +++ b/docs/docs/de/auth-verification/auth-saml/index.md @@ -24,7 +24,7 @@ Gehen Sie zur Verwaltungsseite der Benutzerauthentifizierungs-Plugins. Hinzufügen - SAML -![](https://static-docs.nocobase.com/5076fe5806b7799be308bbaf7c4425d.png) +![](https://static-docs.nocobase.com/5076fe56086b7799be308bbaf7c4425d.png) ## Konfiguration diff --git a/docs/docs/de/auth-verification/auth/dev/index.md b/docs/docs/de/auth-verification/auth/dev/index.md index aa99100a262..7f8732e914f 100644 --- a/docs/docs/de/auth-verification/auth/dev/index.md +++ b/docs/docs/de/auth-verification/auth/dev/index.md @@ -168,7 +168,7 @@ Wenn Sie von der Anmeldeseite zur Registrierungsseite wechseln möchten, müssen ### Admin-Einstellungen-Formular -![](https://static-docs.nocobase.com/f4b544b5b0f4f4ee5621ad4abf66b24f.png) +![](https://static-docs.nocobase.com/f4b544b5b0f5afee5621ad4abf66b24f.png) Oben sehen Sie die allgemeine Authentifikator-Konfiguration, unten den Teil des benutzerdefinierten Konfigurationsformulars, der registriert werden kann. diff --git a/docs/docs/de/data-sources/collection-fdw/index.md b/docs/docs/de/data-sources/collection-fdw/index.md index a5e374084b9..5b051badc38 100644 --- a/docs/docs/de/data-sources/collection-fdw/index.md +++ b/docs/docs/de/data-sources/collection-fdw/index.md @@ -45,7 +45,7 @@ Anschließend installieren und aktivieren Sie das Plugin über den Plugin-Manage Wählen Sie im Dropdown-Menü unter „Sammlungsverwaltung > Sammlung erstellen“ die Option „Fremddaten verbinden“. -![Fremddaten verbinden](https://static-docs.nocobase.com/029d946d067d1c35a39755219d623c.png) +![Fremddaten verbinden](https://static-docs.nocobase.com/029d946a6d067d1c35a39755219d623c.png) Wählen Sie im Dropdown-Menü „Datenbankdienst“ einen bestehenden Datenbankdienst aus oder klicken Sie auf „Datenbankdienst erstellen“. diff --git a/docs/docs/de/data-sources/field-encryption/index.md b/docs/docs/de/data-sources/field-encryption/index.md index 26fc145a03b..98daccb025e 100644 --- a/docs/docs/de/data-sources/field-encryption/index.md +++ b/docs/docs/de/data-sources/field-encryption/index.md @@ -30,7 +30,7 @@ Wenn das Plugin von einer Sub-Anwendung aktiviert wird, wird der Schlüssel stan Es wird die Umschlag-Verschlüsselung (Envelope Encryption) verwendet. -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### Schlüsselgenerierungsprozess 1. Wenn ein verschlüsseltes Feld zum ersten Mal erstellt wird, generiert das System automatisch einen 32-Bit `Anwendungsschlüssel`, der Base64-kodiert im Standardspeicherverzeichnis abgelegt wird. diff --git a/docs/docs/de/email-manager/advanced/batch-send.md b/docs/docs/de/email-manager/advanced/batch-send.md index 8497c8f2f61..58ebc154a55 100644 --- a/docs/docs/de/email-manager/advanced/batch-send.md +++ b/docs/docs/de/email-manager/advanced/batch-send.md @@ -10,27 +10,27 @@ Diese Dokumentation wurde automatisch von KI übersetzt. ## Massenversand im Überblick Sie können E-Mails an mehrere Personen gleichzeitig versenden. Dabei erhält jeder Empfänger eine separate E-Mail. -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## Massenversand über eine Tabelle Sie können E-Mails auch im Massenversand über eine Tabelle versenden: 1. Fügen Sie der Tabelle einen „E-Mail senden“-Button hinzu. - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. Konfigurieren Sie das E-Mail-Feld in der Tabelle (dieses wird verwendet, um E-Mail-Adressen nach der Auswahl von Tabellenzeilen zu ermitteln). - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. Wählen Sie die Tabellendaten aus, um E-Mails zu versenden. - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) Wenn Sie E-Mails an alle Adressen der gesamten Tabelle senden möchten, können Sie die Funktion **Alle Datensätze der aktuellen Tabelle standardmäßig als Empfänger auswählen** aktivieren: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) Nachdem Sie den E-Mail-Inhalt bearbeitet haben, klicken Sie auf den „Massenversand“-Button, um die E-Mails zu versenden: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## E-Mail-Versand verfolgen Im E-Mail-Verwaltungszentrum können Sie den spezifischen E-Mail-Versandstatus einsehen und verfolgen: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/de/email-manager/usage/signature.md b/docs/docs/de/email-manager/usage/signature.md index ef139bc13aa..2f7aa72bd65 100644 --- a/docs/docs/de/email-manager/usage/signature.md +++ b/docs/docs/de/email-manager/usage/signature.md @@ -11,15 +11,15 @@ Diese Dokumentation wurde automatisch von KI übersetzt. ## Signatur konfigurieren Gehen Sie zum E-Mail-Verwaltungszentrum und klicken Sie auf die Schaltfläche Einstellungen: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Wechseln Sie zum Signatur-Panel: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) Hier können Sie Ihre Signaturen verwalten. Aktivieren Sie die Option vor einer Signatur, um sie als Standardsignatur festzulegen: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## Signaturen verwenden Klicken Sie im E-Mail-Textfeld auf das Signatur-Symbol, um die gewünschte Signatur auszuwählen: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/de/email-manager/usage/template.md b/docs/docs/de/email-manager/usage/template.md index 87739de9790..49d6c6adc5a 100644 --- a/docs/docs/de/email-manager/usage/template.md +++ b/docs/docs/de/email-manager/usage/template.md @@ -11,15 +11,15 @@ Diese Dokumentation wurde automatisch von KI übersetzt. ## Vorlagenkonfiguration Gehen Sie zum E-Mail-Verwaltungszentrum und klicken Sie auf die Schaltfläche "Einstellungen": -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Wechseln Sie zum Vorlagen-Panel: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) Hier können Sie Vorlagen verwalten: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## Vorlagen verwenden Klicken Sie im Textfeld der E-Mail auf das Vorlagen-Symbol, um die gewünschte Vorlage auszuwählen: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/de/flow-engine/learning-roadmap.md b/docs/docs/de/flow-engine/learning-roadmap.md index c4365d48a94..ae35ed05029 100644 --- a/docs/docs/de/flow-engine/learning-roadmap.md +++ b/docs/docs/de/flow-engine/learning-roadmap.md @@ -4,4 +4,4 @@ Diese Dokumentation wurde automatisch von KI übersetzt. # Lern-Roadmap -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/de/interface-builder/fields/specific/picker.md b/docs/docs/de/interface-builder/fields/specific/picker.md index 89fc1142e10..03bf01a59be 100644 --- a/docs/docs/de/interface-builder/fields/specific/picker.md +++ b/docs/docs/de/interface-builder/fields/specific/picker.md @@ -12,7 +12,7 @@ Der Daten-Selektor ermöglicht es Ihnen, in Form eines Popup-Tabellen-Selektors, Bereits ausgewählte Daten werden im Tabellen-Selektor nicht angezeigt. -![20251027203717](https://static-docs.nocobase.com/2025103717.gif) +![20251027203717](https://static-docs.nocobase.com/20251027203717.gif) Im Tabellen-Selektor können Sie die Ziel-Sammlung der Verknüpfung auch weiter verwalten (z. B. hinzufügen, löschen, importieren/exportieren). diff --git a/docs/docs/de/solution/ticket-system/design.md b/docs/docs/de/solution/ticket-system/design.md index 7f39d6b5b89..d84c87edd06 100755 --- a/docs/docs/de/solution/ticket-system/design.md +++ b/docs/docs/de/solution/ticket-system/design.md @@ -31,7 +31,7 @@ In Anlehnung an das Konzept der „T-förmigen Talente“ – horizontale Breite - **Horizontal (Haupttabelle)**: Deckt allgemeine Funktionen für alle Geschäftstypen ab – Ticketnummer, Status, Bearbeiter, SLA und andere Kernfelder. - **Vertikal (Erweiterungstabellen)**: Vertieft spezifische Geschäftsfelder – die Gerätereparatur enthält Seriennummern, Beschwerden enthalten Entschädigungspläne. -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **Warum dieses Design?** @@ -61,7 +61,7 @@ Nicht nur „KI-Funktionen“, sondern „KI-Mitarbeiter“. Jede KI hat eine kl #### Philosophie Drei: Wissens-Selbstkreislauf -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) Dies bildet einen geschlossenen Kreislauf aus **Wissensakkumulation und Wissensanwendung**. @@ -71,7 +71,7 @@ Dies bildet einen geschlossenen Kreislauf aus **Wissensakkumulation und Wissensa ### 2.1 Übersicht der Entitätsbeziehungen -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 Details der Kerntabellen @@ -296,18 +296,18 @@ Dies ist das Herzstück des Systems, das ein „Wide Table“-Design verwendet, **Hauptprozess (von links nach rechts)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **Nebenprozesse** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **Vollständige Zustandsmaschine** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 Wichtige Regeln für Statusübergänge @@ -337,7 +337,7 @@ Dies ist das Herzstück des Systems, das ein „Wide Table“-Design verwendet, ### 4.2 SLA-Berechnungslogik -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### Bei Ticket-Erstellung @@ -466,7 +466,7 @@ Jeder KI-Mitarbeiter verfügt über 4 spezifische Aufgaben: ### 5.3 KI-Mitarbeiter und Ticket-Lebenszyklus -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 Beispiele für KI-Antworten @@ -526,12 +526,12 @@ Die von Grace durchgeführte Qualitätsprüfung fängt folgende Probleme ab: ### 6.1 Wissensquellen -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 Prozess: Ticket zu Wissen -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **Bewertungsdimensionen**: - **Allgemeingültigkeit**: Ist dies ein häufiges Problem? @@ -576,19 +576,19 @@ Wenn ein Mitarbeiter die Ticket-Details öffnet, empfiehlt Max automatisch relev #### WF-T01: Ticket-Erstellungsprozess -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: Ticket-KI-Analyse -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: Kommentarübersetzung und -prüfung -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: Wissensgenerierung -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 Geplante Aufgaben @@ -605,11 +605,11 @@ Wenn ein Mitarbeiter die Ticket-Details öffnet, empfiehlt Max automatisch relev ### 8.1 Backend-Verwaltung -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 Kundenportal -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 Dashboard-Design diff --git a/docs/docs/de/users-permissions/acl/permissions.md b/docs/docs/de/users-permissions/acl/permissions.md index b0544cb756c..45e8448f69e 100644 --- a/docs/docs/de/users-permissions/acl/permissions.md +++ b/docs/docs/de/users-permissions/acl/permissions.md @@ -26,7 +26,7 @@ Globale Aktionsberechtigungen gelten universell für alle Sammlungen und sind na ## Sammlungs-Aktionsberechtigungen -![](https://static-docs.nocobase.com/6a6e02817391cecdea5b218e6173c5d7.png) +![](https://static-docs.nocobase.com/6a6e0281391cecdea5b5218e6173c5d7.png) ![](https://static-docs.nocobase.com/9814140434ff9e1bf028a6c282a5a165.png) diff --git a/docs/docs/de/users-permissions/acl/role.md b/docs/docs/de/users-permissions/acl/role.md index f3745f83936..062a02e63f8 100644 --- a/docs/docs/de/users-permissions/acl/role.md +++ b/docs/docs/de/users-permissions/acl/role.md @@ -26,7 +26,7 @@ Der Rollenbezeichner (eine systemweit eindeutige Kennung) ermöglicht es Ihnen, Die Standardrolle wird neuen Benutzern automatisch zugewiesen, wenn bei deren Erstellung keine spezifische Rolle festgelegt wurde. -![](https://static-docs.nocobase.com/f41b4f7ff55ca28715c486dc45bc1708.png) +![](https://static-docs.nocobase.com/f41bba7ff55ca28715c486dc45bc1708.png) ## Persönlicher Bereich diff --git a/docs/docs/de/users-permissions/acl/ui.md b/docs/docs/de/users-permissions/acl/ui.md index ef8523bb22a..9e1478db3a6 100644 --- a/docs/docs/de/users-permissions/acl/ui.md +++ b/docs/docs/de/users-permissions/acl/ui.md @@ -32,7 +32,7 @@ Der vollständige Konfigurationsprozess ist wie folgt: **Anzeigen**: Legt fest, ob bestimmte Felder auf Feldebene sichtbar sind. So können Sie steuern, welche Felder für bestimmte Rollen innerhalb der `Sammlung` „Bestellungen“ sichtbar sind. -![](https://static-docs.nocobase.com/30dea84d95039e6f7b180955a6cf.png) +![](https://static-docs.nocobase.com/30dea84d984d95039e6f7b180955a6cf.png) In der Benutzeroberfläche werden im Block der `Sammlung` „Bestellungen“ nur Felder mit konfigurierten Berechtigungen angezeigt. Systemfelder (Id, Erstellt am, Zuletzt aktualisiert am) behalten die Anzeigeberechtigung auch ohne spezifische Konfiguration bei. diff --git a/docs/docs/de/users-permissions/user.md b/docs/docs/de/users-permissions/user.md index 893dc40a8a7..ab32dbd3a50 100644 --- a/docs/docs/de/users-permissions/user.md +++ b/docs/docs/de/users-permissions/user.md @@ -22,7 +22,7 @@ Darüber hinaus können Sie auf der Seite verschiedene Blöcke der Benutzer-Samm ![](https://static-docs.nocobase.com/4f8ef9ffc1c17f275b62b462f6385b19.png) -![](https://static-docs.nocobase.com/437828173950bd7c21w40a6243ffe150.png) +![](https://static-docs.nocobase.com/437828173950bd7c21b40a6243ffe150.png) ## Benutzerprofil bearbeiten diff --git a/docs/docs/de/workflow/advanced/revisions.md b/docs/docs/de/workflow/advanced/revisions.md index 518a8a4d176..0727da44b44 100644 --- a/docs/docs/de/workflow/advanced/revisions.md +++ b/docs/docs/de/workflow/advanced/revisions.md @@ -8,11 +8,11 @@ Nachdem ein konfigurierter Workflow mindestens einmal ausgelöst wurde, müssen Auf der Konfigurationsseite des Workflows können Sie im Versionsmenü oben rechts die vorhandenen Workflow-Versionen einsehen: -![Workflow-Versionen anzeigen](https://static-docs.nocobase.com/ad93d2c0166b0e3e643fb148713a63f.png) +![Workflow-Versionen anzeigen](https://static-docs.nocobase.com/ad93d2c08166b0e3e643fb148713a63f.png) Im Menü "Weitere Aktionen" ("...") auf der rechten Seite können Sie die aktuell angezeigte Version in eine neue Version kopieren: -![Workflow als neue Version kopieren](https://static-docs.nocobase.com/280798e6caca2af004839a744256.png) +![Workflow als neue Version kopieren](https://static-docs.nocobase.com/2805798e6caca2af004893390a744256.png) Nachdem Sie eine neue Version kopiert haben, klicken Sie auf den Schalter "Aktivieren"/"Deaktivieren", um die entsprechende Version in den aktivierten Zustand zu versetzen. Danach wird die neue Workflow-Version wirksam. diff --git a/docs/docs/de/workflow/nodes/aggregate.md b/docs/docs/de/workflow/nodes/aggregate.md index c266b231342..78757f5bdc3 100644 --- a/docs/docs/de/workflow/nodes/aggregate.md +++ b/docs/docs/de/workflow/nodes/aggregate.md @@ -64,7 +64,7 @@ Als Nächstes erstellen Sie einen Workflow, der durch ein Sammlungsereignis ausg Danach fügen Sie einen Aggregatabfrage-Knoten hinzu und konfigurieren ihn wie folgt: -![Aggregatabfrage-Knoten_Beispiel_Knotenkonfiguration](https://static-docs.nocobase.com/542272e667373d1b37ddda78.png) +![Aggregatabfrage-Knoten_Beispiel_Knotenkonfiguration](https://static-docs.nocobase.com/542272e638c6c0a567373d1b37ddda78.png) Auf diese Weise zählt der Aggregatabfrage-Knoten nach dem Auslösen des Workflows die Anzahl aller Artikel in der Kategorie des neu hinzugefügten Artikels und speichert dies als Knotenergebnis. diff --git a/docs/docs/de/workflow/nodes/calculation.md b/docs/docs/de/workflow/nodes/calculation.md index b48635a3ee9..3a6a1526912 100644 --- a/docs/docs/de/workflow/nodes/calculation.md +++ b/docs/docs/de/workflow/nodes/calculation.md @@ -14,7 +14,7 @@ Klicken Sie in der Workflow-Konfigurationsoberfläche auf das Plus-Symbol ("+") ## Knotenkonfiguration -![计算节点_节点配置](https://static-docs.nocobase.com/6a155de3d8cd1881b2d9c33874.png) +![计算节点_节点配置](https://static-docs.nocobase.com/6a155de3f6a883d8cd1881b2d9c33874.png) ### Berechnungs-Engine diff --git a/docs/docs/de/workflow/nodes/destroy.md b/docs/docs/de/workflow/nodes/destroy.md index 3c9976e08b5..fd7813943d8 100644 --- a/docs/docs/de/workflow/nodes/destroy.md +++ b/docs/docs/de/workflow/nodes/destroy.md @@ -14,7 +14,7 @@ Der Löschen-Knoten unterstützt derzeit kein Löschen Zeile für Zeile; er füh In der Workflow-Konfigurationsoberfläche klicken Sie auf das Plus-Symbol („+“) im Workflow, um einen „Daten löschen“-Knoten hinzuzufügen: -![Löschen-Knoten erstellen](https://static-docs.nocobase.com/e13b6b728251fcdbed6c7f50e5570da2.png) +![Löschen-Knoten erstellen](https://static-docs.nocobase.com/e1d6b8728251fcdbed6c7f50e5570da2.png) ## Knotenkonfiguration diff --git a/docs/docs/de/workflow/nodes/json-query.md b/docs/docs/de/workflow/nodes/json-query.md index c9a00e36fe9..8362b731108 100644 --- a/docs/docs/de/workflow/nodes/json-query.md +++ b/docs/docs/de/workflow/nodes/json-query.md @@ -38,7 +38,7 @@ Der JSON Berechnung-Knoten unterstützt verschiedene Syntaxen durch unterschiedl Die Datenquelle kann das Ergebnis eines vorhergehenden Knotens oder ein Datenobjekt im Workflow-Kontext sein. Dabei handelt es sich typischerweise um ein Datenobjekt ohne integrierte Struktur, wie zum Beispiel das Ergebnis eines SQL-Knotens oder eines HTTP-Anfrage-Knotens. -![Datenquelle](https://static-docs.nocobase.com/f5a79e20693b3d30b3a994a576aa282d.png) +![Datenquelle](https://static-docs.nocobase.com/f5a97e20693b3d30b3a994a576aa282d.png) :::info{title=Hinweis} Normalerweise sind die Datenobjekte von Sammlung-bezogenen Knoten durch die Sammlung-Konfigurationsinformationen strukturiert und müssen in der Regel nicht durch den JSON Berechnung-Knoten geparst werden. diff --git a/docs/docs/de/workflow/nodes/manual.md b/docs/docs/de/workflow/nodes/manual.md index 59da3449622..e70a7cbbc0e 100644 --- a/docs/docs/de/workflow/nodes/manual.md +++ b/docs/docs/de/workflow/nodes/manual.md @@ -61,7 +61,7 @@ Datenblöcke können Trigger-Daten oder die Verarbeitungsergebnisse beliebiger K Knoten-Datenblöcke funktionieren ähnlich; Sie können das Datenergebnis eines vorgelagerten Knotens als Detailanzeige auswählen. Zum Beispiel kann das Ergebnis eines vorgelagerten Berechnungs-Knotens als Kontextreferenzinformation für die Aufgabe des Bearbeiters dienen: -![Manueller Knoten_Knotenkonfiguration_Oberflächenkonfiguration_Datenblock_Knotendaten](https://static-docs.nocobase.com/a583e26e508e9544b310a72c2d0a404c.png) +![Manueller Knoten_Knotenkonfiguration_Oberflächenkonfiguration_Datenblock_Knotendaten](https://static-docs.nocobase.com/a583e26e508e954b47e5ddff80d998c4.png) :::info{title=Hinweis} Da sich der Workflow während der Oberflächenkonfiguration in einem nicht ausgeführten Zustand befindet, werden in den Datenblöcken keine spezifischen Daten angezeigt. Die relevanten Daten für eine bestimmte Workflow-Instanz sind erst im Aufgaben-Pop-up sichtbar, nachdem der Workflow ausgelöst und ausgeführt wurde. @@ -85,7 +85,7 @@ Die Schaltflächen zum Absenden des Formulars können in drei Typen konfiguriert - Absenden und Workflow beenden - Nur Formularwerte speichern -![Manueller Knoten_Knotenkonfiguration_Oberflächenkonfiguration_Formularschaltflächen](https://static-docs.nocobase.com/6b45995b14112e85a821dff6f6e3189a.png) +![Manueller Knoten_Knotenkonfiguration_Oberflächenkonfiguration_Formularschaltflächen](https://static-docs.nocobase.com/6b45995b14152e85a821dff6f6e3189a.png) Die drei Schaltflächen repräsentieren drei Knotenstatus im Workflow-Prozess. Nach dem Absenden ändert sich der Status des Knotens entweder zu „Abgeschlossen“, „Abgelehnt“ oder verbleibt im Status „Wartend“. Ein Formular muss mindestens eine der ersten beiden Optionen konfiguriert haben, um den weiteren Verlauf des gesamten Workflows zu bestimmen. @@ -109,7 +109,7 @@ Sie können aus den Blöcken auf einer Seite „Workflow-Aufgaben“ auswählen, Beispiel für einen Aufgabenlisten-Block: -![Manueller Knoten_Aufgabenliste](https://static-docs.nocobase.com/cfefb0d6b220f34.png) +![Manueller Knoten_Aufgabenliste](https://static-docs.nocobase.com/cfefb0d2c6a91c5c9dfa550d6b220f34.png) ### Aufgabendetails diff --git a/docs/docs/de/workflow/nodes/request.md b/docs/docs/de/workflow/nodes/request.md index ff51163db5d..511b4cd7c4c 100644 --- a/docs/docs/de/workflow/nodes/request.md +++ b/docs/docs/de/workflow/nodes/request.md @@ -26,7 +26,7 @@ Klicken Sie in der Workflow-Konfigurationsoberfläche auf das Plus-Symbol („+ ## Knotenkonfiguration -![HTTP-Anfrage-Knoten_Knotenkonfiguration](https://static-docs.nocobase.com/2fcb29af3f6869c80f8fbd362a54e644.png) +![HTTP-Anfrage-Knoten_Knotenkonfiguration](https://static-docs.nocobase.com/2fcb29af66b892fa704add52e2974a52.png) ### Anfragemethode diff --git a/docs/docs/de/workflow/nodes/variable.md b/docs/docs/de/workflow/nodes/variable.md index b0f7cb8fd58..c2e312feded 100644 --- a/docs/docs/de/workflow/nodes/variable.md +++ b/docs/docs/de/workflow/nodes/variable.md @@ -17,7 +17,7 @@ Sie können in einem Workflow Variablen deklarieren oder bereits deklarierten Va Im Konfigurationsbereich des Workflows klicken Sie auf das Plus-Symbol („+“) im Workflow, um einen „Variablen“-Knoten hinzuzufügen: -![Variablen-Knoten hinzufügen](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![Variablen-Knoten hinzufügen](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## Knoten konfigurieren diff --git a/docs/docs/de/workflow/triggers/post-action.md b/docs/docs/de/workflow/triggers/post-action.md index 64928c6b194..c2727d75941 100644 --- a/docs/docs/de/workflow/triggers/post-action.md +++ b/docs/docs/de/workflow/triggers/post-action.md @@ -179,7 +179,7 @@ Wenn das Ereignis im globalen Modus konfiguriert ist, müssen Sie den URL-Parame Wie in der Abbildung unten gezeigt: -![Aktionsausführungsreihenfolge](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![Aktionsausführungsreihenfolge](https://static-docs.nocobase.com/20251219234806.png) ### Unterschied zum Sammlungsereignis diff --git a/docs/docs/de/workflow/triggers/pre-action.md b/docs/docs/de/workflow/triggers/pre-action.md index 9ef528cd0ca..1514bfa5eef 100644 --- a/docs/docs/de/workflow/triggers/pre-action.md +++ b/docs/docs/de/workflow/triggers/pre-action.md @@ -23,13 +23,13 @@ In Kombination mit dem Knoten „Antwortnachricht“ können Sie eine Antwortnac Wenn Sie einen Workflow erstellen, wählen Sie als Typ „Ereignis vor der Aktion“: -![Ereignis vor der Aktion erstellen](https://static-docs.nocobase.com/2add03f2bdb0a836baae5fe984fc4b6.png) +![Ereignis vor der Aktion erstellen](https://static-docs.nocobase.com/2add03f2bdb0a836baae5fe9864fc4b6.png) ### Sammlung auswählen Im Trigger eines Interzeptions-Workflows konfigurieren Sie zuerst die Sammlung, die der Aktion entspricht: -![Interzeptor-Ereignis-Konfiguration_Sammlung](https://static-docs.nocobase.com/8f7122caca159d334cf77f838d53d6.png) +![Interzeptor-Ereignis-Konfiguration_Sammlung](https://static-docs.nocobase.com/8f7122caca8159d334cf776f838d53d6.png) Wählen Sie anschließend den Interzeptionsmodus. Sie können festlegen, dass nur Aktionsschaltflächen abgefangen werden, die an diesen Workflow gebunden sind, oder dass alle ausgewählten Aktionen für diese Sammlung abgefangen werden (unabhängig davon, von welchem Formular sie stammen und ohne dass der entsprechende Workflow gebunden werden muss). @@ -92,7 +92,7 @@ Damit ist die Konfiguration des entsprechenden Workflows abgeschlossen. Sie kön Wenn der Knoten „Workflow beenden“ so konfiguriert ist, dass er mit dem Status „Erfolg“ beendet wird und dieser Knoten ausgeführt wird, wird die Anfrage für diese Aktion weiterhin abgefangen. Die zurückgegebene Antwortnachricht wird jedoch mit dem Status „Erfolg“ (und nicht „Fehler“) angezeigt: -![Antwortnachricht mit Erfolgsstatus](https://static-docs.nocobase.com/9559b3b6067144759451294b18c790e.png) +![Antwortnachricht mit Erfolgsstatus](https://static-docs.nocobase.com/9559bbf56067144759451294b18c790e.png) ## Beispiel diff --git a/docs/docs/es/ai-employees/knowledge-base/knowledge-base.md b/docs/docs/es/ai-employees/knowledge-base/knowledge-base.md index 8ea6f98e281..de30cf9e693 100644 --- a/docs/docs/es/ai-employees/knowledge-base/knowledge-base.md +++ b/docs/docs/es/ai-employees/knowledge-base/knowledge-base.md @@ -35,13 +35,13 @@ Después de crear la base de conocimiento, en la página de lista de bases de co ![20251023100458](https://static-docs.nocobase.com/20251023100458.png) -![20251023100527](https://static-docs.nocobase.com/2025100527.png) +![20251023100527](https://static-docs.nocobase.com/20251023100527.png) Haga clic en el botón `Upload` para subir documentos. Una vez que los documentos se hayan subido, la vectorización comenzará automáticamente. Espere a que el `Status` cambie de `Pending` a `Success`. Actualmente, la base de conocimiento admite los siguientes tipos de documentos: txt, pdf, doc, docx, ppt, pptx. Tenga en cuenta que los archivos PDF solo admiten texto plano. -![20251023100901](https://static-docs.nocobase.com/2025100901.png) +![20251023100901](https://static-docs.nocobase.com/20251023100901.png) ## Tipos de Base de Conocimiento @@ -49,16 +49,16 @@ Actualmente, la base de conocimiento admite los siguientes tipos de documentos: Una base de conocimiento Local es aquella que NocoBase almacena localmente. Tanto los documentos como sus datos vectoriales se guardan de forma local en NocoBase. -![20251023101620](https://static-docs.nocobase.com/2025101620.png) +![20251023101620](https://static-docs.nocobase.com/20251023101620.png) ### Base de Conocimiento de Solo Lectura Una base de conocimiento de Solo Lectura es aquella en la que los documentos y los datos vectoriales se mantienen externamente. En NocoBase, solo se crea una conexión a la base de datos vectorial (actualmente, solo se admite PGVector). -![20251023101743](https://static-docs.nocobase.com/2025101743.png) +![20251023101743](https://static-docs.nocobase.com/20251023101743.png) ### Base de Conocimiento Externa Una base de conocimiento Externa es aquella en la que los documentos y los datos vectoriales se mantienen fuera de NocoBase. Para la recuperación de la base de datos vectorial, los desarrolladores deben implementar extensiones, lo que permite utilizar bases de datos vectoriales que NocoBase no admite actualmente. -![20251023101949](https://static-docs.nocobase.com/2025101949.png) \ No newline at end of file +![20251023101949](https://static-docs.nocobase.com/20251023101949.png) \ No newline at end of file diff --git a/docs/docs/es/auth-verification/api-keys/index.md b/docs/docs/es/auth-verification/api-keys/index.md index b180a7039be..e76f1a723b4 100644 --- a/docs/docs/es/auth-verification/api-keys/index.md +++ b/docs/docs/es/auth-verification/api-keys/index.md @@ -18,7 +18,7 @@ http://localhost:13000/admin/settings/api-keys/configuration ### Añadir Clave API -![](https://static-docs.nocobase.com/461872fc0ad9a96fa5b14e97fcba12.png) +![](https://static-docs.nocobase.com/46141872fc0ad9a96fa5b14e97fcba12.png) **Notas** diff --git a/docs/docs/es/auth-verification/auth-oidc/examples/google.md b/docs/docs/es/auth-verification/auth-oidc/examples/google.md index 60e796e4861..951d9522b50 100644 --- a/docs/docs/es/auth-verification/auth-oidc/examples/google.md +++ b/docs/docs/es/auth-verification/auth-oidc/examples/google.md @@ -14,7 +14,7 @@ Esta documentación ha sido traducida automáticamente por IA. Acceda a la interfaz de configuración y complete la URL de redireccionamiento autorizada. La URL de redireccionamiento se puede obtener al añadir un autenticador en NocoBase; normalmente es `http(s)://host:port/api/oidc:redirect`. Consulte la sección [Manual de usuario - Configuración](../index.md#configuración). -![](https://static-docs.nocobase.com/24078bf52ec66a16334894cb3d9d126.png) +![](https://static-docs.nocobase.com/24078bf52ec966a16334894cb3d9d126.png) ## Añadir un nuevo autenticador en NocoBase diff --git a/docs/docs/es/data-sources/field-encryption/index.md b/docs/docs/es/data-sources/field-encryption/index.md index e0368aac131..6d1de239c01 100644 --- a/docs/docs/es/data-sources/field-encryption/index.md +++ b/docs/docs/es/data-sources/field-encryption/index.md @@ -30,7 +30,7 @@ Si el plugin se activa en una subaplicación, la clave se guarda por defecto en Utiliza el método de cifrado de sobre (Envelope Encryption). -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### Proceso de creación de claves 1. La primera vez que se crea un campo cifrado, el sistema genera automáticamente una `clave de aplicación` de 32 bits y la guarda codificada en Base64 en el directorio de almacenamiento predeterminado. diff --git a/docs/docs/es/email-manager/advanced/batch-send.md b/docs/docs/es/email-manager/advanced/batch-send.md index 49dcf961803..6ea64d16842 100644 --- a/docs/docs/es/email-manager/advanced/batch-send.md +++ b/docs/docs/es/email-manager/advanced/batch-send.md @@ -11,27 +11,27 @@ Esta documentación ha sido traducida automáticamente por IA. ## Descripción General del Envío Masivo Puede enviar correos electrónicos a varias personas de forma masiva (cada destinatario recibirá un correo electrónico individual). -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## Envío Masivo a Través de una Tabla También puede enviar correos electrónicos de forma masiva a través de una tabla: 1. Agregue un botón de envío de correo electrónico a la tabla - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. Configure el campo de correo electrónico en la tabla (se utiliza para analizar las direcciones de correo electrónico después de seleccionar filas de la tabla) - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. Seleccione los datos de la tabla para enviar correos electrónicos - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) Si necesita enviar correos electrónicos a todas las direcciones de la tabla completa, puede habilitar la función **Seleccionar todos los registros de la tabla actual como destinatarios por defecto**: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) Después de editar el contenido del correo electrónico, haga clic en el botón de envío masivo para enviar: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## Seguimiento de Envío de Correos Electrónicos Puede ver y rastrear el estado específico del envío de correos electrónicos en el Centro de Gestión de Correos Electrónicos: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/es/email-manager/usage/signature.md b/docs/docs/es/email-manager/usage/signature.md index 4e753020ca2..6f1f2267a5d 100644 --- a/docs/docs/es/email-manager/usage/signature.md +++ b/docs/docs/es/email-manager/usage/signature.md @@ -11,15 +11,15 @@ Esta documentación ha sido traducida automáticamente por IA. ## Configuración de Firmas Diríjase al Centro de Gestión de Correo Electrónico y haga clic en el botón de configuración: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Cambie al panel de firmas: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) Aquí puede gestionar sus firmas. Marque la opción junto a una firma para establecerla como predeterminada: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## Uso de Firmas En el cuerpo del correo electrónico, haga clic en el icono de firma para seleccionar la firma que desee: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/es/email-manager/usage/template.md b/docs/docs/es/email-manager/usage/template.md index 113f4649541..97586b90a3d 100644 --- a/docs/docs/es/email-manager/usage/template.md +++ b/docs/docs/es/email-manager/usage/template.md @@ -11,15 +11,15 @@ Esta documentación ha sido traducida automáticamente por IA. ## Configuración de Plantillas Vaya al Centro de Gestión de Email y haga clic en el botón de configuración: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Cambie al panel de plantillas: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) Aquí puede gestionar las plantillas: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## Uso de Plantillas En el campo del cuerpo del mensaje, haga clic en el icono de plantilla para seleccionar la plantilla deseada: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/es/flow-engine/learning-roadmap.md b/docs/docs/es/flow-engine/learning-roadmap.md index 91ef9b30338..3356b755fdb 100644 --- a/docs/docs/es/flow-engine/learning-roadmap.md +++ b/docs/docs/es/flow-engine/learning-roadmap.md @@ -4,4 +4,4 @@ Esta documentación ha sido traducida automáticamente por IA. # Hoja de ruta de aprendizaje -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/es/solution/ticket-system/design.md b/docs/docs/es/solution/ticket-system/design.md index 9d72860661f..4b0ebaf00bd 100755 --- a/docs/docs/es/solution/ticket-system/design.md +++ b/docs/docs/es/solution/ticket-system/design.md @@ -31,7 +31,7 @@ Inspirada en el concepto de "talento en forma de T": amplitud horizontal + profu - **Horizontal (Tabla principal)**: Capacidades universales que cubren todos los tipos de negocio: número de ticket, estado, encargado, SLA y otros campos principales. - **Vertical (Tablas de extensión)**: Campos especializados para tipos de negocio específicos: la reparación de equipos tiene números de serie, las reclamaciones tienen planes de compensación. -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **¿Por qué este diseño?** @@ -61,7 +61,7 @@ No se trata de "funciones de IA", sino de "empleados de IA". Cada IA tiene un ro #### Filosofía tres: Autocirculación del conocimiento -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) Esto forma un ciclo cerrado de **Acumulación de conocimiento - Aplicación de conocimiento**. @@ -71,7 +71,7 @@ Esto forma un ciclo cerrado de **Acumulación de conocimiento - Aplicación de c ### 2.1 Resumen de la relación entre entidades -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 Detalle de las tablas principales @@ -296,18 +296,18 @@ Este es el núcleo del sistema, utiliza un diseño de "tabla ancha" que incluye **Flujo principal (de izquierda a derecha)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **Flujos secundarios** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **Máquina de estados completa** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 Reglas clave de transición de estados @@ -337,7 +337,7 @@ Este es el núcleo del sistema, utiliza un diseño de "tabla ancha" que incluye ### 4.2 Lógica de cálculo de SLA -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### Al crear el ticket @@ -467,7 +467,7 @@ Cada empleado de IA tiene configuradas 4 tareas específicas: ### 5.3 Empleados de IA y ciclo de vida del ticket -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 Ejemplos de respuesta de IA @@ -527,12 +527,12 @@ La revisión de calidad de respuesta de Grace bloquea los siguientes problemas: ### 6.1 Fuentes de conocimiento -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 Flujo de ticket a conocimiento -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **Dimensiones de evaluación**: - **Generalidad**: ¿Es este un problema común? @@ -580,19 +580,19 @@ Cuando un agente abre los detalles del ticket, Max recomienda automáticamente c #### WF-T01: Flujo de creación de tickets -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: Análisis de IA del ticket -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: Traducción y revisión de comentarios -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: Generación de conocimiento -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 Tareas programadas @@ -609,11 +609,11 @@ Cuando un agente abre los detalles del ticket, Max recomienda automáticamente c ### 8.1 Administración del backend -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 Portal del cliente -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 Diseño del tablero diff --git a/docs/docs/es/users-permissions/acl/permissions.md b/docs/docs/es/users-permissions/acl/permissions.md index 255f19ed6f6..7325af3ce9a 100644 --- a/docs/docs/es/users-permissions/acl/permissions.md +++ b/docs/docs/es/users-permissions/acl/permissions.md @@ -26,7 +26,7 @@ Los permisos de operación global se aplican universalmente a todas las **colecc ## Permisos de Operación de Colección -![](https://static-docs.nocobase.com/6a6e0281391cecdea5b381e6173c5d7.png) +![](https://static-docs.nocobase.com/6a6e0281391cecdea5b5218e6173c5d7.png) ![](https://static-docs.nocobase.com/9814140434ff9e1bf028a6c282a5a165.png) diff --git a/docs/docs/es/users-permissions/acl/role.md b/docs/docs/es/users-permissions/acl/role.md index 865493599b0..e03a3dba9ab 100644 --- a/docs/docs/es/users-permissions/acl/role.md +++ b/docs/docs/es/users-permissions/acl/role.md @@ -34,6 +34,6 @@ El rol predeterminado es el que se asigna automáticamente a los nuevos usuarios Se puede asignar múltiples roles a un usuario. Cuando un usuario tiene varios roles, puede cambiarlos en el Centro Personal. -![](https://static-docs.nocobase.com/e31bba7ff55ca28715c486dc45bc1708.png) +![](https://static-docs.nocobase.com/e331d11ec1ca3b8b7e0472105b167819.png) El rol predeterminado al iniciar sesión se determina por el rol que se cambió más recientemente (este valor se actualiza con cada cambio) o, si no aplica, por el primer rol (el rol predeterminado del sistema). \ No newline at end of file diff --git a/docs/docs/es/users-permissions/acl/ui.md b/docs/docs/es/users-permissions/acl/ui.md index 92a0e4612ce..3d54aa4d7b1 100644 --- a/docs/docs/es/users-permissions/acl/ui.md +++ b/docs/docs/es/users-permissions/acl/ui.md @@ -36,7 +36,7 @@ El proceso de configuración completo es el siguiente: En la interfaz de usuario, solo se muestran los campos con permisos configurados dentro del bloque de la colección de Pedidos. Los campos del sistema (Id, CreatedAt, LastUpdatedAt) conservan los permisos de visualización incluso sin una configuración específica. -![](https://static-docs.nocobase.com/40cc51a717efe701147fd2e799e79dcc.png) +![](https://static-docs.nocobase.com/40cc49b517efe701147fd2e799e79dcc.png) - **Editar**: Controla si los campos pueden ser editados y guardados (actualizados). diff --git a/docs/docs/es/workflow/advanced/revisions.md b/docs/docs/es/workflow/advanced/revisions.md index 4a3a60c693c..73fced00b34 100644 --- a/docs/docs/es/workflow/advanced/revisions.md +++ b/docs/docs/es/workflow/advanced/revisions.md @@ -12,7 +12,7 @@ En la página de configuración del `flujo de trabajo`, puede ver las versiones En el menú de más acciones ("...") a su derecha, puede elegir copiar la versión que está viendo actualmente a una nueva versión: -![Copiar flujo de trabajo a una nueva versión](https://static-docs.nocobase.com/280798e6caca2af004893390a744256.png) +![Copiar flujo de trabajo a una nueva versión](https://static-docs.nocobase.com/2805798e6caca2af004893390a744256.png) Después de copiar a una nueva versión, haga clic en el interruptor "Activar"/"Desactivar" para cambiar la versión correspondiente al estado activado. Una vez hecho esto, la nueva versión del `flujo de trabajo` entrará en vigor. diff --git a/docs/docs/es/workflow/nodes/calculation.md b/docs/docs/es/workflow/nodes/calculation.md index 6fbc5639b8d..4a4ca63a53e 100644 --- a/docs/docs/es/workflow/nodes/calculation.md +++ b/docs/docs/es/workflow/nodes/calculation.md @@ -10,7 +10,7 @@ El nodo de Cálculo le permite evaluar una expresión. El resultado de esta eval En la interfaz de configuración del flujo de trabajo, haga clic en el botón de signo más ("+") dentro del flujo para añadir un nodo de "Cálculo": -![Nodo de Cálculo_Añadir](https://static-docs.nocobase.com/58a45540d26945251cd143eb4b16579.png) +![Nodo de Cálculo_Añadir](https://static-docs.nocobase.com/58a455540d26945251cd143eb4b16579.png) ## Configuración del nodo diff --git a/docs/docs/es/workflow/nodes/destroy.md b/docs/docs/es/workflow/nodes/destroy.md index 2d3982f6d16..4208e3994a0 100644 --- a/docs/docs/es/workflow/nodes/destroy.md +++ b/docs/docs/es/workflow/nodes/destroy.md @@ -34,6 +34,6 @@ Similar a las condiciones de filtro para una consulta de **colección** regular, Por ejemplo, para limpiar periódicamente los datos de pedidos históricos cancelados e inválidos, puede utilizar el nodo de eliminación para lograrlo: -![Nodo de eliminación_Ejemplo_Configuración del nodo](https://static-docs.nocobase.com/b94b95077a17252f8523c3f13ce5f320.png) +![Nodo de eliminación_Ejemplo_Configuración del nodo](https://static-docs.nocobase.com/b94b75077a17252f8523c3f13ce5f320.png) El **flujo de trabajo** se activará periódicamente y ejecutará la eliminación de todos los datos de pedidos históricos cancelados e inválidos. \ No newline at end of file diff --git a/docs/docs/es/workflow/nodes/manual.md b/docs/docs/es/workflow/nodes/manual.md index 7baa13023e3..fd4c563c75d 100644 --- a/docs/docs/es/workflow/nodes/manual.md +++ b/docs/docs/es/workflow/nodes/manual.md @@ -104,11 +104,11 @@ Para el procesamiento manual, también necesita añadir una lista de tareas pend Puede seleccionar "Tareas pendientes del **flujo de trabajo**" de los bloques de una página para añadir un bloque de lista de tareas pendientes: -![Nodo manual_Añadir bloque de tareas pendientes](https://static-docs.nocobase.com/198b41754cd73b704267bf30fe5e647.png) +![Nodo manual_Añadir bloque de tareas pendientes](https://static-docs.nocobase.com/198b417454cd73b704267bf30fe5e647.png) Ejemplo de bloque de lista de tareas pendientes: -![Nodo manual_Lista de tareas pendientes](https://static-docs.nocobase.com/cfefb05d6b220f34.png) +![Nodo manual_Lista de tareas pendientes](https://static-docs.nocobase.com/cfefb0d2c6a91c5c9dfa550d6b220f34.png) ### Detalles de la tarea pendiente diff --git a/docs/docs/es/workflow/nodes/variable.md b/docs/docs/es/workflow/nodes/variable.md index 8bb72d5a909..e12aa29af5d 100644 --- a/docs/docs/es/workflow/nodes/variable.md +++ b/docs/docs/es/workflow/nodes/variable.md @@ -17,7 +17,7 @@ Puede declarar variables en un flujo de trabajo o asignar valores a variables ya En la interfaz de configuración del flujo de trabajo, haga clic en el botón de más ("+") en el flujo para añadir un nodo de "Variable": -![Add Variable Node](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![Add Variable Node](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## Configurar nodo diff --git a/docs/docs/es/workflow/triggers/collection.md b/docs/docs/es/workflow/triggers/collection.md index 68c4742d043..5c22260a57e 100644 --- a/docs/docs/es/workflow/triggers/collection.md +++ b/docs/docs/es/workflow/triggers/collection.md @@ -21,7 +21,7 @@ Existen varios tipos de cambios en una colección: Puede elegir el momento del disparo según las diferentes necesidades de su negocio. Cuando el cambio seleccionado incluye la actualización de la colección, también puede especificar los campos que han cambiado. La condición del disparador se cumple solo cuando los campos seleccionados cambian. Si no selecciona ningún campo, significa que cualquier cambio en cualquier campo puede activar el disparador. -![Collection Event_Select Changed Fields](https://static-docs.nocobase.com/874a175f01298b3c00267b2b4674611.png) +![Collection Event_Select Changed Fields](https://static-docs.nocobase.com/874a1475f01298b3c00267b2b4674611.png) Más específicamente, puede configurar reglas de condición para cada campo de la fila de datos que activa el evento. El disparador solo se activará cuando los campos cumplan las condiciones correspondientes. @@ -89,4 +89,4 @@ La configuración de los nodos se explicará en detalle en la documentación par Habilite este flujo de trabajo y pruébelo creando un nuevo pedido a través de la interfaz. Después de realizar un pedido para el "iPhone 14 Pro", el inventario del producto correspondiente se reducirá a 9. Si se realiza un pedido para el "iPhone 13 Pro", el pedido será eliminado debido a la falta de inventario. -![Collection Event_Example_New Order Execution Result](https://static-docs.nocobase.com/24cbe31e24ba4804b3bd48d99415c54f.png) \ No newline at end of file +![Collection Event_Example_New Order Execution Result](https://static-docs.nocobase.com/24cbe51e24ba4804b3bd48d99415c54f.png) \ No newline at end of file diff --git a/docs/docs/es/workflow/triggers/post-action.md b/docs/docs/es/workflow/triggers/post-action.md index 8c6dc0c72d1..7dead0b68d1 100644 --- a/docs/docs/es/workflow/triggers/post-action.md +++ b/docs/docs/es/workflow/triggers/post-action.md @@ -178,7 +178,7 @@ Si el evento está configurado en modo global, no necesita usar el parámetro UR Como se muestra en la siguiente figura: -![Orden de ejecución de la acción](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![Orden de ejecución de la acción](https://static-docs.nocobase.com/20251219234806.png) ### Diferencia con el Evento de Colección diff --git a/docs/docs/es/workflow/triggers/pre-action.md b/docs/docs/es/workflow/triggers/pre-action.md index 406902bf501..14427d9b30e 100644 --- a/docs/docs/es/workflow/triggers/pre-action.md +++ b/docs/docs/es/workflow/triggers/pre-action.md @@ -28,7 +28,7 @@ Al crear un flujo de trabajo, seleccione el tipo "Evento Antes de la Acción": En el disparador de un flujo de trabajo de intercepción, lo primero que debe configurar es la colección correspondiente a la operación: -![Configuración del Evento de Intercepción_Colección](https://static-docs.nocobase.com/8f7122caca8159d334cf776b838d53d6.png) +![Configuración del Evento de Intercepción_Colección](https://static-docs.nocobase.com/8f7122caca8159d334cf776f838d53d6.png) Luego, seleccione el modo de intercepción. Puede optar por interceptar solo el botón de acción vinculado a este flujo de trabajo, o por interceptar todas las operaciones seleccionadas para esta colección (sin importar de qué formulario provengan y sin necesidad de vincular el flujo de trabajo correspondiente): @@ -91,7 +91,7 @@ Con esto, la configuración del flujo de trabajo correspondiente está completa. Si el nodo "Finalizar flujo de trabajo" está configurado para salir con un estado de "Éxito", la solicitud de la operación seguirá siendo interceptada cuando se ejecute este nodo, pero el mensaje de respuesta devuelto se mostrará con un estado de "Éxito" (en lugar de "Error"): -![Mensaje de Respuesta de Estado de Éxito](https://static-docs.nocobase.com/9559bbf65067144759451294b18c790e.png) +![Mensaje de Respuesta de Estado de Éxito](https://static-docs.nocobase.com/9559bbf56067144759451294b18c790e.png) ## Ejemplo @@ -99,7 +99,7 @@ Combinando las instrucciones básicas anteriores, tomemos como ejemplo un escena Los demás pasos son los mismos que en las instrucciones. Sin embargo, dado que un pedido involucra varios productos, además de agregar una relación de muchos a muchos "Pedido" <-- M:1 -- "Detalle de Pedido" -- 1:M --> "Producto" en el modelado de datos, también necesita agregar un nodo de "Bucle" en el flujo de trabajo "Evento Antes de la Acción" para verificar iterativamente si el inventario de cada producto es suficiente: -![Ejemplo_Flujo de Trabajo de Verificación en Bucle](https://static-docs.nocobase.com/8307de47d629595ab6cf00f8aa898e3.png) +![Ejemplo_Flujo de Trabajo de Verificación en Bucle](https://static-docs.nocobase.com/8307de47d5629595ab6cf00f8aa898e3.png) El objeto para el bucle se selecciona como el array "Detalle de Pedido" de los datos del pedido enviado: diff --git a/docs/docs/fr/ai-employees/permission.md b/docs/docs/fr/ai-employees/permission.md index f389f7bf0a7..c61b7dcfd9a 100644 --- a/docs/docs/fr/ai-employees/permission.md +++ b/docs/docs/fr/ai-employees/permission.md @@ -67,7 +67,7 @@ Ces outils sont généralement utilisés pour : #### Exemple 1 : Overall Analytics (Analyse métier générale) -![05viz-configuration-2025-11-03-00-18-55](https://static-docs.nocobase.com/20251022013802.png) +![05viz-configuration-2025-11-03-00-18-55](https://static-docs.nocobase.com/05viz-configuration-2025-11-03-00-18-55.png) Dans la démo CRM, `Overall Analytics` est un moteur d'analyse métier basé sur des modèles : @@ -97,7 +97,7 @@ flowchart TD #### Exemple 2 : SQL Execution (Outil d'analyse avancée) -![05viz-configuration-2025-11-03-00-17-13](https://static-docs.nocobase.com/20251022013942.png) +![05viz-configuration-2025-11-03-00-17-13](https://static-docs.nocobase.com/05viz-configuration-2025-11-03-00-17-13.png) Dans la démo CRM, `SQL Execution` est un outil plus flexible mais qui nécessite un contrôle strict : diff --git a/docs/docs/fr/auth-verification/api-keys/index.md b/docs/docs/fr/auth-verification/api-keys/index.md index 6d0286dcb3d..0fea0319074 100644 --- a/docs/docs/fr/auth-verification/api-keys/index.md +++ b/docs/docs/fr/auth-verification/api-keys/index.md @@ -18,7 +18,7 @@ http://localhost:13000/admin/settings/api-keys/configuration ### Ajouter une clé API -![](https://static-docs.nocobase.com/46182fc0ad9a6fa5b14e97fcba12.png) +![](https://static-docs.nocobase.com/46141872fc0ad9a96fa5b14e97fcba12.png) **Remarques** diff --git a/docs/docs/fr/auth-verification/auth-saml/index.md b/docs/docs/fr/auth-verification/auth-saml/index.md index c55daf9c8cd..8070bcdb6cd 100644 --- a/docs/docs/fr/auth-verification/auth-saml/index.md +++ b/docs/docs/fr/auth-verification/auth-saml/index.md @@ -28,7 +28,7 @@ Ajouter - SAML ## Configuration -![](https://static-docs.nocobase.com/976b66e588973c322d81dcddd22c6146.png) +![](https://static-docs.nocobase.com/976b66e589973c322d81dcddd22c6146.png) - SSO URL - Fournie par l'IdP, utilisée pour l'authentification unique (SSO). - Certificat public - Fourni par l'IdP. diff --git a/docs/docs/fr/auth-verification/auth/authenticators.md b/docs/docs/fr/auth-verification/auth/authenticators.md index 4cc1bcccc40..a9c47de2150 100644 --- a/docs/docs/fr/auth-verification/auth/authenticators.md +++ b/docs/docs/fr/auth-verification/auth/authenticators.md @@ -17,7 +17,7 @@ Lors de l'installation du plugin d'authentification utilisateur, le système ini ## Activer les authentificateurs -![](https://static-docs.nocobase.com/7f1bf8f8ca5de67ffc68eff0a65848f5.png) +![](https://static-docs.nocobase.com/7f1fb8f8ca5de67ffc68eff0a65848f5.png) Seuls les types d'authentification activés s'afficheront sur la page de connexion. diff --git a/docs/docs/fr/auth-verification/auth/dev/index.md b/docs/docs/fr/auth-verification/auth/dev/index.md index 8b2e9c1fc33..1c01a7ff9e5 100644 --- a/docs/docs/fr/auth-verification/auth/dev/index.md +++ b/docs/docs/fr/auth-verification/auth/dev/index.md @@ -168,7 +168,7 @@ Si vous devez passer de la page de connexion à la page d'inscription, vous devr ### Formulaire de paramètres d'administration -![](https://static-docs.nocobase.com/f4b544b5b0f4afee5621ad4abf66b24f.png) +![](https://static-docs.nocobase.com/f4b544b5b0f5afee5621ad4abf66b24f.png) La partie supérieure présente la configuration générique de l'authentificateur, tandis que la partie inférieure correspond à la section du formulaire de configuration personnalisée qui peut être enregistrée. diff --git a/docs/docs/fr/auth-verification/auth/password.md b/docs/docs/fr/auth-verification/auth/password.md index 54ee85f64ba..cd9e96374cf 100644 --- a/docs/docs/fr/auth-verification/auth/password.md +++ b/docs/docs/fr/auth-verification/auth/password.md @@ -24,7 +24,7 @@ Page d'inscription Si l'inscription n'est pas autorisée, le lien de création de compte n'apparaît pas sur la page de connexion. -![](https://static-docs.nocobase.com/8d5e3b6df9991bfc1c2e095a3745121.png) +![](https://static-docs.nocobase.com/8d5e3b6df9991bfc1c2e095a93745121.png) Lorsque l'inscription n'est pas autorisée, la page d'inscription est inaccessible. diff --git a/docs/docs/fr/data-sources/collection-fdw/index.md b/docs/docs/fr/data-sources/collection-fdw/index.md index 8c5216031ff..5da01ff9b70 100644 --- a/docs/docs/fr/data-sources/collection-fdw/index.md +++ b/docs/docs/fr/data-sources/collection-fdw/index.md @@ -57,7 +57,7 @@ Créer un service de base de données Après avoir sélectionné le service de base de données, dans le menu déroulant « Collection distante », choisissez la collection à laquelle vous souhaitez vous connecter. -![Sélectionner la collection à laquelle vous souhaitez vous connecter](https://static-docs.nocobase.com/e915b2b4fc01b3808053cc8dc4.png) +![Sélectionner la collection à laquelle vous souhaitez vous connecter](https://static-docs.nocobase.com/e91fd6152b52b4fc01b3808053cc8dc4.png) Configurer les informations des champs diff --git a/docs/docs/fr/data-sources/data-modeling/collection-fields/associations/o2o/index.md b/docs/docs/fr/data-sources/data-modeling/collection-fields/associations/o2o/index.md index 59959d3ac79..fa6e37acdff 100644 --- a/docs/docs/fr/data-sources/data-modeling/collection-fields/associations/o2o/index.md +++ b/docs/docs/fr/data-sources/data-modeling/collection-fields/associations/o2o/index.md @@ -28,7 +28,7 @@ Cela indique qu'un profil personnel appartient à un employé spécifique. Relation ER -![](https://static-docs.nocobase.com/31e7cc3e630220cf1e98573ca24ac72d.png) +![](https://static-docs.nocobase.com/31e7cc3e630220cf1e98753ca24ac72d.png) Configuration du champ diff --git a/docs/docs/fr/data-sources/field-encryption/index.md b/docs/docs/fr/data-sources/field-encryption/index.md index 51800e2be36..57ebc9b4ac7 100644 --- a/docs/docs/fr/data-sources/field-encryption/index.md +++ b/docs/docs/fr/data-sources/field-encryption/index.md @@ -30,7 +30,7 @@ Si le plugin est activé pour une sous-application, la clé est par défaut enre Utilise le chiffrement par enveloppe. -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### Processus de création des clés 1. Lors de la première création d'un champ chiffré, une `clé d'application` de 32 bits est automatiquement générée par le système et stockée dans le répertoire de stockage par défaut, encodée en Base64. diff --git a/docs/docs/fr/email-manager/advanced/batch-send.md b/docs/docs/fr/email-manager/advanced/batch-send.md index a41ffd944da..690c26c31e1 100644 --- a/docs/docs/fr/email-manager/advanced/batch-send.md +++ b/docs/docs/fr/email-manager/advanced/batch-send.md @@ -12,27 +12,27 @@ Cette documentation a été traduite automatiquement par IA. ## Aperçu de l'envoi en masse Vous pouvez envoyer des e-mails à plusieurs personnes en masse (chaque destinataire recevra un e-mail distinct). -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## Envoi en masse via un tableau Vous pouvez également envoyer des e-mails en masse via un tableau : 1. Ajoutez un bouton d'envoi d'e-mail au tableau - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. Configurez le champ d'e-mail dans le tableau (utilisé pour analyser les adresses e-mail après avoir sélectionné des lignes du tableau) - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. Cochez les données du tableau pour envoyer des e-mails - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) Si vous devez envoyer des e-mails à toutes les adresses du tableau, vous pouvez activer la fonction **Sélectionner tous les enregistrements du tableau actuel comme destinataires par défaut** : -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) Après avoir modifié le contenu de l'e-mail, cliquez sur le bouton d'envoi en masse pour l'envoyer : -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## Suivi des envois d'e-mails Vous pouvez consulter et suivre le statut spécifique des envois d'e-mails dans le Centre de gestion des e-mails : -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/fr/email-manager/usage/signature.md b/docs/docs/fr/email-manager/usage/signature.md index 2cc50ef64d4..af473c749c4 100644 --- a/docs/docs/fr/email-manager/usage/signature.md +++ b/docs/docs/fr/email-manager/usage/signature.md @@ -11,15 +11,15 @@ Cette documentation a été traduite automatiquement par IA. ## Configuration de la signature Rendez-vous dans le Centre de gestion des e-mails et cliquez sur le bouton des paramètres : -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Basculez vers le panneau des signatures : -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) Vous pouvez gérer les signatures ici. Cochez l'option située devant une signature pour la définir comme signature par défaut : -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## Utilisation des signatures Dans le corps du message, cliquez sur l'icône de signature pour sélectionner la signature souhaitée : -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/fr/email-manager/usage/template.md b/docs/docs/fr/email-manager/usage/template.md index 0e3df64f236..fecd51f46e4 100644 --- a/docs/docs/fr/email-manager/usage/template.md +++ b/docs/docs/fr/email-manager/usage/template.md @@ -11,15 +11,15 @@ Cette documentation a été traduite automatiquement par IA. ## Configuration des modèles Accédez au Centre de gestion des e-mails et cliquez sur le bouton Paramètres : -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Passez au panneau des modèles : -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) C'est ici que vous pouvez gérer les modèles : -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## Utilisation des modèles Dans le champ du corps de l'e-mail, cliquez sur l'icône du modèle pour sélectionner le modèle souhaité : -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/fr/flow-engine/learning-roadmap.md b/docs/docs/fr/flow-engine/learning-roadmap.md index 549b659fd37..07f7a054c3f 100644 --- a/docs/docs/fr/flow-engine/learning-roadmap.md +++ b/docs/docs/fr/flow-engine/learning-roadmap.md @@ -4,4 +4,4 @@ Cette documentation a été traduite automatiquement par IA. # Parcours d'apprentissage -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/fr/solution/ticket-system/design.md b/docs/docs/fr/solution/ticket-system/design.md index 722fb38b860..00506bf78ba 100755 --- a/docs/docs/fr/solution/ticket-system/design.md +++ b/docs/docs/fr/solution/ticket-system/design.md @@ -31,7 +31,7 @@ Inspirée du concept de "profil en T" (compétences en T) — largeur horizontal - **Horizontal (Table principale)** : Couvre les capacités universelles communes à tous les types d'activités — numéro de ticket, statut, responsable, SLA et autres champs de base. - **Vertical (Tables d'extension)** : Champs spécialisés pour des activités spécifiques — la réparation d'équipement possède des numéros de série, les réclamations ont des plans de compensation. -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **Pourquoi cette conception ?** @@ -61,7 +61,7 @@ Il ne s'agit pas de "fonctionnalités IA", mais d'"employés IA". Chaque IA a un #### Philosophie 3 : Auto-circulation des connaissances -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) Cela forme une boucle fermée **Accumulation de connaissances - Application de connaissances**. @@ -71,7 +71,7 @@ Cela forme une boucle fermée **Accumulation de connaissances - Application de c ### 2.1 Aperçu des relations entre entités -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 Détails des tables de base @@ -296,18 +296,18 @@ C'est le cœur du système, utilisant une conception de "table large" incluant t **Flux principal (de gauche à droite)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **Flux secondaires** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **Machine à états complète** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 Règles clés de transition de statut @@ -337,7 +337,7 @@ C'est le cœur du système, utilisant une conception de "table large" incluant t ### 4.2 Logique de calcul du SLA -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### À la création du ticket @@ -466,7 +466,7 @@ Chaque employé IA est configuré avec 4 tâches spécifiques : ### 5.3 Employés IA et cycle de vie du ticket -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 Exemples de réponses IA @@ -526,12 +526,12 @@ La révision de qualité des réponses gérée par Grace intercepte les problèm ### 6.1 Sources de connaissances -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 Flux de conversion Ticket vers Connaissance -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **Dimensions d'évaluation** : - **Généralité** : Est-ce un problème courant ? @@ -576,19 +576,19 @@ Lorsque l'agent ouvre les détails d'un ticket, Max recommande automatiquement l #### WF-T01 : Flux de création de ticket -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01 : Analyse IA du ticket -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04 : Traduction et révision des commentaires -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03 : Génération de connaissances -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 Tâches planifiées @@ -605,11 +605,11 @@ Lorsque l'agent ouvre les détails d'un ticket, Max recommande automatiquement l ### 8.1 Interface d'administration (Back-end) -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 Portail client (Front-end) -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 Conception des tableaux de bord diff --git a/docs/docs/fr/users-permissions/acl/permissions.md b/docs/docs/fr/users-permissions/acl/permissions.md index f5731642191..ec209e012b1 100644 --- a/docs/docs/fr/users-permissions/acl/permissions.md +++ b/docs/docs/fr/users-permissions/acl/permissions.md @@ -26,7 +26,7 @@ Les permissions d'action globales s'appliquent universellement à toutes les **c ## Permissions d'action des collections -![](https://static-docs.nocobase.com/6a0281391cecdea6173c5d7.png) +![](https://static-docs.nocobase.com/6a6e0281391cecdea5b5218e6173c5d7.png) ![](https://static-docs.nocobase.com/9814140434ff9e1bf028a6c282a5a165.png) diff --git a/docs/docs/fr/users-permissions/acl/role.md b/docs/docs/fr/users-permissions/acl/role.md index e6c4640888e..3150fe927ca 100644 --- a/docs/docs/fr/users-permissions/acl/role.md +++ b/docs/docs/fr/users-permissions/acl/role.md @@ -21,7 +21,7 @@ Lors de l'installation initiale, l'application intègre deux rôles prédéfinis L'identifiant de rôle, qui est un identifiant système unique, vous permet de personnaliser les rôles par défaut. Cependant, les rôles prédéfinis du système ne peuvent pas être supprimés. -![](https://static-docs.nocobase.com/35f323b6db4f9f12f9bee4dea63302.png) +![](https://static-docs.nocobase.com/35f323b346db4f9f12f9bee4dea63302.png) ### Définir le rôle par défaut diff --git a/docs/docs/fr/users-permissions/acl/ui.md b/docs/docs/fr/users-permissions/acl/ui.md index 1b97562ba33..e2f41ddff81 100644 --- a/docs/docs/fr/users-permissions/acl/ui.md +++ b/docs/docs/fr/users-permissions/acl/ui.md @@ -20,7 +20,7 @@ Configuration des permissions globales : Configuration des permissions individuelles pour la collection « Commandes » : -![](https://static-docs.nocobase.com/a88caba1cad47001c1601bf402a4a2c1.png) +![](https://static-docs.nocobase.com/a88caba1cad47001c1610bf402a4a2c1.png) Dans l'interface utilisateur, tous les blocs de la collection « Commandes » ne sont pas affichés. diff --git a/docs/docs/fr/users-permissions/departments/role.md b/docs/docs/fr/users-permissions/departments/role.md index ccd11a2f4e9..ffa6bf67c6e 100644 --- a/docs/docs/fr/users-permissions/departments/role.md +++ b/docs/docs/fr/users-permissions/departments/role.md @@ -19,7 +19,7 @@ La première consiste à sélectionner un rôle dans le champ des rôles du form La seconde consiste à ajouter des départements au rôle correspondant dans la gestion des rôles. -![](https://static-docs.nocobase.com/f2a2bec937cf2f179ce868a92b98416d.png) +![](https://static-docs.nocobase.com/f2a7bec937cf2f179ce868a92b98416d.png) Les départements qui possèdent déjà ce rôle ne sont pas sélectionnables. diff --git a/docs/docs/fr/users-permissions/user.md b/docs/docs/fr/users-permissions/user.md index 7fbf4844969..ed75e38038b 100644 --- a/docs/docs/fr/users-permissions/user.md +++ b/docs/docs/fr/users-permissions/user.md @@ -20,7 +20,7 @@ De plus, vous pouvez également utiliser la collection d'utilisateurs sur une pa ## Ajouter un utilisateur -![](https://static-docs.nocobase.com/4f8ef9ff1c17f275b62b462f6385b19.png) +![](https://static-docs.nocobase.com/4f8ef9ffc1c17f275b62b462f6385b19.png) ![](https://static-docs.nocobase.com/437828173950bd7c21b40a6243ffe150.png) @@ -32,7 +32,7 @@ De plus, vous pouvez également utiliser la collection d'utilisateurs sur une pa ## Modifier le mot de passe utilisateur -![](https://static-docs.nocobase.com/26c4c4cebda3d144dc4e9b728c2ede5.png) +![](https://static-docs.nocobase.com/26c24c4cebda3d144dc4e9b728c2ede5.png) ![](https://static-docs.nocobase.com/23a2b2223cb5b387b3699cc6143302e8.png) diff --git a/docs/docs/fr/workflow/advanced/revisions.md b/docs/docs/fr/workflow/advanced/revisions.md index f442dad8fbd..0c56a2c7b4b 100644 --- a/docs/docs/fr/workflow/advanced/revisions.md +++ b/docs/docs/fr/workflow/advanced/revisions.md @@ -12,7 +12,7 @@ Sur la page de configuration du flux de travail, vous pouvez consulter les versi Dans le menu « Plus d'actions » (« ... ») situé à sa droite, vous pouvez choisir de copier la version actuellement affichée vers une nouvelle version : -![Copier le flux de travail vers une nouvelle version](https://static-docs.nocobase.com/2805798e6caca2af00483390a744256.png) +![Copier le flux de travail vers une nouvelle version](https://static-docs.nocobase.com/2805798e6caca2af004893390a744256.png) Après avoir copié vers une nouvelle version, cliquez sur le bouton bascule « Activer »/« Désactiver » pour passer la version correspondante à l'état activé. La nouvelle version du flux de travail prendra alors effet. diff --git a/docs/docs/fr/workflow/nodes/aggregate.md b/docs/docs/fr/workflow/nodes/aggregate.md index 1e1e07ce450..666b749a1fb 100644 --- a/docs/docs/fr/workflow/nodes/aggregate.md +++ b/docs/docs/fr/workflow/nodes/aggregate.md @@ -64,7 +64,7 @@ Ensuite, créez un flux de travail déclenché par un événement de collection. Ajoutez ensuite un nœud de requête d'agrégation et configurez-le comme suit : -![Nœud de requête d'agrégation_Exemple_Configuration du nœud](https://static-docs.nocobase.com/542272e63f6c0a567373d1b37ddda78.png) +![Nœud de requête d'agrégation_Exemple_Configuration du nœud](https://static-docs.nocobase.com/542272e638c6c0a567373d1b37ddda78.png) Ainsi, une fois le flux de travail déclenché, le nœud de requête d'agrégation comptera le nombre total d'articles dans la catégorie de l'article nouvellement ajouté et enregistrera ce résultat comme sortie du nœud. diff --git a/docs/docs/fr/workflow/nodes/calculation.md b/docs/docs/fr/workflow/nodes/calculation.md index 56fdf05d4b2..d20a1e0bcd3 100644 --- a/docs/docs/fr/workflow/nodes/calculation.md +++ b/docs/docs/fr/workflow/nodes/calculation.md @@ -10,11 +10,11 @@ Le nœud de **calcul** permet d'évaluer une expression. Le résultat de ce calc Dans l'interface de configuration du **flux de travail**, cliquez sur le bouton plus (« + ») dans le flux pour ajouter un nœud de « Calcul » : -![计算节点_添加](https://static-docs.nocobase.com/58a465540d26945251cd143eb4b16579.png) +![计算节点_添加](https://static-docs.nocobase.com/58a455540d26945251cd143eb4b16579.png) ## Configuration du nœud -![计算节点_节点配置](https://static-docs.nocobase.com/6a155de3f6a83d8cd1881b2d9c33874.png) +![计算节点_节点配置](https://static-docs.nocobase.com/6a155de3f6a883d8cd1881b2d9c33874.png) ### Moteur de calcul diff --git a/docs/docs/fr/workflow/nodes/create.md b/docs/docs/fr/workflow/nodes/create.md index 4b650b85d59..2c8e0d28ec3 100644 --- a/docs/docs/fr/workflow/nodes/create.md +++ b/docs/docs/fr/workflow/nodes/create.md @@ -38,7 +38,7 @@ Si les champs du nouvel enregistrement incluent des champs d'association et que Par exemple, lorsqu'un enregistrement dans la collection « Articles » est créé ou mis à jour, un enregistrement « Versions d'articles » doit être automatiquement créé pour enregistrer l'historique des modifications de l'article. Vous pouvez utiliser le nœud « Créer un enregistrement » pour y parvenir : -![Nœud Créer un enregistrement_Exemple_Configuration du flux de travail](https://static-docs.nocobase.com/dfb4820d49c145fa331883fc09c9161f.png) +![Nœud Créer un enregistrement_Exemple_Configuration du flux de travail](https://static-docs.nocobase.com/dfd4820d49c145fa331883fc09c9161f.png) ![Nœud Créer un enregistrement_Exemple_Configuration du nœud](https://static-docs.nocobase.com/1a0992e66170be12a068da6503298868.png) diff --git a/docs/docs/fr/workflow/nodes/loop.md b/docs/docs/fr/workflow/nodes/loop.md index 40d6d91c707..591c3e6a374 100644 --- a/docs/docs/fr/workflow/nodes/loop.md +++ b/docs/docs/fr/workflow/nodes/loop.md @@ -109,7 +109,7 @@ Par exemple, lorsqu'une commande est passée, vous devez vérifier le stock de c ![Nœud de boucle_Exemple_Configuration du nœud de calcul](https://static-docs.nocobase.com/8df3604c71f8f8705b1552d3ebfe3b50.png) - ![Nœud de boucle_Exemple_Configuration du nœud de mise à jour du stock](https://static-docs.nocobase.com/2d84baa9b3b1bd85fccda9eec992378.png) + ![Nœud de boucle_Exemple_Configuration du nœud de mise à jour du stock](https://static-docs.nocobase.com/2d84baa9b3b01bd85fccda9eec992378.png) 6. Sinon, dans la branche « Non », créez un nœud « Mettre à jour l'enregistrement » pour mettre à jour le statut du détail de commande en « invalide » : diff --git a/docs/docs/fr/workflow/nodes/manual.md b/docs/docs/fr/workflow/nodes/manual.md index 68a319b5566..21739598d98 100644 --- a/docs/docs/fr/workflow/nodes/manual.md +++ b/docs/docs/fr/workflow/nodes/manual.md @@ -60,7 +60,7 @@ Les blocs de données peuvent afficher les données de déclenchement ou les ré Les blocs de données de nœud fonctionnent de manière similaire : vous pouvez sélectionner le résultat des données d'un nœud en amont pour l'afficher en détail. Par exemple, le résultat d'un nœud de calcul en amont peut servir d'information de référence contextuelle pour la tâche à faire du responsable. -![Nœud manuel_Configuration du nœud_Configuration de l'interface_Bloc de données_Données du nœud](https://static-docs.nocobase.com/a583e26e508e954f45db310a72c2d0a404c.png) +![Nœud manuel_Configuration du nœud_Configuration de l'interface_Bloc de données_Données du nœud](https://static-docs.nocobase.com/a583e26e508e954b47e5ddff80d998c4.png) :::info{title=Remarque} Étant donné que le flux de travail n'est pas en cours d'exécution lors de la configuration de l'interface, aucun bloc de données n'affiche de données spécifiques. Les données pertinentes pour une instance de flux de travail donnée ne seront visibles dans la fenêtre contextuelle des tâches à faire qu'après le déclenchement et l'exécution du flux de travail. @@ -84,7 +84,7 @@ Les boutons de soumission du formulaire peuvent être configurés selon trois ty - Soumettre et terminer le flux de travail - Enregistrer uniquement les valeurs du formulaire -![Nœud manuel_Configuration du nœud_Configuration de l'interface_Boutons du formulaire](https://static-docs.nocobase.com/6b45995b14152e831019037001445.png) +![Nœud manuel_Configuration du nœud_Configuration de l'interface_Boutons du formulaire](https://static-docs.nocobase.com/6b45995b14152e85a821dff6f6e3189a.png) Ces trois boutons représentent les trois statuts possibles d'un nœud dans le flux de travail. Après la soumission, le statut du nœud passe à « Terminé », « Rejeté » ou reste en « Attente ». Un formulaire doit obligatoirement configurer au moins l'un des deux premiers boutons pour déterminer la suite du déroulement du flux de travail. diff --git a/docs/docs/fr/workflow/nodes/response-message.md b/docs/docs/fr/workflow/nodes/response-message.md index 5561f29ef61..f390e81eac9 100644 --- a/docs/docs/fr/workflow/nodes/response-message.md +++ b/docs/docs/fr/workflow/nodes/response-message.md @@ -35,7 +35,7 @@ Lorsque le flux de travail exécute ce nœud, le modèle sera analysé pour gén Le produit « iPhone 14 pro » est en rupture de stock. ``` -![Contenu du message](https://static-docs.nocobase.com/06ad4a6b6ec499c853f0c39987f63a6a.png) +![Contenu du message](https://static-docs.nocobase.com/06bd4a6b6ec499c853f0c39987f63a6a.png) ## Configuration du flux de travail diff --git a/docs/docs/fr/workflow/nodes/variable.md b/docs/docs/fr/workflow/nodes/variable.md index b1b6f5500bc..ec7e7364717 100644 --- a/docs/docs/fr/workflow/nodes/variable.md +++ b/docs/docs/fr/workflow/nodes/variable.md @@ -15,7 +15,7 @@ Vous pouvez déclarer des variables dans un flux de travail ou attribuer des val Dans l'interface de configuration du flux de travail, cliquez sur le bouton plus (« + ») dans le flux pour ajouter un nœud « Variable » : -![Ajouter un nœud Variable](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![Ajouter un nœud Variable](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## Configurer le nœud @@ -40,7 +40,7 @@ La valeur d'une variable peut être de n'importe quel type. Il peut s'agir d'une En mode déclaration, définir la valeur de la variable équivaut à lui attribuer une valeur initiale. -![Déclarer la valeur initiale](https://static-docs.nocobase.com/4ce2c50896565ad537343013758c6a4.png) +![Déclarer la valeur initiale](https://static-docs.nocobase.com/4ce2c508986565ad537343013758c6a4.png) En mode attribution, définir la valeur de la variable équivaut à modifier la valeur de la variable cible déclarée pour une nouvelle valeur. Les utilisations ultérieures récupéreront cette nouvelle valeur. @@ -78,6 +78,6 @@ Après le nœud de calcul, créez un autre nœud Variable. Sélectionnez le mode Ainsi, une fois la branche de boucle terminée, la variable de destinataire stockera la chaîne de destinataires de tous les auteurs de l'article. Ensuite, après la boucle, vous pourrez utiliser un nœud de requête HTTP pour appeler une API d'envoi de courrier, en passant la valeur de la variable de destinataire comme paramètre de destinataire à l'API : -![Envoyer un e-mail aux destinataires via le nœud de requête](https://static-docs.nocobase.com/37f71ae1a63e172bcb2dce10a250947e.png) +![Envoyer un e-mail aux destinataires via le nœud de requête](https://static-docs.nocobase.com/37f71aa1a63e172bcb2dce10a250947e.png) À ce stade, une fonctionnalité simple d'envoi d'e-mails en masse a été implémentée à l'aide d'une boucle et d'un nœud Variable. \ No newline at end of file diff --git a/docs/docs/fr/workflow/triggers/post-action.md b/docs/docs/fr/workflow/triggers/post-action.md index 8481e808ff1..ef6e1da9b8c 100644 --- a/docs/docs/fr/workflow/triggers/post-action.md +++ b/docs/docs/fr/workflow/triggers/post-action.md @@ -178,7 +178,7 @@ Si l'événement est configuré en mode global, vous n'avez pas besoin d'utilise Comme illustré ci-dessous : -![Ordre d'exécution de l'action](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![Ordre d'exécution de l'action](https://static-docs.nocobase.com/20251219234806.png) ### Différence avec l'événement de collection diff --git a/docs/docs/fr/workflow/triggers/pre-action.md b/docs/docs/fr/workflow/triggers/pre-action.md index 1b52ceaa42b..91ba7416c66 100644 --- a/docs/docs/fr/workflow/triggers/pre-action.md +++ b/docs/docs/fr/workflow/triggers/pre-action.md @@ -28,7 +28,7 @@ Lors de la création d'un flux de travail, sélectionnez le type "Événement av Dans le déclencheur d'un flux de travail d'interception, la première chose à configurer est la collection (table de données) correspondant à l'opération : -![Configuration de l'événement d'interception_Collection](https://static-docs.nocobase.com/8f712caca8159d334cf776f838d53d6.png) +![Configuration de l'événement d'interception_Collection](https://static-docs.nocobase.com/8f7122caca8159d334cf776f838d53d6.png) Ensuite, sélectionnez le mode d'interception. Vous pouvez choisir d'intercepter uniquement le bouton d'action lié à ce flux de travail, ou d'intercepter toutes les opérations sélectionnées pour cette collection (indépendamment du formulaire d'origine et sans nécessiter de liaison avec le flux de travail correspondant) : @@ -91,7 +91,7 @@ La configuration du flux de travail correspondant est maintenant terminée. Vous Si le nœud "Fin de flux de travail" est configuré pour se terminer avec un statut "Succès", la requête d'opération sera toujours interceptée lorsque ce nœud est exécuté, mais le message de réponse renvoyé s'affichera avec un statut "Succès" (plutôt que "Erreur") : -![Message de réponse avec statut de succès](https://static-docs.nocobase.com/9559bbf56076144759451294b18c790e.png) +![Message de réponse avec statut de succès](https://static-docs.nocobase.com/9559bbf56067144759451294b18c790e.png) ## Exemple @@ -111,7 +111,7 @@ Le nœud de condition dans le flux de travail en boucle est utilisé pour déter Les autres configurations sont identiques à celles de l'utilisation de base. Lors de la soumission finale de la commande, si le stock d'un produit est insuffisant, la soumission de la commande sera interceptée et un message d'information correspondant sera renvoyé. Lors des tests, essayez de soumettre une commande avec plusieurs produits, dont un avec un stock insuffisant et un autre avec un stock suffisant. Vous pourrez alors voir le message de réponse renvoyé : -![Exemple_Message de réponse après soumission](https://static-docs.nocobase.com/dd81084aa237bda0241d399ac19270.png) +![Exemple_Message de réponse après soumission](https://static-docs.nocobase.com/dd9e81084aa237bda0241d399ac19270.png) Comme vous pouvez le constater, le message de réponse n'indique pas que le stock du premier produit, "iPhone 15 Pro", est insuffisant, mais seulement celui du second produit, "iPhone 14 Pro". Cela s'explique par le fait que, dans la boucle, le premier produit avait un stock suffisant et n'a donc pas été intercepté, tandis que le second produit avait un stock insuffisant, ce qui a entraîné l'interception de la soumission de la commande. diff --git a/docs/docs/he/auth-verification/auth-oidc/examples/google.md b/docs/docs/he/auth-verification/auth-oidc/examples/google.md index e1e75c95411..7f5d1835fec 100644 --- a/docs/docs/he/auth-verification/auth-oidc/examples/google.md +++ b/docs/docs/he/auth-verification/auth-oidc/examples/google.md @@ -14,7 +14,7 @@ עברו לממשק התצורה ומלאו את כתובת ה-URL המורשית להפניה מחדש (redirect URL). את כתובת ה-URL להפניה מחדש ניתן לקבל בעת הוספת מאמת (authenticator) חדש ב-NocoBase. בדרך כלל, היא תהיה `http(s)://host:port/api/oidc:redirect`. ראו את סעיף [מדריך למשתמש - תצורה](../index.md#configuration). -![](https://static-docs.nocobase.com/24078bf52ec966a1633489cb3d9d126.png) +![](https://static-docs.nocobase.com/24078bf52ec966a16334894cb3d9d126.png) ## הוספת מאמת (Authenticator) חדש ב-NocoBase diff --git a/docs/docs/he/auth-verification/auth-oidc/index.md b/docs/docs/he/auth-verification/auth-oidc/index.md index 93554a27f60..48f5a1573c1 100644 --- a/docs/docs/he/auth-verification/auth-oidc/index.md +++ b/docs/docs/he/auth-verification/auth-oidc/index.md @@ -44,7 +44,7 @@ pkg: '@nocobase/plugin-auth-oidc' ### מיפוי שדות -![](https://static-docs.nocobase.com/92d3c8f6f4082b50d9f475674cb5650.png) +![](https://static-docs.nocobase.com/92d63c8f6f4082b50d9f475674cb5650.png) | הגדרה | תיאור | | :----------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/docs/docs/he/auth-verification/auth-saml/examples/google.md b/docs/docs/he/auth-verification/auth-saml/examples/google.md index 5b57fb09c68..bd71884ad37 100644 --- a/docs/docs/he/auth-verification/auth-saml/examples/google.md +++ b/docs/docs/he/auth-verification/auth-saml/examples/google.md @@ -18,7 +18,7 @@ הגדרות תוסף - אימות משתמשים - הוספה - SAML -![](https://static-docs.nocobase.com/5bc18c795b8f15828e26bb07251a335.png) +![](https://static-docs.nocobase.com/5bc18c7952b8f15828e26bb07251a335.png) מלאו את הפרטים שהעתקתם זה עתה, לפי הסדר: @@ -33,9 +33,9 @@ חזרו למסוף הניהול של Google, ובדף **פרטי ספק השירות (Service Provider Details)**, הזינו את כתובת ה-ACS ומזהה הישות שהעתקתם קודם לכן, וסמנו את האפשרות **תגובה חתומה (Signed Response)**. -![](https://static-docs.nocobase.com/1536268bf8df4a5ebc2384317172191.png) +![](https://static-docs.nocobase.com/1536268bf8df4a5ebc72384317172191.png) -![](https://static-docs.nocobase.com/c7de1f8b84f335de110e5a7c96255c4.png) +![](https://static-docs.nocobase.com/c7de1f8b84c1335de110e5a7c96255c4.png) תחת **מיפוי מאפיינים (Attribute Mapping)**, הוסיפו מיפויים עבור המאפיינים המתאימים. diff --git a/docs/docs/he/auth-verification/auth/authenticators.md b/docs/docs/he/auth-verification/auth/authenticators.md index 1a887c2f5e6..c70bebc9038 100644 --- a/docs/docs/he/auth-verification/auth/authenticators.md +++ b/docs/docs/he/auth-verification/auth/authenticators.md @@ -24,7 +24,7 @@ pkg: '@nocobase/plugin-auth' ## סוגי אימות משתמשים -![](https://static-docs.nocobase.com/da42343ebe470cbf7be4b12e4.png) +![](https://static-docs.nocobase.com/da4250c0cea343ebe470cbf7be4b12e4.png) על ידי הוספת סוגים שונים של מנהלי אימות, תוכלו להוסיף למערכת שיטות אימות מתאימות. diff --git a/docs/docs/he/auth-verification/auth/password.md b/docs/docs/he/auth-verification/auth/password.md index 8f52a966a34..dfa1b4c8162 100644 --- a/docs/docs/he/auth-verification/auth/password.md +++ b/docs/docs/he/auth-verification/auth/password.md @@ -24,7 +24,7 @@ pkg: '@nocobase/plugin-auth' כאשר הרשמה אינה מאופשרת, עמוד ההתחברות לא יציג קישור ליצירת חשבון. -![](https://static-docs.nocobase.com/8d5e3b6df9991bfc1c2e095a3745121.png) +![](https://static-docs.nocobase.com/8d5e3b6df9991bfc1c2e095a93745121.png) כאשר הרשמה אינה מאופשרת, לא ניתן לגשת לעמוד ההרשמה. diff --git a/docs/docs/he/data-sources/collection-fdw/index.md b/docs/docs/he/data-sources/collection-fdw/index.md index 05804482f09..8f4492e9d78 100644 --- a/docs/docs/he/data-sources/collection-fdw/index.md +++ b/docs/docs/he/data-sources/collection-fdw/index.md @@ -65,7 +65,7 @@ MySQL משתמש במנוע ה-`federated`, שדורש הפעלה, ותומך ב אם חלו שינויים במבנה הטבלה המרוחקת, ניתן גם "לסנכרן מהטבלה המרוחקת" -![סנכרן מהטבלה המרוחקת](https://static-docs.nocobase.com/3751a9f39f933889fb3fcc4d85a6f4ad.png) +![סנכרן מהטבלה המרוחקת](https://static-docs.nocobase.com/3751a9a39f933889fb3fcc4d85a6f4ad.png) סנכרון טבלה מרוחקת diff --git a/docs/docs/he/data-sources/data-modeling/collection-fields/associations/m2o/index.md b/docs/docs/he/data-sources/data-modeling/collection-fields/associations/m2o/index.md index 295954e7b94..3135cc98e82 100644 --- a/docs/docs/he/data-sources/data-modeling/collection-fields/associations/m2o/index.md +++ b/docs/docs/he/data-sources/data-modeling/collection-fields/associations/m2o/index.md @@ -12,7 +12,7 @@ תצורת שדה: -![alt text](https://static-docs.nocobase.com/3b4484ebb98d2832f3dbf752bd84c9.png) +![alt text](https://static-docs.nocobase.com/3b4484ebb98d82f832f3dbf752bd84c9.png) ## תיאור פרמטרים diff --git a/docs/docs/he/data-sources/data-modeling/collection-fields/associations/o2m/index.md b/docs/docs/he/data-sources/data-modeling/collection-fields/associations/o2m/index.md index 9467081cbd0..089dd827517 100644 --- a/docs/docs/he/data-sources/data-modeling/collection-fields/associations/o2m/index.md +++ b/docs/docs/he/data-sources/data-modeling/collection-fields/associations/o2m/index.md @@ -12,7 +12,7 @@ תצורת שדה: -![alt text](https://static-docs.nocobase.com/a608ce5481172dad7e8ab760107ff4e.png) +![alt text](https://static-docs.nocobase.com/a608ce54821172dad7e8ab760107ff4e.png) ## תיאור פרמטרים diff --git a/docs/docs/he/data-sources/field-encryption/index.md b/docs/docs/he/data-sources/field-encryption/index.md index 68a8ab04dd6..49b9807b39b 100644 --- a/docs/docs/he/data-sources/field-encryption/index.md +++ b/docs/docs/he/data-sources/field-encryption/index.md @@ -30,7 +30,7 @@ pkg: "@nocobase/plugin-field-encryption" הצפנת מעטפה (Envelope Encryption) -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### תהליך יצירת מפתח 1. בפעם הראשונה שנוצר שדה מוצפן, המערכת מייצרת באופן אוטומטי `מפתח יישום` באורך 32 סיביות, והוא נשמר בתיקיית האחסון המוגדרת כברירת מחדל בקידוד Base64. diff --git a/docs/docs/he/email-manager/advanced/batch-send.md b/docs/docs/he/email-manager/advanced/batch-send.md index 1c2e1fabd14..62bbae08870 100644 --- a/docs/docs/he/email-manager/advanced/batch-send.md +++ b/docs/docs/he/email-manager/advanced/batch-send.md @@ -11,27 +11,27 @@ pkg: "@nocobase/plugin-email-manager" ## סקירה כללית של שליחה בכמות גדולה באפשרותכם לשלוח מיילים למספר רב של אנשים בבת אחת (כל נמען יקבל מייל נפרד). -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## שליחה בכמות גדולה באמצעות טבלה ניתן גם לשלוח מיילים בכמות גדולה דרך טבלה: 1. הוסיפו כפתור שליחת מייל לטבלה. - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. הגדירו את שדה המייל בטבלה (משמש לזיהוי כתובות מייל לאחר בחירת שורות בטבלה). - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. סמנו את נתוני הטבלה הרצויים לשליחת מיילים. - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) אם אתם צריכים לשלוח מיילים לכל הכתובות בטבלה כולה, תוכלו להפעיל את התכונה **בחירת כל הרשומות בטבלה הנוכחית כנמענים כברירת מחדל**: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) לאחר עריכת תוכן המייל, לחצו על כפתור השליחה בכמות גדולה כדי לשלוח. -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## מעקב אחר שליחת מיילים במרכז ניהול המיילים, תוכלו לצפות ולעקוב אחר סטטוס שליחת המיילים הספציפי. -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/he/email-manager/usage/signature.md b/docs/docs/he/email-manager/usage/signature.md index ea3b713b1bc..644dbd7b922 100644 --- a/docs/docs/he/email-manager/usage/signature.md +++ b/docs/docs/he/email-manager/usage/signature.md @@ -12,18 +12,18 @@ pkg: "@nocobase/plugin-email-manager" עברו למרכז ניהול הדוא"ל ולחצו על כפתור ההגדרות: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) עברו ללשונית החתימה: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) כאן תוכלו לנהל את החתימות שלכם. סמנו את האפשרות שלפני חתימה כדי להגדיר אותה כחתימת ברירת המחדל: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## שימוש בחתימות בתוך תיבת תוכן הדוא"ל, לחצו על אייקון החתימה כדי לבחור את החתימה הרצויה: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/he/email-manager/usage/template.md b/docs/docs/he/email-manager/usage/template.md index 668f9fd364c..da5e92d599a 100644 --- a/docs/docs/he/email-manager/usage/template.md +++ b/docs/docs/he/email-manager/usage/template.md @@ -11,15 +11,15 @@ pkg: "@nocobase/plugin-email-manager" ## הגדרת תבניות עברו למרכז ניהול הדוא"ל ולחצו על כפתור ההגדרות: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) עברו ללשונית התבניות: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) כאן תוכלו לנהל את התבניות: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## שימוש בתבניות בתיבת תוכן ההודעה, לחצו על אייקון התבנית כדי לבחור את התבנית הרצויה: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/he/flow-engine/learning-roadmap.md b/docs/docs/he/flow-engine/learning-roadmap.md index 56efa25178f..1c255c9541b 100644 --- a/docs/docs/he/flow-engine/learning-roadmap.md +++ b/docs/docs/he/flow-engine/learning-roadmap.md @@ -4,4 +4,4 @@ # מפת דרכים ללמידה -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/he/interface-builder/actions/types/link.md b/docs/docs/he/interface-builder/actions/types/link.md index 81778c32647..e7328f05f54 100644 --- a/docs/docs/he/interface-builder/actions/types/link.md +++ b/docs/docs/he/interface-builder/actions/types/link.md @@ -16,7 +16,7 @@ ### עריכת קישור -![20251029174725](https://static-docs.nocobase.com/202510174725.png) +![20251029174725](https://static-docs.nocobase.com/20251029174725.png) ### פתיחה בחלון חדש diff --git a/docs/docs/he/solution/ticket-system/design.md b/docs/docs/he/solution/ticket-system/design.md index 8b5db22b03e..baa2df4dc5b 100755 --- a/docs/docs/he/solution/ticket-system/design.md +++ b/docs/docs/he/solution/ticket-system/design.md @@ -31,7 +31,7 @@ - **אופקי (טבלה ראשית)**: כיסוי יכולות גנריות לכל סוגי העסקים — מספר קריאה, סטטוס, מטפל, SLA ושדות ליבה נוספים. - **אנכי (טבלאות הרחבה)**: שדות מקצועיים המעמיקים בעסק ספציפי — לתיקון ציוד יש מספרי סדרה, לתלונות יש תוכניות פיצוי. -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **למה לעצב כך?** @@ -61,7 +61,7 @@ #### תפיסה 3: מחזוריות ידע עצמית -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) זה יוצר מעגל סגור של **צבירת ידע - יישום ידע**. @@ -71,7 +71,7 @@ ### 2.1 סקירת קשרי ישויות -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 פירוט טבלאות ליבה @@ -296,18 +296,18 @@ **תהליך ראשי (משמאל לימין)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **תהליכי משנה** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **מכונת מצבים מלאה** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 כללי מעבר סטטוסים מרכזיים @@ -337,7 +337,7 @@ ### 4.2 לוגיקת חישוב SLA -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### בעת יצירת קריאה @@ -466,7 +466,7 @@ ### 5.3 עובדי AI ומחזור חיי הקריאה -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 דוגמאות לתגובות AI @@ -527,12 +527,12 @@ ### 6.1 מקורות ידע -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 תהליך הפיכת קריאה לידע -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **ממדי הערכה**: - **כלליות**: האם זו בעיה נפוצה? @@ -577,19 +577,19 @@ #### WF-T01: תהליך יצירת קריאה -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: ניתוח AI לקריאה -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: תרגום וביקורת תגובות -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: יצירת ידע -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 משימות מתוזמנות @@ -606,11 +606,11 @@ ### 8.1 ממשק ניהול (Backend) -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 פורטל לקוחות -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 עיצוב לוחות בקרה (Dashboards) diff --git a/docs/docs/he/users-permissions/acl/role.md b/docs/docs/he/users-permissions/acl/role.md index e5d104faac1..c21a880bb4a 100644 --- a/docs/docs/he/users-permissions/acl/role.md +++ b/docs/docs/he/users-permissions/acl/role.md @@ -34,6 +34,6 @@ pkg: '@nocobase/plugin-acl' ניתן להקצות למשתמש מספר תפקידים, וכאשר למשתמש יש מספר תפקידים, הוא יכול לעבור ביניהם במרכז האישי. -![](https://static-docs.nocobase.com/e311d11ec1ca3b8b7e0472105b167819.png) +![](https://static-docs.nocobase.com/e331d11ec1ca3b8b7e0472105b167819.png) תפקיד ברירת המחדל בעת הכניסה למערכת נקבע לפי התפקיד האחרון שהוחלף (ערך זה מתעדכן בכל החלפת תפקיד), או, אם לא רלוונטי, התפקיד הראשון (תפקיד ברירת המחדל של המערכת). \ No newline at end of file diff --git a/docs/docs/he/users-permissions/acl/ui.md b/docs/docs/he/users-permissions/acl/ui.md index 60c00454d81..25ed21dbeaa 100644 --- a/docs/docs/he/users-permissions/acl/ui.md +++ b/docs/docs/he/users-permissions/acl/ui.md @@ -32,11 +32,11 @@ pkg: '@nocobase/plugin-acl' **צפייה**: קובע אם שדות ספציפיים גלויים ברמת השדה, ומאפשר שליטה אילו שדות גלויים לתפקידים מסוימים בתוך אוסף ההזמנות. -![](https://static-docs.nocobase.com/30dea84d984d95049e6f7b180955a6cf.png) +![](https://static-docs.nocobase.com/30dea84d984d95039e6f7b180955a6cf.png) בממשק המשתמש, רק שדות עם הרשאות מוגדרות גלויים בתוך בלוק אוסף ההזמנות. שדות מערכת (Id, CreatedAt, LastUpdatedAt) שומרים על הרשאות צפייה גם ללא תצורה ספציפית. -![](https://static-docs.nocobase.com/40cc49b51efe701147fd2e799e79dcc.png) +![](https://static-docs.nocobase.com/40cc49b517efe701147fd2e799e79dcc.png) - **עריכה**: קובע אם ניתן לערוך ולשמור (לעדכן) שדות. @@ -137,7 +137,7 @@ pkg: '@nocobase/plugin-acl' תצורת הרשאות פרטניות עבור אוסף ההזמנות, כאשר לשדה הקשר "לקוח" יש את כל הרשאות השדה: -![](https://static-docs.nocobase.com/3a3ab972f14a7b3a35361219d67fa40.png) +![](https://static-docs.nocobase.com/3a3ab9722f14a7b3a35361219d67fa40.png) תצורת הרשאות פרטניות עבור אוסף הלקוחות, כאשר לשדות יש הרשאות צפייה בלבד: diff --git a/docs/docs/he/users-permissions/user.md b/docs/docs/he/users-permissions/user.md index e1a959056ef..1cf396d1859 100644 --- a/docs/docs/he/users-permissions/user.md +++ b/docs/docs/he/users-permissions/user.md @@ -16,7 +16,7 @@ pkg: '@nocobase/plugin-users' בנוסף, ניתן גם להוסיף בלוקים שונים מתוך אוסף המשתמשים כדי לנהל משתמשים, לדוגמה, בלוק טבלה: -![](https://static-docs.nocobase.com/76b5a4652b45d4dd96c424fb08082cf6.png) +![](https://static-docs.nocobase.com/76b5a4652f869541a9e8f18a4568a7c9.png) ## הוספת משתמש diff --git a/docs/docs/he/workflow/advanced/variables.md b/docs/docs/he/workflow/advanced/variables.md index 87700fef6b0..7218425d40c 100644 --- a/docs/docs/he/workflow/advanced/variables.md +++ b/docs/docs/he/workflow/advanced/variables.md @@ -21,7 +21,7 @@ בצומת עדכון, השתמשו בנתוני הקשר של ההפעלה כמשתנה עבור תנאי הסינון, והתייחסו לתוצאה של צומת החישוב כמשתנה עבור ערך השדה שיש לעדכן: -![משתני צומת עדכון נתונים](https://static-docs.nocobase.com/2e147c934c70a1932542caadef3431b.png) +![משתני צומת עדכון נתונים](https://static-docs.nocobase.com/2e147c93643e7ebc709b9b7ab4f3af8c.png) ## מבנה נתונים diff --git a/docs/docs/he/workflow/nodes/aggregate.md b/docs/docs/he/workflow/nodes/aggregate.md index a4bcc5ebd8b..34eac7f4515 100644 --- a/docs/docs/he/workflow/nodes/aggregate.md +++ b/docs/docs/he/workflow/nodes/aggregate.md @@ -64,7 +64,7 @@ pkg: '@nocobase/plugin-workflow-aggregate' לאחר מכן, הוסיפו צומת שאילתת אגרגציה וקבעו את תצורתו באופן הבא: -![צומת שאילתת אגרגציה_דוגמה_תצורת צומת](https://static-docs.nocobase.com/542272e686c6c0a567373d1b37ddda78.png) +![צומת שאילתת אגרגציה_דוגמה_תצורת צומת](https://static-docs.nocobase.com/542272e638c6c0a567373d1b37ddda78.png) בצורה זו, לאחר הפעלת **תהליך העבודה**, צומת שאילתת האגרגציה יספור את מספר כל המאמרים בקטגוריה של המאמר שנוסף זה עתה וישמור זאת כתוצאת הצומת. diff --git a/docs/docs/he/workflow/nodes/calculation.md b/docs/docs/he/workflow/nodes/calculation.md index b308937d77e..372e9dec6ec 100644 --- a/docs/docs/he/workflow/nodes/calculation.md +++ b/docs/docs/he/workflow/nodes/calculation.md @@ -10,7 +10,7 @@ בממשק הגדרות תהליך העבודה, לחצו על כפתור הפלוס ("+") בזרימת העבודה כדי להוסיף צומת "חישוב": -![Calculation Node_Add](https://static-docs.nocobase.com/58a5540d26945251cd143eb4b16579.png) +![Calculation Node_Add](https://static-docs.nocobase.com/58a455540d26945251cd143eb4b16579.png) ## הגדרות צומת diff --git a/docs/docs/he/workflow/nodes/create.md b/docs/docs/he/workflow/nodes/create.md index 48e20ec7289..e52df3e3a46 100644 --- a/docs/docs/he/workflow/nodes/create.md +++ b/docs/docs/he/workflow/nodes/create.md @@ -38,7 +38,7 @@ לדוגמה, כאשר רשומה באוסף "מאמרים" נוצרת או מתעדכנת, יש ליצור אוטומטית רשומה מסוג "גרסאות מאמר" כדי לתעד היסטוריית שינויים עבור המאמר. ניתן להשתמש בצומת "הוספת רשומה" כדי להשיג זאת: -![צומת הוספת רשומה_דוגמה_תצורת תהליך עבודה](https://static-docs.nocobase.com/dfd4820d49c145fa33183fc09c9161f.png) +![צומת הוספת רשומה_דוגמה_תצורת תהליך עבודה](https://static-docs.nocobase.com/dfd4820d49c145fa331883fc09c9161f.png) ![צומת הוספת רשומה_דוגמה_תצורת צומת](https://static-docs.nocobase.com/1a0992e66170be12a068da6503298868.png) diff --git a/docs/docs/he/workflow/nodes/destroy.md b/docs/docs/he/workflow/nodes/destroy.md index 87339bd2946..f96833c469d 100644 --- a/docs/docs/he/workflow/nodes/destroy.md +++ b/docs/docs/he/workflow/nodes/destroy.md @@ -34,6 +34,6 @@ לדוגמה, כדי לנקות באופן תקופתי נתוני הזמנות היסטוריים שבוטלו ואינם תקפים, ניתן להשתמש בצומת המחיקה: -![צומת מחיקה_דוגמה_הגדרות צומת](https://static-docs.nocobase.com/b94b725f8523c3f13ce5f320.png) +![צומת מחיקה_דוגמה_הגדרות צומת](https://static-docs.nocobase.com/b94b75077a17252f8523c3f13ce5f320.png) תהליך העבודה יופעל באופן תקופתי ויבצע את מחיקת כל נתוני ההזמנות ההיסטוריים שבוטלו ואינם תקפים. \ No newline at end of file diff --git a/docs/docs/he/workflow/nodes/end.md b/docs/docs/he/workflow/nodes/end.md index a9f6e4f7ef2..dcc7be225bc 100644 --- a/docs/docs/he/workflow/nodes/end.md +++ b/docs/docs/he/workflow/nodes/end.md @@ -14,7 +14,7 @@ ## הגדרות צומת -![סיום תהליך עבודה_הגדרות צומת](https://static-docs.nocobase.com/bb6a397f25e9afb72836a14a0fe0683e.png) +![סיום תהליך עבודה_הגדרות צומת](https://static-docs.nocobase.com/bb6a597f25e9afb72836a14a0fe0683e.png) ### סטטוס סיום diff --git a/docs/docs/he/workflow/nodes/manual.md b/docs/docs/he/workflow/nodes/manual.md index a8a068356c2..7b73668d61a 100644 --- a/docs/docs/he/workflow/nodes/manual.md +++ b/docs/docs/he/workflow/nodes/manual.md @@ -22,7 +22,7 @@ pkg: '@nocobase/plugin-workflow-manual' בממשק הגדרות תהליך העבודה, לחצו על כפתור הפלוס ("+") בתהליך העבודה כדי להוסיף צומת "טיפול ידני": -![יצירת צומת ידני](https://static-docs.nocobase.com/4dd259f1aceeaf9b25abb4b257df909.png) +![יצירת צומת ידני](https://static-docs.nocobase.com/4dd259f1aceeaf9b825abb4b257df909.png) ## הגדרת צומת @@ -32,7 +32,7 @@ pkg: '@nocobase/plugin-workflow-manual' בחרו משתמש, או בחרו את מפתח ראשי (primary key) או מפתח זר (foreign key) של נתוני משתמש מההקשר באמצעות משתנה. -![צומת ידני_הגדרות_אחראי_בחירת משתנה](https://static-docs.nocobase.com/22fbca3b8e21fda1019037001445.png) +![צומת ידני_הגדרות_אחראי_בחירת משתנה](https://static-docs.nocobase.com/22fbca3b8e21fda3a831019037001445.png) :::info{title=הערה} נכון לעכשיו, אפשרות האחראי בצומת ידני אינה תומכת במספר משתמשים. תמיכה זו תתווסף בגרסה עתידית. @@ -60,7 +60,7 @@ pkg: '@nocobase/plugin-workflow-manual' בלוקי נתוני צומת דומים; תוכלו לבחור את תוצאת הנתונים מצומת קודם כדי להציג כפרטים. לדוגמה, התוצאה של צומת חישוב קודם יכולה לשמש כמידע עזר הקשרי למשימת ה"לביצוע" של האחראי: -![צומת ידני_הגדרות צומת_הגדרות ממשק_בלוק נתונים_נתוני צומת](https://static-docs.nocobase.com/a583e26e51a4f45db310a72c2d0a404c.png) +![צומת ידני_הגדרות צומת_הגדרות ממשק_בלוק נתונים_נתוני צומת](https://static-docs.nocobase.com/a583e26e508e954b47e5ddff80d998c4.png) :::info{title=הערה} מכיוון שתהליך העבודה אינו במצב ביצוע במהלך הגדרת הממשק, לא מוצגים נתונים ספציפיים בבלוקי הנתונים. הנתונים הרלוונטיים עבור מופע ספציפי של תהליך עבודה יוצגו בממשק החלון הקופץ של ה"לביצוע" רק לאחר שתהליך העבודה הופעל ובוצע. @@ -104,7 +104,7 @@ pkg: '@nocobase/plugin-workflow-manual' תוכלו לבחור "משימות לביצוע של תהליך עבודה" מבין הבלוקים בעמוד כדי להוסיף בלוק של רשימת "לביצוע": -![צומת ידני_הוספת בלוק לביצוע](https://static-docs.nocobase.com/198b41754cd73b704267bf30fe5e647.png) +![צומת ידני_הוספת בלוק לביצוע](https://static-docs.nocobase.com/198b417454cd73b704267bf30fe5e647.png) דוגמה לבלוק רשימת "לביצוע": diff --git a/docs/docs/he/workflow/nodes/parallel.md b/docs/docs/he/workflow/nodes/parallel.md index 19bb89d57ad..dc93dddce88 100644 --- a/docs/docs/he/workflow/nodes/parallel.md +++ b/docs/docs/he/workflow/nodes/parallel.md @@ -22,7 +22,7 @@ pkg: '@nocobase/plugin-workflow-parallel' לאחר הוספת צומת ענף מקביל לתהליך העבודה, שני ענפי משנה יתווספו כברירת מחדל. תוכלו גם להוסיף ענפים נוספים על ידי לחיצה על כפתור הוספת ענף. ניתן להוסיף מספר בלתי מוגבל של צמתים לכל ענף. ענפים מיותרים ניתנים להסרה על ידי לחיצה על כפתור המחיקה בתחילת הענף. -![并行分支_分支管理](https://static-docs.nocobase.com/36088a8b4771eb3ee9bc2a757.png) +![并行分支_分支管理](https://static-docs.nocobase.com/36088a8b7970c8a1771eb3ee9bc2a757.png) ## הגדרות צומת diff --git a/docs/docs/he/workflow/nodes/response-message.md b/docs/docs/he/workflow/nodes/response-message.md index f222ca8bb32..fafcb4ad187 100644 --- a/docs/docs/he/workflow/nodes/response-message.md +++ b/docs/docs/he/workflow/nodes/response-message.md @@ -28,7 +28,7 @@ pkg: '@nocobase/plugin-workflow-response-message' תוכן ההודעה הוא מחרוזת תבנית שבה ניתן להכניס משתנים. אתם יכולים לארגן את תוכן התבנית הזה בהגדרות הצומת: -![הגדרות צומת](https://static-docs.nocobase.com/d5fa5f402d50baf3ba16048818fddfc.png) +![הגדרות צומת](https://static-docs.nocobase.com/d5fa5f4002d50baf3ba16048818fddfc.png) כאשר תהליך העבודה מגיע לביצוע צומת זה, התבנית תנותח כדי ליצור את תוכן ההודעה. בהגדרות שלמעלה, המשתנה "משתנה מקומי / לולאת כל המוצרים / אובייקט לולאה / מוצר / כותרת" יוחלף בערך ספציפי בתהליך העבודה בפועל, לדוגמה: diff --git a/docs/docs/he/workflow/nodes/variable.md b/docs/docs/he/workflow/nodes/variable.md index 8ddef46efff..3e140114c21 100644 --- a/docs/docs/he/workflow/nodes/variable.md +++ b/docs/docs/he/workflow/nodes/variable.md @@ -16,7 +16,7 @@ pkg: '@nocobase/plugin-workflow-variable' בממשק הגדרות תהליך העבודה, לחצו על כפתור הפלוס ("+") בתוך התהליך כדי להוסיף צומת "משתנה": -![הוספת צומת משתנה](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![הוספת צומת משתנה](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## הגדרת צומת @@ -24,7 +24,7 @@ pkg: '@nocobase/plugin-workflow-variable' צומת המשתנה דומה למשתנים בתכנות; יש להצהיר עליו לפני שניתן להשתמש בו ולהקצות לו ערך. לכן, בעת יצירת צומת משתנה, עליכם לבחור את מצב המשתנה. קיימים שני מצבים לבחירה: -![בחירת מצב](https://static-docs.nocobase.com/49d8b701de6faef6f303262aa14550.png) +![בחירת מצב](https://static-docs.nocobase.com/49d8b7b501de6faef6f303262aa14550.png) - הצהרה על משתנה חדש: יוצר משתנה חדש. - הקצאה למשתנה קיים: מקצה ערך למשתנה שהוצהר עליו קודם לכן בתהליך העבודה, מה ששקול לשינוי ערך המשתנה. @@ -33,7 +33,7 @@ pkg: '@nocobase/plugin-workflow-variable' כאשר אתם בוחרים להקצות ערך למשתנה שהוצהר עליו, עליכם גם לבחור את משתנה היעד, שהוא הצומת שבו הוצהר המשתנה: -![בחירת המשתנה להקצאת ערך](https://static-docs.nocobase.com/1ce8911548d7347e693d8cc8ac193eb.png) +![בחירת המשתנה להקצאת ערך](https://static-docs.nocobase.com/1ce8911548d7347e693d8cc8ac1953eb.png) ### ערך @@ -51,7 +51,7 @@ pkg: '@nocobase/plugin-workflow-variable' בצמתים הבאים לאחר צומת המשתנה, תוכלו להשתמש בערך המשתנה על ידי בחירת המשתנה שהוצהר עליו מתוך קבוצת "משתני צומת". לדוגמה, בצומת שאילתה, השתמשו בערך המשתנה כתנאי שאילתה: -![שימוש בערך משתנה כתנאי סינון שאילתה](https://static-docs.nocobase.com/1ca91c29524ff85999a1751499f14bc.png) +![שימוש בערך משתנה כתנאי סינון שאילתה](https://static-docs.nocobase.com/1ca91c295254ff85999a1751499f14bc.png) ## דוגמה diff --git a/docs/docs/he/workflow/triggers/post-action.md b/docs/docs/he/workflow/triggers/post-action.md index 94c41d6e62a..c0b296bbbf5 100644 --- a/docs/docs/he/workflow/triggers/post-action.md +++ b/docs/docs/he/workflow/triggers/post-action.md @@ -178,7 +178,7 @@ curl -X POST -H 'Authorization: Bearer ' -H 'X-Role: ' -d כפי שמוצג בתמונה למטה: -![סדר ביצוע פעולות](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![סדר ביצוע פעולות](https://static-docs.nocobase.com/20251219234806.png) ### הבדל מאירוע אוסף diff --git a/docs/docs/he/workflow/triggers/pre-action.md b/docs/docs/he/workflow/triggers/pre-action.md index 7d8e0c19985..81a68f4a93c 100644 --- a/docs/docs/he/workflow/triggers/pre-action.md +++ b/docs/docs/he/workflow/triggers/pre-action.md @@ -28,7 +28,7 @@ pkg: '@nocobase/plugin-workflow-request-interceptor' בטריגר של תהליך עבודה מיירט, הדבר הראשון שיש להגדיר הוא ה אוסף המתאים לפעולה: -![Interceptor Event Configuration_Collection](https://static-docs.nocobase.com/8f712caca8159d334cf776b838d53d6.png) +![Interceptor Event Configuration_Collection](https://static-docs.nocobase.com/8f7122caca8159d334cf776f838d53d6.png) לאחר מכן, בחרו את מצב היירוט. אתם יכולים לבחור ליירט רק את כפתור הפעולה המקושר ל תהליך עבודה זה, או ליירט את כל הפעולות הנבחרות עבור אוסף זה (ללא קשר לטופס שממנו הן מגיעות, וללא צורך לקשר את תהליך העבודה המתאים). @@ -91,7 +91,7 @@ pkg: '@nocobase/plugin-workflow-request-interceptor' אם צומת 'סיום תהליך עבודה' מוגדר לצאת עם סטטוס 'הצלחה', בקשת הפעולה עדיין תיוּרט כאשר צומת זה מבוצע, אך הודעת התגובה שתחזור תוצג עם סטטוס 'הצלחה' (במקום 'שגיאה'): -![Success Status Response Message](https://static-docs.nocobase.com/9599bbf5451294b18c790e.png) +![Success Status Response Message](https://static-docs.nocobase.com/9559bbf56067144759451294b18c790e.png) ## דוגמה diff --git a/docs/docs/hi/auth-verification/api-keys/index.md b/docs/docs/hi/auth-verification/api-keys/index.md index dc777370437..65abd1294eb 100644 --- a/docs/docs/hi/auth-verification/api-keys/index.md +++ b/docs/docs/hi/auth-verification/api-keys/index.md @@ -18,7 +18,7 @@ http://localhost:13000/admin/settings/api-keys/configuration ### API कुंजी जोड़ें -![](https://static-docs.nocobase.com/46141872fc0ad9a96fa5b14e9f81dfe14a0a8.png) +![](https://static-docs.nocobase.com/46141872fc0ad9a96fa5b14e97fcba12.png) **ध्यान दें** diff --git a/docs/docs/hi/auth-verification/auth-saml/examples/google.md b/docs/docs/hi/auth-verification/auth-saml/examples/google.md index a91fc5ce810..6daa16db70e 100644 --- a/docs/docs/hi/auth-verification/auth-saml/examples/google.md +++ b/docs/docs/hi/auth-verification/auth-saml/examples/google.md @@ -12,7 +12,7 @@ ऐप सेट करने के बाद, **SSO URL**, **एंटिटी ID** और **सर्टिफिकेट** कॉपी करें। -![](https://static-docs.nocobase.com/aafd20a730e85411c0c8f368637e0.png) +![](https://static-docs.nocobase.com/aafd20a794730e85411c0c8f368637e0.png) ## NocoBase पर नया ऑथेंटिकेटर जोड़ें diff --git a/docs/docs/hi/auth-verification/auth/authenticators.md b/docs/docs/hi/auth-verification/auth/authenticators.md index 7d6fe7f53a2..337557c0cfd 100644 --- a/docs/docs/hi/auth-verification/auth/authenticators.md +++ b/docs/docs/hi/auth-verification/auth/authenticators.md @@ -16,7 +16,7 @@ pkg: '@nocobase/plugin-auth' ## प्रमाणीकरणकर्ताओं को सक्रिय करें -![](https://static-docs.nocobase.com/7f1bf8f8ca5de67ffc68eff0a65848f5.png) +![](https://static-docs.nocobase.com/7f1fb8f8ca5de67ffc68eff0a65848f5.png) केवल सक्रिय प्रमाणीकरण प्रकार ही लॉगिन पेज पर दिखाई देंगे। diff --git a/docs/docs/hi/data-sources/data-modeling/collection-fields/associations/m2o/index.md b/docs/docs/hi/data-sources/data-modeling/collection-fields/associations/m2o/index.md index 2244d1bdf63..f9cbcffc4f3 100644 --- a/docs/docs/hi/data-sources/data-modeling/collection-fields/associations/m2o/index.md +++ b/docs/docs/hi/data-sources/data-modeling/collection-fields/associations/m2o/index.md @@ -12,7 +12,7 @@ ER आरेख: फ़ील्ड कॉन्फ़िगरेशन: -![alt text](https://static-docs.nocobase.com/3b4484ebb82f832f3dbf752bd84c9.png) +![alt text](https://static-docs.nocobase.com/3b4484ebb98d82f832f3dbf752bd84c9.png) ## पैरामीटर विवरण diff --git a/docs/docs/hi/data-sources/data-modeling/collection-fields/associations/o2m/index.md b/docs/docs/hi/data-sources/data-modeling/collection-fields/associations/o2m/index.md index 605ebdc5b49..2958b4ea2ec 100644 --- a/docs/docs/hi/data-sources/data-modeling/collection-fields/associations/o2m/index.md +++ b/docs/docs/hi/data-sources/data-modeling/collection-fields/associations/o2m/index.md @@ -12,7 +12,7 @@ ER आरेख: फ़ील्ड कॉन्फ़िगरेशन: -![alt text](https://static-docs.nocobase.com/a608ce84821172dad7e8ab760107ff4e.png) +![alt text](https://static-docs.nocobase.com/a608ce54821172dad7e8ab760107ff4e.png) ## पैरामीटर विवरण diff --git a/docs/docs/hi/data-sources/data-modeling/collection-fields/associations/o2o/index.md b/docs/docs/hi/data-sources/data-modeling/collection-fields/associations/o2o/index.md index cf3d453545b..f1d438eeab9 100644 --- a/docs/docs/hi/data-sources/data-modeling/collection-fields/associations/o2o/index.md +++ b/docs/docs/hi/data-sources/data-modeling/collection-fields/associations/o2o/index.md @@ -32,7 +32,7 @@ ER संबंध फ़ील्ड कॉन्फ़िगरेशन -![alt text](https://static-docs.nocobase.com/4f09eeb3c7717d61a34982da43c187c.png) +![alt text](https://static-docs.nocobase.com/4f09eeb3c7717d61a349842da43c187c.png) ## पैरामीटर विवरण diff --git a/docs/docs/hi/data-sources/field-encryption/index.md b/docs/docs/hi/data-sources/field-encryption/index.md index ee67025b971..93b7ff64572 100644 --- a/docs/docs/hi/data-sources/field-encryption/index.md +++ b/docs/docs/hi/data-sources/field-encryption/index.md @@ -30,7 +30,7 @@ pkg: "@nocobase/plugin-field-encryption" यह एनवेलप एन्क्रिप्शन (Envelope Encryption) विधि का उपयोग करता है। -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### कुंजी निर्माण प्रक्रिया 1. जब पहली बार कोई एन्क्रिप्टेड फ़ील्ड बनाया जाता है, तो सिस्टम स्वचालित रूप से एक 32-बिट `एप्लिकेशन कुंजी` बनाता है, जिसे Base64 एन्कोडिंग में डिफ़ॉल्ट स्टोरेज डायरेक्टरी में सहेजा जाता है। diff --git a/docs/docs/hi/email-manager/advanced/batch-send.md b/docs/docs/hi/email-manager/advanced/batch-send.md index 1fe9c0c01f0..36fa9716972 100644 --- a/docs/docs/hi/email-manager/advanced/batch-send.md +++ b/docs/docs/hi/email-manager/advanced/batch-send.md @@ -10,27 +10,27 @@ pkg: "@nocobase/plugin-email-manager" ## थोक में ईमेल भेजने का अवलोकन आप कई लोगों को थोक में ईमेल भेज सकते हैं (प्रत्येक प्राप्तकर्ता को एक अलग ईमेल मिलेगा)। -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## तालिका के माध्यम से थोक में ईमेल भेजना आप एक तालिका (टेबल) के माध्यम से भी थोक में ईमेल भेज सकते हैं: 1. तालिका में ईमेल भेजने का बटन जोड़ें - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. तालिका में ईमेल फ़ील्ड कॉन्फ़िगर करें (इसका उपयोग तालिका की पंक्तियों का चयन करने के बाद ईमेल पते को पार्स करने के लिए किया जाता है) - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. ईमेल भेजने के लिए तालिका डेटा चुनें - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) यदि आपको पूरी तालिका के सभी पतों पर ईमेल भेजने की आवश्यकता है, तो आप **डिफ़ॉल्ट रूप से वर्तमान तालिका के सभी रिकॉर्ड को प्राप्तकर्ता के रूप में चुनें** सुविधा को सक्षम कर सकते हैं: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) ईमेल सामग्री संपादित करने के बाद, भेजने के लिए थोक भेजें बटन पर क्लिक करें: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## ईमेल भेजने की ट्रैकिंग आप ईमेल प्रबंधन केंद्र में ईमेल भेजने की विशिष्ट स्थिति देख और ट्रैक कर सकते हैं: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/hi/email-manager/usage/signature.md b/docs/docs/hi/email-manager/usage/signature.md index e983941d5f3..08d1a6dbd0b 100644 --- a/docs/docs/hi/email-manager/usage/signature.md +++ b/docs/docs/hi/email-manager/usage/signature.md @@ -12,15 +12,15 @@ pkg: "@nocobase/plugin-email-manager" ## हस्ताक्षर कॉन्फ़िगरेशन मेल प्रबंधन केंद्र में जाएँ और सेटिंग्स बटन पर क्लिक करें: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) हस्ताक्षर पैनल पर स्विच करें: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) आप यहाँ हस्ताक्षर प्रबंधित कर सकते हैं। किसी हस्ताक्षर के सामने वाले विकल्प को चेक करके उसे डिफ़ॉल्ट हस्ताक्षर के रूप में सेट कर सकते हैं: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## हस्ताक्षर का उपयोग मेल के मुख्य भाग (बॉडी) में, अपनी इच्छित हस्ताक्षर चुनने के लिए हस्ताक्षर आइकन पर क्लिक करें: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/hi/email-manager/usage/template.md b/docs/docs/hi/email-manager/usage/template.md index 6b1c5afbeea..4ece27479ba 100644 --- a/docs/docs/hi/email-manager/usage/template.md +++ b/docs/docs/hi/email-manager/usage/template.md @@ -11,15 +11,15 @@ pkg: "@nocobase/plugin-email-manager" ## टेम्पलेट कॉन्फ़िगरेशन ईमेल प्रबंधन केंद्र में जाएँ और सेटिंग्स बटन पर क्लिक करें: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) टेम्पलेट पैनल पर स्विच करें: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) आप यहाँ टेम्पलेट प्रबंधित कर सकते हैं: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## टेम्पलेट का उपयोग ईमेल बॉडी बॉक्स में, वांछित टेम्पलेट चुनने के लिए टेम्पलेट आइकन पर क्लिक करें: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/hi/flow-engine/learning-roadmap.md b/docs/docs/hi/flow-engine/learning-roadmap.md index fb3e1d89638..74175a0bc75 100644 --- a/docs/docs/hi/flow-engine/learning-roadmap.md +++ b/docs/docs/hi/flow-engine/learning-roadmap.md @@ -4,4 +4,4 @@ # सीखने का रोडमैप -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/hi/solution/ticket-system/design.md b/docs/docs/hi/solution/ticket-system/design.md index a4a3ba6b807..a0673e81cba 100755 --- a/docs/docs/hi/solution/ticket-system/design.md +++ b/docs/docs/hi/solution/ticket-system/design.md @@ -31,7 +31,7 @@ - **क्षैतिज (मुख्य तालिका)**: सभी प्रकार के व्यवसायों के लिए सामान्य क्षमताएं — जैसे नंबर, स्थिति, असाइनी, SLA और अन्य मुख्य फ़ील्ड। - **लंबवत (विस्तार तालिकाएं)**: विशिष्ट व्यवसाय के लिए गहराई वाले फ़ील्ड — जैसे उपकरण मरम्मत के लिए सीरियल नंबर, शिकायतों के लिए मुआवज़ा योजना। -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **ऐसा डिज़ाइन क्यों?** @@ -61,7 +61,7 @@ #### दर्शन तीन: ज्ञान स्व-चक्र (Knowledge Self-Circulation) -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) यह **ज्ञान संचय - ज्ञान अनुप्रयोग** का एक बंद लूप (closed loop) बनाता है। @@ -71,7 +71,7 @@ ### 2.1 इकाई संबंध अवलोकन (Entity Relationship Overview) -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 मुख्य तालिकाओं का विवरण @@ -296,18 +296,18 @@ **मुख्य प्रवाह (बाएं से दाएं)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **शाखा प्रवाह** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **पूर्ण स्टेट मशीन** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 प्रमुख स्थिति परिवर्तन नियम @@ -337,7 +337,7 @@ ### 4.2 SLA गणना तर्क -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### टिकट निर्माण के समय @@ -466,7 +466,7 @@ SLA रुकने का समय = रिक्त ### 5.3 AI कर्मचारी और टिकट जीवनचक्र -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 AI प्रतिक्रिया उदाहरण @@ -527,12 +527,12 @@ Grace द्वारा की जाने वाली उत्तर गु ### 6.1 ज्ञान के स्रोत -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 टिकट-से-ज्ञान प्रवाह -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **मूल्यांकन आयाम**: - **सामान्यता**: क्या यह एक आम समस्या है? @@ -577,19 +577,19 @@ Grace द्वारा की जाने वाली उत्तर गु #### WF-T01: टिकट निर्माण वर्कफ़्लो -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: टिकट AI विश्लेषण -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: टिप्पणी अनुवाद और समीक्षा -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: ज्ञान निर्माण -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 निर्धारित कार्य (Scheduled Tasks) @@ -606,11 +606,11 @@ Grace द्वारा की जाने वाली उत्तर गु ### 8.1 बैकएंड एडमिन एंड -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 ग्राहक पोर्टल एंड -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 डैशबोर्ड डिज़ाइन diff --git a/docs/docs/hi/users-permissions/acl/permissions.md b/docs/docs/hi/users-permissions/acl/permissions.md index a3c7a40bf7b..c082a069d73 100644 --- a/docs/docs/hi/users-permissions/acl/permissions.md +++ b/docs/docs/hi/users-permissions/acl/permissions.md @@ -26,7 +26,7 @@ pkg: '@nocobase/plugin-acl' ## संग्रह कार्य अनुमतियाँ -![](https://static-docs.nocobase.com/6a6e028173c5d7.png) +![](https://static-docs.nocobase.com/6a6e0281391cecdea5b5218e6173c5d7.png) ![](https://static-docs.nocobase.com/9814140434ff9e1bf028a6c282a5a165.png) diff --git a/docs/docs/hi/users-permissions/acl/ui.md b/docs/docs/hi/users-permissions/acl/ui.md index abcba3f14ed..d8ba084ae67 100644 --- a/docs/docs/hi/users-permissions/acl/ui.md +++ b/docs/docs/hi/users-permissions/acl/ui.md @@ -20,7 +20,7 @@ pkg: '@nocobase/plugin-acl' 'ऑर्डर' संग्रह (Collection) की व्यक्तिगत अनुमति कॉन्फ़िगरेशन इस प्रकार है: -![](https://static-docs.nocobase.com/a88caba1cad47001c1601bf402a4a2c1.png) +![](https://static-docs.nocobase.com/a88caba1cad47001c1610bf402a4a2c1.png) UI में, 'ऑर्डर' संग्रह (Collection) के सभी ब्लॉक प्रदर्शित नहीं होते हैं। @@ -36,7 +36,7 @@ UI में, 'ऑर्डर' संग्रह (Collection) के सभी UI में, 'ऑर्डर' संग्रह (Collection) ब्लॉक के भीतर केवल वे फ़ील्ड दिखाई देते हैं जिनके लिए अनुमतियाँ कॉन्फ़िगर की गई हैं। सिस्टम फ़ील्ड (जैसे Id, CreatedAt, LastUpdatedAt) के पास विशिष्ट कॉन्फ़िगरेशन के बिना भी देखने की अनुमति होती है। -![](https://static-docs.nocobase.com/40cc2717517efe701147fd2e799e79dcc.png) +![](https://static-docs.nocobase.com/40cc49b517efe701147fd2e799e79dcc.png) - **संपादित करें (Edit)**: यह नियंत्रित करता है कि फ़ील्ड को संपादित और सहेजा (अपडेट किया) जा सकता है या नहीं। @@ -73,7 +73,7 @@ UI में, 'ऑर्डर' संग्रह (Collection) ब्लॉक जैसा कि चित्र में दिखाया गया है, 'ऑर्डर' संग्रह (Collection) के लिए व्यक्तिगत क्रिया अनुमतियाँ कॉन्फ़िगर करें ताकि जोड़ने की अनुमति मिल सके: -![](https://static-docs.nocobase.com/2e31235dbc72ae78942481360626629.png) +![](https://static-docs.nocobase.com/2e3123b5dbc72ae78942481360626629.png) जब जोड़ने की क्रिया की अनुमति होती है, तो UI में 'ऑर्डर' संग्रह (Collection) ब्लॉक के क्रिया क्षेत्र में जोड़ने का बटन दिखाई देता है। diff --git a/docs/docs/hi/users-permissions/departments/index.md b/docs/docs/hi/users-permissions/departments/index.md index 26ef6aef3ac..cfd8204613c 100644 --- a/docs/docs/hi/users-permissions/departments/index.md +++ b/docs/docs/hi/users-permissions/departments/index.md @@ -34,7 +34,7 @@ pkg: '@nocobase/plugin-departments' विभाग संपादन फ़ॉर्म में 'उच्च विभाग' फ़ील्ड को बदलें। वर्तमान विभाग और उसके उप-विभागों का चयन नहीं किया जा सकता। -![](https://static-docs.nocobase.com/9d80dd1e10268adcd35445e9f1dac771.png) +![](https://static-docs.nocobase.com/9d80ddf42f32c77186566ed8ada70128.png) ## विभाग सदस्य प्रबंधन diff --git a/docs/docs/hi/users-permissions/departments/role.md b/docs/docs/hi/users-permissions/departments/role.md index 6b8c2978062..edd295db629 100644 --- a/docs/docs/hi/users-permissions/departments/role.md +++ b/docs/docs/hi/users-permissions/departments/role.md @@ -19,7 +19,7 @@ pkg: '@nocobase/plugin-departments' दूसरा तरीका यह है कि भूमिका प्रबंधन (role management) में संबंधित भूमिका (corresponding role) में विभाग जोड़ें। -![](https://static-docs.nocobase.com/f2a7bec89aa1fb415c152a51a51cc23b.png) +![](https://static-docs.nocobase.com/f2a7bec937cf2f179ce868a92b98416d.png) जिन विभागों के पास पहले से यह भूमिका है, उन्हें चुना नहीं जा सकता। diff --git a/docs/docs/hi/users-permissions/user.md b/docs/docs/hi/users-permissions/user.md index 20e6d193914..6c0ef510b1c 100644 --- a/docs/docs/hi/users-permissions/user.md +++ b/docs/docs/hi/users-permissions/user.md @@ -16,7 +16,7 @@ pkg: '@nocobase/plugin-users' इसके अलावा, आप उपयोगकर्ताओं को प्रबंधित करने के लिए उपयोगकर्ता **संग्रह** के विभिन्न प्रकार के ब्लॉक भी जोड़ सकते हैं, जैसे कि टेबल ब्लॉक: -![](https://static-docs.nocobase.com/76b59541a9e8f18a4568a7c9.png) +![](https://static-docs.nocobase.com/76b5a4652f869541a9e8f18a4568a7c9.png) ## उपयोगकर्ता जोड़ें diff --git a/docs/docs/hi/workflow/advanced/variables.md b/docs/docs/hi/workflow/advanced/variables.md index 54551817b13..76f8bafa41f 100644 --- a/docs/docs/hi/workflow/advanced/variables.md +++ b/docs/docs/hi/workflow/advanced/variables.md @@ -21,7 +21,7 @@ एक अपडेट नोड में, फ़िल्टर शर्त के लिए ट्रिगर संदर्भ डेटा को एक वेरिएबल के रूप में उपयोग करें, और अपडेट किए जाने वाले फ़ील्ड मान के लिए एक वेरिएबल के रूप में गणना नोड के परिणाम को संदर्भित करें: -![डेटा नोड वेरिएबल्स अपडेट करें](https://static-docs.nocobase.com/2e147c9364e7ebc709b9b7ab4f3af8c.png) +![डेटा नोड वेरिएबल्स अपडेट करें](https://static-docs.nocobase.com/2e147c93643e7ebc709b9b7ab4f3af8c.png) ## डेटा संरचना diff --git a/docs/docs/hi/workflow/nodes/condition.md b/docs/docs/hi/workflow/nodes/condition.md index 2ef88c37790..f024473014e 100644 --- a/docs/docs/hi/workflow/nodes/condition.md +++ b/docs/docs/hi/workflow/nodes/condition.md @@ -12,7 +12,7 @@ शर्त नोड में दो मोड होते हैं: "'हाँ' होने पर जारी रखें" और "'हाँ' और 'नहीं' पर अलग-अलग शाखाएँ"। नोड बनाते समय आपको इनमें से एक मोड चुनना होगा, और बाद में नोड की कॉन्फ़िगरेशन में इसे बदला नहीं जा सकता। -![शर्त_मोड_चयन](https://static-docs.nocobase.com/3de27308c1179523d606c66bf3a5fb4.png) +![शर्त_मोड_चयन](https://static-docs.nocobase.com/3de27308c1179523d8606c66bf3a5fb4.png) "'हाँ' होने पर जारी रखें" मोड में, जब शर्त का परिणाम "हाँ" होता है, तो वर्कफ़्लो बाद के नोड्स को निष्पादित करना जारी रखेगा। अन्यथा, वर्कफ़्लो समाप्त हो जाएगा और विफल स्थिति के साथ समय से पहले बाहर निकल जाएगा। diff --git a/docs/docs/hi/workflow/nodes/create.md b/docs/docs/hi/workflow/nodes/create.md index 2ded767ba2b..976b6f1043f 100644 --- a/docs/docs/hi/workflow/nodes/create.md +++ b/docs/docs/hi/workflow/nodes/create.md @@ -40,6 +40,6 @@ ![रिकॉर्ड बनाएँ नोड_उदाहरण_वर्कफ़्लो कॉन्फ़िगरेशन](https://static-docs.nocobase.com/dfd4820d49c145fa331883fc09c9161f.png) -![रिकॉर्ड बनाएँ नोड_उदाहरण_नोड कॉन्फ़िगरेशन](https://static-docs.nocobase.com/1a1070be1610be12a068da6503298868.png) +![रिकॉर्ड बनाएँ नोड_उदाहरण_नोड कॉन्फ़िगरेशन](https://static-docs.nocobase.com/1a0992e66170be12a068da6503298868.png) इस कॉन्फ़िगरेशन के साथ वर्कफ़्लो सक्षम करने के बाद, जब "पोस्ट" संग्रह में कोई रिकॉर्ड बदल जाता है, तो पोस्ट के परिवर्तन इतिहास को लॉग करने के लिए एक "पोस्ट संस्करण" रिकॉर्ड स्वचालित रूप से बनाया जाएगा। \ No newline at end of file diff --git a/docs/docs/hi/workflow/nodes/loop.md b/docs/docs/hi/workflow/nodes/loop.md index 07ea5bb7d14..a51507966ab 100644 --- a/docs/docs/hi/workflow/nodes/loop.md +++ b/docs/docs/hi/workflow/nodes/loop.md @@ -117,6 +117,6 @@ pkg: '@nocobase/plugin-workflow-loop' कुल **वर्कफ़्लो** संरचना नीचे दी गई है: -![लूप नोड_उदाहरण_वर्कफ़्लो संरचना](https://static-docs.nocobase.com/6f59ef246c1f1997634a7624c4c4151.png) +![लूप नोड_उदाहरण_वर्कफ़्लो संरचना](https://static-docs.nocobase.com/6f59ef246c1f19976344a7624c4c4151.png) इस **वर्कफ़्लो** को कॉन्फ़िगर और सक्रिय करने के बाद, जब एक नया ऑर्डर बनाया जाता है, तो यह स्वचालित रूप से ऑर्डर विवरण में उत्पादों के स्टॉक की जांच करेगा। यदि स्टॉक पर्याप्त है, तो इसे घटाया जाएगा; अन्यथा, ऑर्डर विवरण में उत्पाद को अमान्य के रूप में अपडेट किया जाएगा (ताकि एक वैध ऑर्डर कुल मूल्य की गणना की जा सके)। \ No newline at end of file diff --git a/docs/docs/hi/workflow/nodes/manual.md b/docs/docs/hi/workflow/nodes/manual.md index b27c97eb634..9d48942921a 100644 --- a/docs/docs/hi/workflow/nodes/manual.md +++ b/docs/docs/hi/workflow/nodes/manual.md @@ -104,11 +104,11 @@ pkg: '@nocobase/plugin-workflow-manual' आप पेज पर ब्लॉक में से "वर्कफ़्लो लंबित" का चयन करके एक लंबित सूची ब्लॉक जोड़ सकते हैं: -![Manual Node_Add To-do Block](https://static-docs.nocobase.com/198b417545cd73b704267bf30fe5e647.png) +![Manual Node_Add To-do Block](https://static-docs.nocobase.com/198b417454cd73b704267bf30fe5e647.png) लंबित सूची ब्लॉक का उदाहरण: -![Manual Node_To-do List](https://static-docs.nocobase.com/cfefb0c9c9dfa550d6b220f34.png) +![Manual Node_To-do List](https://static-docs.nocobase.com/cfefb0d2c6a91c5c9dfa550d6b220f34.png) ### लंबित विवरण diff --git a/docs/docs/hi/workflow/nodes/variable.md b/docs/docs/hi/workflow/nodes/variable.md index f7f8ce13178..c308d5142c0 100644 --- a/docs/docs/hi/workflow/nodes/variable.md +++ b/docs/docs/hi/workflow/nodes/variable.md @@ -16,7 +16,7 @@ pkg: '@nocobase/plugin-workflow-variable' वर्कफ़्लो कॉन्फ़िगरेशन इंटरफ़ेस में, प्रवाह में दिए गए प्लस ("+") बटन पर क्लिक करके एक "वेरिएबल" नोड जोड़ें: -![वेरिएबल नोड जोड़ें](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![वेरिएबल नोड जोड़ें](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## नोड कॉन्फ़िगर करें @@ -41,7 +41,7 @@ pkg: '@nocobase/plugin-workflow-variable' घोषणा मोड में, वेरिएबल का मान सेट करना उसे एक प्रारंभिक मान असाइन करने जैसा है। -![प्रारंभिक मान घोषित करें](https://static-docs.nocobase.com/4ce2c50896565ad537343013758c6a4.png) +![प्रारंभिक मान घोषित करें](https://static-docs.nocobase.com/4ce2c508986565ad537343013758c6a4.png) असाइनमेंट मोड में, वेरिएबल का मान सेट करना घोषित लक्ष्य वेरिएबल के मान को एक नए मान में बदलना है। बाद के उपयोगों में, आपको यही नया मान मिलेगा। @@ -51,7 +51,7 @@ pkg: '@nocobase/plugin-workflow-variable' वेरिएबल नोड के बाद के नोड्स में, आप "नोड वेरिएबल" समूह से घोषित वेरिएबल को चुनकर उसके मान का उपयोग कर सकते हैं। उदाहरण के लिए, एक क्वेरी नोड में, वेरिएबल के मान का उपयोग क्वेरी शर्त के रूप में करें: -![क्वेरी फ़िल्टर शर्त के रूप में वेरिएबल मान का उपयोग करें](https://static-docs.nocobase.com/1ca91c295254ff5999a1751499f14bc.png) +![क्वेरी फ़िल्टर शर्त के रूप में वेरिएबल मान का उपयोग करें](https://static-docs.nocobase.com/1ca91c295254ff85999a1751499f14bc.png) ## उदाहरण diff --git a/docs/docs/hi/workflow/triggers/collection.md b/docs/docs/hi/workflow/triggers/collection.md index 581581f63ca..ac5d197712d 100644 --- a/docs/docs/hi/workflow/triggers/collection.md +++ b/docs/docs/hi/workflow/triggers/collection.md @@ -21,7 +21,7 @@ आप अपनी व्यावसायिक आवश्यकताओं के अनुसार ट्रिगर होने का समय चुन सकते हैं। जब चुने गए बदलावों में संग्रह को अपडेट करने की स्थिति शामिल होती है, तो आप उन फ़ील्ड्स को भी निर्दिष्ट कर सकते हैं जिनमें बदलाव हुए हैं। ट्रिगर की शर्त तभी पूरी होती है जब चुने गए फ़ील्ड्स में बदलाव होता है। यदि कोई फ़ील्ड नहीं चुना जाता है, तो इसका मतलब है कि किसी भी फ़ील्ड में बदलाव होने पर वर्कफ़्लो ट्रिगर हो सकता है। -![Collection Event_Select Changed Fields](https://static-docs.nocobase.com/874a175f01298b3c00267b2b4674611.png) +![Collection Event_Select Changed Fields](https://static-docs.nocobase.com/874a1475f01298b3c00267b2b4674611.png) अधिक विशिष्ट रूप से, आप ट्रिगर होने वाली डेटा पंक्ति के प्रत्येक फ़ील्ड के लिए शर्त नियम कॉन्फ़िगर कर सकते हैं। ट्रिगर तभी सक्रिय होगा जब फ़ील्ड संबंधित शर्तों को पूरा करेंगे। diff --git a/docs/docs/hi/workflow/triggers/post-action.md b/docs/docs/hi/workflow/triggers/post-action.md index e2ad5962972..fa326d62334 100644 --- a/docs/docs/hi/workflow/triggers/post-action.md +++ b/docs/docs/hi/workflow/triggers/post-action.md @@ -178,7 +178,7 @@ curl -X POST -H 'Authorization: Bearer ' -H 'X-Role: ' -d जैसा कि नीचे दिए गए चित्र में दिखाया गया है: -![Action Execution Order](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![Action Execution Order](https://static-docs.nocobase.com/20251219234806.png) ### संग्रह घटना से अंतर diff --git a/docs/docs/hi/workflow/triggers/pre-action.md b/docs/docs/hi/workflow/triggers/pre-action.md index 7e83636ea20..dc8f0443432 100644 --- a/docs/docs/hi/workflow/triggers/pre-action.md +++ b/docs/docs/hi/workflow/triggers/pre-action.md @@ -34,7 +34,7 @@ pkg: '@nocobase/plugin-workflow-request-interceptor' ### अवरोधन मोड -![अवरोधन इवेंट कॉन्फ़िगरेशन_अवरोधन मोड](https://static-docs.nocobase.com/145f7c3ba440bb6ca93a5ee84f16e2.png) +![अवरोधन इवेंट कॉन्फ़िगरेशन_अवरोधन मोड](https://static-docs.nocobase.com/145a7f7c3ba440bb6ca93a5ee84f16e2.png) वर्तमान में समर्थित कार्रवाई प्रकार 'बनाना', 'अपडेट करना' और 'हटाना' हैं। एक साथ कई कार्रवाई प्रकार चुने जा सकते हैं। @@ -85,7 +85,7 @@ pkg: '@nocobase/plugin-workflow-request-interceptor' इस बिंदु पर, संबंधित वर्कफ़्लो का कॉन्फ़िगरेशन पूरा हो गया है। अब आप ऐसे डेटा को सबमिट करने का प्रयास कर सकते हैं जो वर्कफ़्लो के शर्त नोड में कॉन्फ़िगर की गई शर्तों को पूरा नहीं करता है, ताकि अवरोधन तर्क को ट्रिगर किया जा सके। तब आप वापस भेजा गया प्रतिक्रिया संदेश देख सकते हैं: -![त्रुटि प्रतिक्रिया संदेश](https://static-docs.nocobase.com/06bd4a6b6ec493f0c39987f63a6a.png) +![त्रुटि प्रतिक्रिया संदेश](https://static-docs.nocobase.com/06bd4a6b6ec499c853f0c39987f63a6a.png) ### प्रतिक्रिया संदेश की स्थिति @@ -107,11 +107,11 @@ pkg: '@nocobase/plugin-workflow-request-interceptor' लूप के भीतर शर्त नोड का उपयोग यह निर्धारित करने के लिए किया जाता है कि लूप में वर्तमान उत्पाद ऑब्जेक्ट का स्टॉक पर्याप्त है या नहीं: -![उदाहरण_लूप में शर्त](https://static-docs.nocobase.com/4af9112934b0a04a4ce55e657c0833b.png) +![उदाहरण_लूप में शर्त](https://static-docs.nocobase.com/4af91112934b0a04a4ce55e657c0833b.png) अन्य कॉन्फ़िगरेशन बुनियादी उपयोग में समान हैं। जब अंततः ऑर्डर सबमिट किया जाता है, यदि किसी भी उत्पाद का स्टॉक अपर्याप्त है, तो ऑर्डर सबमिशन को रोक दिया जाएगा, और एक संबंधित संकेत संदेश वापस किया जाएगा। परीक्षण के दौरान, कई उत्पादों के साथ एक ऑर्डर सबमिट करने का प्रयास करें, जहाँ एक का स्टॉक अपर्याप्त है और दूसरे का स्टॉक पर्याप्त है। आप वापस भेजा गया प्रतिक्रिया संदेश देख सकते हैं: -![उदाहरण_सबमिशन के बाद प्रतिक्रिया संदेश](https://static-docs.nocobase.com/dd9e81084aa237d5629595ab6cf00f8aa898e3.png) +![उदाहरण_सबमिशन के बाद प्रतिक्रिया संदेश](https://static-docs.nocobase.com/dd9e81084aa237bda0241d399ac19270.png) जैसा कि आप देख सकते हैं, प्रतिक्रिया संदेश में पहले उत्पाद 'iPhone 15 pro' के स्टॉक की कमी का संकेत नहीं दिया गया है, बल्कि केवल दूसरे उत्पाद 'iPhone 14 pro' के स्टॉक की कमी का संकेत दिया गया है। ऐसा इसलिए है क्योंकि लूप में, पहले उत्पाद का स्टॉक पर्याप्त है, इसलिए इसे रोका नहीं गया, जबकि दूसरे उत्पाद का स्टॉक अपर्याप्त है, जिसने ऑर्डर सबमिशन को रोक दिया। diff --git a/docs/docs/id/auth-verification/api-keys/index.md b/docs/docs/id/auth-verification/api-keys/index.md index 5a86aaf029b..1c80b3563b5 100644 --- a/docs/docs/id/auth-verification/api-keys/index.md +++ b/docs/docs/id/auth-verification/api-keys/index.md @@ -18,7 +18,7 @@ http://localhost:13000/admin/settings/api-keys/configuration ### Menambahkan Kunci API -![](https://static-docs.nocobase.com/461872fc0ad9a96fa5b14e97fcba12.png) +![](https://static-docs.nocobase.com/46141872fc0ad9a96fa5b14e97fcba12.png) **Catatan** diff --git a/docs/docs/id/auth-verification/auth-oidc/examples/google.md b/docs/docs/id/auth-verification/auth-oidc/examples/google.md index b578684e1e4..e18296ffbec 100644 --- a/docs/docs/id/auth-verification/auth-oidc/examples/google.md +++ b/docs/docs/id/auth-verification/auth-oidc/examples/google.md @@ -14,7 +14,7 @@ Dokumen ini diterjemahkan oleh AI. Untuk ketidakakuratan apa pun, silakan lihat Masuk ke antarmuka konfigurasi dan isi URL pengalihan yang diotorisasi. URL pengalihan dapat diperoleh saat menambahkan autentikator di NocoBase, biasanya adalah `http(s)://host:port/api/oidc:redirect`. Lihat bagian [Panduan Pengguna - Konfigurasi](../index.md#konfigurasi). -![](https://static-docs.nocobase.com/2407bf52ec966a16334894cb3d9d126.png) +![](https://static-docs.nocobase.com/24078bf52ec966a16334894cb3d9d126.png) ## Tambahkan Autentikator Baru di NocoBase diff --git a/docs/docs/id/auth-verification/auth-saml/examples/google.md b/docs/docs/id/auth-verification/auth-saml/examples/google.md index 3a05400ebab..849289dcda9 100644 --- a/docs/docs/id/auth-verification/auth-saml/examples/google.md +++ b/docs/docs/id/auth-verification/auth-saml/examples/google.md @@ -12,7 +12,7 @@ Dokumen ini diterjemahkan oleh AI. Untuk ketidakakuratan apa pun, silakan lihat Setelah mengatur aplikasi, salin **URL SSO**, **ID Entitas**, dan **Sertifikat**. -![](https://static-docs.nocobase.com/aafd20a7930e85411c0c8f368637e0.png) +![](https://static-docs.nocobase.com/aafd20a794730e85411c0c8f368637e0.png) ## Menambahkan Autentikator Baru di NocoBase @@ -33,7 +33,7 @@ Kemudian salin SP Issuer/EntityID dan URL ACS dari bagian Penggunaan. Kembali ke Konsol Google, pada halaman **Detail Penyedia Layanan**, masukkan URL ACS dan ID Entitas yang telah disalin sebelumnya, lalu centang **Respons yang Ditandatangani**. -![](https://static-docs.nocobase.com/1536268bf8df4a5ebc7384317172191.png) +![](https://static-docs.nocobase.com/1536268bf8df4a5ebc72384317172191.png) ![](https://static-docs.nocobase.com/c7de1f8b84c1335de110e5a7c96255c4.png) diff --git a/docs/docs/id/data-sources/collection-fdw/index.md b/docs/docs/id/data-sources/collection-fdw/index.md index 09669fd7839..eae21f49007 100644 --- a/docs/docs/id/data-sources/collection-fdw/index.md +++ b/docs/docs/id/data-sources/collection-fdw/index.md @@ -57,7 +57,7 @@ Buat layanan basis data Setelah memilih layanan basis data, pada opsi *dropdown* "Tabel Jarak Jauh", pilih koleksi data yang ingin Anda hubungkan. -![Pilih koleksi data yang ingin dihubungkan](https://static-docs.nocobase.com/e91fd61552b52b4fc01b3808053cc8dc4.png) +![Pilih koleksi data yang ingin dihubungkan](https://static-docs.nocobase.com/e91fd6152b52b4fc01b3808053cc8dc4.png) Konfigurasi informasi bidang diff --git a/docs/docs/id/data-sources/data-modeling/collection-fields/associations/o2o/index.md b/docs/docs/id/data-sources/data-modeling/collection-fields/associations/o2o/index.md index e9992c3fc09..0fb0493ee7b 100644 --- a/docs/docs/id/data-sources/data-modeling/collection-fields/associations/o2o/index.md +++ b/docs/docs/id/data-sources/data-modeling/collection-fields/associations/o2o/index.md @@ -20,7 +20,7 @@ Relasi ER Konfigurasi Bidang -![alt text](https://static-docs.nocobase.com/765a87e094b4fb50c9426a108f87105.png) +![alt text](https://static-docs.nocobase.com/7665a87e094b4fb50c9426a108f87105.png) ## Satu-ke-Satu (Milik) @@ -32,7 +32,7 @@ Relasi ER Konfigurasi Bidang -![alt text](https://static-docs.nocobase.com/4f09eeb3c7717d61a3498242da43c187c.png) +![alt text](https://static-docs.nocobase.com/4f09eeb3c7717d61a349842da43c187c.png) ## Deskripsi Parameter diff --git a/docs/docs/id/data-sources/field-encryption/index.md b/docs/docs/id/data-sources/field-encryption/index.md index 61be1053c9a..f3fb2d5e7af 100644 --- a/docs/docs/id/data-sources/field-encryption/index.md +++ b/docs/docs/id/data-sources/field-encryption/index.md @@ -30,7 +30,7 @@ Jika `plugin` diaktifkan oleh sub-aplikasi, kunci akan disimpan secara default d Menggunakan metode Enkripsi Amplop (Envelope Encryption). -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### Proses Pembuatan Kunci 1. Saat pertama kali membuat bidang terenkripsi, sistem akan secara otomatis menghasilkan `kunci aplikasi` 32-bit dan menyimpannya ke direktori penyimpanan default dalam format Base64. diff --git a/docs/docs/id/data-visualization/guide/chart-options.md b/docs/docs/id/data-visualization/guide/chart-options.md index a9c517a9938..79dd3d003aa 100644 --- a/docs/docs/id/data-visualization/guide/chart-options.md +++ b/docs/docs/id/data-visualization/guide/chart-options.md @@ -47,7 +47,7 @@ Pilihan Mode: ### Properti Umum -![20251026191332](https://static-docs.nocobase.com/clipboard-image-1761473695.png) +![20251026191332](https://static-docs.nocobase.com/20251026191332.png) - Tumpuk, haluskan (garis/area) - Tampilan label, tooltip, legenda diff --git a/docs/docs/id/email-manager/advanced/batch-send.md b/docs/docs/id/email-manager/advanced/batch-send.md index f03c653e44f..3be1fbf5b25 100644 --- a/docs/docs/id/email-manager/advanced/batch-send.md +++ b/docs/docs/id/email-manager/advanced/batch-send.md @@ -10,27 +10,27 @@ Dokumen ini diterjemahkan oleh AI. Untuk ketidakakuratan apa pun, silakan lihat ## Gambaran Umum Pengiriman Massal Anda bisa mengirim email secara massal ke banyak orang (setiap penerima akan menerima email terpisah). -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## Pengiriman Massal Melalui Tabel Anda juga bisa mengirim email secara massal melalui tabel: 1. Tambahkan tombol kirim email ke tabel. - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. Konfigurasi kolom email di tabel (digunakan untuk mengurai alamat email setelah memilih baris tabel). - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. Centang data tabel untuk mengirim email. - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) Jika Anda perlu mengirim email ke semua alamat di seluruh tabel, Anda bisa mengaktifkan fitur **Pilih semua catatan di tabel saat ini sebagai penerima secara default**: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) Setelah mengedit konten email, klik tombol kirim massal untuk mengirim: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## Pelacakan Pengiriman Email Anda bisa melihat dan melacak status pengiriman email tertentu di Pusat Manajemen Email: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/id/email-manager/usage/signature.md b/docs/docs/id/email-manager/usage/signature.md index 0e665058866..412fb6d2bf7 100644 --- a/docs/docs/id/email-manager/usage/signature.md +++ b/docs/docs/id/email-manager/usage/signature.md @@ -11,15 +11,15 @@ Dokumen ini diterjemahkan oleh AI. Untuk ketidakakuratan apa pun, silakan lihat ## Konfigurasi Tanda Tangan Masuk ke Pusat Manajemen Email, lalu klik tombol pengaturan: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Beralih ke panel tanda tangan: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) Di sini Anda dapat mengelola tanda tangan. Centang opsi di depan tanda tangan untuk menjadikannya sebagai tanda tangan default: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## Penggunaan Tanda Tangan Di dalam kotak isi email, klik ikon tanda tangan untuk memilih tanda tangan yang Anda inginkan: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/id/email-manager/usage/template.md b/docs/docs/id/email-manager/usage/template.md index a0b3d470a91..ed1c1634f5b 100644 --- a/docs/docs/id/email-manager/usage/template.md +++ b/docs/docs/id/email-manager/usage/template.md @@ -11,15 +11,15 @@ Dokumen ini diterjemahkan oleh AI. Untuk ketidakakuratan apa pun, silakan lihat ## Konfigurasi Templat Masuk ke Pusat Manajemen Email dan klik tombol pengaturan: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Beralih ke panel templat: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) Di sini, Anda dapat mengelola templat: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## Menggunakan Templat Di kotak isi email, klik ikon templat untuk memilih templat yang diinginkan: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/id/flow-engine/learning-roadmap.md b/docs/docs/id/flow-engine/learning-roadmap.md index 25fde34d2be..9430ca1801a 100644 --- a/docs/docs/id/flow-engine/learning-roadmap.md +++ b/docs/docs/id/flow-engine/learning-roadmap.md @@ -4,4 +4,4 @@ Dokumen ini diterjemahkan oleh AI. Untuk ketidakakuratan apa pun, silakan lihat # Peta Jalan Pembelajaran -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/id/solution/ticket-system/design.md b/docs/docs/id/solution/ticket-system/design.md index f35e0bcc5c5..e8d1560ca0f 100755 --- a/docs/docs/id/solution/ticket-system/design.md +++ b/docs/docs/id/solution/ticket-system/design.md @@ -31,7 +31,7 @@ Mengambil inspirasi dari konsep "talenta berbentuk T" — keluasan horizontal + - **Horizontal (Tabel Utama)**: Mencakup kemampuan umum untuk semua tipe bisnis — nomor tiket, status, petugas, SLA, dan bidang inti lainnya. - **Vertikal (Tabel Ekstensi)**: Bidang khusus yang mendalami bisnis tertentu — perbaikan peralatan memiliki nomor seri, keluhan memiliki rencana kompensasi. -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **Mengapa didesain seperti ini?** @@ -61,7 +61,7 @@ Bukan sekadar "fitur AI", melainkan "karyawan AI". Setiap AI memiliki peran, kep #### Filosofi Tiga: Siklus Mandiri Pengetahuan -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) Ini membentuk lingkaran tertutup **Akumulasi Pengetahuan - Aplikasi Pengetahuan**. @@ -71,7 +71,7 @@ Ini membentuk lingkaran tertutup **Akumulasi Pengetahuan - Aplikasi Pengetahuan* ### 2.1 Ikhtisar Hubungan Entitas -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 Detail Tabel Inti @@ -296,18 +296,18 @@ Ini adalah inti dari sistem, menggunakan desain "tabel lebar" (wide table) yang **Alur Utama (Dari Kiri ke Kanan)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **Alur Cabang** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **State Machine Lengkap** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 Aturan Transisi Status Utama @@ -337,7 +337,7 @@ Ini adalah inti dari sistem, menggunakan desain "tabel lebar" (wide table) yang ### 4.2 Logika Perhitungan SLA -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### Saat Membuat Tiket @@ -466,7 +466,7 @@ Setiap karyawan AI dikonfigurasi dengan 4 tugas spesifik: ### 5.3 Karyawan AI dan Siklus Hidup Tiket -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 Contoh Respons AI @@ -528,12 +528,12 @@ Audit kualitas balasan yang dikelola oleh Grace akan memblokir masalah berikut: ### 6.1 Sumber Pengetahuan -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 Alur Konversi Tiket ke Pengetahuan -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **Dimensi Evaluasi**: - **Generalitas**: Apakah ini masalah umum? @@ -580,19 +580,19 @@ Saat staf membuka detail tiket, Max secara otomatis merekomendasikan pengetahuan #### WF-T01: Alur Pembuatan Tiket -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: Analisis AI Tiket -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: Terjemahan dan Audit Komentar -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: Pembuatan Pengetahuan -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 Tugas Terjadwal @@ -609,11 +609,11 @@ Saat staf membuka detail tiket, Max secara otomatis merekomendasikan pengetahuan ### 8.1 Admin Backend -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 Portal Pelanggan -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 Desain Dasbor diff --git a/docs/docs/id/users-permissions/acl/permissions.md b/docs/docs/id/users-permissions/acl/permissions.md index fb79ccae081..ef68785b46c 100644 --- a/docs/docs/id/users-permissions/acl/permissions.md +++ b/docs/docs/id/users-permissions/acl/permissions.md @@ -26,7 +26,7 @@ Izin tindakan global berlaku secara universal untuk semua **koleksi** dan dikate ## Izin Tindakan Koleksi -![](https://static-docs.nocobase.com/6a6e0281939cecdea5b5218e6173c5d7.png) +![](https://static-docs.nocobase.com/6a6e0281391cecdea5b5218e6173c5d7.png) ![](https://static-docs.nocobase.com/9814140434ff9e1bf028a6c282a5a165.png) diff --git a/docs/docs/id/users-permissions/acl/ui.md b/docs/docs/id/users-permissions/acl/ui.md index dcb637efb4a..a0825b59a64 100644 --- a/docs/docs/id/users-permissions/acl/ui.md +++ b/docs/docs/id/users-permissions/acl/ui.md @@ -50,7 +50,7 @@ Di UI, hanya kolom dengan izin yang dikonfigurasi yang terlihat dalam blok kolek Proses konfigurasi lengkap: - ![](https://static-docs.nocobase.com/1dbe559a957c2e052e194e50edc74a7.gif) + ![](https://static-docs.nocobase.com/1dbe559a9579c2e052e194e50edc74a7.gif) - **Tambah**: Menentukan apakah kolom dapat ditambahkan (dibuat). diff --git a/docs/docs/id/workflow/advanced/variables.md b/docs/docs/id/workflow/advanced/variables.md index 95405d7dfa0..6d3f0a2962d 100644 --- a/docs/docs/id/workflow/advanced/variables.md +++ b/docs/docs/id/workflow/advanced/variables.md @@ -21,7 +21,7 @@ Kami telah menggunakan fitur variabel berkali-kali di [Memulai Cepat](../getting Di node pembaruan, gunakan data konteks pemicu sebagai variabel untuk kondisi filter, dan referensikan hasil dari node perhitungan sebagai variabel untuk nilai bidang data yang akan diperbarui: -![Variabel node pembaruan data](https://static-docs.nocobase.com/2e147c9364e7ebc709b9b7ab4f3af8c.png) +![Variabel node pembaruan data](https://static-docs.nocobase.com/2e147c93643e7ebc709b9b7ab4f3af8c.png) ## Struktur Data diff --git a/docs/docs/id/workflow/nodes/manual.md b/docs/docs/id/workflow/nodes/manual.md index c2130b8e373..666c760be14 100644 --- a/docs/docs/id/workflow/nodes/manual.md +++ b/docs/docs/id/workflow/nodes/manual.md @@ -104,11 +104,11 @@ Untuk penanganan manual, Anda juga perlu menambahkan daftar tugas yang perlu dit Anda dapat memilih "Tugas Alur Kerja yang Perlu Ditindaklanjuti" dari blok di halaman untuk menambahkan blok daftar tugas yang perlu ditindaklanjuti: -![Node Manual_Menambahkan Blok Tugas yang Perlu Ditindaklanjuti](https://static-docs.nocobase.com/198b41754cd73b704267bf30fe5e647.png) +![Node Manual_Menambahkan Blok Tugas yang Perlu Ditindaklanjuti](https://static-docs.nocobase.com/198b417454cd73b704267bf30fe5e647.png) Contoh blok daftar tugas yang perlu ditindaklanjuti: -![Node Manual_Daftar Tugas yang Perlu Ditindaklanjuti](https://static-docs.nocobase.com/cfefb0533deebff6b3f6ef4408066e688.png) +![Node Manual_Daftar Tugas yang Perlu Ditindaklanjuti](https://static-docs.nocobase.com/cfefb0d2c6a91c5c9dfa550d6b220f34.png) ### Detail Tugas yang Perlu Ditindaklanjuti diff --git a/docs/docs/id/workflow/nodes/response-message.md b/docs/docs/id/workflow/nodes/response-message.md index c4ccdada56a..37a932cd1ce 100644 --- a/docs/docs/id/workflow/nodes/response-message.md +++ b/docs/docs/id/workflow/nodes/response-message.md @@ -21,7 +21,7 @@ Saat ini, fitur ini didukung untuk digunakan dalam alur kerja jenis "Peristiwa P Pada jenis alur kerja yang didukung, Anda dapat menambahkan node "Pesan respons" di mana saja dalam alur kerja. Cukup klik tombol plus ("+") pada alur kerja untuk menambahkannya: -![Menambahkan node](https://static-docs.nocobase.com/eac2b3566e95e4ce59f340624062ed3d.png) +![Menambahkan node](https://static-docs.nocobase.com/eac2b3565e95e4ce59f340624062ed3d.png) Pesan respons akan ada sebagai array sepanjang proses permintaan. Setiap kali node pesan respons dieksekusi dalam alur kerja, konten pesan baru akan ditambahkan ke array tersebut. Ketika server mengirimkan respons, semua pesan akan dikirimkan ke klien secara bersamaan. @@ -37,7 +37,7 @@ Ketika alur kerja mengeksekusi node ini, template akan diurai untuk menghasilkan Stok produk "iPhone 14 pro" tidak mencukupi ``` -![Konten pesan](https://static-docs.nocobase.com/06bd4a6b6ec499c83f0c39987f63a6a.png) +![Konten pesan](https://static-docs.nocobase.com/06bd4a6b6ec499c853f0c39987f63a6a.png) ## Konfigurasi Alur Kerja diff --git a/docs/docs/id/workflow/nodes/variable.md b/docs/docs/id/workflow/nodes/variable.md index 6f50a23e6db..455c8d5c366 100644 --- a/docs/docs/id/workflow/nodes/variable.md +++ b/docs/docs/id/workflow/nodes/variable.md @@ -17,7 +17,7 @@ Anda dapat mendeklarasikan variabel dalam sebuah alur kerja atau menetapkan nila Pada antarmuka konfigurasi alur kerja, klik tombol plus ("+") di alur kerja untuk menambahkan node "Variabel": -![Menambahkan Node Variabel](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![Menambahkan Node Variabel](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## Mengonfigurasi Node @@ -42,7 +42,7 @@ Nilai variabel dapat berupa tipe apa pun. Ini bisa berupa konstanta, seperti str Dalam mode deklarasi, menetapkan nilai variabel setara dengan memberinya nilai awal. -![Mendeklarasikan nilai awal](https://static-docs.nocobase.com/4ce2c50896565ad537343013758c6a4.png) +![Mendeklarasikan nilai awal](https://static-docs.nocobase.com/4ce2c508986565ad537343013758c6a4.png) Dalam mode penetapan nilai, menetapkan nilai variabel setara dengan memodifikasi nilai variabel target yang sudah dideklarasikan menjadi nilai baru. Penggunaan selanjutnya akan mengambil nilai baru ini. diff --git a/docs/docs/id/workflow/triggers/post-action.md b/docs/docs/id/workflow/triggers/post-action.md index e78470aa6b6..84c33cb41b8 100644 --- a/docs/docs/id/workflow/triggers/post-action.md +++ b/docs/docs/id/workflow/triggers/post-action.md @@ -178,7 +178,7 @@ Jika event dikonfigurasi dalam mode global, Anda tidak perlu menggunakan paramet Seperti yang ditunjukkan pada gambar di bawah ini: -![Action Execution Order](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![Action Execution Order](https://static-docs.nocobase.com/20251219234806.png) ### Perbedaan dengan Event Koleksi diff --git a/docs/docs/id/workflow/triggers/pre-action.md b/docs/docs/id/workflow/triggers/pre-action.md index b1ed4ff11e9..f97782f213d 100644 --- a/docs/docs/id/workflow/triggers/pre-action.md +++ b/docs/docs/id/workflow/triggers/pre-action.md @@ -91,7 +91,7 @@ Pada titik ini, konfigurasi alur kerja yang sesuai telah selesai. Anda sekarang Jika node "Akhiri alur kerja" dikonfigurasi untuk keluar dengan status "Berhasil", permintaan aksi akan tetap diinterupsi saat node ini dieksekusi, tetapi pesan respons yang dikembalikan akan ditampilkan dengan status "Berhasil" (bukan "Kesalahan"): -![Pesan Respons Status Berhasil](https://static-docs.nocobase.com/9559bbf5607144759451294b18c790e.png) +![Pesan Respons Status Berhasil](https://static-docs.nocobase.com/9559bbf56067144759451294b18c790e.png) ## Contoh diff --git a/docs/docs/id/workflow/triggers/schedule.md b/docs/docs/id/workflow/triggers/schedule.md index ff9cc150463..3c5b77b7056 100644 --- a/docs/docs/id/workflow/triggers/schedule.md +++ b/docs/docs/id/workflow/triggers/schedule.md @@ -74,6 +74,6 @@ Buat **alur kerja** berbasis tugas terjadwal. Dalam konfigurasi pemicu, pilih mo Selanjutnya, konfigurasikan node lain sesuai dengan logika proses untuk memperbarui status pesanan dengan ID data pemicu dan status "belum dibayar" menjadi dibatalkan: -![Tugas Terjadwal_Konfigurasi Pemicu_Mode Kolom Waktu Koleksi_Node Pembaruan](https://static-docs.nocobase.com/491dde9df77a1fb24a4e7baa1de6eb29.png) +![Tugas Terjadwal_Konfigurasi Pemicu_Mode Kolom Waktu Koleksi_Node Pembaruan](https://static-docs.nocobase.com/491dde9df8f773f5b14a4fd8ceac9d3e.png) Berbeda dengan mode waktu kustom, di sini tidak perlu menghitung waktu 30 menit yang lalu, karena konteks data pemicu **alur kerja** sudah berisi baris data yang memenuhi kondisi waktu, sehingga Anda dapat langsung memperbarui status pesanan yang sesuai. \ No newline at end of file diff --git a/docs/docs/it/ai-employees/permission.md b/docs/docs/it/ai-employees/permission.md index 2b69cf1b3ea..07f01bd3cb4 100644 --- a/docs/docs/it/ai-employees/permission.md +++ b/docs/docs/it/ai-employees/permission.md @@ -74,7 +74,7 @@ Questi strumenti sono tipicamente utilizzati per: #### Esempio 1: Overall Analytics (Analisi aziendale generale) -![05viz-configuration-2025-11-03-00-18-55](https://static-docs.nocobase.com/20251022013802.png) +![05viz-configuration-2025-11-03-00-18-55](https://static-docs.nocobase.com/05viz-configuration-2025-11-03-00-18-55.png) Nella demo CRM, `Overall Analytics` è un motore di analisi aziendale basato su modelli: @@ -104,7 +104,7 @@ flowchart TD #### Esempio 2: SQL Execution (Strumento di analisi avanzata) -![05viz-configuration-2025-11-03-00-17-13](https://static-docs.nocobase.com/20251022013942.png) +![05viz-configuration-2025-11-03-00-17-13](https://static-docs.nocobase.com/05viz-configuration-2025-11-03-00-17-13.png) Nella demo CRM, `SQL Execution` è uno strumento più flessibile ma che richiede un controllo rigoroso: diff --git a/docs/docs/it/auth-verification/auth-oidc/index.md b/docs/docs/it/auth-verification/auth-oidc/index.md index c88095fe8a7..60955e10555 100644 --- a/docs/docs/it/auth-verification/auth-oidc/index.md +++ b/docs/docs/it/auth-verification/auth-oidc/index.md @@ -44,7 +44,7 @@ Aggiungi - OIDC ### Mappatura dei campi -![](https://static-docs.nocobase.com/92d63c8f6082b50d9f475674cb5650.png) +![](https://static-docs.nocobase.com/92d63c8f6f4082b50d9f475674cb5650.png) | Configurazione | Descrizione | | :---------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/docs/docs/it/auth-verification/auth-saml/examples/google.md b/docs/docs/it/auth-verification/auth-saml/examples/google.md index 0d0f5825b97..6db48c54464 100644 --- a/docs/docs/it/auth-verification/auth-saml/examples/google.md +++ b/docs/docs/it/auth-verification/auth-saml/examples/google.md @@ -12,7 +12,7 @@ Questa documentazione è stata tradotta automaticamente dall'IA. Dopo aver configurato l'applicazione, copiare l'**URL SSO**, l'**ID entità** e il **Certificato**. -![](https://static-docs.nocobase.com/aafd0a794730e85411c0c8f368637e0.png) +![](https://static-docs.nocobase.com/aafd20a794730e85411c0c8f368637e0.png) ## Aggiungere un nuovo autenticatore su NocoBase @@ -33,7 +33,7 @@ Quindi, copiare l'Emittente SP/ID entità e l'URL ACS dalla sezione "Utilizzo". Tornare alla Console Google, nella pagina **Dettagli del provider di servizi**, inserire l'URL ACS e l'ID entità copiati in precedenza e selezionare **Risposta firmata**. -![](https://static-docs.nocobase.com/1536268bf8df4a5ebc7234317172191.png) +![](https://static-docs.nocobase.com/1536268bf8df4a5ebc72384317172191.png) ![](https://static-docs.nocobase.com/c7de1f8b84c1335de110e5a7c96255c4.png) diff --git a/docs/docs/it/auth-verification/auth-saml/index.md b/docs/docs/it/auth-verification/auth-saml/index.md index 6638284237a..2b52c352dce 100644 --- a/docs/docs/it/auth-verification/auth-saml/index.md +++ b/docs/docs/it/auth-verification/auth-saml/index.md @@ -28,7 +28,7 @@ Aggiungi - SAML ## Configurazione -![](https://static-docs.nocobase.com/976b63e589973c322d81dcddd22c6146.png) +![](https://static-docs.nocobase.com/976b66e589973c322d81dcddd22c6146.png) - SSO URL - Fornito dall'IdP, utilizzato per il Single Sign-On (SSO). - Certificato Pubblico - Fornito dall'IdP. diff --git a/docs/docs/it/auth-verification/auth/dev/index.md b/docs/docs/it/auth-verification/auth/dev/index.md index 53339367ad8..afd153c80ee 100644 --- a/docs/docs/it/auth-verification/auth/dev/index.md +++ b/docs/docs/it/auth-verification/auth/dev/index.md @@ -162,7 +162,7 @@ Solitamente si tratta di un pulsante di accesso di terze parti, ma può essere q ### Modulo di registrazione -![](https://static-docs.nocobase.com/f5c53431bf21ec312fcfd51923f0b42.png) +![](https://static-docs.nocobase.com/f95c53431bf21ec312fcfd51923f0b42.png) Se è necessario passare dalla pagina di accesso a quella di registrazione, dovrà gestire questo passaggio autonomamente nel componente di accesso. diff --git a/docs/docs/it/data-sources/data-modeling/collection-fields/associations/m2o/index.md b/docs/docs/it/data-sources/data-modeling/collection-fields/associations/m2o/index.md index 07e2df0bf82..1cc20f47bb2 100644 --- a/docs/docs/it/data-sources/data-modeling/collection-fields/associations/m2o/index.md +++ b/docs/docs/it/data-sources/data-modeling/collection-fields/associations/m2o/index.md @@ -8,7 +8,7 @@ In un database di una biblioteca, abbiamo due entità: libri e autori. Un autore Diagramma ER: -![alt text](https://static-docs.nocobase.com/eaeeac974844db05c75cf0deeedf362.png) +![alt text](https://static-docs.nocobase.com/eaeeac974844db05c75cf0deeedf3652.png) Configurazione del campo: diff --git a/docs/docs/it/data-sources/data-modeling/collection-fields/associations/o2m/index.md b/docs/docs/it/data-sources/data-modeling/collection-fields/associations/o2m/index.md index aa2e20630be..3dbda7185ef 100644 --- a/docs/docs/it/data-sources/data-modeling/collection-fields/associations/o2m/index.md +++ b/docs/docs/it/data-sources/data-modeling/collection-fields/associations/o2m/index.md @@ -12,7 +12,7 @@ Diagramma ER: Configurazione del Campo: -![alt text](https://static-docs.nocobase.com/a608ce54821172dad8e56a077411f8dc.png) +![alt text](https://static-docs.nocobase.com/a608ce54821172dad7e8ab760107ff4e.png) ## Descrizione dei Parametri diff --git a/docs/docs/it/data-sources/field-encryption/index.md b/docs/docs/it/data-sources/field-encryption/index.md index c492f22cff4..1624b13c00b 100644 --- a/docs/docs/it/data-sources/field-encryption/index.md +++ b/docs/docs/it/data-sources/field-encryption/index.md @@ -30,7 +30,7 @@ Se il plugin è abilitato da una sotto-applicazione, la chiave viene salvata di Utilizza la crittografia a busta (Envelope Encryption). -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### Processo di creazione della chiave 1. La prima volta che viene creato un campo crittografato, il sistema genera automaticamente una `chiave applicazione` a 32 bit, che viene salvata nella directory di archiviazione predefinita con codifica Base64. diff --git a/docs/docs/it/email-manager/advanced/batch-send.md b/docs/docs/it/email-manager/advanced/batch-send.md index 61f31b384e3..7897e493d9c 100644 --- a/docs/docs/it/email-manager/advanced/batch-send.md +++ b/docs/docs/it/email-manager/advanced/batch-send.md @@ -10,27 +10,27 @@ Questa documentazione è stata tradotta automaticamente dall'IA. ## Panoramica sull'Invio in Blocco È possibile inviare email a più persone in blocco (ogni destinatario riceverà un'email separata). -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## Invio in Blocco tramite Tabella È anche possibile inviare email in blocco tramite una tabella: 1. Aggiunga un pulsante per l'invio di email alla tabella - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. Configuri il campo email nella tabella (utilizzato per analizzare gli indirizzi email dopo aver selezionato le righe della tabella) - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. Selezioni i dati della tabella per inviare le email - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) Se ha bisogno di inviare email a tutti gli indirizzi presenti nell'intera tabella, può abilitare la funzione **Seleziona tutte le voci della tabella corrente come destinatari per impostazione predefinita**: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) Dopo aver modificato il contenuto dell'email, clicchi sul pulsante di invio in blocco per inviare: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## Tracciamento dell'Invio di Email Può visualizzare e tracciare lo stato specifico dell'invio delle email nel Centro di Gestione Email: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/it/email-manager/usage/signature.md b/docs/docs/it/email-manager/usage/signature.md index 6b1383e87ed..7edc4b0e338 100644 --- a/docs/docs/it/email-manager/usage/signature.md +++ b/docs/docs/it/email-manager/usage/signature.md @@ -11,15 +11,15 @@ Questa documentazione è stata tradotta automaticamente dall'IA. ## Configurazione della Firma Vada al Centro di Gestione Email e clicchi sul pulsante delle impostazioni: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Passi al pannello della firma: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) Qui può gestire le firme. Selezioni l'opzione prima di una firma per impostarla come predefinita: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## Utilizzo delle Firme Nel corpo dell'email, clicchi sull'icona della firma per selezionare la firma desiderata: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/it/email-manager/usage/template.md b/docs/docs/it/email-manager/usage/template.md index e8129f44181..834395109b8 100644 --- a/docs/docs/it/email-manager/usage/template.md +++ b/docs/docs/it/email-manager/usage/template.md @@ -11,15 +11,15 @@ Questa documentazione è stata tradotta automaticamente dall'IA. ## Configurazione dei Modelli Acceda al Centro di Gestione Email e clicchi sul pulsante delle impostazioni: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Passi al pannello dei modelli: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) Qui può gestire i modelli: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## Utilizzo dei Modelli Nella casella del corpo dell'email, clicchi sull'icona del modello per selezionare quello desiderato: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/it/flow-engine/learning-roadmap.md b/docs/docs/it/flow-engine/learning-roadmap.md index 6fe06727e65..d6c9130d852 100644 --- a/docs/docs/it/flow-engine/learning-roadmap.md +++ b/docs/docs/it/flow-engine/learning-roadmap.md @@ -4,4 +4,4 @@ Questa documentazione è stata tradotta automaticamente dall'IA. # Percorso di apprendimento -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/it/solution/ticket-system/design.md b/docs/docs/it/solution/ticket-system/design.md index cfa990f06a9..b29b21e7624 100755 --- a/docs/docs/it/solution/ticket-system/design.md +++ b/docs/docs/it/solution/ticket-system/design.md @@ -31,7 +31,7 @@ Si ispira al concetto di "talento a forma di T": ampiezza orizzontale + profondi - **Orizzontale (Tabella principale)**: Copre le funzionalità comuni a tutti i tipi di business: numero ticket, stato, assegnatario, SLA e altri campi fondamentali. - **Verticale (Tabelle di estensione)**: Campi specializzati per specifici settori di attività: la riparazione di apparecchiature ha numeri di serie, i reclami hanno piani di compensazione. -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **Perché questa progettazione?** @@ -61,7 +61,7 @@ Non semplici "funzionalità IA", ma veri e propri "dipendenti IA". Ogni IA ha un #### Filosofia 3: Auto-circolazione della conoscenza -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) Questo crea un ciclo chiuso di **Accumulo di conoscenza - Applicazione della conoscenza**. @@ -71,7 +71,7 @@ Questo crea un ciclo chiuso di **Accumulo di conoscenza - Applicazione della con ### 2.1 Panoramica delle relazioni tra entità -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 Dettaglio delle tabelle principali @@ -296,18 +296,18 @@ Questo è il cuore del sistema, che utilizza un design a "tabella larga" inseren **Flusso principale (da sinistra a destra)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **Flussi secondari** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **Macchina a stati completa** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 Regole chiave per la transizione di stato @@ -337,7 +337,7 @@ Questo è il cuore del sistema, che utilizza un design a "tabella larga" inseren ### 4.2 Logica di calcolo SLA -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### Alla creazione del ticket @@ -466,7 +466,7 @@ Ogni dipendente IA ha 4 attività specifiche configurate: ### 5.3 Dipendenti IA e ciclo di vita del ticket -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 Esempi di risposta IA @@ -526,12 +526,12 @@ La revisione della qualità delle risposte affidata a Grace intercetta i seguent ### 6.1 Fonti di conoscenza -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 Flusso da ticket a conoscenza -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **Dimensioni di valutazione**: - **Generalità**: È un problema comune? @@ -576,19 +576,19 @@ Quando l'operatore apre i dettagli del ticket, Max raccomanda automaticamente la #### WF-T01: Flusso creazione ticket -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: Analisi IA ticket -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: Traduzione e revisione commenti -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: Generazione conoscenza -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 Attività pianificate @@ -605,11 +605,11 @@ Quando l'operatore apre i dettagli del ticket, Max raccomanda automaticamente la ### 8.1 Pannello di amministrazione backend -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 Portale clienti -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 Design delle Dashboard diff --git a/docs/docs/it/users-permissions/acl/role.md b/docs/docs/it/users-permissions/acl/role.md index 292f443c6cf..267f8f3b57f 100644 --- a/docs/docs/it/users-permissions/acl/role.md +++ b/docs/docs/it/users-permissions/acl/role.md @@ -26,7 +26,7 @@ L'identificatore del ruolo, che è un identificatore univoco di sistema, Le perm Il ruolo predefinito è quello che viene assegnato automaticamente ai nuovi utenti se non viene specificato un ruolo specifico durante la loro creazione. -![](https://static-docs.nocobase.com/f41b47ff55ca28715c486dc45bc1708.png) +![](https://static-docs.nocobase.com/f41bba7ff55ca28715c486dc45bc1708.png) ## Centro Personale diff --git a/docs/docs/it/users-permissions/user.md b/docs/docs/it/users-permissions/user.md index 020dfd992d8..57ec5d90c46 100644 --- a/docs/docs/it/users-permissions/user.md +++ b/docs/docs/it/users-permissions/user.md @@ -16,11 +16,11 @@ Questo plugin offre un'interfaccia di gestione utenti all'interno del centro di Inoltre, può anche aggiungere diversi blocchi dalla collezione Utenti nelle pagine per gestire gli utenti, come ad esempio i blocchi tabella: -![](https://static-docs.nocobase.com/76b5a65d4659e8f18a4568a7c9.png) +![](https://static-docs.nocobase.com/76b5a4652f869541a9e8f18a4568a7c9.png) ## Aggiungere Utente -![](https://static-docs.nocobase.com/4f8ef9ffc17f275b62b462f6385b19.png) +![](https://static-docs.nocobase.com/4f8ef9ffc1c17f275b62b462f6385b19.png) ![](https://static-docs.nocobase.com/437828173950bd7c21b40a6243ffe150.png) diff --git a/docs/docs/it/workflow/advanced/revisions.md b/docs/docs/it/workflow/advanced/revisions.md index e85c02ca661..a0c3e882688 100644 --- a/docs/docs/it/workflow/advanced/revisions.md +++ b/docs/docs/it/workflow/advanced/revisions.md @@ -12,7 +12,7 @@ Nella pagina di configurazione del flusso di lavoro, può visualizzare le versio Nel menu "Altre azioni" ("...") alla sua destra, può scegliere di copiare la versione attualmente visualizzata in una nuova versione: -![Copiare il flusso di lavoro in una nuova versione](https://static-docs.nocobase.com/280598e6caca2af004893390a744256.png) +![Copiare il flusso di lavoro in una nuova versione](https://static-docs.nocobase.com/2805798e6caca2af004893390a744256.png) Dopo aver copiato in una nuova versione, clicchi l'interruttore "Abilita"/"Disabilita" per portare la versione corrispondente allo stato abilitato, e la nuova versione del flusso di lavoro entrerà in vigore. diff --git a/docs/docs/it/workflow/advanced/variables.md b/docs/docs/it/workflow/advanced/variables.md index 32b133077fd..bc88459c9b2 100644 --- a/docs/docs/it/workflow/advanced/variables.md +++ b/docs/docs/it/workflow/advanced/variables.md @@ -21,7 +21,7 @@ Abbiamo già utilizzato più volte la funzionalità delle variabili in [Guida ra In un nodo di aggiornamento, si utilizzano i dati di contesto del trigger come variabile per la condizione di filtro, e si fa riferimento al risultato del nodo di calcolo come variabile per il valore del campo da aggiornare: -![Variabili del nodo di aggiornamento dati](https://static-docs.nocobase.com/2e17c93643e7ebc709b9b7ab4f3af8c.png) +![Variabili del nodo di aggiornamento dati](https://static-docs.nocobase.com/2e147c93643e7ebc709b9b7ab4f3af8c.png) ## Struttura dei dati diff --git a/docs/docs/it/workflow/nodes/destroy.md b/docs/docs/it/workflow/nodes/destroy.md index d8a4acae1f9..1399fa11a67 100644 --- a/docs/docs/it/workflow/nodes/destroy.md +++ b/docs/docs/it/workflow/nodes/destroy.md @@ -20,7 +20,7 @@ Nell'interfaccia di configurazione del flusso di lavoro, clicchi sul pulsante pi ## Configurazione del nodo -![Nodo di eliminazione_Configurazione del nodo](https://static-docs.nocobase.com/580600c2b1ef4e01dfa48b23539648e.png) +![Nodo di eliminazione_Configurazione del nodo](https://static-docs.nocobase.com/580600c2b13ef4e01dfa48b23539648e.png) ### Collezione diff --git a/docs/docs/it/workflow/nodes/end.md b/docs/docs/it/workflow/nodes/end.md index 89b7c4e0235..a04e1c9f83e 100644 --- a/docs/docs/it/workflow/nodes/end.md +++ b/docs/docs/it/workflow/nodes/end.md @@ -14,7 +14,7 @@ Nell'interfaccia di configurazione del flusso di lavoro, clicchi sul pulsante pi ## Configurazione del nodo -![End Workflow_Node Configuration](https://static-docs.nocobase.com/bb6a597f25e9afb72836a140fe0683e.png) +![End Workflow_Node Configuration](https://static-docs.nocobase.com/bb6a597f25e9afb72836a14a0fe0683e.png) ### Stato di conclusione diff --git a/docs/docs/it/workflow/nodes/manual.md b/docs/docs/it/workflow/nodes/manual.md index 944603b77b7..250f7d8d818 100644 --- a/docs/docs/it/workflow/nodes/manual.md +++ b/docs/docs/it/workflow/nodes/manual.md @@ -32,7 +32,7 @@ Un nodo manuale richiede che Lei specifichi un utente come responsabile dell'ese Selezioni un utente, oppure selezioni la chiave primaria o la chiave esterna dei dati utente dal contesto tramite una variabile. -![Nodo Manuale_Configurazione_Responsabile_Selezionare Variabile](https://static-docs.nocobase.com/22fbca3b8e21fda3a813019037001445.png) +![Nodo Manuale_Configurazione_Responsabile_Selezionare Variabile](https://static-docs.nocobase.com/22fbca3b8e21fda3a831019037001445.png) :::info{title=Nota} Attualmente, l'opzione responsabile per i nodi manuali non supporta la gestione di più utenti. Questa funzionalità sarà supportata in una versione futura. @@ -104,11 +104,11 @@ Per la gestione manuale, è necessario aggiungere anche un elenco di attività i Può selezionare "Attività in sospeso del flusso di lavoro" dai blocchi in una pagina per aggiungere un blocco elenco di attività in sospeso: -![Nodo Manuale_Aggiungere Blocco Attività in Sospeso](https://static-docs.nocobase.com/198b41754cd73b704267bf30fe5e647.png) +![Nodo Manuale_Aggiungere Blocco Attività in Sospeso](https://static-docs.nocobase.com/198b417454cd73b704267bf30fe5e647.png) Esempio di blocco elenco attività in sospeso: -![Nodo Manuale_Elenco Attività in Sospeso](https://static-docs.nocobase.com/cfefb0d3c6a91c5c9dfa550d6b220f34.png) +![Nodo Manuale_Elenco Attività in Sospeso](https://static-docs.nocobase.com/cfefb0d2c6a91c5c9dfa550d6b220f34.png) ### Dettagli Attività in Sospeso diff --git a/docs/docs/it/workflow/nodes/request.md b/docs/docs/it/workflow/nodes/request.md index 0c2426d95b8..7ba4c548b20 100644 --- a/docs/docs/it/workflow/nodes/request.md +++ b/docs/docs/it/workflow/nodes/request.md @@ -26,7 +26,7 @@ Nell'interfaccia di configurazione del flusso di lavoro, clicchi sul pulsante pi ## Configurazione del nodo -![Nodo Richiesta HTTP_Configurazione](https://static-docs.nocobase.com/2fcb29af66b892fa704add252e2974a52.png) +![Nodo Richiesta HTTP_Configurazione](https://static-docs.nocobase.com/2fcb29af66b892fa704add52e2974a52.png) ### Metodo di richiesta diff --git a/docs/docs/it/workflow/nodes/variable.md b/docs/docs/it/workflow/nodes/variable.md index 1094ede4ee5..19326f0e77f 100644 --- a/docs/docs/it/workflow/nodes/variable.md +++ b/docs/docs/it/workflow/nodes/variable.md @@ -16,7 +16,7 @@ Questa documentazione è stata tradotta automaticamente dall'IA. Nell'interfaccia di configurazione del **flusso di lavoro**, clicchi sul pulsante più ("+") all'interno del flusso per aggiungere un nodo "**Variabile**": -![Add Variable Node](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![Add Variable Node](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## Configurare il nodo diff --git a/docs/docs/it/workflow/triggers/post-action.md b/docs/docs/it/workflow/triggers/post-action.md index 464d5dfd111..f9a29af6951 100644 --- a/docs/docs/it/workflow/triggers/post-action.md +++ b/docs/docs/it/workflow/triggers/post-action.md @@ -46,7 +46,7 @@ Acceda alla tela del flusso di lavoro, clicchi sul trigger per aprire la finestr Quindi selezioni la modalità di attivazione, che può essere locale o globale: -![Configurazione del flusso di lavoro_Selezione della modalità di attivazione](https://static-docs.nocobase.com/317809c48b2f2a38aedc7d08abdadc.png) +![Configurazione del flusso di lavoro_Selezione della modalità di attivazione](https://static-docs.nocobase.com/317809c48b2f2a2d38aedc7d08abdadc.png) Dove: @@ -178,7 +178,7 @@ Se l'evento è configurato in modalità globale, non è necessario utilizzare il Come mostrato nella figura seguente: -![Ordine di esecuzione dell'azione](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![Ordine di esecuzione dell'azione](https://static-docs.nocobase.com/20251219234806.png) ### Differenza rispetto all'Evento della Collezione diff --git a/docs/docs/it/workflow/triggers/schedule.md b/docs/docs/it/workflow/triggers/schedule.md index 234d1be1ca0..fec108704b8 100644 --- a/docs/docs/it/workflow/triggers/schedule.md +++ b/docs/docs/it/workflow/triggers/schedule.md @@ -74,6 +74,6 @@ Crea un flusso di lavoro basato su attività pianificata. Nella configurazione d Successivamente, configuri gli altri nodi secondo la logica del processo per aggiornare lo stato dell'ordine con l'ID dei dati di attivazione e lo stato "non pagato" a "annullato": -![Attività pianificata_Configurazione trigger_Modalità campo ora della collezione_Nodo di aggiornamento](https://static-docs.nocobase.com/491dde9df773f5b14a4fd8ceac9d3e.png) +![Attività pianificata_Configurazione trigger_Modalità campo ora della collezione_Nodo di aggiornamento](https://static-docs.nocobase.com/491dde9df8f773f5b14a4fd8ceac9d3e.png) A differenza della modalità tempo personalizzato, qui non è necessario calcolare l'ora di 30 minuti fa, poiché il contesto dei dati di attivazione del flusso di lavoro contiene già la riga di dati che soddisfa la condizione temporale, quindi può aggiornare direttamente lo stato dell'ordine corrispondente. \ No newline at end of file diff --git a/docs/docs/ja/auth-verification/api-keys/index.md b/docs/docs/ja/auth-verification/api-keys/index.md index 3c89cbf6ab7..cbef6121501 100644 --- a/docs/docs/ja/auth-verification/api-keys/index.md +++ b/docs/docs/ja/auth-verification/api-keys/index.md @@ -18,7 +18,7 @@ http://localhost:13000/admin/settings/api-keys/configuration ### APIキーの追加 -![](https://static-docs.nocobase.com/46181872fc0ad9a96fa5b14e97fcba12.png) +![](https://static-docs.nocobase.com/46141872fc0ad9a96fa5b14e97fcba12.png) **注意事項** diff --git a/docs/docs/ja/auth-verification/auth-cas/index.md b/docs/docs/ja/auth-verification/auth-cas/index.md index b6ded11f352..c38ab0b2b11 100644 --- a/docs/docs/ja/auth-verification/auth-cas/index.md +++ b/docs/docs/ja/auth-verification/auth-cas/index.md @@ -28,7 +28,7 @@ http://localhost:13000/admin/settings/auth/authenticators CAS認証方法を追加します。 -![](https://static-docs.nocobase.com/268500c5008d3b90e57ff1e2ea41aca.png) +![](https://static-docs.nocobase.com/a268500c5008d3b90e57ff1e2ea41aca.png) CASを設定して有効化します。 diff --git a/docs/docs/ja/auth-verification/auth-saml/examples/google.md b/docs/docs/ja/auth-verification/auth-saml/examples/google.md index 4c1de77163f..ff000d79d6d 100644 --- a/docs/docs/ja/auth-verification/auth-saml/examples/google.md +++ b/docs/docs/ja/auth-verification/auth-saml/examples/google.md @@ -8,7 +8,7 @@ [Google 管理コンソール](https://admin.google.com/) - アプリ - ウェブアプリとモバイルアプリ -![](https://static-docs.nocobase.com/0812780b990a97a63c14ea899195827.png) +![](https://static-docs.nocobase.com/0812780b990a97a63c14ea8991959827.png) アプリの設定が完了したら、**SSO URL**、**エンティティID**、**証明書**をコピーしてください。 @@ -35,7 +35,7 @@ Google コンソールに戻り、「**サービスプロバイダの詳細**」 ![](https://static-docs.nocobase.com/1536268bf8df4a5ebc72384317172191.png) -![](https://static-docs.nocobase.com/c7de1f8b84730e85411c0c8f368637e0.png) +![](https://static-docs.nocobase.com/c7de1f8b84c1335de110e5a7c96255c4.png) 「**属性マッピング**」セクションで、対応する属性をマッピングするためにマッピングを追加します。 diff --git a/docs/docs/ja/auth-verification/auth/dev/index.md b/docs/docs/ja/auth-verification/auth/dev/index.md index 3aa576fe73d..8c97733b5ac 100644 --- a/docs/docs/ja/auth-verification/auth/dev/index.md +++ b/docs/docs/ja/auth-verification/auth/dev/index.md @@ -168,7 +168,7 @@ class CustomAuthPlugin extends Plugin { ### 管理設定フォーム -![](https://static-docs.nocobase.com/f4b544b5b0f4afee5621ad4abf66b24f.png) +![](https://static-docs.nocobase.com/f4b544b5b0f5afee5621ad4abf66b24f.png) 上部には汎用的な認証器設定があり、下部には登録可能なカスタム設定フォームの部分が表示されます。 diff --git a/docs/docs/ja/auth-verification/auth/password.md b/docs/docs/ja/auth-verification/auth/password.md index 4cd30811900..ed47f1c5a21 100644 --- a/docs/docs/ja/auth-verification/auth/password.md +++ b/docs/docs/ja/auth-verification/auth/password.md @@ -24,7 +24,7 @@ pkg: '@nocobase/plugin-auth' 新規登録が許可されていない場合、ログインページにアカウント作成のリンクは表示されません。 -![](https://static-docs.nocobase.com/8d5e3b6df9991bfc1c2e095a3745121.png) +![](https://static-docs.nocobase.com/8d5e3b6df9991bfc1c2e095a93745121.png) 新規登録が許可されていない場合、登録ページにアクセスすることはできません。 diff --git a/docs/docs/ja/data-sources/collection-expression/collection.md b/docs/docs/ja/data-sources/collection-expression/collection.md index c6b582095ce..10f64845deb 100644 --- a/docs/docs/ja/data-sources/collection-expression/collection.md +++ b/docs/docs/ja/data-sources/collection-expression/collection.md @@ -14,7 +14,7 @@ 次に、テーブルブロックを作成し、そのテンプレート コレクションにいくつかの数式データを入力します。「式」テンプレート コレクションの各行データは、特定のコレクションのデータモデルに対する計算ルールとして解釈できます。各数式データ行では、異なるコレクションのデータモデルのフィールド値を変数として使用し、さまざまな式を計算ルールとして記述できます。もちろん、必要に応じて異なる計算エンジンを利用することも可能です。 -![式データの入力](https://static-docs.nocobase.com/761047f8daabacccbc6a6a24a73564093.png) +![式データの入力](https://static-docs.nocobase.com/761047f8daabacccbc6a924a73564093.png) :::info{title=ヒント} 数式を作成したら、ビジネスデータと数式を関連付ける必要があります。各ビジネスデータ行を数式データ行に直接関連付けるのは煩雑になる可能性があるため、通常は分類のようなメタデータ コレクションと数式コレクションを多対一（または一対一）で関連付けます。その後、ビジネスデータを分類メタデータと多対一で関連付けます。こうすることで、ビジネスデータを作成する際に特定の分類メタデータを指定するだけで、その後の使用時にこの関連付けパスを通じて対応する数式データを見つけて利用できるようになります。 diff --git a/docs/docs/ja/data-sources/data-modeling/collection-fields/associations/m2o/index.md b/docs/docs/ja/data-sources/data-modeling/collection-fields/associations/m2o/index.md index 895bc8a816a..0d5b501c3f4 100644 --- a/docs/docs/ja/data-sources/data-modeling/collection-fields/associations/m2o/index.md +++ b/docs/docs/ja/data-sources/data-modeling/collection-fields/associations/m2o/index.md @@ -12,7 +12,7 @@ ER図: フィールド設定: -![alt text](https://static-docs.nocobase.com/3b4484ebb97d82f832f3dbf752bd84c9.png) +![alt text](https://static-docs.nocobase.com/3b4484ebb98d82f832f3dbf752bd84c9.png) ## パラメータの説明 diff --git a/docs/docs/ja/data-sources/data-modeling/collection-fields/associations/o2o/index.md b/docs/docs/ja/data-sources/data-modeling/collection-fields/associations/o2o/index.md index 8d223b54c6b..fae9fd727f1 100644 --- a/docs/docs/ja/data-sources/data-modeling/collection-fields/associations/o2o/index.md +++ b/docs/docs/ja/data-sources/data-modeling/collection-fields/associations/o2o/index.md @@ -32,7 +32,7 @@ ER関係 フィールド設定 -![alt text](https://static-docs.nocobase.com/4f09eeb3c7717d61a349482da43c187c.png) +![alt text](https://static-docs.nocobase.com/4f09eeb3c7717d61a349842da43c187c.png) ## パラメータ説明 diff --git a/docs/docs/ja/data-sources/field-encryption/index.md b/docs/docs/ja/data-sources/field-encryption/index.md index 34ec5936d48..9c2270cd60c 100644 --- a/docs/docs/ja/data-sources/field-encryption/index.md +++ b/docs/docs/ja/data-sources/field-encryption/index.md @@ -30,7 +30,7 @@ pkg: "@nocobase/plugin-field-encryption" エンベロープ暗号化方式を採用しています。 -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### キーの作成プロセス 1. 暗号化フィールドを初めて作成する際、システムは自動的に32ビットの`アプリケーションキー`を生成し、Base64エンコード形式でデフォルトの保存ディレクトリに保存します。 diff --git a/docs/docs/ja/data-visualization/guide/data-query.md b/docs/docs/ja/data-visualization/guide/data-query.md index 8a8cf894ef2..b42671d444e 100644 --- a/docs/docs/ja/data-visualization/guide/data-query.md +++ b/docs/docs/ja/data-visualization/guide/data-query.md @@ -49,7 +49,7 @@ - 「クエリ実行」をクリックして実行します。結果が返されたら、「結果表示」で `Table / JSON` を切り替えて、列と値を確認します。 - チャートフィールドをマッピングする前に、ここで列名と型を確認してください。これにより、後でチャートが空になったりエラーが発生したりするのを防げます。 -![20251026174338](https://static-docs.nocobase.com/clipboard-image-174338.png) +![20251026174338](https://static-docs.nocobase.com/20251026174338.png) ### 後続のフィールドマッピング @@ -70,7 +70,7 @@ ORDER BY mon ASC LIMIT 100; ``` -![20251026175952](https://static-docs.nocobase.com/clipboard-image-175952.png) +![20251026175952](https://static-docs.nocobase.com/20251026175952.png) ### クエリ実行と結果表示 diff --git a/docs/docs/ja/email-manager/advanced/batch-send.md b/docs/docs/ja/email-manager/advanced/batch-send.md index 93cb91ae82f..6a49a05bd8d 100644 --- a/docs/docs/ja/email-manager/advanced/batch-send.md +++ b/docs/docs/ja/email-manager/advanced/batch-send.md @@ -10,27 +10,27 @@ pkg: "@nocobase/plugin-email-manager" ## 一括送信の概要 複数人に対してメールを一括で送信できます（各受信者には個別のメールが届きます）。 -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## テーブルから一括送信する テーブルからメールを一括送信することも可能です。 1. テーブルに「メール送信」ボタンを追加します。 - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. テーブル内のメールアドレスフィールドを設定します（テーブルの行を選択した後にメールアドレスを解析するために使用されます）。 - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. テーブルデータを選択してメールを送信します。 - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) テーブル内のすべてのメールアドレスに送信したい場合は、「**現在のテーブルのすべてのレコードをデフォルトで受信者として選択する**」機能を有効にしてください。 -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) メール内容を編集した後、「一括送信」ボタンをクリックして送信します。 -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## メール送信状況の追跡 メール管理センターで、具体的なメール送信状況を確認・追跡できます。 -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/ja/email-manager/usage/signature.md b/docs/docs/ja/email-manager/usage/signature.md index 04dcb08fc9e..b9306dd9b17 100644 --- a/docs/docs/ja/email-manager/usage/signature.md +++ b/docs/docs/ja/email-manager/usage/signature.md @@ -11,15 +11,15 @@ pkg: "@nocobase/plugin-email-manager" ## 署名設定 メール管理センターにアクセスし、設定ボタンをクリックします。 -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) 署名パネルに切り替えます。 -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) ここで署名を管理できます。署名の前のオプションにチェックを入れると、デフォルトの署名として設定できます。 -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## 署名の利用 メール本文の入力欄で、署名アイコンをクリックして、必要な署名を選択します。 -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/ja/email-manager/usage/template.md b/docs/docs/ja/email-manager/usage/template.md index 95e45cb5902..219948b3858 100644 --- a/docs/docs/ja/email-manager/usage/template.md +++ b/docs/docs/ja/email-manager/usage/template.md @@ -11,15 +11,15 @@ pkg: "@nocobase/plugin-email-manager" ## テンプレートの設定 メール管理センターにアクセスし、「設定」ボタンをクリックします。 -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) 「テンプレート」パネルに切り替えます。 -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) ここでテンプレートを管理できます。 -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## テンプレートの使用 メール本文ボックス内で、「テンプレート」アイコンをクリックして、必要なテンプレートを選択します。 -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/ja/flow-engine/learning-roadmap.md b/docs/docs/ja/flow-engine/learning-roadmap.md index d84ad2206d7..b5326956244 100644 --- a/docs/docs/ja/flow-engine/learning-roadmap.md +++ b/docs/docs/ja/flow-engine/learning-roadmap.md @@ -4,4 +4,4 @@ # 学習ロードマップ -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/ja/solution/ticket-system/design.md b/docs/docs/ja/solution/ticket-system/design.md index 3c6aa4ac73e..586c62b3158 100755 --- a/docs/docs/ja/solution/ticket-system/design.md +++ b/docs/docs/ja/solution/ticket-system/design.md @@ -31,7 +31,7 @@ - **横方向（主テーブル）**：すべての業務タイプに共通する汎用能力 —— 番号、ステータス、担当者、SLAなどのコアフィールドをカバー - **縦方向（拡張テーブル）**：特定の業務に特化した専門フィールド —— 機器修理ならシリアル番号、苦情なら賠償案など -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **なぜこのように設計するのか？** @@ -61,7 +61,7 @@ #### 理念3：ナレッジの自己循環 -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) これにより、**ナレッジの蓄積 ─ ナレッジの活用** というクローズドループが形成されます。 @@ -71,7 +71,7 @@ ### 2.1 エンティティ関係の概要 -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 コアテーブル詳細 @@ -296,18 +296,18 @@ **メインフロー（左から右へ）** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **分岐フロー** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **完全なステートマシン** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 主要なステータス遷移ルール @@ -337,7 +337,7 @@ ### 4.2 SLA計算ロジック -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### チケット作成時 @@ -466,7 +466,7 @@ SLA一時停止開始時間 = NULL ### 5.3 AI従業員とチケットライフサイクル -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 AI応答例 @@ -528,12 +528,12 @@ Graceが担当する回答品質監査では、以下の問題をブロックし ### 6.1 ナレッジソース -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 チケットからナレッジへの変換フロー -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **評価基準**： - **汎用性**: これはよくある問題か？ @@ -578,19 +578,19 @@ Graceが担当する回答品質監査では、以下の問題をブロックし #### WF-T01: チケット作成フロー -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: チケットAI分析 -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: コメント翻訳と監査 -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: ナレッジ生成 -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 定期タスク @@ -607,11 +607,11 @@ Graceが担当する回答品質監査では、以下の問題をブロックし ### 8.1 管理バックエンド -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 顧客ポータル -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 ダッシュボード設計 diff --git a/docs/docs/ja/users-permissions/acl/role.md b/docs/docs/ja/users-permissions/acl/role.md index e5d4fb6e725..461acbd707a 100644 --- a/docs/docs/ja/users-permissions/acl/role.md +++ b/docs/docs/ja/users-permissions/acl/role.md @@ -34,6 +34,6 @@ pkg: '@nocobase/plugin-acl' 1人のユーザーに複数のロールを割り当てることができます。複数のロールを持つユーザーは、個人センターでロールを切り替えることが可能です。 -![](https://static-docs.nocobase.com/e311d11ec1ca3b8b7e0472105b167819.png) +![](https://static-docs.nocobase.com/e331d11ec1ca3b8b7e0472105b167819.png) システムにログインする際のデフォルトロールの優先順位は、以下の通りです。最後に切り替えたロール（ロールを切り替えるたびにデフォルトロール値が更新されます）> 最初のロール（システムデフォルトロール）。 \ No newline at end of file diff --git a/docs/docs/ja/users-permissions/acl/ui.md b/docs/docs/ja/users-permissions/acl/ui.md index d784e0d3992..1a6190d82d6 100644 --- a/docs/docs/ja/users-permissions/acl/ui.md +++ b/docs/docs/ja/users-permissions/acl/ui.md @@ -20,7 +20,7 @@ pkg: '@nocobase/plugin-acl' `注文` コレクションの個別権限設定は以下の通りです。 -![](https://static-docs.nocobase.com/a88c1cad47001c1610bf402a4a2c1.png) +![](https://static-docs.nocobase.com/a88caba1cad47001c1610bf402a4a2c1.png) UI上では、`注文` コレクションのすべてのブロックが表示されなくなります。 @@ -36,7 +36,7 @@ UI上では、`注文` コレクションのすべてのブロックが表示さ UI上では、`注文` コレクションのブロック内には、権限が設定されているフィールドのみが表示されます。システムフィールド（`Id`、`CreatedAt`、`Last updated at`）は、特に設定しなくても表示権限を持っています。 -![](https://static-docs.nocobase.com/40cc9e79dcc.png) +![](https://static-docs.nocobase.com/40cc49b517efe701147fd2e799e79dcc.png) - **編集**: フィールドが編集・保存（更新）できるかどうかを制御します。 @@ -183,4 +183,4 @@ UI上では、このリレーションフィールドは表示されます。し 図のように、`顧客` コレクションの個別のフィールドに表示権限を設定できます。 -![](https://static-docs.nocobase.com/35af9426c20911ecf81bac8fc.gif) \ No newline at end of file +![](https://static-docs.nocobase.com/35af9426c20911323b17f67f81bac8fc.gif) \ No newline at end of file diff --git a/docs/docs/ja/workflow/advanced/executions.md b/docs/docs/ja/workflow/advanced/executions.md index b38d8ede207..a7180249734 100644 --- a/docs/docs/ja/workflow/advanced/executions.md +++ b/docs/docs/ja/workflow/advanced/executions.md @@ -24,7 +24,7 @@ [クイックスタート](../getting-started.md)の例で、ワークフローの実行履歴の詳細を確認することで、実行中のすべてのノードが正常に実行されたか、および各実行済みノードの実行ステータスと結果データをチェックできることを学びました。高度なワークフローやノードでは、ループノードの結果のように、ノードが複数の結果を持つ場合があります。 -![複数回実行されたノードの結果](https://static-docs.nocobase.com/bbda259fa2ddf62b0fc0f928efbedae9.png) +![複数回実行されたノードの結果](https://static-docs.nocobase.com/bbda259fa2ddf62b0fc0f982efbedae9.png) :::info{title=ヒント} ワークフローは同時にトリガーできますが、実行はキューで順次行われます。複数のワークフローが同時にトリガーされた場合でも、並行ではなく、1つずつ順番に実行されます。したがって、「キュー中」のステータスが表示されている場合は、他のワークフローが実行中であり、待機する必要があることを意味します。 diff --git a/docs/docs/ja/workflow/advanced/options.md b/docs/docs/ja/workflow/advanced/options.md index d964bc2a7d0..6c5dcaf8a40 100644 --- a/docs/docs/ja/workflow/advanced/options.md +++ b/docs/docs/ja/workflow/advanced/options.md @@ -22,7 +22,7 @@ 同様に、ワークフローの新規作成・編集ダイアログで、そのワークフローの実行履歴を自動削除するかどうかを設定できます。 -![実行履歴の自動削除設定](https://static-docs.nocobase.com/b2e4c08e7a01e21306795.png) +![実行履歴の自動削除設定](https://static-docs.nocobase.com/b2e4c08e7a01e213069912fe04baa7bd.png) 自動削除は、実行結果のステータスに基づいて設定できます。ほとんどの場合、「完了」ステータスのみをチェックすることをお勧めします。そうすることで、実行失敗の記録を保持し、後続の問題調査に役立てることができます。 diff --git a/docs/docs/ja/workflow/nodes/create.md b/docs/docs/ja/workflow/nodes/create.md index 462f17d939e..776e11f0503 100644 --- a/docs/docs/ja/workflow/nodes/create.md +++ b/docs/docs/ja/workflow/nodes/create.md @@ -38,7 +38,7 @@ 例えば、「記事」**コレクション**のレコードが新規作成または更新された際に、記事の変更履歴を記録するために「記事バージョン」レコードを自動的に新規作成する必要がある場合、「レコードの新規作成」ノードを使用することでこれを実現できます。 -![「レコードの新規作成」ノード_例_ワークフロー設定](https://static-docs.nocobase.com/dfb4820d49c145fa33183fc09c9161f.png) +![「レコードの新規作成」ノード_例_ワークフロー設定](https://static-docs.nocobase.com/dfd4820d49c145fa331883fc09c9161f.png) ![「レコードの新規作成」ノード_例_ノード設定](https://static-docs.nocobase.com/1a0992e66170be12a068da6503298868.png) diff --git a/docs/docs/ja/workflow/nodes/destroy.md b/docs/docs/ja/workflow/nodes/destroy.md index 92d5bd6f756..3c5b4cfb87c 100644 --- a/docs/docs/ja/workflow/nodes/destroy.md +++ b/docs/docs/ja/workflow/nodes/destroy.md @@ -34,6 +34,6 @@ 例えば、キャンセルされた無効な過去の注文データを定期的にクリーンアップする場合、削除ノードを使用して実現できます。 -![削除ノード_例_ノード設定](https://static-docs.nocobase.com/b94b7507417252f8523c3f13ce5f320.png) +![削除ノード_例_ノード設定](https://static-docs.nocobase.com/b94b75077a17252f8523c3f13ce5f320.png) ワークフローは定期的にトリガーされ、キャンセルされたすべての無効な過去の注文データを削除します。 \ No newline at end of file diff --git a/docs/docs/ja/workflow/nodes/manual.md b/docs/docs/ja/workflow/nodes/manual.md index 2d041a0291e..32526b357eb 100644 --- a/docs/docs/ja/workflow/nodes/manual.md +++ b/docs/docs/ja/workflow/nodes/manual.md @@ -32,7 +32,7 @@ pkg: '@nocobase/plugin-workflow-manual' ユーザーを直接選択するか、変数を使用してコンテキストからユーザーデータの主キーまたは外部キーを選択します。 -![人工节点_配置_负责人_选择变量](https://static-docs.nocobase.com/22fbca3b8e21fda3a81019037001445.png) +![人工节点_配置_负责人_选择变量](https://static-docs.nocobase.com/22fbca3b8e21fda3a831019037001445.png) :::info{title=ヒント} 現在、手動処理ノードの担当者オプションは複数ユーザーに対応していません。この機能は将来のバージョンでサポートされる予定です。 @@ -104,7 +104,7 @@ ToDoインターフェースには、ワークフローを続行するかどう ページ内のブロックから「ワークフローToDo」を選択し、ToDoリストブロックを追加できます。 -![人工节点_追加待办区块](https://static-docs.nocobase.com/198b41754cd73b704267bf30fe5e647.png) +![人工节点_追加待办区块](https://static-docs.nocobase.com/198b417454cd73b704267bf30fe5e647.png) ToDoリストブロックの例： diff --git a/docs/docs/ja/workflow/nodes/parallel.md b/docs/docs/ja/workflow/nodes/parallel.md index 3363a2c8dd1..51b02b32e63 100644 --- a/docs/docs/ja/workflow/nodes/parallel.md +++ b/docs/docs/ja/workflow/nodes/parallel.md @@ -22,7 +22,7 @@ pkg: '@nocobase/plugin-workflow-parallel' ワークフローに並列ブランチノードを追加すると、デフォルトで2つのサブブランチが追加されます。「ブランチを追加」ボタンをクリックして、任意の数のブランチを追加することも可能です。各ブランチには任意のノードを追加できます。不要なブランチは、ブランチの開始位置にある削除ボタンをクリックして削除できます。 -![並列ブランチ_ブランチ管理](https://static-docs.nocobase.com/36088a8b7971eb3ee9bc2a757.png) +![並列ブランチ_ブランチ管理](https://static-docs.nocobase.com/36088a8b7970c8a1771eb3ee9bc2a757.png) ## ノード設定 diff --git a/docs/docs/ja/workflow/nodes/request.md b/docs/docs/ja/workflow/nodes/request.md index 2fdf2ecd2f7..ffd9e71f116 100644 --- a/docs/docs/ja/workflow/nodes/request.md +++ b/docs/docs/ja/workflow/nodes/request.md @@ -26,7 +26,7 @@ Postmanのようなリクエスト送信ツールに慣れている方であれ ## ノード設定 -![HTTPリクエストノード_ノード設定](https://static-docs.nocobase.com/2fcb29af6b892fa704add52e2974a52.png) +![HTTPリクエストノード_ノード設定](https://static-docs.nocobase.com/2fcb29af66b892fa704add52e2974a52.png) ### リクエストメソッド diff --git a/docs/docs/ja/workflow/nodes/variable.md b/docs/docs/ja/workflow/nodes/variable.md index 863036ca55d..2d863e4a81f 100644 --- a/docs/docs/ja/workflow/nodes/variable.md +++ b/docs/docs/ja/workflow/nodes/variable.md @@ -16,7 +16,7 @@ pkg: '@nocobase/plugin-workflow-variable' ワークフロー設定画面で、フロー内のプラス（「+」）ボタンをクリックして、「変数」ノードを追加します。 -![変数ノードを追加](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![変数ノードを追加](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## ノードの設定 diff --git a/docs/docs/ja/workflow/triggers/post-action.md b/docs/docs/ja/workflow/triggers/post-action.md index d68bacc0826..952dcd8835f 100644 --- a/docs/docs/ja/workflow/triggers/post-action.md +++ b/docs/docs/ja/workflow/triggers/post-action.md @@ -178,7 +178,7 @@ curl -X POST -H 'Authorization: Bearer ' -H 'X-Role: ' -d 下図の通りです。 -![操作実行順序](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![操作実行順序](https://static-docs.nocobase.com/20251219234806.png) ### **コレクション**イベントとの違い diff --git a/docs/docs/ja/workflow/triggers/pre-action.md b/docs/docs/ja/workflow/triggers/pre-action.md index b20bf3f2e32..6fd3d5a8021 100644 --- a/docs/docs/ja/workflow/triggers/pre-action.md +++ b/docs/docs/ja/workflow/triggers/pre-action.md @@ -34,7 +34,7 @@ pkg: '@nocobase/plugin-workflow-request-interceptor' ### インターセプトモード -![Interceptor Event Configuration_Interception Mode](https://static-docs.nocobase.com/145f7c3ba440bb6ca93a5ee84f16e2.png) +![Interceptor Event Configuration_Interception Mode](https://static-docs.nocobase.com/145a7f7c3ba440bb6ca93a5ee84f16e2.png) 現在サポートされている操作タイプは「作成」、「更新」、「削除」です。複数の操作タイプを同時に選択できます。 @@ -91,7 +91,7 @@ pkg: '@nocobase/plugin-workflow-request-interceptor' 「ワークフローを終了」ノードが「成功」ステータスで終了するように設定されており、このノードが実行された場合、その操作のリクエストは引き続きインターセプトされますが、返される応答メッセージは「成功」（「エラー」ではなく）ステータスで表示されます。 -![Success Status Response Message](https://static-docs.nocobase.com/9559bbf5607144759451294b18c790e.png) +![Success Status Response Message](https://static-docs.nocobase.com/9559bbf56067144759451294b18c790e.png) ## 例 diff --git a/docs/docs/ja/workflow/triggers/schedule.md b/docs/docs/ja/workflow/triggers/schedule.md index 43305420e08..a04f8d1c2d9 100644 --- a/docs/docs/ja/workflow/triggers/schedule.md +++ b/docs/docs/ja/workflow/triggers/schedule.md @@ -74,6 +74,6 @@ その後、ワークフローのロジックに従って他のノードを設定します。トリガーされたデータのIDと一致し、かつステータスが「未支払い」の注文をキャンセル済みのステータスに更新します。 -![定期実行タスク_トリガー設定_コレクションの時刻フィールドモード_更新ノード](https://static-docs.nocobase.com/491dde9df8f771fb24a4e7baa1de6eb29.png) +![定期実行タスク_トリガー設定_コレクションの時刻フィールドモード_更新ノード](https://static-docs.nocobase.com/491dde9df8f773f5b14a4fd8ceac9d3e.png) カスタム時間モードとは異なり、ここでは30分前の時刻を計算する必要はありません。ワークフローのトリガーデータコンテキストには、時刻条件に合致するデータ行がすでに含まれているため、対応する注文のステータスを直接更新できます。 \ No newline at end of file diff --git a/docs/docs/ko/ai-employees/permission.md b/docs/docs/ko/ai-employees/permission.md index 74b9973723e..403f2f0ffc4 100644 --- a/docs/docs/ko/ai-employees/permission.md +++ b/docs/docs/ko/ai-employees/permission.md @@ -36,7 +36,7 @@ AI 직원 목록의 `Available` 열에 있는 체크박스를 클릭하여 현 AI 직원이 데이터를 처리할 때, 권한 제어 방식은 사용되는 도구 유형에 따라 달라집니다: ### 시스템 내장 데이터 쿼리 도구 (사용자 권한 준수) -![05viz-configuration-2025-11-03-00-15-04](https://static-docs.nocobase.com/20251022013802.png) +![05viz-configuration-2025-11-03-00-15-04](https://static-docs.nocobase.com/05viz-configuration-2025-11-03-00-15-04.png) 다음 도구들은 **현재 사용자의 데이터 권한을 엄격히 준수**하여 데이터에 접근합니다: diff --git a/docs/docs/ko/auth-verification/api-keys/index.md b/docs/docs/ko/auth-verification/api-keys/index.md index 40a15f2ec1d..cdc65ab502e 100644 --- a/docs/docs/ko/auth-verification/api-keys/index.md +++ b/docs/docs/ko/auth-verification/api-keys/index.md @@ -18,7 +18,7 @@ http://localhost:13000/admin/settings/api-keys/configuration ### API 키 추가 -![](https://static-docs.nocobase.com/461872fc0ad9a96fa5b14e97fcba12.png) +![](https://static-docs.nocobase.com/46141872fc0ad9a96fa5b14e97fcba12.png) **주의 사항** diff --git a/docs/docs/ko/auth-verification/auth-oidc/index.md b/docs/docs/ko/auth-verification/auth-oidc/index.md index 7359b212253..84284f8eb16 100644 --- a/docs/docs/ko/auth-verification/auth-oidc/index.md +++ b/docs/docs/ko/auth-verification/auth-oidc/index.md @@ -44,7 +44,7 @@ pkg: '@nocobase/plugin-auth-oidc' ### 필드 매핑 -![](https://static-docs.nocobase.com/92d3c8f6f4082b50d9f475674cb5650.png) +![](https://static-docs.nocobase.com/92d63c8f6f4082b50d9f475674cb5650.png) | 설정 | 설명 | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------- | diff --git a/docs/docs/ko/auth-verification/auth/authenticators.md b/docs/docs/ko/auth-verification/auth/authenticators.md index 8c70db49827..79a76e3ccaf 100644 --- a/docs/docs/ko/auth-verification/auth/authenticators.md +++ b/docs/docs/ko/auth-verification/auth/authenticators.md @@ -16,7 +16,7 @@ pkg: '@nocobase/plugin-auth' ## 인증기 활성화 -![](https://static-docs.nocobase.com/7f1b8f8ca5de67ffc68eff0a366bd8a5d5.png) +![](https://static-docs.nocobase.com/7f1fb8f8ca5de67ffc68eff0a65848f5.png) 활성화된 인증 유형만 로그인 페이지에 표시됩니다. diff --git a/docs/docs/ko/auth-verification/auth/dev/index.md b/docs/docs/ko/auth-verification/auth/dev/index.md index 85096d128e1..9d62c8251ad 100644 --- a/docs/docs/ko/auth-verification/auth/dev/index.md +++ b/docs/docs/ko/auth-verification/auth/dev/index.md @@ -168,7 +168,7 @@ class CustomAuthPlugin extends Plugin { ### 관리자 설정 폼 -![](https://static-docs.nocobase.com/f4b544b5b0f4afee5621ad4abf66b24f.png) +![](https://static-docs.nocobase.com/f4b544b5b0f5afee5621ad4abf66b24f.png) 위쪽은 일반적인 인증기 설정이며, 아래쪽은 등록 가능한 사용자 정의 설정 폼 부분입니다. diff --git a/docs/docs/ko/auth-verification/auth/password.md b/docs/docs/ko/auth-verification/auth/password.md index 495de174c92..ad5af37dca9 100644 --- a/docs/docs/ko/auth-verification/auth/password.md +++ b/docs/docs/ko/auth-verification/auth/password.md @@ -24,7 +24,7 @@ pkg: '@nocobase/plugin-auth' 회원가입이 허용되지 않은 경우, 로그인 페이지에 계정 생성 링크가 표시되지 않습니다. -![](https://static-docs.nocobase.com/8d5e3b6df9991bfc1c2e095a3745121.png) +![](https://static-docs.nocobase.com/8d5e3b6df9991bfc1c2e095a93745121.png) 회원가입이 허용되지 않은 경우, 회원가입 페이지에 접근할 수 없습니다. diff --git a/docs/docs/ko/data-sources/collection-expression/collection.md b/docs/docs/ko/data-sources/collection-expression/collection.md index 4f8383022e9..f74753fe019 100644 --- a/docs/docs/ko/data-sources/collection-expression/collection.md +++ b/docs/docs/ko/data-sources/collection-expression/collection.md @@ -14,7 +14,7 @@ 다음으로, 테이블 블록을 생성하고 해당 템플릿 컬렉션에 몇 가지 수식 데이터를 추가할 수 있습니다. "표현식" 템플릿 컬렉션의 각 행 데이터는 특정 컬렉션 데이터 모델에 대한 계산 규칙으로 이해될 수 있습니다. 각 수식 데이터 행은 다양한 컬렉션의 데이터 모델에 있는 필드 값을 변수로 사용하여 계산 규칙으로 작동하는 고유한 표현식을 작성할 수 있습니다. 물론, 필요에 따라 다른 계산 엔진을 사용할 수도 있습니다. -![표현식 데이터 입력하기](https://static-docs.nocobase.com/761047f8daabacccbc6a6a24a73564093.png) +![표현식 데이터 입력하기](https://static-docs.nocobase.com/761047f8daabacccbc6a924a73564093.png) :::info{title=팁} 수식을 생성한 후에는 비즈니스 데이터와 수식을 연결해야 합니다. 각 비즈니스 데이터 행을 수식 데이터 행에 직접 연결하는 것은 번거로울 수 있습니다. 따라서 일반적으로 분류 컬렉션과 유사한 메타데이터 컬렉션을 사용하여 수식 컬렉션과 다대일(또는 일대일) 관계를 만듭니다. 그런 다음 비즈니스 데이터를 분류된 메타데이터와 다대일 관계로 연결합니다. 이러한 접근 방식을 통해 비즈니스 데이터를 생성할 때 관련 분류된 메타데이터만 지정하면, 설정된 연결 경로를 통해 해당 수식 데이터를 쉽게 찾아 활용할 수 있습니다. diff --git a/docs/docs/ko/data-sources/data-modeling/collection-fields/associations/o2o/index.md b/docs/docs/ko/data-sources/data-modeling/collection-fields/associations/o2o/index.md index 7587eb597e2..92544443629 100644 --- a/docs/docs/ko/data-sources/data-modeling/collection-fields/associations/o2o/index.md +++ b/docs/docs/ko/data-sources/data-modeling/collection-fields/associations/o2o/index.md @@ -20,7 +20,7 @@ ER 관계 필드 설정 -![alt text](https://static-docs.nocobase.com/7659e128936bbd7c9ff51bcff1d646dd.png) +![alt text](https://static-docs.nocobase.com/7665a87e094b4fb50c9426a108f87105.png) ## 일대일 (소속됨) @@ -32,7 +32,7 @@ ER 관계 필드 설정 -![alt text](https://static-docs.nocobase.com/4f09eeb3c7717d61a34982da43c187c.png) +![alt text](https://static-docs.nocobase.com/4f09eeb3c7717d61a349842da43c187c.png) ## 파라미터 설명 diff --git a/docs/docs/ko/data-sources/field-encryption/index.md b/docs/docs/ko/data-sources/field-encryption/index.md index 572c9211b2d..a31443d2f92 100644 --- a/docs/docs/ko/data-sources/field-encryption/index.md +++ b/docs/docs/ko/data-sources/field-encryption/index.md @@ -30,7 +30,7 @@ pkg: "@nocobase/plugin-field-encryption" 봉투 암호화(Envelope Encryption) 방식을 사용합니다. -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### 키 생성 과정 1. 암호화 필드를 처음 생성할 때, 시스템은 32비트 `애플리케이션 키`를 자동으로 생성하여 Base64 인코딩 방식으로 기본 저장 디렉터리에 저장합니다. diff --git a/docs/docs/ko/email-manager/advanced/batch-send.md b/docs/docs/ko/email-manager/advanced/batch-send.md index 9dac8cf0acf..d47bc538e1f 100644 --- a/docs/docs/ko/email-manager/advanced/batch-send.md +++ b/docs/docs/ko/email-manager/advanced/batch-send.md @@ -10,27 +10,27 @@ pkg: "@nocobase/plugin-email-manager" ## 대량 발송 개요 여러 사람에게 이메일을 대량으로 발송할 수 있습니다. 각 수신자는 개별 이메일을 받게 됩니다. -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## 테이블을 통한 대량 발송 테이블을 통해 이메일을 대량 발송할 수도 있습니다: 1. 테이블에 이메일 발송 버튼을 추가합니다. - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. 테이블에서 이메일 필드를 설정합니다. (테이블 행 선택 후 이메일 주소를 파싱하는 데 사용됩니다.) - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. 테이블 데이터를 선택하여 이메일을 발송합니다. - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) 테이블의 모든 이메일 주소로 발송해야 하는 경우, **현재 테이블의 모든 기록을 기본 수신자로 선택** 기능을 활성화할 수 있습니다. -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) 이메일 내용을 편집한 후, 대량 발송 버튼을 클릭하여 발송합니다. -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## 이메일 발송 추적 이메일 관리 센터에서 구체적인 이메일 발송 상황을 확인하고 추적할 수 있습니다. -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/ko/email-manager/usage/signature.md b/docs/docs/ko/email-manager/usage/signature.md index 5305a949406..ba0dd2e196e 100644 --- a/docs/docs/ko/email-manager/usage/signature.md +++ b/docs/docs/ko/email-manager/usage/signature.md @@ -11,15 +11,15 @@ pkg: "@nocobase/plugin-email-manager" ## 서명 설정 이메일 관리 센터로 이동하여 설정 버튼을 클릭합니다: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) 서명 패널로 전환합니다: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) 여기서 서명을 관리할 수 있습니다. 서명 앞의 옵션을 선택하여 기본 서명으로 설정할 수 있습니다: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## 서명 사용 이메일 본문 입력란에서 서명 아이콘을 클릭하여 원하는 서명을 선택합니다: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/ko/email-manager/usage/template.md b/docs/docs/ko/email-manager/usage/template.md index 73e6751be77..88c62a886d6 100644 --- a/docs/docs/ko/email-manager/usage/template.md +++ b/docs/docs/ko/email-manager/usage/template.md @@ -11,15 +11,15 @@ pkg: "@nocobase/plugin-email-manager" ## 템플릿 설정 이메일 관리 센터로 이동하여 설정 버튼을 클릭합니다. -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) 템플릿 패널로 전환합니다. -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) 여기에서 템플릿을 관리할 수 있습니다. -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## 템플릿 사용 발신 본문 상자에서 템플릿 아이콘을 클릭하여 원하는 템플릿을 선택합니다. -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/ko/flow-engine/learning-roadmap.md b/docs/docs/ko/flow-engine/learning-roadmap.md index 97ff68ffd65..19e3d7f3cd0 100644 --- a/docs/docs/ko/flow-engine/learning-roadmap.md +++ b/docs/docs/ko/flow-engine/learning-roadmap.md @@ -4,4 +4,4 @@ # 학습 로드맵 -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/ko/integration/api-doc/index.md b/docs/docs/ko/integration/api-doc/index.md index 51932a11ba0..ef825d21dd7 100644 --- a/docs/docs/ko/integration/api-doc/index.md +++ b/docs/docs/ko/integration/api-doc/index.md @@ -25,7 +25,7 @@ pkg: "@nocobase/plugin-api-doc" http://localhost:13000/admin/settings/api-doc/documentation -![](https://static-docs.nocobase.com/8db51cf50e3c666aba5a50a0fb664a0.png) +![](https://static-docs.nocobase.com/8db51cf50e3c666aba5a850a0fb664a0.png) ### 문서 개요 diff --git a/docs/docs/ko/solution/ticket-system/design.md b/docs/docs/ko/solution/ticket-system/design.md index db0b76a3d7c..a9de5e388fa 100755 --- a/docs/docs/ko/solution/ticket-system/design.md +++ b/docs/docs/ko/solution/ticket-system/design.md @@ -31,7 +31,7 @@ - **가로(메인 테이블)**: 모든 비즈니스 유형을 아우르는 공통 기능 — 번호, 상태, 처리자, SLA 등 핵심 필드 - **세로(확장 테이블)**: 특정 비즈니스에 특화된 전문 필드 — 장비 수리에는 일련번호, 고객 불만에는 보상 방안 등 -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **왜 이렇게 설계했나요?** @@ -61,7 +61,7 @@ #### 이념 3: 지식 자가 순환 -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) 이는 **지식 축적 - 지식 활용**의 선순환 구조를 형성합니다. @@ -71,7 +71,7 @@ ### 2.1 엔티티 관계 개요 -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 핵심 테이블 상세 설명 @@ -296,18 +296,18 @@ **메인 프로세스 (왼쪽에서 오른쪽으로)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **분기 프로세스** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **전체 상태 머신** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 주요 상태 전환 규칙 @@ -337,7 +337,7 @@ ### 4.2 SLA 계산 로직 -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### 티켓 생성 시 @@ -466,7 +466,7 @@ SLA 일시 중지 시작 시간 = NULL ### 5.3 AI 직원과 티켓 생애주기 -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 AI 응답 예시 @@ -525,12 +525,12 @@ Grace가 담당하는 답변 품질 검토는 다음과 같은 문제를 차단 ### 6.1 지식 출처 -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 티켓의 지식화 프로세스 -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **평가 차원**: - **범용성**: 자주 발생하는 문제인가? @@ -575,19 +575,19 @@ Grace가 담당하는 답변 품질 검토는 다음과 같은 문제를 차단 #### WF-T01: 티켓 생성 프로세스 -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: 티켓 AI 분석 -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: 댓글 번역 및 검토 -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: 지식 생성 -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 예약 작업 (스케줄러) @@ -604,11 +604,11 @@ Grace가 담당하는 답변 품질 검토는 다음과 같은 문제를 차단 ### 8.1 백엔드 관리자 화면 -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 고객 포털 화면 -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 대시보드 설계 diff --git a/docs/docs/ko/template-print/faq.md b/docs/docs/ko/template-print/faq.md index 60f2a738098..2bf08202741 100644 --- a/docs/docs/ko/template-print/faq.md +++ b/docs/docs/ko/template-print/faq.md @@ -44,10 +44,10 @@ Excel 템플릿에서 모든 대상 셀에 연한 회색 배경을 설정하고 ![20250820080712](https://static-docs.nocobase.com/20250820080712.png) **올바른 방식 1 (레이아웃 조정)**: "주문 요약" 정보를 "주문 상세 내역" 테이블 위로 이동하여 반복 영역이 페이지의 맨 아래 요소가 되도록 합니다. -![20250820082226](https://static-docs.nocobase.com/2025082226.png) +![20250820082226](https://static-docs.nocobase.com/20250820082226.png) **올바른 방식 2 (빈 행 확보)**: "주문 상세 내역"과 "주문 요약" 사이에 충분한 빈 행을 확보하여 반복 내용이 확장될 공간을 충분히 확보합니다. -![20250820081510](https://static-docs.nocobase.com/2025081510.png) +![20250820081510](https://static-docs.nocobase.com/20250820081510.png) **올바른 방식 3**: Word 템플릿을 사용합니다. diff --git a/docs/docs/ko/users-permissions/acl/permissions.md b/docs/docs/ko/users-permissions/acl/permissions.md index 391795f8c0b..1aeb323f774 100644 --- a/docs/docs/ko/users-permissions/acl/permissions.md +++ b/docs/docs/ko/users-permissions/acl/permissions.md @@ -26,7 +26,7 @@ pkg: '@nocobase/plugin-acl' ## 컬렉션 작업 권한 -![](https://static-docs.nocobase.com/6a0281391cecdea5b218e6173c5d7.png) +![](https://static-docs.nocobase.com/6a6e0281391cecdea5b5218e6173c5d7.png) ![](https://static-docs.nocobase.com/9814140434ff9e1bf028a6c282a5a165.png) diff --git a/docs/docs/ko/users-permissions/user.md b/docs/docs/ko/users-permissions/user.md index 30d8e8aba88..56ff7a2fc2f 100644 --- a/docs/docs/ko/users-permissions/user.md +++ b/docs/docs/ko/users-permissions/user.md @@ -28,7 +28,7 @@ pkg: '@nocobase/plugin-users' ![](https://static-docs.nocobase.com/d25e06872bd1d48ed8c1139728fa5ff3.png) -![](https://static-docs.nocobase.com/c140cabb240385b9b5aca32a2ec2801.png) +![](https://static-docs.nocobase.com/c140bcaab240385b9b5aca32a2ec2801.png) ## 사용자 비밀번호 변경 diff --git a/docs/docs/ko/workflow/advanced/revisions.md b/docs/docs/ko/workflow/advanced/revisions.md index 68a972cfa10..1614e8ec710 100644 --- a/docs/docs/ko/workflow/advanced/revisions.md +++ b/docs/docs/ko/workflow/advanced/revisions.md @@ -12,7 +12,7 @@ 그 오른쪽에 있는 더 보기("...") 메뉴에서 현재 보고 있는 버전을 기반으로 새 버전으로 복사할 수 있습니다. -![워크플로우를 새 버전으로 복사](https://static-docs.nocobase.com/280798e6caca2af004893390a744256.png) +![워크플로우를 새 버전으로 복사](https://static-docs.nocobase.com/2805798e6caca2af004893390a744256.png) 새 버전으로 복사한 후, "활성화"/"비활성화" 스위치를 클릭하여 해당 버전을 활성화 상태로 전환하면 새로운 워크플로우 버전이 적용됩니다. diff --git a/docs/docs/ko/workflow/nodes/condition.md b/docs/docs/ko/workflow/nodes/condition.md index d41a6cfffc9..d914b99b8a8 100644 --- a/docs/docs/ko/workflow/nodes/condition.md +++ b/docs/docs/ko/workflow/nodes/condition.md @@ -12,7 +12,7 @@ 조건 판단 노드에는 두 가지 모드가 있습니다. "'참'이면 계속" 모드와 "'참'/'거짓' 분기" 모드입니다. 노드를 생성할 때 이 중 하나를 선택해야 하며, 노드 설정에서는 변경할 수 없습니다. -![조건 판단_모드 선택](https://static-docs.nocobase.com/3de27308c1179523d4ad7.png) +![조건 판단_모드 선택](https://static-docs.nocobase.com/3de27308c1179523d8606c66bf3a5fb4.png) "'참'이면 계속" 모드에서는 조건 판단 결과가 '참'일 경우, 워크플로우는 다음 노드를 계속 실행합니다. 그렇지 않으면 워크플로우가 종료되고 실패 상태로 미리 종료됩니다. diff --git a/docs/docs/ko/workflow/nodes/manual.md b/docs/docs/ko/workflow/nodes/manual.md index dc572421832..b87cbbcfc95 100644 --- a/docs/docs/ko/workflow/nodes/manual.md +++ b/docs/docs/ko/workflow/nodes/manual.md @@ -60,7 +60,7 @@ pkg: '@nocobase/plugin-workflow-manual' 노드 데이터 블록도 유사하게, 상위 노드의 데이터 결과를 상세 정보로 표시할 수 있습니다. 예를 들어, 상위 계산 노드의 결과는 담당자의 할 일 작업에 대한 컨텍스트 참조 정보로 활용될 수 있습니다: -![수동 노드_노드 설정_인터페이스 설정_데이터 블록_노드 데이터](https://static-docs.nocobase.com/a583e258a1a4f45db310a72c2d0a404c.png) +![수동 노드_노드 설정_인터페이스 설정_데이터 블록_노드 데이터](https://static-docs.nocobase.com/a583e26e508e954b47e5ddff80d998c4.png) :::info{title=참고} 인터페이스 설정 시 워크플로우는 아직 실행되지 않은 상태이므로, 데이터 블록에는 구체적인 데이터가 표시되지 않습니다. 워크플로우가 트리거되어 실행된 후에야 할 일 팝업 화면에서 특정 워크플로우 인스턴스와 관련된 데이터를 확인할 수 있습니다. @@ -104,11 +104,11 @@ pkg: '@nocobase/plugin-workflow-manual' 페이지의 블록 중에서 "워크플로우 할 일"을 선택하여 할 일 목록 블록을 추가할 수 있습니다: -![수동 노드_할 일 블록 추가](https://static-docs.nocobase.com/198b41754cd73b704267bf30fe5e647.png) +![수동 노드_할 일 블록 추가](https://static-docs.nocobase.com/198b417454cd73b704267bf30fe5e647.png) 할 일 목록 블록 예시: -![수동 노드_할 일 목록](https://static-docs.nocobase.com/cfefb053c6a91c5c9dfa550d6b220f34.png) +![수동 노드_할 일 목록](https://static-docs.nocobase.com/cfefb0d2c6a91c5c9dfa550d6b220f34.png) ### 할 일 상세 정보 diff --git a/docs/docs/ko/workflow/nodes/parallel.md b/docs/docs/ko/workflow/nodes/parallel.md index 0a024e66c55..57716d3014f 100644 --- a/docs/docs/ko/workflow/nodes/parallel.md +++ b/docs/docs/ko/workflow/nodes/parallel.md @@ -22,7 +22,7 @@ pkg: '@nocobase/plugin-workflow-parallel' 워크플로우에 병렬 브랜치 노드를 추가하면 기본적으로 두 개의 하위 브랜치가 추가됩니다. "브랜치 추가" 버튼을 클릭하여 원하는 만큼 브랜치를 더 추가할 수 있습니다. 각 브랜치에는 원하는 수의 노드를 추가할 수 있으며, 필요 없는 브랜치는 브랜치 시작 부분의 삭제 버튼을 클릭하여 제거할 수 있습니다. -![병렬 브랜치 관리](https://static-docs.nocobase.com/36084b8b7970c8a1771eb3ee9bc2a757.png) +![병렬 브랜치 관리](https://static-docs.nocobase.com/36088a8b7970c8a1771eb3ee9bc2a757.png) ## 노드 설정 diff --git a/docs/docs/ko/workflow/nodes/request.md b/docs/docs/ko/workflow/nodes/request.md index 2fbc7f17057..5f0083e0025 100644 --- a/docs/docs/ko/workflow/nodes/request.md +++ b/docs/docs/ko/workflow/nodes/request.md @@ -26,7 +26,7 @@ Postman과 같은 요청 전송 도구에 익숙하시다면 HTTP 요청 노드 ## 노드 설정 -![HTTP请求节点_节点配置](https://static-docs.nocobase.com/2fcb29af63f6869c80f8fbd362a54e644.png) +![HTTP请求节点_节点配置](https://static-docs.nocobase.com/2fcb29af66b892fa704add52e2974a52.png) ### 요청 메서드 diff --git a/docs/docs/ko/workflow/nodes/variable.md b/docs/docs/ko/workflow/nodes/variable.md index 32b24a53b35..4592550e3f7 100644 --- a/docs/docs/ko/workflow/nodes/variable.md +++ b/docs/docs/ko/workflow/nodes/variable.md @@ -16,7 +16,7 @@ pkg: '@nocobase/plugin-workflow-variable' 워크플로우 설정 화면에서 워크플로우 내의 더하기('+'') 버튼을 클릭하여 '변수' 노드를 추가합니다. -![변수 노드 추가](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![변수 노드 추가](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## 노드 설정 @@ -79,6 +79,6 @@ pkg: '@nocobase/plugin-workflow-variable' 이렇게 하면 반복 분기가 완료된 후 수신자 변수에 모든 게시글 작성자의 수신자 문자열이 저장됩니다. 그 다음, 반복 후에 HTTP 요청 노드를 사용하여 이메일 발송 API를 호출하고 수신자 변수의 값을 수신자 매개변수로 API에 전달할 수 있습니다. -![요청 노드를 통해 수신자에게 메일 발송](https://static-docs.nocobase.com/37f71ae1a63e172bcb2dce10a250947e.png) +![요청 노드를 통해 수신자에게 메일 발송](https://static-docs.nocobase.com/37f71aa1a63e172bcb2dce10a250947e.png) 이로써 간단한 대량 이메일 발송 기능이 반복 및 변수 노드를 통해 구현되었습니다. \ No newline at end of file diff --git a/docs/docs/ko/workflow/triggers/post-action.md b/docs/docs/ko/workflow/triggers/post-action.md index cc044ab4d1a..0daf963534b 100644 --- a/docs/docs/ko/workflow/triggers/post-action.md +++ b/docs/docs/ko/workflow/triggers/post-action.md @@ -178,7 +178,7 @@ curl -X POST -H 'Authorization: Bearer ' -H 'X-Role: ' -d 아래 그림과 같습니다. -![작업 실행 순서](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![작업 실행 순서](https://static-docs.nocobase.com/20251219234806.png) ### 컬렉션 이벤트와의 차이점 diff --git a/docs/docs/ko/workflow/triggers/pre-action.md b/docs/docs/ko/workflow/triggers/pre-action.md index df8e1b6599d..b5188c41b78 100644 --- a/docs/docs/ko/workflow/triggers/pre-action.md +++ b/docs/docs/ko/workflow/triggers/pre-action.md @@ -22,7 +22,7 @@ pkg: '@nocobase/plugin-workflow-request-interceptor' 워크플로우를 생성할 때, 유형을 "작업 전 이벤트"로 선택합니다: -![작업 전 이벤트 생성](https://static-docs.nocobase.com/2add03f2bdb0a836baae5fe9846fc4b6.png) +![작업 전 이벤트 생성](https://static-docs.nocobase.com/2add03f2bdb0a836baae5fe9864fc4b6.png) ### 컬렉션 선택 diff --git a/docs/docs/ko/workflow/triggers/schedule.md b/docs/docs/ko/workflow/triggers/schedule.md index 87608bbebe2..12bbd2c351e 100644 --- a/docs/docs/ko/workflow/triggers/schedule.md +++ b/docs/docs/ko/workflow/triggers/schedule.md @@ -74,6 +74,6 @@ 이후 프로세스 로직에 따라 다른 노드를 설정하여, 트리거 데이터 ID와 일치하고 상태가 '미결제'인 주문의 상태를 취소됨으로 업데이트합니다. -![정기 작업_트리거 설정_컬렉션 시간 필드 모드_업데이트 노드](https://static-docs.nocobase.com/491dde9df87ffa1fb24a4e7baa1de6eb29.png) +![정기 작업_트리거 설정_컬렉션 시간 필드 모드_업데이트 노드](https://static-docs.nocobase.com/491dde9df8f773f5b14a4fd8ceac9d3e.png) 사용자 지정 시간 모드와 달리, 여기서는 30분 전 시간을 계산할 필요가 없습니다. 워크플로우 트리거 데이터 컨텍스트에 시간 조건을 만족하는 해당 데이터 행이 이미 포함되어 있기 때문에, 해당 주문의 상태를 직접 업데이트할 수 있습니다. \ No newline at end of file diff --git a/docs/docs/nl/ai-employees/knowledge-base/knowledge-base.md b/docs/docs/nl/ai-employees/knowledge-base/knowledge-base.md index 531747185f2..c74a6e685ed 100644 --- a/docs/docs/nl/ai-employees/knowledge-base/knowledge-base.md +++ b/docs/docs/nl/ai-employees/knowledge-base/knowledge-base.md @@ -55,10 +55,10 @@ Een lokale kennisbank is een kennisbank die lokaal in NocoBase wordt opgeslagen. Een alleen-lezen kennisbank is een kennisbank waarvan de documenten en vectorgegevens extern worden beheerd. Alleen een vector databaseverbinding wordt in NocoBase aangemaakt (momenteel wordt alleen PGVector ondersteund). -![20251023101743](https://static-docs.nocobase.com/2025101743.png) +![20251023101743](https://static-docs.nocobase.com/20251023101743.png) ### Externe kennisbank Een externe kennisbank is een kennisbank waarvan de documenten en vectorgegevens extern worden beheerd. Het ophalen van gegevens uit de vector database moet door ontwikkelaars worden uitgebreid, waardoor het gebruik van vector databases die momenteel niet door NocoBase worden ondersteund, mogelijk wordt. -![20251023101949](https://static-docs.nocobase.com/2025101949.png) \ No newline at end of file +![20251023101949](https://static-docs.nocobase.com/20251023101949.png) \ No newline at end of file diff --git a/docs/docs/nl/ai-employees/permission.md b/docs/docs/nl/ai-employees/permission.md index 5e8b5b28100..1658fd8fa2c 100644 --- a/docs/docs/nl/ai-employees/permission.md +++ b/docs/docs/nl/ai-employees/permission.md @@ -74,7 +74,7 @@ Deze tools worden doorgaans gebruikt voor: #### Voorbeeld 1: Overall Analytics (algemene bedrijfsanalyse) -![05viz-configuration-2025-11-03-00-18-55](https://static-docs.nocobase.com/20251103001855.png) +![05viz-configuration-2025-11-03-00-18-55](https://static-docs.nocobase.com/05viz-configuration-2025-11-03-00-18-55.png) In de CRM Demo is `Overall Analytics` een sjabloongebaseerde bedrijfsanalysemotor: @@ -104,7 +104,7 @@ flowchart TD #### Voorbeeld 2: SQL Execution (geavanceerde analysetool) -![05viz-configuration-2025-11-03-00-17-13](https://static-docs.nocobase.com/20251103001713.png) +![05viz-configuration-2025-11-03-00-17-13](https://static-docs.nocobase.com/05viz-configuration-2025-11-03-00-17-13.png) In de CRM Demo is `SQL Execution` een flexibelere, maar strikt te controleren tool: diff --git a/docs/docs/nl/auth-verification/api-keys/index.md b/docs/docs/nl/auth-verification/api-keys/index.md index 21d30f88f1c..4b400d4e81e 100644 --- a/docs/docs/nl/auth-verification/api-keys/index.md +++ b/docs/docs/nl/auth-verification/api-keys/index.md @@ -17,7 +17,7 @@ http://localhost:13000/admin/settings/api-keys/configuration ### API-sleutel toevoegen -![](https://static-docs.nocobase.com/461872fc0ad9a96fa5b14e97fcba12.png) +![](https://static-docs.nocobase.com/46141872fc0ad9a96fa5b14e97fcba12.png) **Belangrijke opmerkingen** diff --git a/docs/docs/nl/auth-verification/auth-oidc/examples/google.md b/docs/docs/nl/auth-verification/auth-oidc/examples/google.md index 04562c2eba0..de07d0f60d9 100644 --- a/docs/docs/nl/auth-verification/auth-oidc/examples/google.md +++ b/docs/docs/nl/auth-verification/auth-oidc/examples/google.md @@ -10,7 +10,7 @@ Dit document is vertaald door AI. Voor onnauwkeurigheden, raadpleeg [de Engelse [Google Cloud Console](https://console.cloud.google.com/apis/credentials) - Referenties maken - OAuth-client-ID -![](https://static-docs.nocobase.com/0f2946c8643565ecc4ac1324988638c.png) +![](https://static-docs.nocobase.com/0f2946c8643565ecc4ac13249882638c.png) Ga naar de configuratie-interface en vul de geautoriseerde omleidings-URL in. De omleidings-URL kunt u verkrijgen wanneer u een authenticator toevoegt in NocoBase. Meestal is dit `http(s)://host:port/api/oidc:redirect`. Zie het gedeelte [Gebruikershandleiding - Configuratie](../index.md#configuratie). diff --git a/docs/docs/nl/auth-verification/auth-saml/examples/google.md b/docs/docs/nl/auth-verification/auth-saml/examples/google.md index ce9d18c354f..1cfd78d1d30 100644 --- a/docs/docs/nl/auth-verification/auth-saml/examples/google.md +++ b/docs/docs/nl/auth-verification/auth-saml/examples/google.md @@ -33,7 +33,7 @@ Kopieer vervolgens de SP Issuer/Entiteits-ID en de ACS URL uit het gedeelte 'Usa Ga terug naar de Google Console en voer op de pagina **Service Provider Details** de zojuist gekopieerde ACS URL en Entiteits-ID in. Vink ook **Signed Response** aan. -![](https://static-docs.nocobase.com/1536268bf8df4a5ebc7234317172191.png) +![](https://static-docs.nocobase.com/1536268bf8df4a5ebc72384317172191.png) ![](https://static-docs.nocobase.com/c7de1f8b84c1335de110e5a7c96255c4.png) diff --git a/docs/docs/nl/auth-verification/auth-saml/index.md b/docs/docs/nl/auth-verification/auth-saml/index.md index 3d8a67a961f..32a667d8d45 100644 --- a/docs/docs/nl/auth-verification/auth-saml/index.md +++ b/docs/docs/nl/auth-verification/auth-saml/index.md @@ -59,4 +59,4 @@ Het toewijzen van gebruikersorganisaties en -rollen wordt momenteel niet onderst Ga naar de inlogpagina en klik op de knop onder het inlogformulier om in te loggen via een externe service. -![](https://static-docs.nocobase.com/7496365c9d36a294948e6adeb5b24bc.png) \ No newline at end of file +![](https://static-docs.nocobase.com/74963865c9d36a294948e6adeb5b24bc.png) \ No newline at end of file diff --git a/docs/docs/nl/auth-verification/auth/authenticators.md b/docs/docs/nl/auth-verification/auth/authenticators.md index 81985fd75ce..812f852f647 100644 --- a/docs/docs/nl/auth-verification/auth/authenticators.md +++ b/docs/docs/nl/auth-verification/auth/authenticators.md @@ -16,7 +16,7 @@ Wanneer de gebruikersauthenticatie-plugin wordt geïnstalleerd, initialiseert de ## Authenticators activeren -![](https://static-docs.nocobase.com/7f1bf8f8ca5de67ffc68eff0a65848f5.png) +![](https://static-docs.nocobase.com/7f1fb8f8ca5de67ffc68eff0a65848f5.png) Alleen geactiveerde authenticatietypen worden weergegeven op de inlogpagina. diff --git a/docs/docs/nl/auth-verification/auth/dev/index.md b/docs/docs/nl/auth-verification/auth/dev/index.md index b9e4a38da5e..d0e5b1394cc 100644 --- a/docs/docs/nl/auth-verification/auth/dev/index.md +++ b/docs/docs/nl/auth-verification/auth/dev/index.md @@ -168,7 +168,7 @@ Als u van de inlogpagina naar de registratiepagina moet navigeren, moet u dit ze ### Beheerinstellingenformulier -![](https://static-docs.nocobase.com/f4b544b5b0f4f5afee5621ad4abf66b24f.png) +![](https://static-docs.nocobase.com/f4b544b5b0f5afee5621ad4abf66b24f.png) Bovenaan vindt u de algemene authenticatorconfiguratie, en onderaan het deel van het aangepaste configuratieformulier dat kan worden geregistreerd. diff --git a/docs/docs/nl/data-sources/data-modeling/collection-fields/associations/o2o/index.md b/docs/docs/nl/data-sources/data-modeling/collection-fields/associations/o2o/index.md index a5d37d0fee7..8992a77e7d6 100644 --- a/docs/docs/nl/data-sources/data-modeling/collection-fields/associations/o2o/index.md +++ b/docs/docs/nl/data-sources/data-modeling/collection-fields/associations/o2o/index.md @@ -32,7 +32,7 @@ ER Relatie Veldconfiguratie -![alt text](https://static-docs.nocobase.com/4f09eeb3c7717d61a34942da43c187c.png) +![alt text](https://static-docs.nocobase.com/4f09eeb3c7717d61a349842da43c187c.png) ## Parameterbeschrijvingen diff --git a/docs/docs/nl/data-sources/field-encryption/index.md b/docs/docs/nl/data-sources/field-encryption/index.md index 6c039b61fd5..8bfbfe450d8 100644 --- a/docs/docs/nl/data-sources/field-encryption/index.md +++ b/docs/docs/nl/data-sources/field-encryption/index.md @@ -30,7 +30,7 @@ Als de plugin is ingeschakeld voor een sub-applicatie, wordt de sleutel standaar Maakt gebruik van envelopversleuteling. -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### Proces voor sleutelcreatie 1. De eerste keer dat u een versleuteld veld aanmaakt, genereert het systeem automatisch een 32-bits `applicatiesleutel`. Deze wordt in Base64-codering opgeslagen in de standaard opslagmap. diff --git a/docs/docs/nl/email-manager/advanced/batch-send.md b/docs/docs/nl/email-manager/advanced/batch-send.md index 0aa134b61e4..9a167d58f6d 100644 --- a/docs/docs/nl/email-manager/advanced/batch-send.md +++ b/docs/docs/nl/email-manager/advanced/batch-send.md @@ -10,27 +10,27 @@ Dit document is vertaald door AI. Voor onnauwkeurigheden, raadpleeg [de Engelse ## Overzicht bulkverzending U kunt e-mails in bulk naar meerdere personen verzenden (elke ontvanger krijgt een aparte e-mail). -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## Bulkverzending via een tabel U kunt e-mails ook in bulk verzenden via een tabel: 1. Voeg een 'E-mail verzenden'-knop toe aan de tabel - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. Configureer het e-mailveld in de tabel (dit wordt gebruikt om e-mailadressen te parseren nadat u tabelrijen heeft geselecteerd) - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. Vink de tabelgegevens aan om e-mails te verzenden - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) Als u e-mails wilt verzenden naar alle adressen in de hele tabel, kunt u de functie **Standaard alle records in de huidige tabel als ontvangers selecteren** inschakelen: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) Nadat u de e-mailinhoud heeft bewerkt, klikt u op de knop 'Bulk verzenden' om de e-mails te versturen: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## E-mailverzending volgen U kunt de status van specifieke e-mailverzendingen bekijken en volgen in het E-mailbeheercentrum: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/nl/email-manager/usage/signature.md b/docs/docs/nl/email-manager/usage/signature.md index 10539ee799b..3492d1b3027 100644 --- a/docs/docs/nl/email-manager/usage/signature.md +++ b/docs/docs/nl/email-manager/usage/signature.md @@ -11,15 +11,15 @@ Dit document is vertaald door AI. Voor onnauwkeurigheden, raadpleeg [de Engelse ## Handtekening configureren Ga naar het E-mailbeheercentrum en klik op de instellingenknop: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Schakel over naar het handtekeningenpaneel: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) Hier kunt u uw handtekeningen beheren. Vink de optie vóór een handtekening aan om deze als standaard in te stellen: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## Handtekeningen gebruiken Klik in het e-mailtekstvak op het handtekeningpictogram om de gewenste handtekening te selecteren: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/nl/email-manager/usage/template.md b/docs/docs/nl/email-manager/usage/template.md index 0945f75c7f7..bcfd3ae9306 100644 --- a/docs/docs/nl/email-manager/usage/template.md +++ b/docs/docs/nl/email-manager/usage/template.md @@ -11,15 +11,15 @@ Dit document is vertaald door AI. Voor onnauwkeurigheden, raadpleeg [de Engelse ## Sjabloonconfiguratie Ga naar het E-mailbeheercentrum en klik op de instellingenknop: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Schakel over naar het sjablonenpaneel: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) Hier kunt u uw sjablonen beheren: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## Sjablonen gebruiken Klik in het tekstvak van de e-mail op het sjabloonpictogram om het gewenste sjabloon te selecteren: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/nl/flow-engine/learning-roadmap.md b/docs/docs/nl/flow-engine/learning-roadmap.md index 06f3851bc8e..df63d270d3f 100644 --- a/docs/docs/nl/flow-engine/learning-roadmap.md +++ b/docs/docs/nl/flow-engine/learning-roadmap.md @@ -4,4 +4,4 @@ Dit document is vertaald door AI. Voor onnauwkeurigheden, raadpleeg [de Engelse # Leerroutekaart -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/nl/integration/api-doc/index.md b/docs/docs/nl/integration/api-doc/index.md index 543875a7b98..c86214ead50 100644 --- a/docs/docs/nl/integration/api-doc/index.md +++ b/docs/docs/nl/integration/api-doc/index.md @@ -25,7 +25,7 @@ Dit is een ingebouwde plugin, u hoeft deze niet te installeren. Activeer de plug http://localhost:13000/admin/settings/api-doc/documentation -![](https://static-docs.nocobase.com/8db51cf50e3c666aba5a5a850a0fb664a0.png) +![](https://static-docs.nocobase.com/8db51cf50e3c666aba5a850a0fb664a0.png) ### Overzicht van de documentatie diff --git a/docs/docs/nl/integration/api-keys/index.md b/docs/docs/nl/integration/api-keys/index.md index efe5d3e90f5..7642af46f07 100644 --- a/docs/docs/nl/integration/api-keys/index.md +++ b/docs/docs/nl/integration/api-keys/index.md @@ -16,7 +16,7 @@ http://localhost:13000/admin/settings/api-keys/configuration ### API-sleutel toevoegen -![](https://static-docs.nocobase.com/46181872fc0ad9a96fa5b14e97fcba12.png) +![](https://static-docs.nocobase.com/46141872fc0ad9a96fa5b14e97fcba12.png) **Belangrijke opmerkingen** diff --git a/docs/docs/nl/solution/ticket-system/design.md b/docs/docs/nl/solution/ticket-system/design.md index 33f957b6223..cafcdc07549 100755 --- a/docs/docs/nl/solution/ticket-system/design.md +++ b/docs/docs/nl/solution/ticket-system/design.md @@ -31,7 +31,7 @@ Geïnspireerd door het concept van de "T-shaped professional" — horizontale br - **Horizontaal (Hoofdtabel)**: Omvat universele mogelijkheden voor alle bedrijfstypen — ticketnummer, status, behandelaar, SLA en andere kernvelden. - **Verticaal (Extensietabellen)**: Specifieke velden voor gespecialiseerde bedrijfstypen — apparatuurreparatie heeft serienummers, klachten hebben compensatieplannen. -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **Waarom dit ontwerp?** @@ -61,7 +61,7 @@ Geen "AI-functies", maar "AI-medewerkers". Elke AI heeft een duidelijke rol, per #### Filosofie 3: Zelfcirculatie van kennis -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) Dit vormt een gesloten cirkel van **kennisopbouw en kennistoepassing**. @@ -71,7 +71,7 @@ Dit vormt een gesloten cirkel van **kennisopbouw en kennistoepassing**. ### 2.1 Overzicht entiteitsrelaties -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 Details kerntabellen @@ -296,18 +296,18 @@ Dit is de kern van het systeem, ontworpen als een "brede tabel" waarin alle veel **Hoofdstroom (van links naar rechts)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **Substromen** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **Volledige State Machine** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 Belangrijke regels voor statusovergang @@ -337,7 +337,7 @@ Dit is de kern van het systeem, ontworpen als een "brede tabel" waarin alle veel ### 4.2 SLA-berekeningslogica -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### Bij aanmaak ticket @@ -466,7 +466,7 @@ Elke AI-medewerker heeft 4 specifieke taken: ### 5.3 AI-medewerkers en ticket-levenscyclus -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 Voorbeelden van AI-reacties @@ -526,12 +526,12 @@ De kwaliteitscontrole van Grace blokkeert de volgende problemen in antwoorden: ### 6.1 Kennisbronnen -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 Proces van ticket naar kennis -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **Beoordelingsdimensies**: - **Algemeenheid**: Is dit een veelvoorkomend probleem? @@ -576,19 +576,19 @@ Wanneer een medewerker de ticketdetails opent, beveelt Max automatisch relevante #### WF-T01: Ticket-aanmaakproces -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: AI-analyse van tickets -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: Vertaling en beoordeling van opmerkingen -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: Kennisgeneratie -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 Geplande taken @@ -605,11 +605,11 @@ Wanneer een medewerker de ticketdetails opent, beveelt Max automatisch relevante ### 8.1 Beheerdersinterface (Backend) -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 Klantportaal -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 Dashboard-ontwerp diff --git a/docs/docs/nl/users-permissions/acl/role.md b/docs/docs/nl/users-permissions/acl/role.md index 22bc30ccaa4..87ede0d3b6f 100644 --- a/docs/docs/nl/users-permissions/acl/role.md +++ b/docs/docs/nl/users-permissions/acl/role.md @@ -20,7 +20,7 @@ Bij de initiële installatie van de applicatie zijn twee rollen ingebouwd: "Admi De rol-identificatie (een unieke systeem-identificatie) stelt u in staat om standaardrollen aan te passen. De vooraf gedefinieerde systeemrollen kunnen echter niet worden verwijderd. -![](https://static-docs.nocobase.com/35f323b6db4f9f12f9bee4dea63302.png) +![](https://static-docs.nocobase.com/35f323b346db4f9f12f9bee4dea63302.png) ### De standaardrol instellen diff --git a/docs/docs/nl/users-permissions/acl/ui.md b/docs/docs/nl/users-permissions/acl/ui.md index 3838cc624c9..3aed238e8bc 100644 --- a/docs/docs/nl/users-permissions/acl/ui.md +++ b/docs/docs/nl/users-permissions/acl/ui.md @@ -32,11 +32,11 @@ Het volledige configuratieproces ziet er als volgt uit: **Bekijken**: Bepaalt of specifieke velden zichtbaar zijn op veldniveau. Hiermee kunt u bijvoorbeeld instellen welke velden van de collectie 'Bestellingen' zichtbaar zijn voor bepaalde rollen. -![](https://static-docs.nocobase.com/30dea84d84d95039e6f7b180955a6cf.png) +![](https://static-docs.nocobase.com/30dea84d984d95039e6f7b180955a6cf.png) In de UI worden in het blok van de collectie 'Bestellingen' alleen velden weergegeven waarvoor rechten zijn geconfigureerd. Systeemvelden (Id, CreatedAt, LastUpdatedAt) behouden hun 'bekijken'-rechten, zelfs zonder specifieke configuratie. -![](https://static-docs.nocobase.com/40cc4717efe701147fd2e799e79dcc.png) +![](https://static-docs.nocobase.com/40cc49b517efe701147fd2e799e79dcc.png) - **Bewerken**: Bepaalt of velden bewerkt en opgeslagen (bijgewerkt) kunnen worden. diff --git a/docs/docs/nl/users-permissions/departments/role.md b/docs/docs/nl/users-permissions/departments/role.md index 4c2108acec5..eedad006078 100644 --- a/docs/docs/nl/users-permissions/departments/role.md +++ b/docs/docs/nl/users-permissions/departments/role.md @@ -18,7 +18,7 @@ De eerste manier is om een rol te selecteren in het rolveld van het afdeling-bew De tweede manier is om in het rolbeheer afdelingen toe te voegen aan de betreffende rol. -![](https://static-docs.nocobase.com/f2a7bec37cf2f179ce868a92b98416d.png) +![](https://static-docs.nocobase.com/f2a7bec937cf2f179ce868a92b98416d.png) Afdelingen die deze rol al hebben, kunnen niet worden geselecteerd. diff --git a/docs/docs/nl/users-permissions/user.md b/docs/docs/nl/users-permissions/user.md index 42265fe7b9f..000f289612b 100644 --- a/docs/docs/nl/users-permissions/user.md +++ b/docs/docs/nl/users-permissions/user.md @@ -16,7 +16,7 @@ Deze plugin biedt een gebruikersbeheerinterface in het configuratiecentrum. Na h Daarnaast kunt u op de pagina verschillende blokken van de Gebruikers **collectie** toevoegen om gebruikers te beheren, zoals tabelblokken: -![](https://static-docs.nocobase.com/76c5a4652f869541a9e8f18a4568a7c9.png) +![](https://static-docs.nocobase.com/76b5a4652f869541a9e8f18a4568a7c9.png) ## Gebruiker toevoegen diff --git a/docs/docs/nl/workflow/nodes/calculation.md b/docs/docs/nl/workflow/nodes/calculation.md index 83a3ce50204..77a55bf516a 100644 --- a/docs/docs/nl/workflow/nodes/calculation.md +++ b/docs/docs/nl/workflow/nodes/calculation.md @@ -10,11 +10,11 @@ Met het Berekeningsknooppunt kunt u een uitdrukking evalueren. Het resultaat wor In de **workflow**-configuratie-interface klikt u op de plusknop ('+') in de flow om een 'Berekening'-knooppunt toe te voegen: -![计算节点_添加](https://static-docs.nocobase.com/58a466540d26945251cd143eb4b16579.png) +![计算节点_添加](https://static-docs.nocobase.com/58a455540d26945251cd143eb4b16579.png) ## Knooppuntconfiguratie -![计算节点_节点配置](https://static-docs.nocobase.com/6a155de3f8d3cd1881b2d9c33874.png) +![计算节点_节点配置](https://static-docs.nocobase.com/6a155de3f6a883d8cd1881b2d9c33874.png) ### Berekeningsengine diff --git a/docs/docs/nl/workflow/nodes/condition.md b/docs/docs/nl/workflow/nodes/condition.md index 84a3c24e962..d073c1320df 100644 --- a/docs/docs/nl/workflow/nodes/condition.md +++ b/docs/docs/nl/workflow/nodes/condition.md @@ -12,7 +12,7 @@ Net als een `if`-statement in programmeertalen, bepaalt een conditie de verdere De Conditie-node heeft twee modi: 'Doorgaan bij waar' en 'Splitsen bij waar/onwaar'. U moet één van deze modi kiezen wanneer u de node aanmaakt; deze kan later niet meer worden gewijzigd in de configuratie van de node. -![条件判断_模式选择](https://static-docs.nocobase.com/3de27308c1179523d606c66bf3a5fb4.png) +![条件判断_模式选择](https://static-docs.nocobase.com/3de27308c1179523d8606c66bf3a5fb4.png) In de modus 'Doorgaan bij waar' zal de workflow de volgende nodes uitvoeren wanneer het resultaat van de conditie 'waar' is. Anders wordt de workflow beëindigd en voortijdig afgesloten met een mislukte status. diff --git a/docs/docs/nl/workflow/nodes/manual.md b/docs/docs/nl/workflow/nodes/manual.md index 73707b7b256..8f9449a442f 100644 --- a/docs/docs/nl/workflow/nodes/manual.md +++ b/docs/docs/nl/workflow/nodes/manual.md @@ -60,7 +60,7 @@ Datablokken kunnen triggergegevens of de verwerkingsresultaten van elke knoop we Datablokken voor knoopgegevens werken op een vergelijkbare manier; u kunt het gegevensresultaat van een stroomopwaartse knoop selecteren om als details weer te geven. Denk bijvoorbeeld aan het resultaat van een stroomopwaartse rekenknoop, dat dient als contextuele referentie-informatie voor de taak van de verantwoordelijke: -![Handmatige knoop_Knoopconfiguratie_Interfaceconfiguratie_Datablok_Knoopgegevens](https://static-docs.nocobase.com/a583e26e508e95440d998c4.png) +![Handmatige knoop_Knoopconfiguratie_Interfaceconfiguratie_Datablok_Knoopgegevens](https://static-docs.nocobase.com/a583e26e508e954b47e5ddff80d998c4.png) :::info{title=Tip} Aangezien de workflow zich tijdens de interfaceconfiguratie in een niet-uitgevoerde staat bevindt, worden er geen specifieke gegevens weergegeven in de datablokken. De relevante gegevens voor een specifieke workflow-instantie zijn pas zichtbaar in de takenlijstpop-up nadat de workflow is geactiveerd en uitgevoerd. @@ -104,11 +104,11 @@ Voor handmatige verwerking moet u ook een takenlijst aan een pagina toevoegen om U kunt "Workflow Takenlijst" selecteren uit de blokken op een pagina om een blok voor de takenlijst toe te voegen: -![Handmatige knoop_Takenlijstblok toevoegen](https://static-docs.nocobase.com/198b41754cd73b704267bf30fe5e647.png) +![Handmatige knoop_Takenlijstblok toevoegen](https://static-docs.nocobase.com/198b417454cd73b704267bf30fe5e647.png) Voorbeeld van een takenlijstblok: -![Handmatige knoop_Takenlijst](https://static-docs.nocobase.com/cfefb0d34.png) +![Handmatige knoop_Takenlijst](https://static-docs.nocobase.com/cfefb0d2c6a91c5c9dfa550d6b220f34.png) ### Takenlijstdetails diff --git a/docs/docs/nl/workflow/nodes/update.md b/docs/docs/nl/workflow/nodes/update.md index e650a85ec2c..48950a39a94 100644 --- a/docs/docs/nl/workflow/nodes/update.md +++ b/docs/docs/nl/workflow/nodes/update.md @@ -16,7 +16,7 @@ In de workflow configuratie-interface klikt u op de plusknop ('+') in de workflo ## Node configuratie -![更新节点_节点配置](https://static-docs.nocobase.com/98e0f941c7275fc835f08260d0b2e86.png) +![更新节点_节点配置](https://static-docs.nocobase.com/98e0f941c57275fc835f08260d0b2e86.png) ### Collectie @@ -45,6 +45,6 @@ Let op: Gegevens die door de 'Gegevens bijwerken' node in een workflow worden bi Stel bijvoorbeeld dat u bij het aanmaken van een nieuw 'Artikel' automatisch het veld 'Aantal artikelen' in de 'Artikelcategorie' collectie wilt bijwerken. Dit kunt u realiseren met de 'Gegevens bijwerken' node: -![更新节点_示例_节点配置](https://static-docs.nocobase.com/98e0f941c7275fc835f08260d0b2e86.png) +![更新节点_示例_节点配置](https://static-docs.nocobase.com/98e0f941c57275fc835f08260d0b2e86.png) Nadat de workflow is geactiveerd, wordt het veld 'Aantal artikelen' in de 'Artikelcategorie' collectie automatisch bijgewerkt naar het huidige aantal artikelen + 1. \ No newline at end of file diff --git a/docs/docs/nl/workflow/nodes/variable.md b/docs/docs/nl/workflow/nodes/variable.md index d23fe3c2120..a8e30a0677f 100644 --- a/docs/docs/nl/workflow/nodes/variable.md +++ b/docs/docs/nl/workflow/nodes/variable.md @@ -16,7 +16,7 @@ U kunt variabelen declareren in een workflow of waarden toewijzen aan reeds gede In de workflow configuratie-interface klikt u op de plusknop ("+") in de workflow om een "Variabele" knooppunt toe te voegen: -![Add Variable Node](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![Add Variable Node](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## Knooppunt configureren @@ -79,6 +79,6 @@ Na het rekenknooppunt maakt u nog een variabele knooppunt aan. Selecteer de toew Op deze manier, nadat de lusvertakking is voltooid, bevat de ontvanger-variabele de ontvanger-string van alle auteurs van het artikel. Vervolgens kunt u na de lus een HTTP-verzoek knooppunt gebruiken om een e-mailverzend-API aan te roepen, waarbij u de waarde van de ontvanger-variabele als ontvangerparameter aan de API doorgeeft: -![Send mail to recipients via the request node](https://static-docs.nocobase.com/37f71aa1c3e172bcb2dce10a250947e.png) +![Send mail to recipients via the request node](https://static-docs.nocobase.com/37f71aa1a63e172bcb2dce10a250947e.png) Hiermee is een eenvoudige bulk-e-mailfunctie geïmplementeerd met behulp van een lus en een variabele knooppunt. \ No newline at end of file diff --git a/docs/docs/nl/workflow/triggers/post-action.md b/docs/docs/nl/workflow/triggers/post-action.md index 9350e530125..30cd5d8747a 100644 --- a/docs/docs/nl/workflow/triggers/post-action.md +++ b/docs/docs/nl/workflow/triggers/post-action.md @@ -178,7 +178,7 @@ Als de gebeurtenis is geconfigureerd in de globale modus, hoeft u de URL-paramet Zoals weergegeven in de onderstaande afbeelding: -![Action Execution Order](https://static-docs.nocobase.com/7c901be2267d785205b70391332b7.png) +![Action Execution Order](https://static-docs.nocobase.com/20251219234806.png) ### Verschil met **collectie**-gebeurtenis diff --git a/docs/docs/nl/workflow/triggers/pre-action.md b/docs/docs/nl/workflow/triggers/pre-action.md index 6d6b5cdc845..db109aa83fe 100644 --- a/docs/docs/nl/workflow/triggers/pre-action.md +++ b/docs/docs/nl/workflow/triggers/pre-action.md @@ -22,13 +22,13 @@ Door het te gebruiken in combinatie met het knooppunt "Antwoordbericht", kunt u Wanneer u een **workflow** aanmaakt, selecteert u het type "Gebeurtenis vóór actie": -![Create Before Action Event](https://static-docs.nocobase.com/2add03f2bdb0a86baae5fe9864fc4b6.png) +![Create Before Action Event](https://static-docs.nocobase.com/2add03f2bdb0a836baae5fe9864fc4b6.png) ### Collectie selecteren In de trigger van een interceptie-**workflow** is het eerste wat u moet configureren de **collectie** die overeenkomt met de actie: -![Interceptor Event Configuration_Collection](https://static-docs.nocobase.com/8f712caca159d334cf776f838d53d6.png) +![Interceptor Event Configuration_Collection](https://static-docs.nocobase.com/8f7122caca8159d334cf776f838d53d6.png) Vervolgens selecteert u de interceptiemodus. U kunt ervoor kiezen om alleen de actieknop te onderscheppen die aan deze **workflow** is gekoppeld, of om alle geselecteerde acties voor deze **collectie** te onderscheppen (ongeacht uit welk formulier ze komen, en zonder dat de bijbehorende **workflow** hoeft te worden gekoppeld): @@ -111,7 +111,7 @@ Het conditieknooppunt binnen de lus wordt gebruikt om te bepalen of de voorraad Andere configuraties zijn hetzelfde als in het basisgebruik. Wanneer de bestelling uiteindelijk wordt ingediend, wordt de bestelling onderschept en wordt een bijbehorende melding teruggestuurd als een product onvoldoende voorraad heeft. Probeer tijdens het testen een bestelling in te dienen met meerdere producten, waarbij één product onvoldoende voorraad heeft en een ander voldoende. U ziet dan het geretourneerde antwoordbericht: -![Example_Response Message after Submission](https://static-docs.nocobase.com/dd9e81084aa237d5629595ab6cf00f8aa898e3.png) +![Example_Response Message after Submission](https://static-docs.nocobase.com/dd9e81084aa237bda0241d399ac19270.png) Zoals u kunt zien, geeft het antwoordbericht niet aan dat het eerste product, "iPhone 15 pro", onvoldoende voorraad heeft, maar alleen dat het tweede product, "iPhone 14 pro", onvoldoende voorraad heeft. Dit komt omdat in de lus het eerste product voldoende voorraad had en daarom niet werd onderschept, terwijl het tweede product onvoldoende voorraad had, wat de orderinzending onderschepte. diff --git a/docs/docs/nl/workflow/triggers/schedule.md b/docs/docs/nl/workflow/triggers/schedule.md index 5828117abf2..c1b64ee7ae3 100644 --- a/docs/docs/nl/workflow/triggers/schedule.md +++ b/docs/docs/nl/workflow/triggers/schedule.md @@ -70,7 +70,7 @@ Nadat de workflow is ingeschakeld, wordt deze elke minuut geactiveerd vanaf de s Maak een workflow aan op basis van een geplande taak. In de triggerconfiguratie kiest u de modus "Tijdveld van een collectie". Selecteer de collectie "Bestellingen". Stel de starttijd in op 30 minuten na de aanmaaktijd van de bestelling en kies "Niet herhalen" voor de herhalingsregel: -![Geplande taak_Triggerconfiguratie_Tijdveld van een collectie modus_Trigger](https://static-docs.nocobase.com/d40b5aef57f42799d31cc5882dd94246.png) +![Geplande taak_Triggerconfiguratie_Tijdveld van een collectie modus_Trigger](https://static-docs.nocobase.com/d40d5aef57f42799d31cc5882dd94246.png) Configureer vervolgens andere knooppunten volgens de proceslogica. Werk de status van de bestelling met de triggerdata-ID en de status "onbetaald" bij naar 'geannuleerd': diff --git a/docs/docs/pl/ai-employees/knowledge-base/knowledge-base.md b/docs/docs/pl/ai-employees/knowledge-base/knowledge-base.md index ecb2a77e1e3..a6c7841d363 100644 --- a/docs/docs/pl/ai-employees/knowledge-base/knowledge-base.md +++ b/docs/docs/pl/ai-employees/knowledge-base/knowledge-base.md @@ -35,13 +35,13 @@ Po utworzeniu bazy wiedzy, na stronie listy baz wiedzy, proszę kliknąć nowo u ![20251023100458](https://static-docs.nocobase.com/20251023100458.png) -![20251023100527](https://static-docs.nocobase.com/2025100527.png) +![20251023100527](https://static-docs.nocobase.com/20251023100527.png) Proszę kliknąć przycisk `Upload`, aby przesłać dokumenty. Po przesłaniu dokumentów automatycznie rozpocznie się wektoryzacja. Proszę poczekać, aż `Status` zmieni się ze stanu `Pending` na `Success`. Obecnie baza wiedzy obsługuje następujące typy dokumentów: txt, pdf, doc, docx, ppt, pptx; pliki PDF obsługują wyłącznie czysty tekst. -![20251023100901](https://static-docs.nocobase.com/2025100901.png) +![20251023100901](https://static-docs.nocobase.com/20251023100901.png) ## Typy baz wiedzy @@ -49,16 +49,16 @@ Obecnie baza wiedzy obsługuje następujące typy dokumentów: txt, pdf, doc, do Lokalna baza wiedzy to baza wiedzy przechowywana lokalnie w NocoBase. Zarówno dokumenty, jak i ich dane wektorowe są przechowywane lokalnie przez NocoBase. -![20251023101620](https://static-docs.nocobase.com/2025101620.png) +![20251023101620](https://static-docs.nocobase.com/20251023101620.png) ### Baza wiedzy tylko do odczytu Baza wiedzy tylko do odczytu to baza wiedzy, której dokumenty i dane wektorowe są utrzymywane zewnętrznie. W NocoBase tworzone jest jedynie połączenie z wektorową bazą danych (obecnie obsługiwany jest tylko PGVector). -![20251023101743](https://static-docs.nocobase.com/2025101743.png) +![20251023101743](https://static-docs.nocobase.com/20251023101743.png) ### Zewnętrzna baza wiedzy Zewnętrzna baza wiedzy to baza wiedzy, której dokumenty i dane wektorowe są utrzymywane zewnętrznie. Wyszukiwanie w wektorowej bazie danych wymaga rozszerzenia przez deweloperów, co umożliwia korzystanie z baz danych wektorowych, które nie są obecnie obsługiwane przez NocoBase. -![20251023101949](https://static-docs.nocobase.com/2025101949.png) \ No newline at end of file +![20251023101949](https://static-docs.nocobase.com/20251023101949.png) \ No newline at end of file diff --git a/docs/docs/pl/auth-verification/auth-oidc/index.md b/docs/docs/pl/auth-verification/auth-oidc/index.md index 14da8aa612c..c4b1f1623ec 100644 --- a/docs/docs/pl/auth-verification/auth-oidc/index.md +++ b/docs/docs/pl/auth-verification/auth-oidc/index.md @@ -44,7 +44,7 @@ Dodaj - OIDC ### Mapowanie pól -![](https://static-docs.nocobase.com/92d3c8f6f4082b50d9f475674cb5650.png) +![](https://static-docs.nocobase.com/92d63c8f6f4082b50d9f475674cb5650.png) | Ustawienie | Opis | | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/docs/docs/pl/auth-verification/auth-saml/examples/google.md b/docs/docs/pl/auth-verification/auth-saml/examples/google.md index d71007d4dfb..6bb9c18be98 100644 --- a/docs/docs/pl/auth-verification/auth-saml/examples/google.md +++ b/docs/docs/pl/auth-verification/auth-saml/examples/google.md @@ -12,7 +12,7 @@ Ten dokument został przetłumaczony przez AI. W przypadku niedokładności, pro Po skonfigurowaniu aplikacji proszę skopiować **URL SSO**, **Entity ID** oraz **Certyfikat**. -![](https://static-docs.nocobase.com/aafd20a730e85411c0c8f368637e0.png) +![](https://static-docs.nocobase.com/aafd20a794730e85411c0c8f368637e0.png) ## Dodawanie nowego uwierzytelniacza w NocoBase diff --git a/docs/docs/pl/auth-verification/auth-saml/index.md b/docs/docs/pl/auth-verification/auth-saml/index.md index fdc5af42fcb..2db8dbf1dec 100644 --- a/docs/docs/pl/auth-verification/auth-saml/index.md +++ b/docs/docs/pl/auth-verification/auth-saml/index.md @@ -28,7 +28,7 @@ Dodaj - SAML ## Konfiguracja -![](https://static-docs.nocobase.com/976b66e58973c322d81dcddd22c6146.png) +![](https://static-docs.nocobase.com/976b66e589973c322d81dcddd22c6146.png) - Adres URL SSO (Single Sign-On) – dostarczany przez IdP, używany do logowania jednokrotnego. - Certyfikat publiczny (Public Certificate) – dostarczany przez IdP. diff --git a/docs/docs/pl/data-sources/collection-expression/collection.md b/docs/docs/pl/data-sources/collection-expression/collection.md index 776c234a541..90a6ed6880e 100644 --- a/docs/docs/pl/data-sources/collection-expression/collection.md +++ b/docs/docs/pl/data-sources/collection-expression/collection.md @@ -24,4 +24,4 @@ Po utworzeniu formuł należy je powiązać z danymi biznesowymi. Bezpośrednie Na przykład, proszę utworzyć przepływ pracy wyzwalany zdarzeniem kolekcji. Gdy zamówienie zostanie utworzone, wyzwalacz powinien wstępnie załadować powiązane dane produktów wraz z danymi wyrażeń dotyczącymi produktów: -![Zdarzenie kolekcji_Konfiguracja wyzwalacza](https://static-docs.nocobase.com/f181f1b5b10007afd5de068f3458d2e04.png) \ No newline at end of file +![Zdarzenie kolekcji_Konfiguracja wyzwalacza](https://static-docs.nocobase.com/f181f75b10007afd5de068f3458d2e04.png) \ No newline at end of file diff --git a/docs/docs/pl/data-sources/collection-fdw/index.md b/docs/docs/pl/data-sources/collection-fdw/index.md index 4a6b9ea006e..5df9d39672a 100644 --- a/docs/docs/pl/data-sources/collection-fdw/index.md +++ b/docs/docs/pl/data-sources/collection-fdw/index.md @@ -45,7 +45,7 @@ Następnie należy zainstalować i aktywować wtyczkę za pomocą menedżera wty W menu rozwijanym „Zarządzanie kolekcjami > Utwórz kolekcję” proszę wybrać opcję „Połącz z danymi zewnętrznymi”. -![Połącz z danymi zewnętrznymi](https://static-docs.nocobase.com/029d946a6d067d1c35a397551219d623c.png) +![Połącz z danymi zewnętrznymi](https://static-docs.nocobase.com/029d946a6d067d1c35a39755219d623c.png) W menu rozwijanym „Usługa bazy danych” proszę wybrać istniejącą usługę bazy danych lub opcję „Utwórz usługę bazy danych”. @@ -73,4 +73,4 @@ Synchronizacja zdalnej kolekcji danych Na koniec, wyświetlanie w interfejsie. -![Wyświetlanie w interfejsie](https://static-docs.nocobase.com/368fca27a9938080530949357.png) \ No newline at end of file +![Wyświetlanie w interfejsie](https://static-docs.nocobase.com/368fca27a99277d9360ca81350949357.png) \ No newline at end of file diff --git a/docs/docs/pl/data-sources/data-modeling/collection-fields/associations/m2o/index.md b/docs/docs/pl/data-sources/data-modeling/collection-fields/associations/m2o/index.md index 67f0c41ae32..030b779278f 100644 --- a/docs/docs/pl/data-sources/data-modeling/collection-fields/associations/m2o/index.md +++ b/docs/docs/pl/data-sources/data-modeling/collection-fields/associations/m2o/index.md @@ -12,7 +12,7 @@ Diagram ER: Konfiguracja pola: -![alt text](https://static-docs.nocobase.com/3b4484ebb84f82f832f3dbf752bd84c9.png) +![alt text](https://static-docs.nocobase.com/3b4484ebb98d82f832f3dbf752bd84c9.png) ## Opis parametrów diff --git a/docs/docs/pl/data-sources/data-modeling/collection-fields/associations/o2o/index.md b/docs/docs/pl/data-sources/data-modeling/collection-fields/associations/o2o/index.md index dfb45b571ad..7b1c9a4e14a 100644 --- a/docs/docs/pl/data-sources/data-modeling/collection-fields/associations/o2o/index.md +++ b/docs/docs/pl/data-sources/data-modeling/collection-fields/associations/o2o/index.md @@ -20,7 +20,7 @@ Relacja ER Konfiguracja pola -![alt text](https://static-docs.nocobase.com/765a87e094b4fb50c9426a108f87105.png) +![alt text](https://static-docs.nocobase.com/7665a87e094b4fb50c9426a108f87105.png) ## Jeden do jednego (Należy do) diff --git a/docs/docs/pl/data-sources/field-encryption/index.md b/docs/docs/pl/data-sources/field-encryption/index.md index 5656b04cd78..2c5bec5babc 100644 --- a/docs/docs/pl/data-sources/field-encryption/index.md +++ b/docs/docs/pl/data-sources/field-encryption/index.md @@ -30,7 +30,7 @@ Jeśli wtyczka jest włączona dla podaplikacji, klucz jest domyślnie zapisywan Wykorzystuje szyfrowanie kopertowe (Envelope Encryption). -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### Proces tworzenia kluczy 1. Przy pierwszym tworzeniu zaszyfrowanego pola automatycznie generowany jest 32-bitowy `klucz aplikacji` i zapisywany w domyślnym katalogu przechowywania w kodowaniu Base64. diff --git a/docs/docs/pl/data-visualization/guide/chart-options.md b/docs/docs/pl/data-visualization/guide/chart-options.md index 3f1dd55992b..b93477e58d4 100644 --- a/docs/docs/pl/data-visualization/guide/chart-options.md +++ b/docs/docs/pl/data-visualization/guide/chart-options.md @@ -90,7 +90,7 @@ return { - W trybie Custom, po zakończeniu edycji, mogą Państwo kliknąć przycisk „Podgląd” po prawej stronie, aby zaktualizować podgląd wykresu. - Na dole proszę kliknąć „Zapisz”, aby zastosować i utrwalić konfigurację; proszę kliknąć „Anuluj”, aby cofnąć wszystkie wprowadzone zmiany. -![20251026192816](https://static-docs.nocobase.com/clipboard-image-1761473695.png) +![20251026192816](https://static-docs.nocobase.com/20251026192816.png) > [!TIP] > Więcej informacji na temat opcji wykresów znajdą Państwo w sekcji Zaawansowane — Niestandardowa konfiguracja wykresów. \ No newline at end of file diff --git a/docs/docs/pl/email-manager/advanced/batch-send.md b/docs/docs/pl/email-manager/advanced/batch-send.md index c28ed1aac61..57b16ee9666 100644 --- a/docs/docs/pl/email-manager/advanced/batch-send.md +++ b/docs/docs/pl/email-manager/advanced/batch-send.md @@ -10,27 +10,27 @@ Ten dokument został przetłumaczony przez AI. W przypadku niedokładności, pro ## Przegląd wysyłki masowej Mogą Państwo wysyłać wiadomości e-mail do wielu osób jednocześnie (każdy odbiorca otrzyma osobną wiadomość). -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## Wysyłka masowa za pomocą tabeli Mogą Państwo również wysyłać wiadomości e-mail masowo, korzystając z tabeli: 1. Dodaj przycisk wysyłki e-mail do tabeli - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. Skonfiguruj pole e-mail w tabeli (służy do parsowania adresów e-mail po zaznaczeniu wierszy tabeli) - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. Zaznacz dane w tabeli, aby wysłać wiadomości e-mail - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) Jeśli chcą Państwo wysłać wiadomości e-mail do wszystkich adresów w całej tabeli, mogą Państwo włączyć funkcję **Domyślnie zaznacz wszystkie rekordy w bieżącej tabeli jako odbiorców**: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) Po edycji treści wiadomości e-mail, proszę kliknąć przycisk wysyłki masowej, aby wysłać: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## Śledzenie wysyłki e-mail Mogą Państwo przeglądać i śledzić status wysyłki poszczególnych wiadomości e-mail w Centrum Zarządzania E-mailami: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/pl/email-manager/usage/signature.md b/docs/docs/pl/email-manager/usage/signature.md index 1fe8e388b59..b3475ec6168 100644 --- a/docs/docs/pl/email-manager/usage/signature.md +++ b/docs/docs/pl/email-manager/usage/signature.md @@ -12,18 +12,18 @@ Ten dokument został przetłumaczony przez AI. W przypadku niedokładności, pro Proszę przejść do Centrum Zarządzania E-mailami i kliknąć przycisk ustawień: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Następnie proszę przełączyć się na panel podpisu: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) Tutaj mogą Państwo zarządzać podpisami. Zaznaczenie opcji przed podpisem pozwala ustawić go jako domyślny: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## Używanie podpisów W treści wiadomości e-mail proszę kliknąć ikonę podpisu, aby wybrać żądany podpis: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/pl/email-manager/usage/template.md b/docs/docs/pl/email-manager/usage/template.md index e8907becc65..ee6e1783cce 100644 --- a/docs/docs/pl/email-manager/usage/template.md +++ b/docs/docs/pl/email-manager/usage/template.md @@ -13,18 +13,18 @@ Ten dokument został przetłumaczony przez AI. W przypadku niedokładności, pro Proszę przejść do Centrum Zarządzania E-mailami i kliknąć przycisk ustawień: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Następnie proszę przełączyć się do panelu szablonów: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) Tutaj mogą Państwo zarządzać szablonami: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## Używanie Szablonów W polu treści wiadomości e-mail proszę kliknąć ikonę szablonu, aby wybrać odpowiedni szablon: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/pl/flow-engine/learning-roadmap.md b/docs/docs/pl/flow-engine/learning-roadmap.md index 8c4dfa8dd2d..d9f9a2bd4aa 100644 --- a/docs/docs/pl/flow-engine/learning-roadmap.md +++ b/docs/docs/pl/flow-engine/learning-roadmap.md @@ -4,4 +4,4 @@ Ten dokument został przetłumaczony przez AI. W przypadku niedokładności, pro # Mapa drogowa nauki -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/pl/integration/sso/index.md b/docs/docs/pl/integration/sso/index.md index 952537feb80..34ae924eaf4 100644 --- a/docs/docs/pl/integration/sso/index.md +++ b/docs/docs/pl/integration/sso/index.md @@ -92,7 +92,7 @@ Po zakończeniu konfiguracji zalecamy przeprowadzenie testowego logowania: 1. Proszę wylogować się z bieżącej sesji. 2. Na stronie logowania proszę wybrać skonfigurowaną metodę SSO. -![](https://static-docs.nocobase.com/74963865c9d36a2949486adeb5b24bc.png) +![](https://static-docs.nocobase.com/74963865c9d36a294948e6adeb5b24bc.png) 3. Proszę ukończyć proces uwierzytelniania u dostawcy tożsamości. 4. Proszę zweryfikować, czy logowanie do NocoBase zakończyło się sukcesem. diff --git a/docs/docs/pl/solution/ticket-system/design.md b/docs/docs/pl/solution/ticket-system/design.md index 46d3ce036cb..6425800fc22 100755 --- a/docs/docs/pl/solution/ticket-system/design.md +++ b/docs/docs/pl/solution/ticket-system/design.md @@ -31,7 +31,7 @@ Nawiązuje ona do koncepcji "talentu typu T" — pozioma szerokość + pionowa g - **Poziomo (Tabela główna)**: Obejmuje uniwersalne możliwości dla wszystkich typów biznesowych — numer zgłoszenia, status, osoba przypisana, SLA i inne kluczowe pola. - **Pionowo (Tabele rozszerzeń)**: Specjalistyczne pola dla konkretnych rodzajów działalności — naprawa sprzętu zawiera numery seryjne, a reklamacje zawierają plany rekompensat. -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **Dlaczego taka konstrukcja?** @@ -61,7 +61,7 @@ To nie tylko "funkcje AI", ale "pracownicy AI". Każdy AI ma określoną rolę, #### Koncepcja trzecia: Samoobieg wiedzy -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) Tworzy to zamkniętą pętlę **gromadzenia wiedzy i jej stosowania**. @@ -71,7 +71,7 @@ Tworzy to zamkniętą pętlę **gromadzenia wiedzy i jej stosowania**. ### 2.1 Przegląd relacji encji -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 Szczegóły kluczowych tabel @@ -296,18 +296,18 @@ Jest to rdzeń systemu, wykorzystujący konstrukcję "szerokiej tabeli", w któr **Główny proces (od lewej do prawej)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **Procesy poboczne** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **Pełny automat stanów** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 Kluczowe reguły zmiany statusu @@ -337,7 +337,7 @@ Jest to rdzeń systemu, wykorzystujący konstrukcję "szerokiej tabeli", w któr ### 4.2 Logika obliczeń SLA -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### Przy tworzeniu zgłoszenia @@ -466,7 +466,7 @@ Każdy pracownik AI ma skonfigurowane 4 konkretne zadania: ### 5.3 Pracownicy AI w cyklu życia zgłoszenia -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 Przykłady odpowiedzi AI @@ -526,12 +526,12 @@ Grace odpowiada za audyt jakości odpowiedzi, blokując następujące problemy: ### 6.1 Źródła wiedzy -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 Proces przekształcania zgłoszenia w wiedzę -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **Wymiary oceny**: - **Uniwersalność**: Czy to częsty problem? @@ -576,19 +576,19 @@ Gdy agent otwiera szczegóły zgłoszenia, Max automatycznie rekomenduje wiedzę #### WF-T01: Proces tworzenia zgłoszenia -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: Analiza zgłoszenia przez AI -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: Tłumaczenie i audyt komentarzy -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: Generowanie wiedzy -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 Zadania zaplanowane @@ -605,11 +605,11 @@ Gdy agent otwiera szczegóły zgłoszenia, Max automatycznie rekomenduje wiedzę ### 8.1 Panel administracyjny -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 Portal klienta -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 Projekt pulpitów nawigacyjnych diff --git a/docs/docs/pl/users-permissions/acl/permissions.md b/docs/docs/pl/users-permissions/acl/permissions.md index 38a213abc5e..0ed6e3e693c 100644 --- a/docs/docs/pl/users-permissions/acl/permissions.md +++ b/docs/docs/pl/users-permissions/acl/permissions.md @@ -26,7 +26,7 @@ Globalne uprawnienia do operacji mają zastosowanie uniwersalnie do wszystkich k ## Uprawnienia do operacji na kolekcjach -![](https://static-docs.nocobase.com/6a6e028139cecdea5b71210121d0d3a435d.png) +![](https://static-docs.nocobase.com/6a6e0281391cecdea5b5218e6173c5d7.png) ![](https://static-docs.nocobase.com/9814140434ff9e1bf028a6c282a5a165.png) diff --git a/docs/docs/pl/users-permissions/acl/role.md b/docs/docs/pl/users-permissions/acl/role.md index e9e4c78e67e..9b46ce18130 100644 --- a/docs/docs/pl/users-permissions/acl/role.md +++ b/docs/docs/pl/users-permissions/acl/role.md @@ -26,7 +26,7 @@ Identyfikator roli, będący unikalnym identyfikatorem systemowym, pozwala Pańs Rola domyślna to ta, która zostanie automatycznie przypisana nowym użytkownikom, jeśli podczas ich tworzenia nie wskażą Państwo żadnej konkretnej roli. -![](https://static-docs.nocobase.com/f41b4b7ff55ca28715c486dc45bc1708.png) +![](https://static-docs.nocobase.com/f41bba7ff55ca28715c486dc45bc1708.png) ## Centrum Osobiste diff --git a/docs/docs/pl/users-permissions/acl/ui.md b/docs/docs/pl/users-permissions/acl/ui.md index 8b08fdac91f..5dec46b47a8 100644 --- a/docs/docs/pl/users-permissions/acl/ui.md +++ b/docs/docs/pl/users-permissions/acl/ui.md @@ -36,7 +36,7 @@ Pełny proces konfiguracji przedstawiono poniżej: W interfejsie użytkownika w bloku kolekcji "Zamówienia" widoczne są tylko pola, dla których skonfigurowano uprawnienia. Pola systemowe (Id, CreatedAt, LastUpdatedAt) zachowują uprawnienia do podglądu nawet bez specjalnej konfiguracji. -![](https://static-docs.nocobase.com/40cc43b517efe701147fd2e799e79dcc.png) +![](https://static-docs.nocobase.com/40cc49b517efe701147fd2e799e79dcc.png) - **Edycja**: Kontroluje, czy pola mogą być edytowane i zapisywane (aktualizowane). diff --git a/docs/docs/pl/users-permissions/departments/role.md b/docs/docs/pl/users-permissions/departments/role.md index 9a6c4da54a1..082dc0653a1 100644 --- a/docs/docs/pl/users-permissions/departments/role.md +++ b/docs/docs/pl/users-permissions/departments/role.md @@ -17,8 +17,8 @@ Pierwszy sposób polega na wybraniu roli w polu roli formularza edycji działu. Drugi sposób polega na dodaniu działów do odpowiedniej roli w zarządzaniu rolami. -![](https://static-docs.nocobase.com/f2a77bb89aa1fb415c152a51a51cc23b.png) +![](https://static-docs.nocobase.com/f2a7bec937cf2f179ce868a92b98416d.png) Działów, które już posiadają tę rolę, nie można wybrać. -![](https://static-docs.nocobase.com/be1029983581e1f97a4e01ddd5c7e59.png) \ No newline at end of file +![](https://static-docs.nocobase.com/be10299893581e1f97a4e01ddd5c7e59.png) \ No newline at end of file diff --git a/docs/docs/pl/workflow/nodes/calculation.md b/docs/docs/pl/workflow/nodes/calculation.md index bb5d34ac5e2..cf8f8d5245a 100644 --- a/docs/docs/pl/workflow/nodes/calculation.md +++ b/docs/docs/pl/workflow/nodes/calculation.md @@ -14,7 +14,7 @@ W interfejsie konfiguracji przepływu pracy proszę kliknąć przycisk plusa ( ## Konfiguracja węzła -![Węzeł Obliczenia_Konfiguracja](https://static-docs.nocobase.com/6a155de3c883d8cd1881b2d9c33874.png) +![Węzeł Obliczenia_Konfiguracja](https://static-docs.nocobase.com/6a155de3f6a883d8cd1881b2d9c33874.png) ### Silnik obliczeniowy diff --git a/docs/docs/pl/workflow/nodes/destroy.md b/docs/docs/pl/workflow/nodes/destroy.md index cce3df7831a..979b6842ba9 100644 --- a/docs/docs/pl/workflow/nodes/destroy.md +++ b/docs/docs/pl/workflow/nodes/destroy.md @@ -16,7 +16,7 @@ Obecnie węzeł usuwania nie obsługuje usuwania pojedynczych rekordów; zawsze W interfejsie konfiguracji `przepływu pracy` proszę kliknąć przycisk plusa („+”) w przepływie, aby dodać węzeł „Usuń dane”: -![Tworzenie węzła usuwania danych](https://static-docs.nocobase.com/e1d6b87251fcdbed6c7f50e5570da2.png) +![Tworzenie węzła usuwania danych](https://static-docs.nocobase.com/e1d6b8728251fcdbed6c7f50e5570da2.png) ## Konfiguracja węzła diff --git a/docs/docs/pl/workflow/nodes/manual.md b/docs/docs/pl/workflow/nodes/manual.md index bb525d81e38..fd44c218966 100644 --- a/docs/docs/pl/workflow/nodes/manual.md +++ b/docs/docs/pl/workflow/nodes/manual.md @@ -32,7 +32,7 @@ Węzeł ręczny wymaga przypisania użytkownika jako wykonawcy zadania do wykona Proszę wybrać użytkownika lub wybrać klucz podstawowy bądź klucz obcy danych użytkownika z kontekstu za pomocą zmiennej. -![Węzeł ręczny_Konfiguracja_Osoba odpowiedzialna_Wybór zmiennej](https://static-docs.nocobase.com/22fbca3b8e21fda3b825abb4b257df909.png) +![Węzeł ręczny_Konfiguracja_Osoba odpowiedzialna_Wybór zmiennej](https://static-docs.nocobase.com/22fbca3b8e21fda3a831019037001445.png) :::info{title=Uwaga} Obecnie opcja osoby odpowiedzialnej dla węzłów ręcznych nie obsługuje wielu użytkowników. Funkcjonalność ta zostanie dodana w przyszłych wersjach. @@ -104,11 +104,11 @@ W przypadku ręcznego przetwarzania, należy również dodać listę zadań do w Mogą Państwo wybrać „Zadania do wykonania przepływu pracy” z dostępnych bloków na stronie, aby dodać blok listy zadań do wykonania: -![Węzeł ręczny_Dodaj blok zadań do wykonania](https://static-docs.nocobase.com/198b41754cd73b704267bf30fe5e647.png) +![Węzeł ręczny_Dodaj blok zadań do wykonania](https://static-docs.nocobase.com/198b417454cd73b704267bf30fe5e647.png) Przykład bloku listy zadań do wykonania: -![Węzeł ręczny_Lista zadań do wykonania](https://static-docs.nocobase.com/cfefb054cd73b704267bf30fe5e647.png) +![Węzeł ręczny_Lista zadań do wykonania](https://static-docs.nocobase.com/cfefb0d2c6a91c5c9dfa550d6b220f34.png) ### Szczegóły zadania do wykonania diff --git a/docs/docs/pl/workflow/nodes/variable.md b/docs/docs/pl/workflow/nodes/variable.md index 993a8169283..841cd6dc4be 100644 --- a/docs/docs/pl/workflow/nodes/variable.md +++ b/docs/docs/pl/workflow/nodes/variable.md @@ -16,7 +16,7 @@ Mogą Państwo deklarować zmienne w przepływie pracy lub przypisywać wartośc W interfejsie konfiguracji przepływu pracy, proszę kliknąć przycisk plusa („+”) w przepływie, aby dodać węzeł „Zmienna”: -![Dodaj węzeł zmiennej](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![Dodaj węzeł zmiennej](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## Konfiguracja węzła @@ -41,7 +41,7 @@ Wartość zmiennej może być dowolnego typu. Może to być stała, taka jak ci W trybie deklaracji, ustawienie wartości zmiennej jest równoznaczne z przypisaniem jej wartości początkowej. -![Deklaruj wartość początkową](https://static-docs.nocobase.com/4ce2c608986565ad537343013758c6a4.png) +![Deklaruj wartość początkową](https://static-docs.nocobase.com/4ce2c508986565ad537343013758c6a4.png) W trybie przypisania, ustawienie wartości zmiennej jest równoznaczne ze zmianą wartości zadeklarowanej zmiennej docelowej na nową wartość. Kolejne użycia będą pobierać tę nową wartość. @@ -79,6 +79,6 @@ Po węźle obliczeniowym proszę utworzyć kolejny węzeł zmiennej. Proszę wyb W ten sposób, po zakończeniu rozgałęzienia pętli, zmienna odbiorcy będzie przechowywać ciąg znaków odbiorców wszystkich autorów artykułu. Następnie, po pętli, mogą Państwo użyć węzła żądania HTTP, aby wywołać interfejs API wysyłania wiadomości e-mail, przekazując wartość zmiennej odbiorcy jako parametr odbiorcy do interfejsu API: -![Wyślij wiadomość e-mail do odbiorców za pośrednictwem węzła żądania](https://static-docs.nocobase.com/37f71a63e172bcb2dce10a250947e.png) +![Wyślij wiadomość e-mail do odbiorców za pośrednictwem węzła żądania](https://static-docs.nocobase.com/37f71aa1a63e172bcb2dce10a250947e.png) W tym momencie prosta funkcja masowej wysyłki wiadomości e-mail została zaimplementowana za pomocą pętli i węzła zmiennej. \ No newline at end of file diff --git a/docs/docs/pl/workflow/triggers/post-action.md b/docs/docs/pl/workflow/triggers/post-action.md index 9dff2543c7f..ca0e5e2f663 100644 --- a/docs/docs/pl/workflow/triggers/post-action.md +++ b/docs/docs/pl/workflow/triggers/post-action.md @@ -179,7 +179,7 @@ Jeśli zdarzenie jest skonfigurowane w trybie globalnym, nie ma potrzeby używan Jak pokazano na poniższym rysunku: -![Action Execution Order](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![Action Execution Order](https://static-docs.nocobase.com/20251219234806.png) ### Różnica w stosunku do zdarzenia kolekcji diff --git a/docs/docs/pl/workflow/triggers/pre-action.md b/docs/docs/pl/workflow/triggers/pre-action.md index 84b368d578b..098002f8557 100644 --- a/docs/docs/pl/workflow/triggers/pre-action.md +++ b/docs/docs/pl/workflow/triggers/pre-action.md @@ -85,7 +85,7 @@ Po skonfigurowaniu wyzwalacza mogą Państwo dostosować odpowiednią logikę de W tym momencie konfiguracja odpowiadającego przepływu pracy jest zakończona. Mogą Państwo teraz spróbować przesłać dane, które nie spełniają warunków skonfigurowanych w węźle warunkowym przepływu pracy, aby uruchomić logikę przechwytywania. Wówczas zobaczą Państwo zwróconą wiadomość zwrotną: -![Wiadomość Zwrotna o Błędzie](https://static-docs.nocobase.com/06bd4a6b6ec499c39987f63a6a.png) +![Wiadomość Zwrotna o Błędzie](https://static-docs.nocobase.com/06bd4a6b6ec499c853f0c39987f63a6a.png) ### Status wiadomości zwrotnej diff --git a/docs/docs/pl/workflow/triggers/schedule.md b/docs/docs/pl/workflow/triggers/schedule.md index 030931c4dd6..2561560e126 100644 --- a/docs/docs/pl/workflow/triggers/schedule.md +++ b/docs/docs/pl/workflow/triggers/schedule.md @@ -70,7 +70,7 @@ Po włączeniu przepływu pracy będzie on wyzwalany raz na minutę od czasu roz Proszę utworzyć przepływ pracy oparty na zadaniu cyklicznym. W konfiguracji wyzwalacza proszę wybrać tryb „Pole czasowe kolekcji”, wybrać kolekcję „Zamówienia”, ustawić czas rozpoczęcia na 30 minut po czasie utworzenia zamówienia i wybrać „Nie powtarzaj” dla reguły powtarzania: -![Zadanie cykliczne_Konfiguracja wyzwalacza_Tryb pola czasowego kolekcji_Wyzwalacz](https://static-docs.nocobase.com/d40b5aef57f42799d31cc5882dd94246.png) +![Zadanie cykliczne_Konfiguracja wyzwalacza_Tryb pola czasowego kolekcji_Wyzwalacz](https://static-docs.nocobase.com/d40d5aef57f42799d31cc5882dd94246.png) Następnie proszę skonfigurować inne węzły zgodnie z logiką procesu, aby zaktualizować status zamówienia o ID danych wyzwalających i statusie „nieopłacone” na anulowane: diff --git a/docs/docs/pt/auth-verification/auth/password.md b/docs/docs/pt/auth-verification/auth/password.md index 1b8eeaa3ba6..a40a96ec2fa 100644 --- a/docs/docs/pt/auth-verification/auth/password.md +++ b/docs/docs/pt/auth-verification/auth/password.md @@ -24,7 +24,7 @@ Página de cadastro Quando o cadastro não é permitido, a página de login não exibirá o link para criar uma conta. -![](https://static-docs.nocobase.com/8d5e3b6df9991bfc1c2e095a934745121.png) +![](https://static-docs.nocobase.com/8d5e3b6df9991bfc1c2e095a93745121.png) Quando o cadastro não é permitido, a página de cadastro não poderá ser acessada. diff --git a/docs/docs/pt/data-sources/collection-expression/collection.md b/docs/docs/pt/data-sources/collection-expression/collection.md index 569780f0bcb..977fd35bf3d 100644 --- a/docs/docs/pt/data-sources/collection-expression/collection.md +++ b/docs/docs/pt/data-sources/collection-expression/collection.md @@ -14,7 +14,7 @@ Antes de usar nós de operação de expressão dinâmica em um fluxo de trabalho Em seguida, você pode configurar um bloco de tabela e inserir vários dados de fórmula na coleção de modelo. Cada linha na coleção de modelo "Expressão" pode ser vista como uma regra de cálculo projetada para um modelo de dados específico dentro da coleção. Você pode usar diferentes campos dos modelos de dados de várias coleções como variáveis, criando expressões únicas como regras de cálculo. Além disso, você pode aproveitar diferentes motores de cálculo, conforme necessário. -![Inserindo Dados de Expressão](https://static-docs.nocobase.com/761047f8daabacccbc6a6a24a73564093.png) +![Inserindo Dados de Expressão](https://static-docs.nocobase.com/761047f8daabacccbc6a924a73564093.png) :::info{title=Dica} Depois que as fórmulas são estabelecidas, elas precisam ser vinculadas aos dados de negócio. Associar diretamente cada linha de dados de negócio com os dados de fórmula pode ser tedioso. Por isso, uma abordagem comum é usar uma coleção de metadados, similar a uma coleção de classificação, para criar um relacionamento de muitos para um (ou um para um) com a coleção de fórmulas. Em seguida, os dados de negócio são associados aos metadados classificados em um relacionamento de muitos para um. Essa abordagem permite que você simplesmente especifique os metadados classificados relevantes ao criar dados de negócio, facilitando a localização e utilização dos dados de fórmula correspondentes através do caminho de associação estabelecido. diff --git a/docs/docs/pt/data-sources/data-modeling/collection-fields/associations/o2m/index.md b/docs/docs/pt/data-sources/data-modeling/collection-fields/associations/o2m/index.md index 982722509db..0411b576acc 100644 --- a/docs/docs/pt/data-sources/data-modeling/collection-fields/associations/o2m/index.md +++ b/docs/docs/pt/data-sources/data-modeling/collection-fields/associations/o2m/index.md @@ -12,7 +12,7 @@ Diagrama ER: Configuração do Campo: -![alt text](https://static-docs.nocobase.com/a608ce5421172dad7e8ab760107ff4e.png) +![alt text](https://static-docs.nocobase.com/a608ce54821172dad7e8ab760107ff4e.png) ## Descrição dos Parâmetros diff --git a/docs/docs/pt/data-sources/field-encryption/index.md b/docs/docs/pt/data-sources/field-encryption/index.md index d8733880ce5..d2ac2e54eae 100644 --- a/docs/docs/pt/data-sources/field-encryption/index.md +++ b/docs/docs/pt/data-sources/field-encryption/index.md @@ -30,7 +30,7 @@ Se o plugin for ativado por uma sub-aplicação, a chave será salva por padrão Utiliza Criptografia de Envelope -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### Processo de criação da chave 1. Na primeira vez que um campo criptografado é criado, o sistema gera automaticamente uma `chave de aplicação` de 32 bits e a armazena no diretório de armazenamento padrão, codificada em Base64. diff --git a/docs/docs/pt/data-visualization/guide/chart-options.md b/docs/docs/pt/data-visualization/guide/chart-options.md index 023972277a5..5086012cb4b 100644 --- a/docs/docs/pt/data-visualization/guide/chart-options.md +++ b/docs/docs/pt/data-visualization/guide/chart-options.md @@ -92,7 +92,7 @@ return { - Na modalidade Custom, após fazer as edições, você pode clicar no botão **Pré-visualizar** à direita para atualizar a pré-visualização do gráfico. - Na parte inferior, clique em **Salvar** para aplicar e persistir as configurações; clique em **Cancelar** para reverter todas as alterações feitas. -![20251026192816](https://static-docs.nocobase.com/clipboard-image-1761473695.png) +![20251026192816](https://static-docs.nocobase.com/20251026192816.png) > [!TIP] > Para mais informações sobre as opções de gráfico, consulte Uso Avançado — Configuração de gráfico personalizado. \ No newline at end of file diff --git a/docs/docs/pt/email-manager/advanced/batch-send.md b/docs/docs/pt/email-manager/advanced/batch-send.md index 804d69afb94..ec39dd95232 100644 --- a/docs/docs/pt/email-manager/advanced/batch-send.md +++ b/docs/docs/pt/email-manager/advanced/batch-send.md @@ -11,27 +11,27 @@ Esta documentação foi traduzida automaticamente por IA. ## Visão Geral do Envio em Massa Você pode enviar e-mails para várias pessoas em massa (cada destinatário receberá um e-mail separado). -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## Envio em Massa via Tabela Você também pode enviar e-mails em massa através de uma tabela: 1. Adicione um botão de envio de e-mail à tabela - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. Configure o campo de e-mail na tabela (usado para analisar endereços de e-mail após selecionar as linhas da tabela) - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. Marque os dados da tabela para enviar e-mails - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) Se você precisar enviar e-mails para todos os endereços da tabela, pode habilitar a função **Selecionar todos os registros da tabela atual como destinatários por padrão**: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) Após editar o conteúdo do e-mail, clique no botão de envio em massa para enviar: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## Rastreamento de Envio de E-mail Você pode visualizar e rastrear o status específico do envio de e-mail no Centro de Gerenciamento de E-mails: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/pt/email-manager/usage/signature.md b/docs/docs/pt/email-manager/usage/signature.md index 87ff476e674..00873b41269 100644 --- a/docs/docs/pt/email-manager/usage/signature.md +++ b/docs/docs/pt/email-manager/usage/signature.md @@ -11,15 +11,15 @@ Esta documentação foi traduzida automaticamente por IA. ## Configuração da Assinatura Acesse a Central de Gerenciamento de E-mail e clique no botão de configurações: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Alterne para o painel de assinaturas: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) Aqui você pode gerenciar as assinaturas. Marque a opção antes de uma assinatura para defini-la como padrão: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## Usando Assinaturas No corpo do e-mail, clique no ícone de assinatura para selecionar a assinatura desejada: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/pt/email-manager/usage/template.md b/docs/docs/pt/email-manager/usage/template.md index 27a432e3e81..ff24fe0fd95 100644 --- a/docs/docs/pt/email-manager/usage/template.md +++ b/docs/docs/pt/email-manager/usage/template.md @@ -12,18 +12,18 @@ Esta documentação foi traduzida automaticamente por IA. Acesse o Centro de Gerenciamento de E-mail e clique no botão de configurações: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Alterne para o painel de modelos: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) Aqui você pode gerenciar os modelos: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## Utilizando Modelos Na caixa de texto do corpo do e-mail, clique no ícone de modelo para selecionar o modelo desejado: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/pt/flow-engine/learning-roadmap.md b/docs/docs/pt/flow-engine/learning-roadmap.md index 8e3ffa14587..ce8cbbb6c41 100644 --- a/docs/docs/pt/flow-engine/learning-roadmap.md +++ b/docs/docs/pt/flow-engine/learning-roadmap.md @@ -4,4 +4,4 @@ Esta documentação foi traduzida automaticamente por IA. # Roteiro de Aprendizagem -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/pt/integration/api-doc/index.md b/docs/docs/pt/integration/api-doc/index.md index 2b91537b7dc..e64d92d8a5e 100644 --- a/docs/docs/pt/integration/api-doc/index.md +++ b/docs/docs/pt/integration/api-doc/index.md @@ -27,7 +27,7 @@ http://localhost:13000/admin/settings/api-doc/documentation ### Visão Geral da Documentação -![](https://static-docs.nocobase.com/5bb4d3e5bba6c6fdfcd30592e72385b.png) +![](https://static-docs.nocobase.com/5bb4d3e5bba6c6fdfcd830592e72385b.png) - Documentação total da API: `/api/swagger:get` - Documentação da API do núcleo: `/api/swagger:get?ns=core` diff --git a/docs/docs/pt/solution/ticket-system/design.md b/docs/docs/pt/solution/ticket-system/design.md index cd9517e589f..e540d57477c 100755 --- a/docs/docs/pt/solution/ticket-system/design.md +++ b/docs/docs/pt/solution/ticket-system/design.md @@ -31,7 +31,7 @@ Inspirada no conceito de "profissionais em T" — amplitude horizontal + profund - **Horizontal (Tabela Principal)**: Abrange capacidades universais para todos os tipos de negócio — número do chamado, status, responsável, SLA e outros campos essenciais. - **Vertical (Tabelas de Extensão)**: Campos especializados para tipos de negócio específicos — reparo de equipamentos possui números de série, reclamações possuem planos de compensação. -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **Por que este design?** @@ -61,7 +61,7 @@ Não são apenas "recursos de IA", mas "funcionários de IA". Cada IA tem uma fu #### Filosofia Três: Autociclo de Conhecimento -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) Isso forma um ciclo fechado de **Acúmulo de Conhecimento - Aplicação de Conhecimento**. @@ -71,7 +71,7 @@ Isso forma um ciclo fechado de **Acúmulo de Conhecimento - Aplicação de Conhe ### 2.1 Visão Geral do Relacionamento de Entidades -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 Detalhes das Tabelas Principais @@ -296,18 +296,18 @@ Este é o núcleo do sistema, utilizando um design de "tabela larga" com todos o **Fluxo Principal (Esquerda para Direita)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **Fluxos de Ramificação** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **Máquina de Estados Completa** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 Regras de Transição de Status Principais @@ -337,7 +337,7 @@ Este é o núcleo do sistema, utilizando um design de "tabela larga" com todos o ### 4.2 Lógica de Cálculo de SLA -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### Na Criação do Chamado @@ -467,7 +467,7 @@ Cada funcionário de IA é configurado com 4 tarefas específicas: ### 5.3 Funcionários de IA e Ciclo de Vida do Chamado -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 Exemplos de Resposta de IA @@ -527,12 +527,12 @@ A revisão de qualidade de resposta da Grace bloqueia os seguintes problemas: ### 6.1 Fontes de Conhecimento -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 Fluxo de Chamado para Conhecimento -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **Dimensões de Avaliação**: - **Generalidade**: Este é um problema comum? @@ -577,19 +577,19 @@ Quando um agente abre os detalhes do chamado, o Max recomenda automaticamente co #### WF-T01: Fluxo de Criação de Chamado -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: Análise de Chamado por IA -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: Tradução e Revisão de Comentários -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: Geração de Conhecimento -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 Tarefas Agendadas @@ -606,11 +606,11 @@ Quando um agente abre os detalhes do chamado, o Max recomenda automaticamente co ### 8.1 Painel Administrativo (Backend) -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 Portal do Cliente -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 Design do Painel de Indicadores (Dashboard) diff --git a/docs/docs/pt/users-permissions/acl/ui.md b/docs/docs/pt/users-permissions/acl/ui.md index 3f6b5383c8a..6dae4e979e0 100644 --- a/docs/docs/pt/users-permissions/acl/ui.md +++ b/docs/docs/pt/users-permissions/acl/ui.md @@ -32,11 +32,11 @@ Processo de configuração completo: **Visualizar**: Determina se campos específicos são visíveis no nível do campo, permitindo controlar quais campos são visíveis para certas funções dentro da **coleção** de Pedidos. -![](https://static-docs.nocobase.com/30dea84d984d95036e6f7b180955a6cf.png) +![](https://static-docs.nocobase.com/30dea84d984d95039e6f7b180955a6cf.png) Na UI, apenas os campos com permissões configuradas são visíveis dentro do bloco da **coleção** de Pedidos. Campos do sistema (Id, CreatedAt, LastUpdatedAt) mantêm as permissões de visualização mesmo sem configuração específica. -![](https://static-docs.nocobase.com/40cc49b17efe701147fd2e799e79dcc.png) +![](https://static-docs.nocobase.com/40cc49b517efe701147fd2e799e79dcc.png) - **Editar**: Controla se os campos podem ser editados e salvos (atualizados). diff --git a/docs/docs/pt/users-permissions/user.md b/docs/docs/pt/users-permissions/user.md index 42ed4a27e5e..c4c44e24189 100644 --- a/docs/docs/pt/users-permissions/user.md +++ b/docs/docs/pt/users-permissions/user.md @@ -20,7 +20,7 @@ Além disso, você também pode usar a **coleção** de **usuários** nas págin ## Adicionar Usuário -![](https://static-docs.nocobase.com/4fef9ffc1c17f275b62b462f6385b19.png) +![](https://static-docs.nocobase.com/4f8ef9ffc1c17f275b62b462f6385b19.png) ![](https://static-docs.nocobase.com/437828173950bd7c21b40a6243ffe150.png) diff --git a/docs/docs/pt/workflow/nodes/aggregate.md b/docs/docs/pt/workflow/nodes/aggregate.md index 9b52b2d03bd..5989ce1eabd 100644 --- a/docs/docs/pt/workflow/nodes/aggregate.md +++ b/docs/docs/pt/workflow/nodes/aggregate.md @@ -64,7 +64,7 @@ Em seguida, crie um fluxo de trabalho acionado por um evento de coleção. Selec Depois, adicione um nó de consulta de agregação e configure-o da seguinte forma: -![Nó de Consulta de Agregação_Exemplo_Configuração do Nó](https://static-docs.nocobase.com/542272e6373d1b37ddda78.png) +![Nó de Consulta de Agregação_Exemplo_Configuração do Nó](https://static-docs.nocobase.com/542272e638c6c0a567373d1b37ddda78.png) Dessa forma, após o fluxo de trabalho ser acionado, o nó de consulta de agregação contará o número de todos os artigos na categoria do artigo recém-adicionado e o salvará como o resultado do nó. diff --git a/docs/docs/pt/workflow/nodes/calculation.md b/docs/docs/pt/workflow/nodes/calculation.md index b9273486fbc..8c7e5467cae 100644 --- a/docs/docs/pt/workflow/nodes/calculation.md +++ b/docs/docs/pt/workflow/nodes/calculation.md @@ -14,7 +14,7 @@ Na interface de configuração do fluxo de trabalho, clique no botão de adiçã ## Configuração do Nó -![Nó de Cálculo_Configuração](https://static-docs.nocobase.com/6a155de3c81881b2d9c33874.png) +![Nó de Cálculo_Configuração](https://static-docs.nocobase.com/6a155de3f6a883d8cd1881b2d9c33874.png) ### Mecanismo de Cálculo diff --git a/docs/docs/pt/workflow/nodes/create.md b/docs/docs/pt/workflow/nodes/create.md index dec9df019d1..30e4b0dd64b 100644 --- a/docs/docs/pt/workflow/nodes/create.md +++ b/docs/docs/pt/workflow/nodes/create.md @@ -38,7 +38,7 @@ Se os campos do novo registro incluírem campos de relacionamento e você quiser Por exemplo, quando um registro na **coleção** "Artigos" é criado ou atualizado, um registro de "Versões de Artigo" precisa ser criado automaticamente para registrar o histórico de alterações do artigo. Você pode usar o nó "Adicionar Dados" para conseguir isso: -![Create Record Node_Example_Workflow Configuration](https://static-docs.nocobase.com/dfd4820d49c145fa33183fc09c9161f.png) +![Create Record Node_Example_Workflow Configuration](https://static-docs.nocobase.com/dfd4820d49c145fa331883fc09c9161f.png) ![Create Record Node_Example_Node Configuration](https://static-docs.nocobase.com/1a0992e66170be12a068da6503298868.png) diff --git a/docs/docs/pt/workflow/nodes/manual.md b/docs/docs/pt/workflow/nodes/manual.md index c67f1e2bb34..212b267b28f 100644 --- a/docs/docs/pt/workflow/nodes/manual.md +++ b/docs/docs/pt/workflow/nodes/manual.md @@ -32,7 +32,7 @@ Um nó manual precisa que você especifique um usuário como executor da tarefa Selecione um usuário ou escolha a chave primária ou estrangeira dos dados do usuário a partir do contexto, usando uma variável. -![Nó Manual_Configurar_Responsável_Selecionar Variável](https://static-docs.nocobase.com/22fbca3b8e21fda3a81019037001445.png) +![Nó Manual_Configurar_Responsável_Selecionar Variável](https://static-docs.nocobase.com/22fbca3b8e21fda3a831019037001445.png) :::info{title=Observação} Atualmente, a opção de responsável para nós manuais não suporta múltiplos usuários. Isso será implementado em uma versão futura. diff --git a/docs/docs/pt/workflow/nodes/request.md b/docs/docs/pt/workflow/nodes/request.md index b74ce510d5f..a86ac4761ee 100644 --- a/docs/docs/pt/workflow/nodes/request.md +++ b/docs/docs/pt/workflow/nodes/request.md @@ -26,7 +26,7 @@ Na interface de configuração do fluxo de trabalho, clique no botão de adiçã ## Configuração do Nó -![Nó de Requisição HTTP_Configuração](https://static-docs.nocobase.com/2fcb29af66d869c80f8fbd362a54e644.png) +![Nó de Requisição HTTP_Configuração](https://static-docs.nocobase.com/2fcb29af66b892fa704add52e2974a52.png) ### Método da Requisição diff --git a/docs/docs/pt/workflow/nodes/variable.md b/docs/docs/pt/workflow/nodes/variable.md index 712096398c8..422daadeaf3 100644 --- a/docs/docs/pt/workflow/nodes/variable.md +++ b/docs/docs/pt/workflow/nodes/variable.md @@ -16,7 +16,7 @@ Você pode declarar variáveis em um fluxo ou atribuir valores a variáveis já Na interface de configuração do **fluxo de trabalho**, clique no botão de adição ("+") no fluxo para adicionar um nó de "Variável": -![Adicionar Nó de Variável](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![Adicionar Nó de Variável](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## Configurar Nó @@ -33,7 +33,7 @@ Quando o nó que você está criando é o primeiro nó de variável no fluxo, vo Ao escolher atribuir um valor a uma variável já declarada, você também precisará selecionar a variável de destino, que é o nó onde a variável foi declarada: -![Selecionar a variável para atribuir um valor](https://static-docs.nocobase.com/1ce88b71526ef3ee.png) +![Selecionar a variável para atribuir um valor](https://static-docs.nocobase.com/1ce8911548d7347e693d8cc8ac1953eb.png) ### Valor diff --git a/docs/docs/pt/workflow/triggers/post-action.md b/docs/docs/pt/workflow/triggers/post-action.md index 133a44db2da..c4a4172dd98 100644 --- a/docs/docs/pt/workflow/triggers/post-action.md +++ b/docs/docs/pt/workflow/triggers/post-action.md @@ -178,7 +178,7 @@ Se o evento estiver configurado no modo global, você não precisa usar o parâm Conforme mostrado na figura abaixo: -![Ordem de Execução da Ação](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![Ordem de Execução da Ação](https://static-docs.nocobase.com/20251219234806.png) ### Diferença em relação ao Evento de Coleção diff --git a/docs/docs/pt/workflow/triggers/pre-action.md b/docs/docs/pt/workflow/triggers/pre-action.md index 7f0db45677a..3803823d73b 100644 --- a/docs/docs/pt/workflow/triggers/pre-action.md +++ b/docs/docs/pt/workflow/triggers/pre-action.md @@ -34,7 +34,7 @@ Em seguida, selecione o modo de interceptação. Você pode optar por intercepta ### Modo de Interceptação -![Configuração do Evento Interceptor_Modo de Interceptação](https://static-docs.nocobase.com/145a7f7c3db440bb6ca93a5ee84f16e2.png) +![Configuração do Evento Interceptor_Modo de Interceptação](https://static-docs.nocobase.com/145a7f7c3ba440bb6ca93a5ee84f16e2.png) Os tipos de ação atualmente suportados são "Criar", "Atualizar" e "Excluir". Vários tipos de ação podem ser selecionados simultaneamente. @@ -99,7 +99,7 @@ Combinando as instruções básicas acima, vamos usar um cenário de "Envio de P Outras etapas são as mesmas das instruções. No entanto, como um pedido envolve vários produtos, além de adicionar um relacionamento muitos-para-muitos "Pedido" <-- M:1 -- "Item do Pedido" -- 1:M --> "Produto" no modelo de dados, você também precisa adicionar um nó "Loop" no **fluxo de trabalho** "Evento Antes da Ação" para verificar iterativamente se o estoque de cada produto é suficiente: -![Exemplo_Fluxo de Trabalho de Verificação de Loop](https://static-docs.nocobase.com/8307de47d5629595ab6cf00f8aa898e2.png) +![Exemplo_Fluxo de Trabalho de Verificação de Loop](https://static-docs.nocobase.com/8307de47d5629595ab6cf00f8aa898e3.png) O objeto para o loop é selecionado como o array "Item do Pedido" dos dados do pedido enviados: diff --git a/docs/docs/pt/workflow/triggers/schedule.md b/docs/docs/pt/workflow/triggers/schedule.md index 52622ded309..4ca150e1d76 100644 --- a/docs/docs/pt/workflow/triggers/schedule.md +++ b/docs/docs/pt/workflow/triggers/schedule.md @@ -74,6 +74,6 @@ Crie um **fluxo de trabalho** baseado em tarefa agendada. Na configuração do a Em seguida, configure outros nós de acordo com a lógica do processo para atualizar o status do pedido com o ID dos dados acionados e um status de "não pago" para cancelado: -![Tarefa Agendada_Configuração do Acionador_Modo de Campo de Tempo da Coleção_Nó de Atualização](https://static-docs.nocobase.com/491dde9df7741fb24a4e7baa1de6eb29.png) +![Tarefa Agendada_Configuração do Acionador_Modo de Campo de Tempo da Coleção_Nó de Atualização](https://static-docs.nocobase.com/491dde9df8f773f5b14a4fd8ceac9d3e.png) Ao contrário do modo de tempo personalizado, não há necessidade de calcular o horário de 30 minutos atrás aqui, porque o contexto dos dados acionados já contém a linha de dados que atende à condição de tempo, então você pode atualizar diretamente o status do pedido correspondente. \ No newline at end of file diff --git a/docs/docs/ru/auth-verification/auth-saml/examples/google.md b/docs/docs/ru/auth-verification/auth-saml/examples/google.md index a41f53a7751..2f7eca4326e 100644 --- a/docs/docs/ru/auth-verification/auth-saml/examples/google.md +++ b/docs/docs/ru/auth-verification/auth-saml/examples/google.md @@ -12,7 +12,7 @@ После настройки приложения скопируйте **URL-адрес SSO**, **Идентификатор сущности** и **Сертификат**. -![](https://static-docs.nocobase.com/aafd20a74730e85411c0c8f368637e0.png) +![](https://static-docs.nocobase.com/aafd20a794730e85411c0c8f368637e0.png) ## Добавление нового аутентификатора в NocoBase diff --git a/docs/docs/ru/auth-verification/auth-saml/index.md b/docs/docs/ru/auth-verification/auth-saml/index.md index c9e31952fd0..f0a434ed02f 100644 --- a/docs/docs/ru/auth-verification/auth-saml/index.md +++ b/docs/docs/ru/auth-verification/auth-saml/index.md @@ -28,7 +28,7 @@ pkg: '@nocobase/plugin-auth-saml' ## Конфигурация -![](https://static-docs.nocobase.com/976b66e58973c322d81dcddd22c6146.png) +![](https://static-docs.nocobase.com/976b66e589973c322d81dcddd22c6146.png) - SSO URL — предоставляется IdP, используется для единого входа (Single Sign-On). - Открытый ключ (Public Certificate) — предоставляется IdP. diff --git a/docs/docs/ru/auth-verification/auth/authenticators.md b/docs/docs/ru/auth-verification/auth/authenticators.md index 070e4190114..62724aba71f 100644 --- a/docs/docs/ru/auth-verification/auth/authenticators.md +++ b/docs/docs/ru/auth-verification/auth/authenticators.md @@ -17,7 +17,7 @@ pkg: '@nocobase/plugin-auth' ## Активация аутентификаторов -![](https://static-docs.nocobase.com/7f1f8ca5de67ffc68eff0a65848f5.png) +![](https://static-docs.nocobase.com/7f1fb8f8ca5de67ffc68eff0a65848f5.png) На странице входа отображаются только активированные типы аутентификации. diff --git a/docs/docs/ru/data-sources/collection-fdw/index.md b/docs/docs/ru/data-sources/collection-fdw/index.md index 5ff0e138a25..9c68423c374 100644 --- a/docs/docs/ru/data-sources/collection-fdw/index.md +++ b/docs/docs/ru/data-sources/collection-fdw/index.md @@ -73,4 +73,4 @@ MySQL использует движок `federated`, который необхо Наконец, отображение в интерфейсе. -![Отображение в интерфейсе](https://static-docs.nocobase.com/368fca27a9933889fb3fcc4d85a6f4ad.png) \ No newline at end of file +![Отображение в интерфейсе](https://static-docs.nocobase.com/368fca27a99277d9360ca81350949357.png) \ No newline at end of file diff --git a/docs/docs/ru/data-sources/data-modeling/collection-fields/associations/m2o/index.md b/docs/docs/ru/data-sources/data-modeling/collection-fields/associations/m2o/index.md index 1cf21e4a2e9..f1a3809857f 100644 --- a/docs/docs/ru/data-sources/data-modeling/collection-fields/associations/m2o/index.md +++ b/docs/docs/ru/data-sources/data-modeling/collection-fields/associations/m2o/index.md @@ -12,7 +12,7 @@ ER-диаграмма: Конфигурация поля: -![alt text](https://static-docs.nocobase.com/3b4484ebb8d82f832f3dbf752bd84c9.png) +![alt text](https://static-docs.nocobase.com/3b4484ebb98d82f832f3dbf752bd84c9.png) ## Описание параметров diff --git a/docs/docs/ru/data-sources/data-modeling/collection-fields/associations/o2o/index.md b/docs/docs/ru/data-sources/data-modeling/collection-fields/associations/o2o/index.md index 6011ed677f3..8b30a664748 100644 --- a/docs/docs/ru/data-sources/data-modeling/collection-fields/associations/o2o/index.md +++ b/docs/docs/ru/data-sources/data-modeling/collection-fields/associations/o2o/index.md @@ -28,7 +28,7 @@ ER-диаграмма ER-диаграмма -![](https://static-docs.nocobase.com/31e7cc3e630220cf1e9853ca24ac72d.png) +![](https://static-docs.nocobase.com/31e7cc3e630220cf1e98753ca24ac72d.png) Конфигурация поля diff --git a/docs/docs/ru/data-sources/field-encryption/index.md b/docs/docs/ru/data-sources/field-encryption/index.md index 2f16fc7a054..ea802eeb8ff 100644 --- a/docs/docs/ru/data-sources/field-encryption/index.md +++ b/docs/docs/ru/data-sources/field-encryption/index.md @@ -30,7 +30,7 @@ pkg: "@nocobase/plugin-field-encryption" Используется метод конвертного шифрования. -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### Процесс создания ключей 1. При первом создании зашифрованного поля система автоматически генерирует 32-битный `ключ приложения` и сохраняет его в директории хранения по умолчанию в кодировке Base64. diff --git a/docs/docs/ru/data-visualization/guide/chart-options.md b/docs/docs/ru/data-visualization/guide/chart-options.md index 82d42a68e22..19221482ac6 100644 --- a/docs/docs/ru/data-visualization/guide/chart-options.md +++ b/docs/docs/ru/data-visualization/guide/chart-options.md @@ -62,7 +62,7 @@ Этот режим позволяет вернуть полный объект `option` ECharts и подходит для расширенной настройки, такой как объединение нескольких серий, сложные всплывающие подсказки и динамические стили. Рекомендуемый подход: консолидируйте данные в `dataset.source`. Подробности см. в документации ECharts: [Dataset](https://echarts.apache.org/handbook/en/concepts/dataset/#map-row-or-column-of-dataset-to-series) -![20251026191728](https://static-docs.nocobase.com/clipboard-image-1761473695.png) +![20251026191728](https://static-docs.nocobase.com/20251026191728.png) ### Контекст данных - `ctx.data.objects`: массив объектов (каждая строка как объект, рекомендуется) diff --git a/docs/docs/ru/email-manager/advanced/batch-send.md b/docs/docs/ru/email-manager/advanced/batch-send.md index 0cf8bac2d8e..638e8c87c97 100644 --- a/docs/docs/ru/email-manager/advanced/batch-send.md +++ b/docs/docs/ru/email-manager/advanced/batch-send.md @@ -11,33 +11,33 @@ pkg: "@nocobase/plugin-email-manager" ## Обзор массовой отправки Вы можете отправлять электронные письма нескольким получателям одновременно (каждый получатель получит отдельное письмо). -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## Массовая отправка с помощью таблицы Вы также можете выполнить массовую отправку писем с помощью таблицы: 1. Добавьте кнопку отправки письма в таблицу. -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. Настройте поле для электронной почты в таблице (оно будет использоваться для извлечения адресов после выбора строк таблицы). -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. Выберите данные в таблице для отправки писем. -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) Если вам нужно отправить письма на все адреса в таблице, вы можете включить функцию **По умолчанию выбирать все записи текущей таблицы в качестве получателей**. -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) После редактирования содержимого письма нажмите кнопку массовой отправки, чтобы отправить его. -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## Отслеживание отправки писем Вы можете просматривать и отслеживать статус отправки писем в Центре управления электронной почтой. -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/ru/email-manager/usage/signature.md b/docs/docs/ru/email-manager/usage/signature.md index de3653d40e0..8f2538a074c 100644 --- a/docs/docs/ru/email-manager/usage/signature.md +++ b/docs/docs/ru/email-manager/usage/signature.md @@ -11,15 +11,15 @@ pkg: "@nocobase/plugin-email-manager" ## Настройка подписи Перейдите в Центр управления почтой и нажмите кнопку настроек: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Переключитесь на панель подписей: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) Здесь вы можете управлять подписями. Установите флажок перед подписью, чтобы сделать ее подписью по умолчанию: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## Использование подписей В теле письма нажмите на значок подписи, чтобы выбрать нужную подпись: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/ru/email-manager/usage/template.md b/docs/docs/ru/email-manager/usage/template.md index accdd605c1f..99c48750f2c 100644 --- a/docs/docs/ru/email-manager/usage/template.md +++ b/docs/docs/ru/email-manager/usage/template.md @@ -11,15 +11,15 @@ pkg: "@nocobase/plugin-email-manager" ## Настройка шаблонов Перейдите в Центр управления письмами и нажмите кнопку настроек: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Переключитесь на панель шаблонов: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) Здесь вы можете управлять шаблонами: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## Использование шаблонов В поле для ввода текста письма нажмите на значок шаблона, чтобы выбрать нужный шаблон: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/ru/flow-engine/learning-roadmap.md b/docs/docs/ru/flow-engine/learning-roadmap.md index dcce22d14d4..2750f743661 100644 --- a/docs/docs/ru/flow-engine/learning-roadmap.md +++ b/docs/docs/ru/flow-engine/learning-roadmap.md @@ -4,4 +4,4 @@ # Дорожная карта обучения -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/ru/interface-builder/fields/association-field.md b/docs/docs/ru/interface-builder/fields/association-field.md index abf72808770..89285fa1afb 100644 --- a/docs/docs/ru/interface-builder/fields/association-field.md +++ b/docs/docs/ru/interface-builder/fields/association-field.md @@ -44,7 +44,7 @@ Вложенные детали — это компонент, соответствующий вложенной форме в режиме просмотра. Он поддерживает отображение данных с многоуровневыми вложенными связями. -![20251030213050](https://static-docs.nocobase.com/2025103050.png) +![20251030213050](https://static-docs.nocobase.com/20251030213050.png) Подробнее см. [Вложенные детали](/interface-builder/fields/specific/sub-detail) diff --git a/docs/docs/ru/solution/ticket-system/design.md b/docs/docs/ru/solution/ticket-system/design.md index 266162ac45e..d95699c05d1 100755 --- a/docs/docs/ru/solution/ticket-system/design.md +++ b/docs/docs/ru/solution/ticket-system/design.md @@ -31,7 +31,7 @@ - **Горизонталь (Основная таблица)**: Универсальные возможности, охватывающие все типы бизнеса — номер тикета, статус, исполнитель, SLA и другие ключевые поля. - **Вертикаль (Таблицы расширения)**: Специализированные поля для конкретных бизнес-задач — серийные номера для ремонта оборудования, планы компенсации для жалоб. -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **Почему выбрана такая архитектура?** @@ -61,7 +61,7 @@ #### Концепция 3: Самоциркуляция знаний -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) Это формирует замкнутый цикл: **накопление знаний — применение знаний**. @@ -71,7 +71,7 @@ ### 2.1 Обзор связей сущностей -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 Подробное описание основных таблиц @@ -296,18 +296,18 @@ **Основной процесс (слева направо)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **Вспомогательные процессы** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **Полная диаграмма состояний** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 Ключевые правила смены статусов @@ -337,7 +337,7 @@ ### 4.2 Логика расчета SLA -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### При создании тикета @@ -466,7 +466,7 @@ ### 5.3 ИИ-сотрудники и жизненный цикл тикета -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 Примеры ответов ИИ @@ -527,12 +527,12 @@ ### 6.1 Источники знаний -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 Процесс превращения тикета в знание -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **Критерии оценки**: - **Универсальность**: Является ли это частой проблемой? @@ -577,19 +577,19 @@ #### WF-T01: Процесс создания тикета -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: ИИ-анализ тикета -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: Перевод и проверка комментариев -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: Генерация знаний -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 Запланированные задачи @@ -606,11 +606,11 @@ ### 8.1 Панель администратора -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 Портал клиента -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 Дизайн дашбордов diff --git a/docs/docs/ru/users-permissions/acl/permissions.md b/docs/docs/ru/users-permissions/acl/permissions.md index 1dc68f0c647..13a6a5fd340 100644 --- a/docs/docs/ru/users-permissions/acl/permissions.md +++ b/docs/docs/ru/users-permissions/acl/permissions.md @@ -26,7 +26,7 @@ pkg: '@nocobase/plugin-acl' ## Права на операции с коллекциями -![](https://static-docs.nocobase.com/6a6e0281713cecdea5b5218e6173c5d7.png) +![](https://static-docs.nocobase.com/6a6e0281391cecdea5b5218e6173c5d7.png) ![](https://static-docs.nocobase.com/9814140434ff9e1bf028a6c282a5a165.png) diff --git a/docs/docs/ru/users-permissions/acl/role.md b/docs/docs/ru/users-permissions/acl/role.md index 933a3e699a9..b3f95ec66cc 100644 --- a/docs/docs/ru/users-permissions/acl/role.md +++ b/docs/docs/ru/users-permissions/acl/role.md @@ -20,7 +20,7 @@ pkg: '@nocobase/plugin-acl' Идентификатор роли — это уникальный системный идентификатор. Вы можете настраивать роли по умолчанию, но системные роли удалить нельзя. -![](https://static-docs.nocobase.com/35f346db4f9f12f9bee4dea63302.png) +![](https://static-docs.nocobase.com/35f323b346db4f9f12f9bee4dea63302.png) ### Настройка роли по умолчанию diff --git a/docs/docs/ru/users-permissions/acl/ui.md b/docs/docs/ru/users-permissions/acl/ui.md index a80a9f88135..d8804d3c06a 100644 --- a/docs/docs/ru/users-permissions/acl/ui.md +++ b/docs/docs/ru/users-permissions/acl/ui.md @@ -20,7 +20,7 @@ pkg: '@nocobase/plugin-acl' Конфигурация индивидуальных разрешений для коллекции "Заказы": -![](https://static-docs.nocobase.com/a88c47001c160bf402a4a2c1.png) +![](https://static-docs.nocobase.com/a88caba1cad47001c1610bf402a4a2c1.png) В UI это проявляется в том, что все блоки коллекции "Заказы" не отображаются. @@ -36,7 +36,7 @@ pkg: '@nocobase/plugin-acl' В UI в блоке коллекции "Заказы" отображаются только те поля, для которых настроены разрешения. Системные поля (Id, CreatedAt, LastUpdatedAt) сохраняют разрешения на просмотр даже без специальной настройки. -![](https://static-docs.nocobase.com/40cc517efe701147fd2e799e79dcc.png) +![](https://static-docs.nocobase.com/40cc49b517efe701147fd2e799e79dcc.png) - **Редактирование**: Определяет, можно ли редактировать и сохранять (обновлять) поля. @@ -153,7 +153,7 @@ pkg: '@nocobase/plugin-acl' Как показано, для коллекции "Клиенты" настроены индивидуальные разрешения для полей (поле "Имя клиента" невидимо и нередактируемо). -![](https://static-docs.nocobase.com/e7b8752cbc4e28640f027f36d0413c.png) +![](https://static-docs.nocobase.com/e7b875521cbc4e28640f027f36d0413c.png) Полный пример процесса настройки: diff --git a/docs/docs/ru/users-permissions/departments/role.md b/docs/docs/ru/users-permissions/departments/role.md index 4dde53a6d7b..0fc01b7270f 100644 --- a/docs/docs/ru/users-permissions/departments/role.md +++ b/docs/docs/ru/users-permissions/departments/role.md @@ -18,7 +18,7 @@ pkg: '@nocobase/plugin-departments' Второй способ — добавить отделы к соответствующей роли в разделе управления ролями. -![](https://static-docs.nocobase.com/f2a7bec8937cf2f179ce868a92b98416d.png) +![](https://static-docs.nocobase.com/f2a7bec937cf2f179ce868a92b98416d.png) Отделы, которым уже назначена эта роль, недоступны для выбора. diff --git a/docs/docs/ru/workflow/advanced/options.md b/docs/docs/ru/workflow/advanced/options.md index 8db027cd7f4..1adb7e6dc31 100644 --- a/docs/docs/ru/workflow/advanced/options.md +++ b/docs/docs/ru/workflow/advanced/options.md @@ -22,7 +22,7 @@ Вы также можете настроить автоматическое удаление истории выполнения для рабочего процесса в диалоговых окнах его создания и редактирования: -![Настройка автоматического удаления истории выполнения](https://static-docs.nocobase.com/b2c4c08e7a01e213069912fe04baa7bd.png) +![Настройка автоматического удаления истории выполнения](https://static-docs.nocobase.com/b2e4c08e7a01e213069912fe04baa7bd.png) Автоматическое удаление можно настроить в зависимости от статуса результата выполнения. В большинстве случаев рекомендуется выбирать только статус «Завершено», чтобы сохранить записи о неудачных выполнениях для последующего устранения неполадок. diff --git a/docs/docs/ru/workflow/nodes/aggregate.md b/docs/docs/ru/workflow/nodes/aggregate.md index 9b4ab7564db..d1a90cee83e 100644 --- a/docs/docs/ru/workflow/nodes/aggregate.md +++ b/docs/docs/ru/workflow/nodes/aggregate.md @@ -64,7 +64,7 @@ pkg: '@nocobase/plugin-workflow-aggregate' Затем добавьте узел агрегирующего запроса и настройте его следующим образом: -![Пример настройки узла агрегирующего запроса](https://static-docs.nocobase.com/542272e6c6c0a67373d1b37ddda78.png) +![Пример настройки узла агрегирующего запроса](https://static-docs.nocobase.com/542272e638c6c0a567373d1b37ddda78.png) Таким образом, после запуска рабочего процесса узел агрегирующего запроса подсчитает количество всех статей в категории только что добавленной статьи и сохранит его в качестве результата узла. diff --git a/docs/docs/ru/workflow/nodes/calculation.md b/docs/docs/ru/workflow/nodes/calculation.md index 0a4357cd3d1..c1e8fdda8b5 100644 --- a/docs/docs/ru/workflow/nodes/calculation.md +++ b/docs/docs/ru/workflow/nodes/calculation.md @@ -10,7 +10,7 @@ Чтобы добавить узел «Вычисление», в интерфейсе настройки **рабочего процесса** нажмите кнопку с плюсом («+») в нужном месте потока: -![Узел Вычисление_Добавление](https://static-docs.nocobase.com/58a45540d26945251cd143eb4b16579.png) +![Узел Вычисление_Добавление](https://static-docs.nocobase.com/58a455540d26945251cd143eb4b16579.png) ## Настройка узла diff --git a/docs/docs/ru/workflow/nodes/create.md b/docs/docs/ru/workflow/nodes/create.md index ddf87d438d2..ebc5e0873c6 100644 --- a/docs/docs/ru/workflow/nodes/create.md +++ b/docs/docs/ru/workflow/nodes/create.md @@ -40,6 +40,6 @@ ![Create Record Node_Example_Workflow Configuration](https://static-docs.nocobase.com/dfd4820d49c145fa331883fc09c9161f.png) -![Create Record Node_Example_Node Configuration](https://static-docs.nocobase.com/1a0992e6170be12a068da6503298868.png) +![Create Record Node_Example_Node Configuration](https://static-docs.nocobase.com/1a0992e66170be12a068da6503298868.png) После включения **рабочего процесса** с этой конфигурацией, при изменении записи в **коллекции** «Статьи» автоматически будет создана запись «Версии статей» для регистрации истории изменений статьи. \ No newline at end of file diff --git a/docs/docs/ru/workflow/nodes/manual.md b/docs/docs/ru/workflow/nodes/manual.md index 1826bad010e..088076b37d5 100644 --- a/docs/docs/ru/workflow/nodes/manual.md +++ b/docs/docs/ru/workflow/nodes/manual.md @@ -33,7 +33,7 @@ pkg: '@nocobase/plugin-workflow-manual' Выберите пользователя или укажите первичный/внешний ключ пользовательских данных из контекста с помощью переменной. -![Ручной узел_Настройка_Ответственный_Выбор переменной](https://static-docs.nocobase.com/22fbca3b8e21fda3a81019037001445.png) +![Ручной узел_Настройка_Ответственный_Выбор переменной](https://static-docs.nocobase.com/22fbca3b8e21fda3a831019037001445.png) :::info{title=Примечание} В настоящее время опция «Ответственный» для ручных узлов не поддерживает нескольких пользователей. Эта функция будет добавлена в будущих версиях. @@ -61,7 +61,7 @@ pkg: '@nocobase/plugin-workflow-manual' Блоки данных узла работают аналогично: вы можете выбрать результат данных из предыдущего узла для отображения в качестве деталей. Например, результат узла вычислений, расположенного выше по потоку, может служить контекстной справочной информацией для задачи ответственного. -![Ручной узел_Настройка узла_Настройка интерфейса_Блок данных_Данные узла](https://static-docs.nocobase.com/a583e26e508e95b47e5ddff80d998c4.png) +![Ручной узел_Настройка узла_Настройка интерфейса_Блок данных_Данные узла](https://static-docs.nocobase.com/a583e26e508e954b47e5ddff80d998c4.png) :::info{title=Примечание} Поскольку во время настройки интерфейса рабочий процесс находится в невыполненном состоянии, в блоках данных не отображаются конкретные данные. Соответствующие данные для конкретного экземпляра рабочего процесса будут видны во всплывающем окне задачи только после того, как рабочий процесс будет запущен и выполнен. diff --git a/docs/docs/ru/workflow/nodes/parallel.md b/docs/docs/ru/workflow/nodes/parallel.md index 355204dddf5..882259a5048 100644 --- a/docs/docs/ru/workflow/nodes/parallel.md +++ b/docs/docs/ru/workflow/nodes/parallel.md @@ -18,7 +18,7 @@ pkg: '@nocobase/plugin-workflow-parallel' В интерфейсе настройки рабочего процесса нажмите кнопку плюс («+») в потоке, чтобы добавить узел «Параллельная ветвь»: -![Добавить параллельную ветвь](https://static-docs.nocobase.com/9e0f3faa0b9335270647a3047759eac.png) +![Добавить параллельную ветвь](https://static-docs.nocobase.com/9e0f3faa0b9335270647a30477559eac.png) После добавления узла параллельной ветви в рабочий процесс по умолчанию добавляются две подветви. Вы также можете добавить любое количество дополнительных ветвей, нажав кнопку добавления ветви. В каждую ветвь можно добавить любое количество узлов. Ненужные ветви можно удалить, нажав кнопку удаления в начале ветви. diff --git a/docs/docs/ru/workflow/nodes/response-message.md b/docs/docs/ru/workflow/nodes/response-message.md index 12b632c3b62..e293f3a62e4 100644 --- a/docs/docs/ru/workflow/nodes/response-message.md +++ b/docs/docs/ru/workflow/nodes/response-message.md @@ -20,7 +20,7 @@ pkg: '@nocobase/plugin-workflow-response-message' В поддерживаемых типах рабочих процессов вы можете добавить узел «Ответное сообщение» в любом месте рабочего процесса. Нажмите кнопку плюса («+») в рабочем процессе, чтобы добавить узел «Ответное сообщение». -![Добавление узла](https://static-docs.nocobase.com/eac2b3562e95e4ce59f340624062ed3d.png) +![Добавление узла](https://static-docs.nocobase.com/eac2b3565e95e4ce59f340624062ed3d.png) Ответное сообщение существует в виде массива на протяжении всего процесса запроса. При каждом выполнении узла ответного сообщения в рабочий процесс новое содержимое сообщения добавляется в этот массив. Когда сервер отправляет ответ, все сообщения отправляются клиенту вместе. diff --git a/docs/docs/ru/workflow/nodes/variable.md b/docs/docs/ru/workflow/nodes/variable.md index a975fb6b13c..9929d1836c2 100644 --- a/docs/docs/ru/workflow/nodes/variable.md +++ b/docs/docs/ru/workflow/nodes/variable.md @@ -17,7 +17,7 @@ pkg: '@nocobase/plugin-workflow-variable' В интерфейсе настройки рабочего процесса нажмите кнопку «плюс» («+») в потоке, чтобы добавить узел «Переменная»: -![Добавить узел Переменная](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![Добавить узел Переменная](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## Настройка узла @@ -42,7 +42,7 @@ pkg: '@nocobase/plugin-workflow-variable' В режиме объявления установка значения переменной эквивалентна присвоению ей начального значения. -![Объявление начального значения](https://static-docs.nocobase.com/4ce2c50886565ad537343013758c6a4.png) +![Объявление начального значения](https://static-docs.nocobase.com/4ce2c508986565ad537343013758c6a4.png) В режиме присвоения установка значения переменной эквивалентна изменению значения объявленной целевой переменной на новое. Последующие использования будут получать это новое значение. @@ -80,6 +80,6 @@ pkg: '@nocobase/plugin-workflow-variable' Таким образом, после завершения циклического ветвления переменная получателя будет содержать строку получателей всех авторов статьи. Затем, после цикла, вы можете использовать узел HTTP-запроса для вызова API отправки почты, передав значение переменной получателя в качестве параметра получателя для API: -![Отправка почты получателям через узел запроса](https://static-docs.nocobase.com/37a6e172bcb2dce10a250947e.png) +![Отправка почты получателям через узел запроса](https://static-docs.nocobase.com/37f71aa1a63e172bcb2dce10a250947e.png) На этом простая функция массовой рассылки электронной почты реализована с использованием циклов и узлов переменных. \ No newline at end of file diff --git a/docs/docs/ru/workflow/triggers/collection.md b/docs/docs/ru/workflow/triggers/collection.md index b41da52e509..1c3b6713fb6 100644 --- a/docs/docs/ru/workflow/triggers/collection.md +++ b/docs/docs/ru/workflow/triggers/collection.md @@ -21,7 +21,7 @@ Вы можете выбрать момент срабатывания триггера в соответствии с вашими бизнес-потребностями. Если выбранный тип изменения включает обновление коллекции, вы также можете указать поля, которые должны измениться. Условие срабатывания будет выполнено только при изменении выбранных полей. Если поля не выбраны, это означает, что изменение любого поля может запустить рабочий процесс. -![События коллекции_Выбор измененных полей](https://static-docs.nocobase.com/874a175f01298b3c00267b2b4674611.png) +![События коллекции_Выбор измененных полей](https://static-docs.nocobase.com/874a1475f01298b3c00267b2b4674611.png) Более того, вы можете настроить правила условий для каждого поля строки данных, которая вызывает срабатывание. Триггер сработает только в том случае, если поля соответствуют заданным условиям. diff --git a/docs/docs/ru/workflow/triggers/post-action.md b/docs/docs/ru/workflow/triggers/post-action.md index 1fb813f05e9..96c8c2e7d5a 100644 --- a/docs/docs/ru/workflow/triggers/post-action.md +++ b/docs/docs/ru/workflow/triggers/post-action.md @@ -178,7 +178,7 @@ curl -X POST -H 'Authorization: Bearer ' -H 'X-Role: ' -d Как показано на рисунке ниже: -![Порядок выполнения действий](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![Порядок выполнения действий](https://static-docs.nocobase.com/20251219234806.png) ### Отличие от события коллекции diff --git a/docs/docs/ru/workflow/triggers/pre-action.md b/docs/docs/ru/workflow/triggers/pre-action.md index 91fd8888a6c..00e01b375d0 100644 --- a/docs/docs/ru/workflow/triggers/pre-action.md +++ b/docs/docs/ru/workflow/triggers/pre-action.md @@ -42,7 +42,7 @@ pkg: '@nocobase/plugin-workflow-request-interceptor' Если в настройках триггера выбран режим "Перехватывать только при отправке формы, привязанной к этому рабочему процессу", вам также необходимо вернуться к интерфейсу формы и привязать этот рабочий процесс к соответствующей кнопке действия: -![Добавить заказ_Привязать рабочий процесс](https://static-docs.nocobase.com/bae931e60f9bcc51bbc222e40e891e5.png) +![Добавить заказ_Привязать рабочий процесс](https://static-docs.nocobase.com/bae3931e60f9bcc51bbc222e40e891e5.png) В настройках привязки рабочего процесса выберите соответствующий рабочий процесс. Обычно для контекста запуска данных достаточно выбрать значение по умолчанию "Все данные формы": diff --git a/docs/docs/sv/ai-employees/knowledge-base/knowledge-base.md b/docs/docs/sv/ai-employees/knowledge-base/knowledge-base.md index 9fb59b6f44e..b170a81d437 100644 --- a/docs/docs/sv/ai-employees/knowledge-base/knowledge-base.md +++ b/docs/docs/sv/ai-employees/knowledge-base/knowledge-base.md @@ -33,15 +33,15 @@ Klicka på knappen `Submit` för att skapa kunskapsbasen. När ni har skapat kunskapsbasen, klicka på den nyskapade kunskapsbasen på listan över kunskapsbaser för att komma till sidan för hantering av dokument i kunskapsbasen. -![20251023100458](https://static-docs.nocobase.com/2025100458.png) +![20251023100458](https://static-docs.nocobase.com/20251023100458.png) -![20251023100527](https://static-docs.nocobase.com/2025100527.png) +![20251023100527](https://static-docs.nocobase.com/20251023100527.png) Klicka på knappen `Upload` för att ladda upp dokument. Efter att dokumenten har laddats upp startar vektoriseringen automatiskt. Vänta tills `Status` ändras från `Pending` till `Success`. För närvarande stöder kunskapsbasen följande dokumenttyper: txt, pdf, doc, docx, ppt, pptx; PDF stöder endast ren text. -![20251023100901](https://static-docs.nocobase.com/2025100901.png) +![20251023100901](https://static-docs.nocobase.com/20251023100901.png) ## Typer av kunskapsbaser @@ -49,16 +49,16 @@ För närvarande stöder kunskapsbasen följande dokumenttyper: txt, pdf, doc, d En lokal kunskapsbas är en kunskapsbas som lagras lokalt i NocoBase. Både dokumenten och deras vektordata lagras lokalt av NocoBase. -![20251023101620](https://static-docs.nocobase.com/2025101620.png) +![20251023101620](https://static-docs.nocobase.com/20251023101620.png) ### Skrivskyddad kunskapsbas En skrivskyddad kunskapsbas är en kunskapsbas där dokument och vektordata underhålls externt. Endast en anslutning till vektordatabasen skapas i NocoBase (för närvarande stöds endast PGVector). -![20251023101743](https://static-docs.nocobase.com/2025101743.png) +![20251023101743](https://static-docs.nocobase.com/20251023101743.png) ### Extern kunskapsbas En extern kunskapsbas är en kunskapsbas där dokument och vektordata underhålls externt. Hämtning från vektordatabasen behöver utökas av utvecklare, vilket möjliggör användning av vektordatabaser som för närvarande inte stöds av NocoBase. -![20251023101949](https://static-docs.nocobase.com/2025101949.png) \ No newline at end of file +![20251023101949](https://static-docs.nocobase.com/20251023101949.png) \ No newline at end of file diff --git a/docs/docs/sv/auth-verification/auth-oidc/examples/google.md b/docs/docs/sv/auth-verification/auth-oidc/examples/google.md index a1b36b3acd0..b839c1f3aea 100644 --- a/docs/docs/sv/auth-verification/auth-oidc/examples/google.md +++ b/docs/docs/sv/auth-verification/auth-oidc/examples/google.md @@ -10,11 +10,11 @@ Detta dokument har översatts av AI. För eventuella felaktigheter, se [den enge [Google Cloud Console](https://console.cloud.google.com/apis/credentials) – Skapa autentiseringsuppgifter – OAuth-klient-ID -![](https://static-docs.nocobase.com/0f2946c8643565ecc4ac1324988638c.png) +![](https://static-docs.nocobase.com/0f2946c8643565ecc4ac13249882638c.png) Gå till konfigurationsgränssnittet och fyll i den auktoriserade omdirigerings-URL:en. Omdirigerings-URL:en kan hämtas när du lägger till en autentiserare i NocoBase. Vanligtvis är den `http(s)://host:port/api/oidc:redirect`. Se avsnittet [Användarmanual – Konfiguration](../index.md#configuration). -![](https://static-docs.nocobase.com/24078bf52ec966a16334984cb3d9d126.png) +![](https://static-docs.nocobase.com/24078bf52ec966a16334894cb3d9d126.png) ## Lägg till en ny autentiserare i NocoBase diff --git a/docs/docs/sv/auth-verification/auth-saml/examples/google.md b/docs/docs/sv/auth-verification/auth-saml/examples/google.md index 69c3bc04404..d60dd5c057e 100644 --- a/docs/docs/sv/auth-verification/auth-saml/examples/google.md +++ b/docs/docs/sv/auth-verification/auth-saml/examples/google.md @@ -33,7 +33,7 @@ Kopiera sedan SP Issuer/EntityID och ACS URL från avsnittet "Usage". Gå tillbaka till Googles konsol. På sidan **Information om tjänsteleverantör** anger du den ACS-URL och det entitets-ID du kopierade tidigare, och markerar **Signerat svar**. -![](https://static-docs.nocobase.com/1536268bf8df4a5ebc4834317172191.png) +![](https://static-docs.nocobase.com/1536268bf8df4a5ebc72384317172191.png) ![](https://static-docs.nocobase.com/c7de1f8b84c1335de110e5a7c96255c4.png) diff --git a/docs/docs/sv/data-sources/collection-fdw/index.md b/docs/docs/sv/data-sources/collection-fdw/index.md index 1f226272f7c..39df52b2ac9 100644 --- a/docs/docs/sv/data-sources/collection-fdw/index.md +++ b/docs/docs/sv/data-sources/collection-fdw/index.md @@ -73,4 +73,4 @@ Synkronisering av fjärrtabell Slutligen visas den i gränssnittet -![Visas i gränssnittet](https://static-docs.nocobase.com/368fca27c99277d9360ca81350949357.png) \ No newline at end of file +![Visas i gränssnittet](https://static-docs.nocobase.com/368fca27a99277d9360ca81350949357.png) \ No newline at end of file diff --git a/docs/docs/sv/data-sources/data-modeling/collection-fields/associations/m2o/index.md b/docs/docs/sv/data-sources/data-modeling/collection-fields/associations/m2o/index.md index 7da0b627046..dd3ed170456 100644 --- a/docs/docs/sv/data-sources/data-modeling/collection-fields/associations/m2o/index.md +++ b/docs/docs/sv/data-sources/data-modeling/collection-fields/associations/m2o/index.md @@ -12,7 +12,7 @@ ER-diagram: Fältkonfiguration: -![alt text](https://static-docs.nocobase.com/3b4484ebb82f3dbf752bd84c9.png) +![alt text](https://static-docs.nocobase.com/3b4484ebb98d82f832f3dbf752bd84c9.png) ## Parameterbeskrivning diff --git a/docs/docs/sv/data-sources/data-modeling/collection-fields/associations/o2o/index.md b/docs/docs/sv/data-sources/data-modeling/collection-fields/associations/o2o/index.md index a40dc688f73..47be691c147 100644 --- a/docs/docs/sv/data-sources/data-modeling/collection-fields/associations/o2o/index.md +++ b/docs/docs/sv/data-sources/data-modeling/collection-fields/associations/o2o/index.md @@ -20,7 +20,7 @@ ER-relation Fältkonfiguration -![alt text](https://static-docs.nocobase.com/7665a87e094b4fb0c9426a108f87105.png) +![alt text](https://static-docs.nocobase.com/7665a87e094b4fb50c9426a108f87105.png) ## En-till-en (Tillhör) @@ -32,7 +32,7 @@ ER-relation Fältkonfiguration -![alt text](https://static-docs.nocobase.com/4f09eeb3c7717d61a34982da43c187c.png) +![alt text](https://static-docs.nocobase.com/4f09eeb3c7717d61a349842da43c187c.png) ## Parameterbeskrivningar diff --git a/docs/docs/sv/data-sources/field-encryption/index.md b/docs/docs/sv/data-sources/field-encryption/index.md index a92dda19a57..3d92fe1af22 100644 --- a/docs/docs/sv/data-sources/field-encryption/index.md +++ b/docs/docs/sv/data-sources/field-encryption/index.md @@ -30,7 +30,7 @@ Om pluginet aktiveras av en underapplikation sparas nyckeln som standard i katal Vi använder kuvertkryptering. -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### Process för nyckelskapande 1. Första gången ett krypterat fält skapas genererar systemet automatiskt en 32-bitars `applikationsnyckel` som sparas i standardlagringskatalogen, Base64-kodad. diff --git a/docs/docs/sv/email-manager/advanced/batch-send.md b/docs/docs/sv/email-manager/advanced/batch-send.md index 174769938f8..b8780775f57 100644 --- a/docs/docs/sv/email-manager/advanced/batch-send.md +++ b/docs/docs/sv/email-manager/advanced/batch-send.md @@ -10,27 +10,27 @@ Detta dokument har översatts av AI. För eventuella felaktigheter, se [den enge ## Massutskick – översikt Ni kan skicka e-postmeddelanden till flera personer som massutskick (varje mottagare får ett separat meddelande). -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## Massutskick via tabell Ni kan också skicka e-post som massutskick via en tabell: 1. Lägg till en knapp för att skicka e-post i tabellen - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. Konfigurera e-postfältet i tabellen (används för att tolka e-postadresser efter att ni har valt tabellrader) - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. Markera tabelldata för att skicka e-post - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) Om ni behöver skicka e-post till alla adresser i hela tabellen kan ni aktivera funktionen **Välj alla poster i den aktuella tabellen som mottagare som standard**: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) Efter att ni har redigerat e-postinnehållet klickar ni på knappen för massutskick för att skicka: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## Spårning av e-postutskick Ni kan se och spåra den specifika statusen för e-postutskick i E-posthanteringscentret: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/sv/email-manager/usage/signature.md b/docs/docs/sv/email-manager/usage/signature.md index 43ac0407562..72a230fba0f 100644 --- a/docs/docs/sv/email-manager/usage/signature.md +++ b/docs/docs/sv/email-manager/usage/signature.md @@ -11,15 +11,15 @@ Detta dokument har översatts av AI. För eventuella felaktigheter, se [den enge ## Konfigurera signaturer Gå till E-posthanteringscentret och klicka på inställningsknappen: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Växla till signaturpanelen: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) Här kan ni hantera signaturer. Markera alternativet framför en signatur för att ställa in den som standardsignatur: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## Använda signaturer I meddelandetexten klickar ni på signaturikonen för att välja önskad signatur: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/sv/email-manager/usage/template.md b/docs/docs/sv/email-manager/usage/template.md index 17aceedb24f..3059d18bc03 100644 --- a/docs/docs/sv/email-manager/usage/template.md +++ b/docs/docs/sv/email-manager/usage/template.md @@ -12,18 +12,18 @@ Detta dokument har översatts av AI. För eventuella felaktigheter, se [den enge Gå till E-posthanteringscentret och klicka på inställningsknappen: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Växla till mallpanelen: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) Här kan ni hantera mallar: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## Använda mallar I meddelandetexten klickar ni på mallikonen för att välja önskad mall: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/sv/flow-engine/learning-roadmap.md b/docs/docs/sv/flow-engine/learning-roadmap.md index 3b8e91ca270..7eb67949fed 100644 --- a/docs/docs/sv/flow-engine/learning-roadmap.md +++ b/docs/docs/sv/flow-engine/learning-roadmap.md @@ -4,4 +4,4 @@ Detta dokument har översatts av AI. För eventuella felaktigheter, se [den enge # Lärandekarta -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/sv/solution/ticket-system/design.md b/docs/docs/sv/solution/ticket-system/design.md index 9a0f1414f89..23c4d5ef89d 100755 --- a/docs/docs/sv/solution/ticket-system/design.md +++ b/docs/docs/sv/solution/ticket-system/design.md @@ -31,7 +31,7 @@ Inspirerad av konceptet "T-formad kompetens" — horisontell bredd + vertikalt d - **Horisontell (huvudtabell)**: Täcker universella funktioner för alla affärstyper — ärendenummer, status, handläggare, SLA och andra kärnfält. - **Vertikal (expansionstabeller)**: Specialiserade fält för specifika affärstyper — utrustningsreparation har serienummer, klagomål har kompensationsplaner. -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **Varför denna design?** @@ -61,7 +61,7 @@ Inte bara "AI-funktioner", utan "AI-medarbetare". Varje AI har en tydlig roll, p #### Filosofi tre: Kunskapens självcirkulation -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) Detta skapar ett slutet kretslopp för **kunskapsackumulering och kunskapsapplikation**. @@ -71,7 +71,7 @@ Detta skapar ett slutet kretslopp för **kunskapsackumulering och kunskapsapplik ### 2.1 Översikt över entitetsrelationer -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 Detaljer om kärntabeller @@ -296,18 +296,18 @@ Detta är systemets kärna, som använder en design med "bred tabell" där alla **Huvudflöde (från vänster till höger)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **Sidoflöden** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **Fullständig tillståndsmaskin** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 Regler för statusövergångar @@ -337,7 +337,7 @@ Detta är systemets kärna, som använder en design med "bred tabell" där alla ### 4.2 SLA-beräkningslogik -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### Vid skapande av ärende @@ -466,7 +466,7 @@ Varje AI-medarbetare har 4 specifika uppgifter: ### 5.3 AI-medarbetare och ärendets livscykel -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 Exempel på AI-svar @@ -526,12 +526,12 @@ Grace ansvarar för kvalitetsgranskning av svar och blockerar följande problem: ### 6.1 Kunskapskällor -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 Flöde för att omvandla ärende till kunskap -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **Utvärderingsdimensioner**: - **Allmängiltighet**: Är detta ett vanligt problem? @@ -576,19 +576,19 @@ När en handläggare öppnar ärendedetaljer rekommenderar Max automatiskt relev #### WF-T01: Flöde för skapande av ärende -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: AI-analys av ärende -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: Översättning och granskning av kommentarer -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: Kunskapsgenerering -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 Schemalagda uppgifter @@ -605,11 +605,11 @@ När en handläggare öppnar ärendedetaljer rekommenderar Max automatiskt relev ### 8.1 Administrationsgränssnitt -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 Kundportal -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 Design av instrumentpaneler diff --git a/docs/docs/sv/users-permissions/acl/ui.md b/docs/docs/sv/users-permissions/acl/ui.md index 70d263218f4..70fd03a4a9d 100644 --- a/docs/docs/sv/users-permissions/acl/ui.md +++ b/docs/docs/sv/users-permissions/acl/ui.md @@ -20,7 +20,7 @@ Global behörighetskonfiguration: **Samlingen** "Ordrar" individuell behörighetskonfiguration: -![](https://static-docs.nocobase.com/a88caba1cad47001c16010bf402a4a2c1.png) +![](https://static-docs.nocobase.com/a88caba1cad47001c1610bf402a4a2c1.png) I användargränssnittet visas inga block från **samlingen** "Ordrar". @@ -50,7 +50,7 @@ I användargränssnittet visas endast fält med konfigurerade behörigheter inom Så här ser den fullständiga konfigurationsprocessen ut: - ![](https://static-docs.nocobase.com/1dbe559a97c2e052e194e50edc74a7.gif) + ![](https://static-docs.nocobase.com/1dbe559a9579c2e052e194e50edc74a7.gif) - **Lägg till**: Bestämmer om fält kan läggas till (skapas). diff --git a/docs/docs/sv/workflow/nodes/aggregate.md b/docs/docs/sv/workflow/nodes/aggregate.md index a8f5007e32c..d2224ff1ef2 100644 --- a/docs/docs/sv/workflow/nodes/aggregate.md +++ b/docs/docs/sv/workflow/nodes/aggregate.md @@ -26,7 +26,7 @@ I arbetsflödets konfigurationsgränssnitt klickar du på plusknappen ("+") i fl ## Nodkonfiguration -![Aggregerad fråga-nod_Nodkonfiguration](https://static-docs.nocobase.com/5732f747b999230567c6bb5e986fd2.png) +![Aggregerad fråga-nod_Nodkonfiguration](https://static-docs.nocobase.com/57362f747b9992230567c6bb5e986fd2.png) ### Aggregeringsfunktion @@ -64,7 +64,7 @@ Därefter skapar du ett arbetsflöde som utlöses av en samlingshändelse. Välj Lägg sedan till en aggregerad fråga-nod och konfigurera den enligt följande: -![Aggregerad fråga-nod_Exempel_Nodkonfiguration](https://static-docs.nocobase.com/542272e636c6c0a567373d1b37ddda78.png) +![Aggregerad fråga-nod_Exempel_Nodkonfiguration](https://static-docs.nocobase.com/542272e638c6c0a567373d1b37ddda78.png) På så sätt, efter att arbetsflödet har utlösts, kommer noden för aggregerad fråga att räkna antalet alla artiklar i kategorin för den nyligen tillagda artikeln och spara resultatet som nodens utdata. diff --git a/docs/docs/sv/workflow/nodes/loop.md b/docs/docs/sv/workflow/nodes/loop.md index 739d8133a59..b47da1f5c4f 100644 --- a/docs/docs/sv/workflow/nodes/loop.md +++ b/docs/docs/sv/workflow/nodes/loop.md @@ -95,7 +95,7 @@ Till exempel, när en order läggs, behöver ni kontrollera lagret för varje pr 2. Skapa ett arbetsflöde. För triggern, välj "Samlingshändelse", och välj samlingen "Ordrar" för att triggas "När en post läggs till". Ni behöver också konfigurera den för att förladda relationsdata för samlingen "Orderdetaljer" och samlingen "Produkter" under detaljerna: - ![Loop-nod_Exempel_Triggerkonfiguration](https://static-docs.nocobase.com/0086601c71c0e17a64d046a4c86b49b7.png) + ![Loop-nod_Exempel_Triggerkonfiguration](https://static-docs.nocobase.com/0086601c2fc0e17a64d046a4c86b49b7.png) 3. Skapa en loop-nod och välj loop-objektet som "Triggerdata / Orderdetaljer", vilket innebär att den kommer att bearbeta varje post i samlingen Orderdetaljer: diff --git a/docs/docs/sv/workflow/nodes/manual.md b/docs/docs/sv/workflow/nodes/manual.md index ed79c05c3d1..913c8d66f37 100644 --- a/docs/docs/sv/workflow/nodes/manual.md +++ b/docs/docs/sv/workflow/nodes/manual.md @@ -84,7 +84,7 @@ Formulärets skicka-knappar kan konfigureras i tre typer: - Skicka och avsluta arbetsflödet - Spara endast formulärvärden -![人工节点_节点配置_界面配置_表单按钮](https://static-docs.nocobase.com/6b4599b14152e832a265405492104a8.png) +![人工节点_节点配置_界面配置_表单按钮](https://static-docs.nocobase.com/6b45995b14152e85a821dff6f6e3189a.png) De tre knapparna representerar tre nodstatusar i arbetsflödesprocessen. Efter inlämning ändras nodens status till "Slutförd", "Avvisad" eller förblir i ett "Väntande" tillstånd. Ett formulär måste ha minst en av de två första konfigurerade för att bestämma det efterföljande flödet för hela arbetsflödet. @@ -104,11 +104,11 @@ För manuell hantering behöver ni också lägga till en att-göra-lista på en Ni kan välja "Arbetsflöde Att-göra" från blocken på en sida för att lägga till ett block för att-göra-listan: -![人工节点_添加待办区块](https://static-docs.nocobase.com/198b41754cd73b704267bf30fe5e647.png) +![人工节点_添加待办区块](https://static-docs.nocobase.com/198b417454cd73b704267bf30fe5e647.png) Exempel på att-göra-listblock: -![人工节点_待办列表](https://static-docs.nocobase.com/cfefb053c9dfa550d6b220f34.png) +![人工节点_待办列表](https://static-docs.nocobase.com/cfefb0d2c6a91c5c9dfa550d6b220f34.png) ### Att-göra-detaljer diff --git a/docs/docs/sv/workflow/nodes/parallel.md b/docs/docs/sv/workflow/nodes/parallel.md index 34faa1de6f0..12cdeddb087 100644 --- a/docs/docs/sv/workflow/nodes/parallel.md +++ b/docs/docs/sv/workflow/nodes/parallel.md @@ -18,11 +18,11 @@ Inbyggd plugin, ingen installation krävs. I gränssnittet för arbetsflödeskonfiguration klickar ni på plusknappen ("+") i flödet för att lägga till en nod för "Parallell gren": -![Lägg till parallell gren](https://static-docs.nocobase.com/9e0f3faa0b9335270647a3047759eac.png) +![Lägg till parallell gren](https://static-docs.nocobase.com/9e0f3faa0b9335270647a30477559eac.png) När ni har lagt till en nod för parallell gren i arbetsflödet läggs två undergrenar till som standard. Ni kan också lägga till fler grenar genom att klicka på knappen för att lägga till gren. Valfritt antal noder kan läggas till i varje gren. Onödiga grenar kan tas bort genom att klicka på borttagningsknappen i början av grenen. -![Hantera parallella grenar](https://static-docs.nocobase.com/36089b8b79711eb3ee9bc2a757.png) +![Hantera parallella grenar](https://static-docs.nocobase.com/36088a8b7970c8a1771eb3ee9bc2a757.png) ## Nodkonfiguration diff --git a/docs/docs/sv/workflow/nodes/variable.md b/docs/docs/sv/workflow/nodes/variable.md index d69b4f03261..82c6d199284 100644 --- a/docs/docs/sv/workflow/nodes/variable.md +++ b/docs/docs/sv/workflow/nodes/variable.md @@ -16,7 +16,7 @@ Ni kan deklarera variabler i ett arbetsflöde eller tilldela värden till redan I arbetsflödets konfigurationsgränssnitt klickar ni på plusknappen ("+") i arbetsflödet för att lägga till en "Variabel"-nod: -![Add Variable Node](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![Add Variable Node](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## Konfigurera nod @@ -79,6 +79,6 @@ Efter beräkningsnoden skapar ni ytterligare en variabelnod. Välj tilldelningsl På så sätt, efter att loopgrenen har avslutats, kommer mottagarvariabeln att lagra mottagarsträngen för alla artikelns författare. Därefter, efter loopen, kan ni använda en HTTP-förfrågningsnod för att anropa ett e-postsändnings-API och skicka värdet från mottagarvariabeln som mottagarparameter till API:et: -![Send mail to recipients via the request node](https://static-docs.nocobase.com/37f71aa1a36e172bcb2dce10a250947e.png) +![Send mail to recipients via the request node](https://static-docs.nocobase.com/37f71aa1a63e172bcb2dce10a250947e.png) Härmed har en enkel massutskicksfunktion för e-post implementerats med hjälp av en loop och en variabelnod. \ No newline at end of file diff --git a/docs/docs/sv/workflow/triggers/collection.md b/docs/docs/sv/workflow/triggers/collection.md index 86540a3b2c9..0d06afb6a7a 100644 --- a/docs/docs/sv/workflow/triggers/collection.md +++ b/docs/docs/sv/workflow/triggers/collection.md @@ -21,7 +21,7 @@ Det finns flera typer av ändringar i en samling: Ni kan välja när triggern ska utlösas baserat på olika affärsbehov. När den valda ändringen inkluderar uppdatering av samlingen, kan ni även specificera vilka fält som har ändrats. Triggervillkoret uppfylls endast när de valda fälten ändras. Om inga fält väljs, innebär det att en ändring i vilket fält som helst kan utlösa arbetsflödet. -![数据表事件_发生变动的字段选择](https://static-docs.nocobase.com/8741475f01298b3c00267b2b4674611.png) +![数据表事件_发生变动的字段选择](https://static-docs.nocobase.com/874a1475f01298b3c00267b2b4674611.png) Mer specifikt kan ni konfigurera villkorsregler för varje fält i den utlösande dataraden. Triggern utlöses endast när fälten uppfyller de motsvarande villkoren. diff --git a/docs/docs/sv/workflow/triggers/post-action.md b/docs/docs/sv/workflow/triggers/post-action.md index 0ca7185b638..a71f9992458 100644 --- a/docs/docs/sv/workflow/triggers/post-action.md +++ b/docs/docs/sv/workflow/triggers/post-action.md @@ -178,7 +178,7 @@ Om händelsen är konfigurerad i globalt läge, behöver ni inte använda URL-pa Som visas i figuren nedan: -![Åtgärdsutförandeordning](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![Åtgärdsutförandeordning](https://static-docs.nocobase.com/20251219234806.png) ### Skillnad från samlingshändelse diff --git a/docs/docs/sv/workflow/triggers/pre-action.md b/docs/docs/sv/workflow/triggers/pre-action.md index c0ec0cae6ee..52921096ade 100644 --- a/docs/docs/sv/workflow/triggers/pre-action.md +++ b/docs/docs/sv/workflow/triggers/pre-action.md @@ -28,7 +28,7 @@ När ni skapar ett arbetsflöde, välj typen "Före åtgärd-händelse": I triggaren för ett avlyssnande arbetsflöde är det första ni behöver konfigurera den samling som motsvarar åtgärden: -![Avlyssningshändelsekonfiguration_Samling](https://static-docs.nocobase.com/8f7122caca1f5425e2b472053f89baba.png) +![Avlyssningshändelsekonfiguration_Samling](https://static-docs.nocobase.com/8f7122caca8159d334cf776f838d53d6.png) Välj sedan avlyssningsläge. Ni kan välja att endast avlyssna åtgärdsknappen som är kopplad till detta arbetsflöde, eller att avlyssna alla valda åtgärder för denna samling (oavsett vilket formulär de kommer ifrån, och utan att behöva koppla till ett specifikt arbetsflöde): diff --git a/docs/docs/sv/workflow/triggers/schedule.md b/docs/docs/sv/workflow/triggers/schedule.md index f779b4d57c6..608a86940c3 100644 --- a/docs/docs/sv/workflow/triggers/schedule.md +++ b/docs/docs/sv/workflow/triggers/schedule.md @@ -74,6 +74,6 @@ Skapa ett arbetsflöde baserat på en schemalagd uppgift. I utlösarkonfiguratio Konfigurera sedan andra noder enligt processlogiken för att uppdatera statusen för ordern med utlösningsdata-ID och statusen "obetald" till annullerad: -![Schemalagd uppgift_Utlösarkonfiguration_Tidsfält i samling-läge_Uppdateringsnod](https://static-docs.nocobase.com/491dde9df773f5b14a4fd8ceac9d3e.png) +![Schemalagd uppgift_Utlösarkonfiguration_Tidsfält i samling-läge_Uppdateringsnod](https://static-docs.nocobase.com/491dde9df8f773f5b14a4fd8ceac9d3e.png) Till skillnad från läget Anpassad tid behöver ni här inte beräkna tiden för 30 minuter sedan, eftersom arbetsflödets utlösningsdata-kontext redan innehåller den datarad som uppfyller tidskriteriet. Därför kan ni direkt uppdatera statusen för den motsvarande ordern. \ No newline at end of file diff --git a/docs/docs/th/ai-employees/permission.md b/docs/docs/th/ai-employees/permission.md index 745088f2f78..314309f457f 100644 --- a/docs/docs/th/ai-employees/permission.md +++ b/docs/docs/th/ai-employees/permission.md @@ -74,7 +74,7 @@ #### ตัวอย่างที่ 1: Overall Analytics (การวิเคราะห์ทางธุรกิจทั่วไป) -![05viz-configuration-2025-11-03-00-18-55](https://static-docs.nocobase.com/05viz-configuration-2025-11-01-00-18-55.png) +![05viz-configuration-2025-11-03-00-18-55](https://static-docs.nocobase.com/05viz-configuration-2025-11-03-00-18-55.png) ใน CRM Demo, `Overall Analytics` คือเอนจินการวิเคราะห์ทางธุรกิจที่ใช้เทมเพลตครับ/ค่ะ diff --git a/docs/docs/th/auth-verification/auth-saml/examples/google.md b/docs/docs/th/auth-verification/auth-saml/examples/google.md index 005469f4c2e..018d2fad0e9 100644 --- a/docs/docs/th/auth-verification/auth-saml/examples/google.md +++ b/docs/docs/th/auth-verification/auth-saml/examples/google.md @@ -36,7 +36,7 @@ ![](https://static-docs.nocobase.com/1536268bf8df4a5ebc72384317172191.png) -![](https://static-docs.nocobase.com/c7de1f8b84f34a5ebc72384317172191.png) +![](https://static-docs.nocobase.com/c7de1f8b84c1335de110e5a7c96255c4.png) ในส่วน **Attribute Mapping** (การแมปแอตทริบิวต์) ให้เพิ่มการแมปเพื่อเชื่อมโยงแอตทริบิวต์ที่เกี่ยวข้องครับ/ค่ะ diff --git a/docs/docs/th/auth-verification/auth/authenticators.md b/docs/docs/th/auth-verification/auth/authenticators.md index 2bfc8a42bbc..c87715199b1 100644 --- a/docs/docs/th/auth-verification/auth/authenticators.md +++ b/docs/docs/th/auth-verification/auth/authenticators.md @@ -15,7 +15,7 @@ pkg: '@nocobase/plugin-auth' ## การเปิดใช้งาน Authenticator -![](https://static-docs.nocobase.com/7f1b8f8ca5de67ffc68eff0a65848f5.png) +![](https://static-docs.nocobase.com/7f1fb8f8ca5de67ffc68eff0a65848f5.png) เฉพาะประเภทการยืนยันตัวตนที่เปิดใช้งานแล้วเท่านั้นที่จะแสดงบนหน้าเข้าสู่ระบบครับ diff --git a/docs/docs/th/data-sources/collection-fdw/index.md b/docs/docs/th/data-sources/collection-fdw/index.md index cf6d4c45c51..4b549c5b9a1 100644 --- a/docs/docs/th/data-sources/collection-fdw/index.md +++ b/docs/docs/th/data-sources/collection-fdw/index.md @@ -64,7 +64,7 @@ MySQL ใช้เอนจิน `federated` ซึ่งจำเป็นต หากตารางระยะไกลมีการเปลี่ยนแปลงโครงสร้าง คุณสามารถ "ซิงค์จากตารางระยะไกล" ได้ครับ/ค่ะ -![ซิงค์จากตารางระยะไกล](https://static-docs.nocobase.com/3751a9c5712851fb3ff33af3f1ff0f59.png) +![ซิงค์จากตารางระยะไกล](https://static-docs.nocobase.com/3751a9a39f933889fb3fcc4d85a6f4ad.png) การซิงค์ตารางระยะไกล diff --git a/docs/docs/th/data-sources/data-modeling/collection-fields/associations/o2o/index.md b/docs/docs/th/data-sources/data-modeling/collection-fields/associations/o2o/index.md index a1cdb87bb7f..3019c9e2bd4 100644 --- a/docs/docs/th/data-sources/data-modeling/collection-fields/associations/o2o/index.md +++ b/docs/docs/th/data-sources/data-modeling/collection-fields/associations/o2o/index.md @@ -21,7 +21,7 @@ ER Relationship Field Configuration -![alt text](https://static-docs.nocobase.com/7659e128936bbd7c9ff51bcff1d646dd.png) +![alt text](https://static-docs.nocobase.com/7665a87e094b4fb50c9426a108f87105.png) ## หนึ่งต่อหนึ่ง (เป็นของ) diff --git a/docs/docs/th/data-sources/field-encryption/index.md b/docs/docs/th/data-sources/field-encryption/index.md index d28b15c4314..6fbb7138026 100644 --- a/docs/docs/th/data-sources/field-encryption/index.md +++ b/docs/docs/th/data-sources/field-encryption/index.md @@ -29,7 +29,7 @@ pkg: "@nocobase/plugin-field-encryption" ใช้วิธีการเข้ารหัสแบบ Envelope Encryption ครับ/ค่ะ -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### ขั้นตอนการสร้างคีย์ 1. เมื่อสร้างฟิลด์ที่เข้ารหัสเป็นครั้งแรก ระบบจะสร้าง`คีย์แอปพลิเคชัน`ขนาด 32 บิตโดยอัตโนมัติ และบันทึกในรูปแบบ Base64 ไปยังไดเรกทอรีจัดเก็บเริ่มต้นครับ/ค่ะ diff --git a/docs/docs/th/email-manager/advanced/batch-send.md b/docs/docs/th/email-manager/advanced/batch-send.md index b3151ce298c..d7a40060de6 100644 --- a/docs/docs/th/email-manager/advanced/batch-send.md +++ b/docs/docs/th/email-manager/advanced/batch-send.md @@ -9,27 +9,27 @@ pkg: "@nocobase/plugin-email-manager" ## ภาพรวมการส่งอีเมลแบบกลุ่ม คุณสามารถส่งอีเมลแบบกลุ่มไปยังผู้รับหลายคนได้ โดยที่ผู้รับแต่ละคนจะได้รับอีเมลแยกกันครับ/ค่ะ -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## การส่งอีเมลแบบกลุ่มผ่านตาราง คุณยังสามารถส่งอีเมลแบบกลุ่มผ่านตารางได้ด้วยครับ/ค่ะ: 1. เพิ่มปุ่มส่งอีเมลลงในตาราง - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. กำหนดค่าฟิลด์อีเมลในตาราง (ใช้สำหรับแยกวิเคราะห์ที่อยู่อีเมลหลังจากเลือกแถวในตาราง) - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. เลือกข้อมูลในตารางเพื่อส่งอีเมล - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) หากคุณต้องการส่งอีเมลไปยังที่อยู่ทั้งหมดในตาราง คุณสามารถเปิดใช้งานฟังก์ชัน **เลือกบันทึกทั้งหมดในตารางปัจจุบันเป็นผู้รับโดยค่าเริ่มต้น** ได้ครับ/ค่ะ: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) หลังจากแก้ไขเนื้อหาอีเมลแล้ว ให้คลิกปุ่มส่งอีเมลแบบกลุ่มเพื่อส่งครับ/ค่ะ: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## การติดตามการส่งอีเมล คุณสามารถดูและติดตามสถานะการส่งอีเมลที่เฉพาะเจาะจงได้ที่ศูนย์จัดการอีเมลครับ/ค่ะ: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/th/email-manager/usage/signature.md b/docs/docs/th/email-manager/usage/signature.md index 04580e95b93..f56abf2df60 100644 --- a/docs/docs/th/email-manager/usage/signature.md +++ b/docs/docs/th/email-manager/usage/signature.md @@ -10,15 +10,15 @@ pkg: "@nocobase/plugin-email-manager" ## การตั้งค่าลายเซ็น เข้าไปที่ศูนย์จัดการอีเมล แล้วคลิกปุ่มตั้งค่าครับ/ค่ะ: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) จากนั้นสลับไปที่แผงลายเซ็นครับ/ค่ะ: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) ที่นี่คุณสามารถจัดการลายเซ็นได้ครับ/ค่ะ โดยติ๊กช่องตัวเลือกหน้าลายเซ็นเพื่อตั้งเป็นลายเซ็นเริ่มต้น: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## การใช้งานลายเซ็น ในช่องเนื้อหาอีเมล ให้คลิกไอคอนลายเซ็นเพื่อเลือกลายเซ็นที่คุณต้องการครับ/ค่ะ: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/th/email-manager/usage/template.md b/docs/docs/th/email-manager/usage/template.md index 8c22e3ccd4b..920616cda0f 100644 --- a/docs/docs/th/email-manager/usage/template.md +++ b/docs/docs/th/email-manager/usage/template.md @@ -10,15 +10,15 @@ pkg: "@nocobase/plugin-email-manager" ## การตั้งค่าเทมเพลต ไปที่ศูนย์จัดการอีเมล แล้วคลิกปุ่มตั้งค่าครับ/ค่ะ: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) สลับไปที่แผงเทมเพลตครับ/ค่ะ: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) คุณสามารถจัดการเทมเพลตได้ที่นี่ครับ/ค่ะ: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## การใช้งานเทมเพลต ในช่องเนื้อหาอีเมล ให้คลิกที่ไอคอนเทมเพลตเพื่อเลือกเทมเพลตที่คุณต้องการครับ/ค่ะ: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/th/flow-engine/learning-roadmap.md b/docs/docs/th/flow-engine/learning-roadmap.md index de3d956ac19..c132fdd019a 100644 --- a/docs/docs/th/flow-engine/learning-roadmap.md +++ b/docs/docs/th/flow-engine/learning-roadmap.md @@ -5,4 +5,4 @@ # เส้นทางการเรียนรู้ -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/th/solution/ticket-system/design.md b/docs/docs/th/solution/ticket-system/design.md index 7c0ffcf877d..526f25c2ef5 100755 --- a/docs/docs/th/solution/ticket-system/design.md +++ b/docs/docs/th/solution/ticket-system/design.md @@ -31,7 +31,7 @@ - **แนวนอน (ตารางหลัก)**: ครอบคลุมความสามารถทั่วไปของทุกประเภทธุรกิจ — เช่น หมายเลขใบสั่งงาน, สถานะ, ผู้รับผิดชอบ, SLA และฟิลด์หลักอื่น ๆ - **แนวตั้ง (ตารางส่วนขยาย)**: ฟิลด์เฉพาะทางสำหรับธุรกิจเฉพาะ — เช่น การซ่อมแซมอุปกรณ์จะมีหมายเลขซีเรียล (Serial Number), การร้องเรียนจะมีแผนการชดเชย -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **ทำไมต้องออกแบบเช่นนี้?** @@ -61,7 +61,7 @@ #### แนวคิดที่ 3: วงจรความรู้ด้วยตนเอง (Knowledge Self-Circulation) -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) สิ่งนี้ทำให้เกิดวงจรปิดของ **การสะสมความรู้ - การประยุกต์ใช้ความรู้** ครับ @@ -71,7 +71,7 @@ ### 2.1 ภาพรวมความสัมพันธ์ของเอนทิตี -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 รายละเอียดตารางหลัก @@ -296,18 +296,18 @@ **กระบวนการหลัก (จากซ้ายไปขวา)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **กระบวนการย่อย** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **สถานะของระบบทั้งหมด (State Machine)** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 กฎการเปลี่ยนสถานะที่สำคัญ @@ -337,7 +337,7 @@ ### 4.2 ตรรกะการคำนวณ SLA -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### เมื่อสร้างใบสั่งงาน @@ -466,7 +466,7 @@ ### 5.3 พนักงาน AI และวงจรชีวิตใบสั่งงาน -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 ตัวอย่างการตอบสนองของ AI @@ -527,12 +527,12 @@ Grace จะรับผิดชอบการตรวจสอบคุณ ### 6.1 แหล่งที่มาของความรู้ -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 กระบวนการเปลี่ยนใบสั่งงานเป็นความรู้ -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **เกณฑ์การประเมิน**: - **ความเป็นสากล**: นี่เป็นปัญหาที่พบบ่อยหรือไม่? @@ -577,19 +577,19 @@ Grace จะรับผิดชอบการตรวจสอบคุณ #### WF-T01: กระบวนการสร้างใบสั่งงาน -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: การวิเคราะห์ใบสั่งงานด้วย AI -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: การแปลและการตรวจสอบความคิดเห็น -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: การสร้างความรู้ -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 งานที่กำหนดเวลาไว้ (Scheduled Tasks) @@ -606,11 +606,11 @@ Grace จะรับผิดชอบการตรวจสอบคุณ ### 8.1 ส่วนการจัดการหลังบ้าน (Backend Admin) -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 ส่วนพอร์ทัลลูกค้า (Customer Portal) -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 การออกแบบแดชบอร์ด diff --git a/docs/docs/th/users-permissions/acl/role.md b/docs/docs/th/users-permissions/acl/role.md index 1cc0b79fc17..26baf1314d3 100644 --- a/docs/docs/th/users-permissions/acl/role.md +++ b/docs/docs/th/users-permissions/acl/role.md @@ -33,6 +33,6 @@ pkg: '@nocobase/plugin-acl' คุณสามารถกำหนดหลายบทบาทให้กับผู้ใช้หนึ่งคนได้ครับ/ค่ะ เมื่อผู้ใช้มีหลายบทบาท พวกเขาสามารถสลับบทบาทได้ที่ศูนย์ข้อมูลส่วนตัวครับ/ค่ะ -![](https://static-docs.nocobase.com/e31b11ec1ca3b8b7e0472105b167819.png) +![](https://static-docs.nocobase.com/e331d11ec1ca3b8b7e0472105b167819.png) ลำดับความสำคัญของบทบาทเริ่มต้นเมื่อผู้ใช้เข้าสู่ระบบจะเป็นดังนี้ครับ/ค่ะ: บทบาทที่สลับใช้งานล่าสุด (ค่านี้จะอัปเดตทุกครั้งที่มีการสลับบทบาท) > บทบาทแรก (บทบาทเริ่มต้นของระบบ) \ No newline at end of file diff --git a/docs/docs/th/users-permissions/acl/ui.md b/docs/docs/th/users-permissions/acl/ui.md index 17469731147..605bddb8cba 100644 --- a/docs/docs/th/users-permissions/acl/ui.md +++ b/docs/docs/th/users-permissions/acl/ui.md @@ -49,7 +49,7 @@ pkg: '@nocobase/plugin-acl' ขั้นตอนการตั้งค่าทั้งหมดมีดังนี้ครับ/ค่ะ -![](https://static-docs.nocobase.com/1dbe559a9597c2e052e194e50edc74a7.gif) +![](https://static-docs.nocobase.com/1dbe559a9579c2e052e194e50edc74a7.gif) - `เพิ่ม`: ควบคุมว่าฟิลด์สามารถเพิ่ม (สร้าง) ได้หรือไม่ครับ/ค่ะ diff --git a/docs/docs/th/users-permissions/departments/role.md b/docs/docs/th/users-permissions/departments/role.md index 4cd5f29437f..684974ec80b 100644 --- a/docs/docs/th/users-permissions/departments/role.md +++ b/docs/docs/th/users-permissions/departments/role.md @@ -17,7 +17,7 @@ pkg: '@nocobase/plugin-departments' วิธีที่สองคือการเพิ่มแผนกให้กับบทบาทที่เกี่ยวข้องในหน้าการจัดการบทบาทครับ/ค่ะ -![](https://static-docs.nocobase.com/f2a77bec937cf2f179ce868a92b98416d.png) +![](https://static-docs.nocobase.com/f2a7bec937cf2f179ce868a92b98416d.png) แผนกที่มีบทบาทนี้อยู่แล้วจะไม่สามารถเลือกได้ครับ/ค่ะ diff --git a/docs/docs/th/users-permissions/user.md b/docs/docs/th/users-permissions/user.md index 069fe681ceb..40bfed7c08b 100644 --- a/docs/docs/th/users-permissions/user.md +++ b/docs/docs/th/users-permissions/user.md @@ -25,7 +25,7 @@ pkg: '@nocobase/plugin-users' ## การแก้ไขโปรไฟล์ผู้ใช้งาน -![](https://static-docs.nocobase.com/d2e06872bd1d48ed8c1139728fa5ff3.png) +![](https://static-docs.nocobase.com/d25e06872bd1d48ed8c1139728fa5ff3.png) ![](https://static-docs.nocobase.com/c140bcaab240385b9b5aca32a2ec2801.png) diff --git a/docs/docs/th/workflow/advanced/variables.md b/docs/docs/th/workflow/advanced/variables.md index 0976927ad0d..765a6b278bd 100644 --- a/docs/docs/th/workflow/advanced/variables.md +++ b/docs/docs/th/workflow/advanced/variables.md @@ -18,7 +18,7 @@ เราได้ใช้งานฟังก์ชันตัวแปรหลายครั้งแล้วในส่วน [เริ่มต้นใช้งานอย่างรวดเร็ว](../getting-started.md) ครับ/ค่ะ ตัวอย่างเช่น ในโหนดการคำนวณ เราสามารถใช้ตัวแปรเพื่ออ้างอิงข้อมูลบริบทการทริกเกอร์สำหรับการคำนวณได้ดังนี้: -![โหนดการคำนวณที่ใช้ฟังก์ชันและตัวแปร](https://static-docs.nocobase.com/837e4851a4c70a1932542caade3431b.png) +![โหนดการคำนวณที่ใช้ฟังก์ชันและตัวแปร](https://static-docs.nocobase.com/837e4851a4c70a1932542caadef3431b.png) ในโหนดอัปเดต เราใช้ข้อมูลบริบทการทริกเกอร์เป็นตัวแปรสำหรับเงื่อนไขการกรอง และอ้างอิงผลลัพธ์จากโหนดการคำนวณเป็นตัวแปรสำหรับค่าฟิลด์ที่จะอัปเดตครับ/ค่ะ: diff --git a/docs/docs/th/workflow/nodes/calculation.md b/docs/docs/th/workflow/nodes/calculation.md index 8c432348fa7..cf20c8f5c46 100644 --- a/docs/docs/th/workflow/nodes/calculation.md +++ b/docs/docs/th/workflow/nodes/calculation.md @@ -11,7 +11,7 @@ ในหน้าจอการตั้งค่าเวิร์กโฟลว์ ให้คลิกปุ่มเครื่องหมายบวก ("+") ในโฟลว์เพื่อเพิ่มโหนด "การคำนวณ" ครับ/ค่ะ: -![Calculation Node_Add](https://static-docs.nocobase.com/58a445540d26945251cd143eb4b16579.png) +![Calculation Node_Add](https://static-docs.nocobase.com/58a455540d26945251cd143eb4b16579.png) ## การตั้งค่าโหนด diff --git a/docs/docs/th/workflow/nodes/destroy.md b/docs/docs/th/workflow/nodes/destroy.md index 99aa6cdc440..722506fa4df 100644 --- a/docs/docs/th/workflow/nodes/destroy.md +++ b/docs/docs/th/workflow/nodes/destroy.md @@ -17,7 +17,7 @@ ในหน้าจอการตั้งค่าเวิร์กโฟลว์ ให้คลิกปุ่มเครื่องหมายบวก (“+”) ในโฟลว์ เพื่อเพิ่มโหนด “ลบข้อมูล” ครับ/ค่ะ -![สร้างโหนดลบข้อมูล](https://static-docs.nocobase.com/e1c6b8728251fcdbed6c7f50e5570da2.png) +![สร้างโหนดลบข้อมูล](https://static-docs.nocobase.com/e1d6b8728251fcdbed6c7f50e5570da2.png) ## การตั้งค่าโหนด diff --git a/docs/docs/th/workflow/nodes/manual.md b/docs/docs/th/workflow/nodes/manual.md index af86b561043..d1a89aa088d 100644 --- a/docs/docs/th/workflow/nodes/manual.md +++ b/docs/docs/th/workflow/nodes/manual.md @@ -59,7 +59,7 @@ pkg: '@nocobase/plugin-workflow-manual' บล็อกข้อมูลโหนดก็คล้ายกันครับ/ค่ะ คุณสามารถเลือกผลลัพธ์ข้อมูลจากโหนดต้นทางเพื่อแสดงเป็นรายละเอียดได้ ตัวอย่างเช่น ผลลัพธ์จากโหนดคำนวณต้นทางสามารถใช้เป็นข้อมูลอ้างอิงบริบทสำหรับงานที่ต้องทำของผู้รับผิดชอบได้ครับ/ค่ะ -![โหนดการทำงานด้วยตนเอง_การตั้งค่าโหนด_การตั้งค่าส่วนติดต่อ_บล็อกข้อมูล_ข้อมูลโหนด](https://static-docs.nocobase.com/a538e26e58a1a4f45db310a72c2d0a404c.png) +![โหนดการทำงานด้วยตนเอง_การตั้งค่าโหนด_การตั้งค่าส่วนติดต่อ_บล็อกข้อมูล_ข้อมูลโหนด](https://static-docs.nocobase.com/a583e26e508e954b47e5ddff80d998c4.png) :::info{title=ข้อแนะนำ} เนื่องจากขณะตั้งค่าส่วนติดต่อผู้ใช้ เวิร์กโฟลว์ยังไม่ได้อยู่ในสถานะที่ทำงานอยู่ ดังนั้นจึงไม่มีข้อมูลเฉพาะเจาะจงแสดงในบล็อกข้อมูลครับ/ค่ะ ข้อมูลที่เกี่ยวข้องกับกระบวนการเฉพาะจะปรากฏให้เห็นในหน้าต่างป๊อปอัปงานที่ต้องทำก็ต่อเมื่อ เวิร์กโฟลว์ ถูกทริกเกอร์และทำงานแล้วเท่านั้นครับ/ค่ะ @@ -103,11 +103,11 @@ pkg: '@nocobase/plugin-workflow-manual' คุณสามารถเลือก "งานที่ต้องทำของ เวิร์กโฟลว์" จากบล็อกในหน้า เพื่อเพิ่มบล็อกรายการงานที่ต้องทำได้ครับ/ค่ะ -![โหนดการทำงานด้วยตนเอง_เพิ่มบล็อกงานที่ต้องทำ](https://static-docs.nocobase.com/198b41754cd73b704267bf30fe5e647.png) +![โหนดการทำงานด้วยตนเอง_เพิ่มบล็อกงานที่ต้องทำ](https://static-docs.nocobase.com/198b417454cd73b704267bf30fe5e647.png) ตัวอย่างบล็อกรายการงานที่ต้องทำ: -![โหนดการทำงานด้วยตนเอง_รายการงานที่ต้องทำ](https://static-docs.nocobase.com/cfefb0534.png) +![โหนดการทำงานด้วยตนเอง_รายการงานที่ต้องทำ](https://static-docs.nocobase.com/cfefb0d2c6a91c5c9dfa550d6b220f34.png) ### รายละเอียดงานที่ต้องทำ diff --git a/docs/docs/th/workflow/nodes/parallel.md b/docs/docs/th/workflow/nodes/parallel.md index 11427011783..c6fceb48fc2 100644 --- a/docs/docs/th/workflow/nodes/parallel.md +++ b/docs/docs/th/workflow/nodes/parallel.md @@ -21,7 +21,7 @@ pkg: '@nocobase/plugin-workflow-parallel' หลังจากเพิ่มโหนดแขนงคู่ขนานในเวิร์กโฟลว์แล้ว ระบบจะเพิ่มแขนงย่อยสองแขนงให้โดยอัตโนมัติครับ/ค่ะ คุณสามารถคลิกปุ่มเพิ่มแขนงเพื่อเพิ่มแขนงได้อีกหลายแขนงตามต้องการ แต่ละแขนงสามารถเพิ่มโหนดได้ไม่จำกัดจำนวน ส่วนแขนงที่ไม่ต้องการ สามารถลบออกได้โดยคลิกปุ่มลบที่จุดเริ่มต้นของแขนงนั้นๆ ครับ/ค่ะ -![จัดการแขนงคู่ขนาน](https://static-docs.nocobase.com/36088a8b771eb3ee9bc2a757.png) +![จัดการแขนงคู่ขนาน](https://static-docs.nocobase.com/36088a8b7970c8a1771eb3ee9bc2a757.png) ## การตั้งค่าโหนด diff --git a/docs/docs/th/workflow/nodes/variable.md b/docs/docs/th/workflow/nodes/variable.md index c38f2740c59..cec73784e41 100644 --- a/docs/docs/th/workflow/nodes/variable.md +++ b/docs/docs/th/workflow/nodes/variable.md @@ -15,7 +15,7 @@ pkg: '@nocobase/plugin-workflow-variable' ในหน้าจอการตั้งค่าเวิร์กโฟลว์ ให้คลิกปุ่มเครื่องหมายบวก ("+") ในเวิร์กโฟลว์ เพื่อเพิ่มโหนด "ตัวแปร" ครับ/ค่ะ -![เพิ่มโหนดตัวแปร](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![เพิ่มโหนดตัวแปร](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## การตั้งค่าโหนด diff --git a/docs/docs/th/workflow/triggers/collection.md b/docs/docs/th/workflow/triggers/collection.md index 5bea658b127..71f5adcd44a 100644 --- a/docs/docs/th/workflow/triggers/collection.md +++ b/docs/docs/th/workflow/triggers/collection.md @@ -90,4 +90,4 @@ เปิดใช้งานเวิร์กโฟลว์นี้ และทดสอบโดยการสร้างคำสั่งซื้อใหม่ผ่านอินเทอร์เฟซครับ/ค่ะ หลังจากสั่งซื้อ "iPhone 14 Pro" สต็อกสินค้าที่เกี่ยวข้องจะถูกหักเหลือ 9 แต่หากสั่งซื้อ "iPhone 13 Pro" คำสั่งซื้อจะถูกลบเนื่องจากสต็อกไม่เพียงพอครับ/ค่ะ -![เหตุการณ์คอลเลกชัน_ตัวอย่าง_ผลลัพธ์การทำงานของคำสั่งซื้อใหม่](https://static-docs.nocobase.com/24cbe31e24ba4804b3bd48d99415c54f.png) \ No newline at end of file +![เหตุการณ์คอลเลกชัน_ตัวอย่าง_ผลลัพธ์การทำงานของคำสั่งซื้อใหม่](https://static-docs.nocobase.com/24cbe51e24ba4804b3bd48d99415c54f.png) \ No newline at end of file diff --git a/docs/docs/th/workflow/triggers/post-action.md b/docs/docs/th/workflow/triggers/post-action.md index 479840b4e99..587b8f86292 100644 --- a/docs/docs/th/workflow/triggers/post-action.md +++ b/docs/docs/th/workflow/triggers/post-action.md @@ -177,7 +177,7 @@ curl -X POST -H 'Authorization: Bearer ' -H 'X-Role: ' -d ดังที่แสดงในภาพด้านล่างครับ/ค่ะ: -![ลำดับการดำเนินการ](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![ลำดับการดำเนินการ](https://static-docs.nocobase.com/20251219234806.png) ### ความแตกต่างจากเหตุการณ์ คอลเลกชัน diff --git a/docs/docs/th/workflow/triggers/pre-action.md b/docs/docs/th/workflow/triggers/pre-action.md index eed093bd38b..24b54c28e69 100644 --- a/docs/docs/th/workflow/triggers/pre-action.md +++ b/docs/docs/th/workflow/triggers/pre-action.md @@ -27,7 +27,7 @@ pkg: '@nocobase/plugin-workflow-request-interceptor' สิ่งแรกที่ต้องกำหนดค่าในทริกเกอร์ของเวิร์กโฟลว์การดักจับ คือ คอลเลกชันที่เกี่ยวข้องกับการดำเนินการนั้น ๆ ครับ/ค่ะ -![การกำหนดค่าเหตุการณ์ดักจับ_คอลเลกชัน](https://static-docs.nocobase.com/8f7122caca8159d334cf776f7838d53d6.png) +![การกำหนดค่าเหตุการณ์ดักจับ_คอลเลกชัน](https://static-docs.nocobase.com/8f7122caca8159d334cf776f838d53d6.png) จากนั้นให้เลือกโหมดการดักจับครับ/ค่ะ คุณสามารถเลือกที่จะดักจับเฉพาะปุ่มดำเนินการที่ผูกกับเวิร์กโฟลว์นี้เท่านั้น หรือจะเลือกดักจับการดำเนินการที่เลือกทั้งหมดสำหรับคอลเลกชันนี้ก็ได้ (โดยไม่คำนึงว่าจะมาจากฟอร์มใด และไม่จำเป็นต้องผูกกับเวิร์กโฟลว์ที่เกี่ยวข้อง) @@ -90,7 +90,7 @@ pkg: '@nocobase/plugin-workflow-request-interceptor' หากในโหนด "สิ้นสุดเวิร์กโฟลว์" ถูกกำหนดค่าให้ออกด้วยสถานะ "สำเร็จ" และเมื่อทำงานมาถึงโหนด "สิ้นสุดเวิร์กโฟลว์" นี้ คำขอสำหรับการดำเนินการนั้นจะยังคงถูกดักจับไว้ครับ/ค่ะ แต่ข้อความตอบกลับที่ส่งคืนมาจะแสดงด้วยสถานะ "สำเร็จ" (แทนที่จะเป็น "ข้อผิดพลาด") -![ข้อความตอบกลับสถานะสำเร็จ](https://static-docs.nocobase.com/959bbf56067144759451294b18c790e.png) +![ข้อความตอบกลับสถานะสำเร็จ](https://static-docs.nocobase.com/9559bbf56067144759451294b18c790e.png) ## ตัวอย่าง diff --git a/docs/docs/tr/ai-employees/permission.md b/docs/docs/tr/ai-employees/permission.md index 2bb7675dd0e..ac5c81ce440 100644 --- a/docs/docs/tr/ai-employees/permission.md +++ b/docs/docs/tr/ai-employees/permission.md @@ -103,7 +103,7 @@ flowchart TD #### Örnek 2: SQL Execution (Gelişmiş Analiz Aracı) -![05viz-configuration-2025-11-03-00-17-13](https://static-docs.nocobase.com/20251022013942.png) +![05viz-configuration-2025-11-03-00-17-13](https://static-docs.nocobase.com/05viz-configuration-2025-11-03-00-17-13.png) CRM Demosunda, `SQL Execution` daha esnek ancak sıkı kontrol gerektiren bir araçtır: diff --git a/docs/docs/tr/auth-verification/auth-oidc/index.md b/docs/docs/tr/auth-verification/auth-oidc/index.md index b6a5a0348a5..2758a4d78f3 100644 --- a/docs/docs/tr/auth-verification/auth-oidc/index.md +++ b/docs/docs/tr/auth-verification/auth-oidc/index.md @@ -46,7 +46,7 @@ Ekle - OIDC ### Alan Eşleme -![](https://static-docs.nocobase.com/92d3c8f6f4082b50d9f475674cb5650.png) +![](https://static-docs.nocobase.com/92d63c8f6f4082b50d9f475674cb5650.png) | Konfigürasyon | Açıklama | | :------------------------------ | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/docs/docs/tr/data-sources/data-modeling/collection-fields/associations/o2m/index.md b/docs/docs/tr/data-sources/data-modeling/collection-fields/associations/o2m/index.md index f6e2c8431f6..e2e45501a33 100644 --- a/docs/docs/tr/data-sources/data-modeling/collection-fields/associations/o2m/index.md +++ b/docs/docs/tr/data-sources/data-modeling/collection-fields/associations/o2m/index.md @@ -13,7 +13,7 @@ ER Diyagramı: Alan Yapılandırması: -![alt text](https://static-docs.nocobase.com/a608ce44821172dad7e8ab760107ff4e.png) +![alt text](https://static-docs.nocobase.com/a608ce54821172dad7e8ab760107ff4e.png) ## Parametre Açıklamaları diff --git a/docs/docs/tr/data-sources/field-encryption/index.md b/docs/docs/tr/data-sources/field-encryption/index.md index db1de5982e3..0b25418973a 100644 --- a/docs/docs/tr/data-sources/field-encryption/index.md +++ b/docs/docs/tr/data-sources/field-encryption/index.md @@ -29,7 +29,7 @@ Eğer bir alt uygulama eklentiyi etkinleştirdiyse, anahtar varsayılan olarak ` Zarf Şifreleme yöntemini kullanır. -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### Anahtar Oluşturma Süreci 1. İlk kez şifreli bir alan oluşturulduğunda, sistem otomatik olarak 32 bitlik bir `uygulama anahtarı` oluşturur ve bunu Base64 kodlamasıyla varsayılan depolama dizinine kaydeder. diff --git a/docs/docs/tr/email-manager/advanced/batch-send.md b/docs/docs/tr/email-manager/advanced/batch-send.md index 0027844e077..bbd186c2bf5 100644 --- a/docs/docs/tr/email-manager/advanced/batch-send.md +++ b/docs/docs/tr/email-manager/advanced/batch-send.md @@ -10,27 +10,27 @@ Bu belge AI tarafından çevrilmiştir. Herhangi bir yanlışlık için lütfen ## Toplu Gönderime Genel Bakış Birden fazla kişiye toplu e-posta gönderebilirsiniz (her alıcı ayrı bir e-posta alacaktır). -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## Tablo Üzerinden Toplu Gönderim E-postaları bir tablo üzerinden de toplu olarak gönderebilirsiniz: 1. Tabloya bir e-posta gönderme düğmesi ekleyin. - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. Tablodaki e-posta alanını yapılandırın (tablo satırlarını seçtikten sonra e-posta adreslerini ayrıştırmak için kullanılır). - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. E-posta göndermek için tablo verilerini işaretleyin. - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) Eğer tablodaki tüm adreslere e-posta göndermeniz gerekiyorsa, **Varsayılan olarak mevcut tablodaki tüm kayıtları alıcı olarak seç** özelliğini etkinleştirebilirsiniz: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) E-posta içeriğini düzenledikten sonra, göndermek için toplu gönder düğmesine tıklayın: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## E-posta Gönderim Takibi E-posta Yönetim Merkezi'nde belirli e-posta gönderim durumunu görüntüleyebilir ve takip edebilirsiniz: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/tr/email-manager/usage/signature.md b/docs/docs/tr/email-manager/usage/signature.md index 56006cd7df6..e09c82f013e 100644 --- a/docs/docs/tr/email-manager/usage/signature.md +++ b/docs/docs/tr/email-manager/usage/signature.md @@ -13,15 +13,15 @@ Bu belge AI tarafından çevrilmiştir. Herhangi bir yanlışlık için lütfen ## İmza Yapılandırması E-posta Yönetim Merkezi'ne gidin ve ayarlar düğmesine tıklayın: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) İmza paneline geçin: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) Burada imzaları yönetebilirsiniz. Bir imzanın önündeki seçeneği işaretleyerek onu varsayılan imza olarak ayarlayabilirsiniz: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## İmza Kullanımı E-posta gövdesindeki metin kutusunda, istediğiniz imzayı seçmek için imza simgesine tıklayın: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/tr/email-manager/usage/template.md b/docs/docs/tr/email-manager/usage/template.md index 5983f6e054e..e85c797598f 100644 --- a/docs/docs/tr/email-manager/usage/template.md +++ b/docs/docs/tr/email-manager/usage/template.md @@ -10,15 +10,15 @@ Bu belge AI tarafından çevrilmiştir. Herhangi bir yanlışlık için lütfen ## Şablon Yapılandırması E-posta Yönetim Merkezi'ne gidin ve ayarlar düğmesine tıklayın: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Şablonlar paneline geçin: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) Şablonları buradan yönetebilirsiniz: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## Şablon Kullanımı E-posta gövde kutusunda, istediğiniz şablonu seçmek için şablon simgesine tıklayın: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/tr/flow-engine/learning-roadmap.md b/docs/docs/tr/flow-engine/learning-roadmap.md index 75120d68ed3..0e220fdd655 100644 --- a/docs/docs/tr/flow-engine/learning-roadmap.md +++ b/docs/docs/tr/flow-engine/learning-roadmap.md @@ -5,4 +5,4 @@ Bu belge AI tarafından çevrilmiştir. Herhangi bir yanlışlık için lütfen # Öğrenme Yol Haritası -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/tr/solution/ticket-system/design.md b/docs/docs/tr/solution/ticket-system/design.md index b52ce22a2a3..6041b5c8768 100755 --- a/docs/docs/tr/solution/ticket-system/design.md +++ b/docs/docs/tr/solution/ticket-system/design.md @@ -31,7 +31,7 @@ Müşteri hizmetlerinin sıkıcı süreç operasyonlarına değil, sorunları ç - **Yatay (Ana Tablo)**: Tüm iş türlerini kapsayan evrensel yetenekler — numara, durum, atanan kişi, SLA gibi temel alanlar. - **Dikey (Genişletme Tabloları)**: Belirli iş kollarına özgü uzmanlık alanları — cihaz onarımı için seri numaraları, şikayetler için tazminat planları. -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **Neden Bu Tasarım?** @@ -61,7 +61,7 @@ Sadece "AI özellikleri" değil, "AI çalışanları". Her AI'nın net bir rolü #### Felsefe 3: Bilgi Öz-Döngüsü -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) Bu, bir **Bilgi Birikimi - Bilgi Uygulaması** kapalı döngüsü oluşturur. @@ -71,7 +71,7 @@ Bu, bir **Bilgi Birikimi - Bilgi Uygulaması** kapalı döngüsü oluşturur. ### 2.1 Varlık İlişkilerine Genel Bakış -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 Temel Tablo Detayları @@ -296,18 +296,18 @@ Sistemin çekirdeğidir; sık kullanılan tüm alanları ana tabloda toplayan "g **Ana Akış (Soldan Sağa)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **Yan Akışlar** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **Tam Durum Makinesi** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 Kritik Durum Geçiş Kuralları @@ -337,7 +337,7 @@ Sistemin çekirdeğidir; sık kullanılan tüm alanları ana tabloda toplayan "g ### 4.2 SLA Hesaplama Mantığı -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### Talep Oluşturulduğunda @@ -466,7 +466,7 @@ Her AI çalışanı 4 spesifik görevle yapılandırılmıştır: ### 5.3 AI Çalışanları ve Talep Yaşam Döngüsü -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 AI Yanıt Örnekleri @@ -528,12 +528,12 @@ Grace tarafından yürütülen yanıt kalitesi denetimi şu sorunları engeller: ### 6.1 Bilgi Kaynakları -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 Talepten Bilgiye Dönüşüm Akışı -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **Değerlendirme Boyutları**: - **Genellik**: Bu yaygın bir sorun mu? @@ -578,19 +578,19 @@ Bir temsilci talep detaylarını açtığında, Max otomatik olarak ilgili bilgi #### WF-T01: Talep Oluşturma Akışı -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: Talep AI Analizi -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: Yorum Çevirisi ve Denetimi -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: Bilgi Oluşturma -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 Zamanlanmış Görevler @@ -607,11 +607,11 @@ Bir temsilci talep detaylarını açtığında, Max otomatik olarak ilgili bilgi ### 8.1 Yönetim Paneli -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 Müşteri Portalı -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 Gösterge Paneli Tasarımı diff --git a/docs/docs/tr/users-permissions/acl/role.md b/docs/docs/tr/users-permissions/acl/role.md index 15d52a70c90..92fa69474ec 100644 --- a/docs/docs/tr/users-permissions/acl/role.md +++ b/docs/docs/tr/users-permissions/acl/role.md @@ -25,7 +25,7 @@ Rol tanımlayıcısı (sisteme özgü benzersiz bir tanımlayıcı), varsayılan Buradaki varsayılan rol, yeni oluşturulan kullanıcılara belirli bir rol atanmadığında otomatik olarak verilen roldür. -![](https://static-docs.nocobase.com/f41bba7ff55ca28717c486dc45bc1708.png) +![](https://static-docs.nocobase.com/f41bba7ff55ca28715c486dc45bc1708.png) ## Kişisel Merkez diff --git a/docs/docs/tr/users-permissions/departments/index.md b/docs/docs/tr/users-permissions/departments/index.md index 009afeeda98..8515a785602 100644 --- a/docs/docs/tr/users-permissions/departments/index.md +++ b/docs/docs/tr/users-permissions/departments/index.md @@ -33,7 +33,7 @@ Bu belge AI tarafından çevrilmiştir. Herhangi bir yanlışlık için lütfen Bölüm düzenleme formunda üst bölüm alanını değiştirebilirsiniz. Ancak, mevcut bölüm ve bu bölümün altındaki bölümler seçilemez. -![](https://static-docs.nocobase.com/9d80dd1e4f32c77186566ed8ada70128.png) +![](https://static-docs.nocobase.com/9d80ddf42f32c77186566ed8ada70128.png) ## Bölüm Üyeleri Yönetimi diff --git a/docs/docs/tr/users-permissions/departments/role.md b/docs/docs/tr/users-permissions/departments/role.md index de390c34f8a..cc1563a6b8e 100644 --- a/docs/docs/tr/users-permissions/departments/role.md +++ b/docs/docs/tr/users-permissions/departments/role.md @@ -20,7 +20,7 @@ Departmanlara rol atamanın iki yolu vardır. İkinci yöntem ise rol yönetimi içinde, ilgili rollere departman eklemektir. -![](https://static-docs.nocobase.com/70f77bb89aa1fb415c152a51a51cc23b.png) +![](https://static-docs.nocobase.com/f2a7bec937cf2f179ce868a92b98416d.png) Bu role zaten sahip olan departmanlar seçilemez. diff --git a/docs/docs/tr/workflow/advanced/revisions.md b/docs/docs/tr/workflow/advanced/revisions.md index 8fb4495aa54..e7cda716ff0 100644 --- a/docs/docs/tr/workflow/advanced/revisions.md +++ b/docs/docs/tr/workflow/advanced/revisions.md @@ -9,7 +9,7 @@ Yapılandırılmış bir iş akışı en az bir kez tetiklendikten sonra, eğer İş akışı yapılandırma sayfasında, sağ üst köşedeki sürüm menüsünden mevcut iş akışı sürümlerini görüntüleyebilirsiniz: -![İş akışı sürümlerini görüntüle](https://static-docs.nocobase.com/ad93d2b08166b0e3e643fb148713a63f.png) +![İş akışı sürümlerini görüntüle](https://static-docs.nocobase.com/ad93d2c08166b0e3e643fb148713a63f.png) Sağındaki daha fazla işlem (“...”) menüsünde, o an görüntülediğiniz sürümü yeni bir sürüme kopyalama seçeneğini bulabilirsiniz: diff --git a/docs/docs/tr/workflow/nodes/aggregate.md b/docs/docs/tr/workflow/nodes/aggregate.md index 4a56059690c..db42eb39832 100644 --- a/docs/docs/tr/workflow/nodes/aggregate.md +++ b/docs/docs/tr/workflow/nodes/aggregate.md @@ -63,7 +63,7 @@ Ardından, bir koleksiyon olayı tarafından tetiklenen bir iş akışı oluştu Daha sonra bir agrega sorgusu düğümü ekleyin ve aşağıdaki gibi yapılandırın: -![Agrega Sorgusu Düğümü_Örnek_Düğüm Yapılandırması](https://static-docs.nocobase.com/542272e6373d1b37ddda78.png) +![Agrega Sorgusu Düğümü_Örnek_Düğüm Yapılandırması](https://static-docs.nocobase.com/542272e638c6c0a567373d1b37ddda78.png) Bu şekilde, iş akışı tetiklendikten sonra, agrega sorgusu düğümü, yeni eklenen makalenin kategorisindeki tüm makalelerin sayısını sayacak ve bunu düğümün sonucu olarak kaydedecektir. diff --git a/docs/docs/tr/workflow/nodes/destroy.md b/docs/docs/tr/workflow/nodes/destroy.md index 059c497e9db..f8fe55a9462 100644 --- a/docs/docs/tr/workflow/nodes/destroy.md +++ b/docs/docs/tr/workflow/nodes/destroy.md @@ -21,7 +21,7 @@ Silme düğümünün temel kullanımı, güncelleme düğümüne benzer. Ancak s ## Düğüm Yapılandırması -![Silme düğümü_Düğüm yapılandırması](https://static-docs.nocobase.com/580600c2b3ef4e01dfa48b23539648e.png) +![Silme düğümü_Düğüm yapılandırması](https://static-docs.nocobase.com/580600c2b13ef4e01dfa48b23539648e.png) ### Koleksiyon diff --git a/docs/docs/tr/workflow/nodes/json-query.md b/docs/docs/tr/workflow/nodes/json-query.md index 015d422a8e5..2ee11ec3eb2 100644 --- a/docs/docs/tr/workflow/nodes/json-query.md +++ b/docs/docs/tr/workflow/nodes/json-query.md @@ -15,7 +15,7 @@ Farklı JSON hesaplama motorlarını kullanarak, yukarı akış düğümleri tar İş akışı yapılandırma arayüzünde, süreçteki artı ("+") düğmesine tıklayarak bir "JSON Hesaplama" düğümü ekleyebilirsiniz: -![Düğüm Oluşturma](https://static-docs.nocobase.com/7de76517539ad9dfc88b7160f1d0dd7.png) +![Düğüm Oluşturma](https://static-docs.nocobase.com/7de796517539ad9dfc88b7160f1d0dd7.png) :::info{title=İpucu} Genellikle, JSON Hesaplama düğümü, diğer veri düğümlerinin altına oluşturulur, böylece bu verileri ayrıştırabilirsiniz. diff --git a/docs/docs/tr/workflow/nodes/manual.md b/docs/docs/tr/workflow/nodes/manual.md index 6478f64c0f1..3797846de44 100644 --- a/docs/docs/tr/workflow/nodes/manual.md +++ b/docs/docs/tr/workflow/nodes/manual.md @@ -31,7 +31,7 @@ Manuel bir düğüm, yapılacaklar görevinin yürütücüsü olarak bir kullan Bir kullanıcı seçin veya bir değişken aracılığıyla bağlamdaki kullanıcı verilerinin birincil veya yabancı anahtarını seçin. -![人工节点_配置_负责人_选择变量](https://static-docs.nocobase.com/22fbca3b8e21fda319037001445.png) +![人工节点_配置_负责人_选择变量](https://static-docs.nocobase.com/22fbca3b8e21fda3a831019037001445.png) :::info{title=İpucu} Şu anda, manuel düğümler için sorumlu seçeneği birden fazla kullanıcıyı desteklememektedir. Bu özellik gelecekteki sürümlerde desteklenecektir. @@ -103,11 +103,11 @@ Manuel işlem için, yapılacaklar görevlerini görüntülemek üzere bir sayfa Bir sayfadaki bloklardan "İş Akışı Yapılacaklar" seçeneğini belirleyerek bir yapılacaklar listesi bloğu ekleyebilirsiniz: -![人工节点_添加待办区块](https://static-docs.nocobase.com/198b41754cd73b704267bf30fe5e647.png) +![人工节点_添加待办区块](https://static-docs.nocobase.com/198b417454cd73b704267bf30fe5e647.png) Yapılacaklar listesi bloğu örneği: -![人工节点_待办列表](https://static-docs.nocobase.com/cfefb06a91c5c9dfa550d6b220f34.png) +![人工节点_待办列表](https://static-docs.nocobase.com/cfefb0d2c6a91c5c9dfa550d6b220f34.png) ### Yapılacaklar Ayrıntıları diff --git a/docs/docs/tr/workflow/nodes/parallel.md b/docs/docs/tr/workflow/nodes/parallel.md index 0c79032d234..de12ae0fd2e 100644 --- a/docs/docs/tr/workflow/nodes/parallel.md +++ b/docs/docs/tr/workflow/nodes/parallel.md @@ -17,7 +17,7 @@ Yerleşik bir eklentidir, kurulum gerektirmez. İş akışı yapılandırma arayüzünde, akıştaki artı (“+”) düğmesine tıklayarak bir “Paralel Dallanma” düğümü ekleyin: -![Paralel Dallanma Ekle](https://static-docs.nocobase.com/9e0f3faa0b9335270647a3047759eac.png) +![Paralel Dallanma Ekle](https://static-docs.nocobase.com/9e0f3faa0b9335270647a30477559eac.png) İş akışına bir paralel dallanma düğümü ekledikten sonra, varsayılan olarak iki alt dal eklenir. Ayrıca, dal ekle düğmesine tıklayarak istediğiniz sayıda dal ekleyebilirsiniz. Her dala istediğiniz sayıda düğüm ekleyebilirsiniz. Gereksiz dalları, dalın başlangıcındaki sil düğmesine tıklayarak kaldırabilirsiniz. diff --git a/docs/docs/tr/workflow/nodes/response-message.md b/docs/docs/tr/workflow/nodes/response-message.md index 5f57ee52232..5559bbe41b5 100644 --- a/docs/docs/tr/workflow/nodes/response-message.md +++ b/docs/docs/tr/workflow/nodes/response-message.md @@ -35,7 +35,7 @@ Mesaj içeriği, içine değişkenlerin eklenebildiği bir şablon dizesidir. Bu "iPhone 14 pro" ürününün stoğu yetersiz. ``` -![Mesaj içeriği](https://static-docs.nocobase.com/06fd4a6b6ec499c853f0c39987f63a6a.png) +![Mesaj içeriği](https://static-docs.nocobase.com/06bd4a6b6ec499c853f0c39987f63a6a.png) ## İş Akışı Yapılandırması diff --git a/docs/docs/tr/workflow/nodes/update.md b/docs/docs/tr/workflow/nodes/update.md index 46eff36b846..06ee9743592 100644 --- a/docs/docs/tr/workflow/nodes/update.md +++ b/docs/docs/tr/workflow/nodes/update.md @@ -17,7 +17,7 @@ Belirli koşulları karşılayan bir `koleksiyon`daki verileri güncellemek içi ## Düğüm Yapılandırması -![Veri Güncelle Düğümü Yapılandırması](https://static-docs.nocobase.com/98e0f41c57275fc835f08260d0b2e86.png) +![Veri Güncelle Düğümü Yapılandırması](https://static-docs.nocobase.com/98e0f941c57275fc835f08260d0b2e86.png) ### Koleksiyon @@ -46,6 +46,6 @@ Not: Bir `iş akışı`ndaki "Veri Güncelle" düğümü tarafından güncellene Örneğin, yeni bir "Makale" oluşturulduğunda, "Makale Kategorisi" `koleksiyon`undaki "Makale Sayısı" alanını otomatik olarak güncellemeniz gerekebilir. Bu, "Veri Güncelle" düğümü kullanılarak gerçekleştirilebilir: -![Veri Güncelle Düğümü Örnek Yapılandırması](https://static-docs.nocobase.com/98e0f41c57275fc835f08260d0b2e86.png) +![Veri Güncelle Düğümü Örnek Yapılandırması](https://static-docs.nocobase.com/98e0f941c57275fc835f08260d0b2e86.png) `iş akışı` tetiklendiğinde, "Makale Kategorisi" `koleksiyon`unun "Makale Sayısı" alanı otomatik olarak mevcut makale sayısı + 1 olarak güncellenecektir. \ No newline at end of file diff --git a/docs/docs/tr/workflow/nodes/variable.md b/docs/docs/tr/workflow/nodes/variable.md index c6910130e9a..fd001c2ca00 100644 --- a/docs/docs/tr/workflow/nodes/variable.md +++ b/docs/docs/tr/workflow/nodes/variable.md @@ -15,7 +15,7 @@ Bir iş akışında değişkenler tanımlayabilir veya tanımlanmış değişken iş akışı yapılandırma arayüzünde, iş akışındaki artı ('+') düğmesine tıklayarak bir "Değişken" düğümü ekleyebilirsiniz: -![Değişken Düğümü Ekle](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![Değişken Düğümü Ekle](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## Düğümü Yapılandırma @@ -32,7 +32,7 @@ Oluşturulan düğüm, iş akışındaki ilk değişken düğümü olduğunda, y Tanımlanmış bir değişkene değer atamayı seçtiğinizde, hedef değişkeni, yani değişkenin tanımlandığı düğümü de seçmeniz gerekir: -![Değer Atanacak Değişkeni Seçin](https://static-docs.nocobase.com/1ce891154d87347e693d8cc8ac1953eb.png) +![Değer Atanacak Değişkeni Seçin](https://static-docs.nocobase.com/1ce8911548d7347e693d8cc8ac1953eb.png) ### Değer diff --git a/docs/docs/tr/workflow/triggers/collection.md b/docs/docs/tr/workflow/triggers/collection.md index 95939ae9a28..25a5edbc9b8 100644 --- a/docs/docs/tr/workflow/triggers/collection.md +++ b/docs/docs/tr/workflow/triggers/collection.md @@ -90,4 +90,4 @@ Düğümlerin yapılandırması, belirli düğüm türleri için hazırlanan bel Bu iş akışını etkinleştirin ve arayüz üzerinden yeni bir sipariş oluşturarak test edin. "iPhone 14 Pro" için sipariş verdikten sonra, ilgili ürünün stoğu 9'a düşecektir. Eğer "iPhone 13 Pro" için sipariş verilirse, stok yetersizliği nedeniyle sipariş silinecektir. -![Koleksiyon Olayı_Örnek_Yeni Sipariş Yürütme Sonucu](https://static-docs.nocobase.com/24cbe31e24ba4804b3bd48d99415c54f.png) \ No newline at end of file +![Koleksiyon Olayı_Örnek_Yeni Sipariş Yürütme Sonucu](https://static-docs.nocobase.com/24cbe51e24ba4804b3bd48d99415c54f.png) \ No newline at end of file diff --git a/docs/docs/tr/workflow/triggers/post-action.md b/docs/docs/tr/workflow/triggers/post-action.md index cf43253c435..f62e79bb049 100644 --- a/docs/docs/tr/workflow/triggers/post-action.md +++ b/docs/docs/tr/workflow/triggers/post-action.md @@ -39,7 +39,7 @@ Kullanıcı işlemi sonrasında hemen yürütülmesi ve sonuç döndürmesi gere İş akışı tuvaline girin, yapılandırma açılır penceresini açmak için tetikleyiciye tıklayın ve öncelikle bağlanacak koleksiyonu seçmeniz gerekir: -![工作流配置_选择数据表](https://static-docs.nocobase.com/35c49a71eba731127edcf76719c97634.png) +![工作流配置_选择数据表](https://static-docs.nocobase.com/35c49a91eba731127edcf76719c97634.png) ### Tetikleme Modunu Seçme @@ -177,7 +177,7 @@ Eğer olay global modda yapılandırılmışsa, ilgili iş akışını belirtmek Aşağıdaki şekilde gösterildiği gibi: -![操作执行顺序](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![操作执行顺序](https://static-docs.nocobase.com/20251219234806.png) ### Koleksiyon Olayından Farkı diff --git a/docs/docs/uk/auth-verification/api-keys/index.md b/docs/docs/uk/auth-verification/api-keys/index.md index 7f043cea391..3b1ba246136 100644 --- a/docs/docs/uk/auth-verification/api-keys/index.md +++ b/docs/docs/uk/auth-verification/api-keys/index.md @@ -17,7 +17,7 @@ http://localhost:13000/admin/settings/api-keys/configuration ### Додати API-ключ -![](https://static-docs.nocobase.com/461872fc0ad9a96fa5b14e97fcba12.png) +![](https://static-docs.nocobase.com/46141872fc0ad9a96fa5b14e97fcba12.png) **Примітка** diff --git a/docs/docs/uk/data-sources/data-modeling/collection-fields/associations/o2o/index.md b/docs/docs/uk/data-sources/data-modeling/collection-fields/associations/o2o/index.md index a96195c7739..59c9d05e4f2 100644 --- a/docs/docs/uk/data-sources/data-modeling/collection-fields/associations/o2o/index.md +++ b/docs/docs/uk/data-sources/data-modeling/collection-fields/associations/o2o/index.md @@ -21,7 +21,7 @@ ER Зв'язок Конфігурація поля -![alt text](https://static-docs.nocobase.com/7659e128936bbd7c9ff51bcff1d646dd.png) +![alt text](https://static-docs.nocobase.com/7665a87e094b4fb50c9426a108f87105.png) ## Один-до-одного (Належить) diff --git a/docs/docs/uk/data-sources/field-encryption/index.md b/docs/docs/uk/data-sources/field-encryption/index.md index faaa666d8cb..da6a16c23ef 100644 --- a/docs/docs/uk/data-sources/field-encryption/index.md +++ b/docs/docs/uk/data-sources/field-encryption/index.md @@ -29,7 +29,7 @@ pkg: "@nocobase/plugin-field-encryption" Використовується шифрування конвертів. -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### Процес створення ключа 1. При першому створенні зашифрованого поля система автоматично генерує 32-бітний `ключ застосунку`, який зберігається в каталозі зберігання за замовчуванням у кодуванні Base64. diff --git a/docs/docs/uk/data-visualization/guide/chart-options.md b/docs/docs/uk/data-visualization/guide/chart-options.md index 8ab27333dcc..96ebc6edb84 100644 --- a/docs/docs/uk/data-visualization/guide/chart-options.md +++ b/docs/docs/uk/data-visualization/guide/chart-options.md @@ -90,7 +90,7 @@ return { - У режимі Custom після редагування можна натиснути кнопку «Попередній перегляд» праворуч, щоб оновити попередній перегляд діаграми. - Внизу натисніть «Зберегти», щоб застосувати та зберегти налаштування; натисніть «Скасувати», щоб відхилити всі зміни, внесені цього разу. -![20251026192816](https://static-docs.nocobase.com/clipboard-image-1761473695.png) +![20251026192816](https://static-docs.nocobase.com/20251026192816.png) > [!TIP] > Щоб дізнатися більше про опції діаграм, дивіться розділ Розширене використання — Налаштування діаграм. \ No newline at end of file diff --git a/docs/docs/uk/email-manager/advanced/batch-send.md b/docs/docs/uk/email-manager/advanced/batch-send.md index 54446a3a80c..7cfd296b2ab 100644 --- a/docs/docs/uk/email-manager/advanced/batch-send.md +++ b/docs/docs/uk/email-manager/advanced/batch-send.md @@ -9,27 +9,27 @@ pkg: "@nocobase/plugin-email-manager" ## Огляд масової розсилки Ви можете надсилати електронні листи багатьом людям одночасно (кожен отримувач отримає окремий лист). -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## Масова розсилка через таблицю Ви також можете надсилати електронні листи масово за допомогою таблиці: 1. Додайте кнопку надсилання електронного листа до таблиці - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. Налаштуйте поле електронної пошти в таблиці (використовується для аналізу адрес електронної пошти після вибору рядків таблиці) - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. Виберіть дані таблиці для надсилання електронних листів - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) Якщо вам потрібно надіслати листи на всі адреси в усій таблиці, ви можете увімкнути функцію **За замовчуванням вибрати всі записи в поточній таблиці як отримувачів**: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) Після редагування вмісту електронного листа натисніть кнопку масової розсилки, щоб надіслати його: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## Відстеження надсилання електронних листів Ви можете переглядати та відстежувати статус надсилання конкретних електронних листів у Центрі керування електронною поштою: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/uk/email-manager/usage/signature.md b/docs/docs/uk/email-manager/usage/signature.md index c719c426429..9ad42538a2a 100644 --- a/docs/docs/uk/email-manager/usage/signature.md +++ b/docs/docs/uk/email-manager/usage/signature.md @@ -10,15 +10,15 @@ pkg: "@nocobase/plugin-email-manager" ## Налаштування підпису Перейдіть до Центру керування електронною поштою та натисніть кнопку налаштувань: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Перейдіть до панелі підписів: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) Тут ви можете керувати підписами. Поставте позначку біля підпису, щоб встановити його як стандартний: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## Використання підписів У полі для тексту листа натисніть на іконку підпису, щоб вибрати потрібний підпис: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/uk/email-manager/usage/template.md b/docs/docs/uk/email-manager/usage/template.md index 41ccdfa0348..8d37c7374d4 100644 --- a/docs/docs/uk/email-manager/usage/template.md +++ b/docs/docs/uk/email-manager/usage/template.md @@ -10,15 +10,15 @@ pkg: "@nocobase/plugin-email-manager" ## Налаштування шаблонів Перейдіть до Центру керування електронною поштою та натисніть кнопку налаштувань: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Перейдіть на панель шаблонів: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) Тут можна керувати шаблонами: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## Використання шаблонів У полі для тексту електронного листа натисніть на іконку шаблону, щоб вибрати потрібний шаблон: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/uk/integration/sso/index.md b/docs/docs/uk/integration/sso/index.md index e3e9874720d..644930dcb80 100644 --- a/docs/docs/uk/integration/sso/index.md +++ b/docs/docs/uk/integration/sso/index.md @@ -93,7 +93,7 @@ NocoBase підтримує наступні протоколи та метод 1. Вийдіть з поточної сесії. 2. На сторінці входу виберіть налаштований метод SSO. -![](https://static-docs.nocobase.com/74963865c936a2949486adeb5b24bc.png) +![](https://static-docs.nocobase.com/74963865c9d36a294948e6adeb5b24bc.png) 3. Завершіть процес автентифікації постачальника ідентифікації. 4. Перевірте, чи вдалося успішно увійти в NocoBase. diff --git a/docs/docs/uk/solution/ticket-system/design.md b/docs/docs/uk/solution/ticket-system/design.md index 9c82c7faa87..799a1595f1d 100755 --- a/docs/docs/uk/solution/ticket-system/design.md +++ b/docs/docs/uk/solution/ticket-system/design.md @@ -31,7 +31,7 @@ - **Горизонтальна (головна таблиця)**: охоплює загальні можливості для всіх типів бізнесу — номер, статус, виконавець, SLA та інші основні поля. - **Вертикальна (таблиці розширень)**: спеціалізовані поля для конкретних видів діяльності — ремонт обладнання має серійні номери, скарги мають плани компенсації. -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **Чому обрано такий дизайн?** @@ -61,7 +61,7 @@ #### Концепція третя: Самоциркуляція знань -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) Це формує замкнений цикл **Накопичення знань — Застосування знань**. @@ -71,7 +71,7 @@ ### 2.1 Огляд зв'язків між сутностями -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 Детальний опис основних таблиць @@ -296,18 +296,18 @@ **Основний процес (зліва направо)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **Допоміжні процеси** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **Повна машина станів** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 Ключові правила зміни статусів @@ -337,7 +337,7 @@ ### 4.2 Логіка розрахунку SLA -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### При створенні тікета @@ -466,7 +466,7 @@ ### 5.3 ШІ-співробітники та життєвий цикл тікета -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 Приклади відповідей ШІ @@ -526,12 +526,12 @@ ### 6.1 Джерела знань -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 Процес перетворення тікета на знання -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **Критерії оцінки**: - **Універсальність**: Чи є це поширеною проблемою? @@ -578,19 +578,19 @@ #### WF-T01: Процес створення тікета -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: ШІ-аналіз тікета -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: Переклад та перевірка коментарів -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: Генерація знань -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 Завдання за розкладом @@ -607,11 +607,11 @@ ### 8.1 Панель адміністратора -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 Портал клієнта -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 Дизайн дашбордів diff --git a/docs/docs/uk/users-permissions/acl/ui.md b/docs/docs/uk/users-permissions/acl/ui.md index 42efd58013b..9ccabfb4445 100644 --- a/docs/docs/uk/users-permissions/acl/ui.md +++ b/docs/docs/uk/users-permissions/acl/ui.md @@ -49,7 +49,7 @@ pkg: '@nocobase/plugin-acl' Повний процес налаштування: - ![](https://static-docs.nocobase.com/1dbe559a92c052e194e50edc74a7.gif) + ![](https://static-docs.nocobase.com/1dbe559a9579c2e052e194e50edc74a7.gif) - **Додавання**: Визначає, чи можна додавати (створювати) поля. diff --git a/docs/docs/uk/users-permissions/departments/index.md b/docs/docs/uk/users-permissions/departments/index.md index 74b608d91fb..c824342802a 100644 --- a/docs/docs/uk/users-permissions/departments/index.md +++ b/docs/docs/uk/users-permissions/departments/index.md @@ -27,7 +27,7 @@ pkg: '@nocobase/plugin-departments' ![](https://static-docs.nocobase.com/a147319577e5cc36b5862c1e511f6722.png) -![](https://static-docs.nocobase.com/f206f866757cf30ac78aadf4f76bad32.png) +![](https://static-docs.nocobase.com/f206f866753cf30ac78aadf4f76bad32.png) ### Зміна вищого відділу diff --git a/docs/docs/uk/users-permissions/departments/role.md b/docs/docs/uk/users-permissions/departments/role.md index 00e0ae8f23f..7985719bfc9 100644 --- a/docs/docs/uk/users-permissions/departments/role.md +++ b/docs/docs/uk/users-permissions/departments/role.md @@ -17,7 +17,7 @@ pkg: '@nocobase/plugin-departments' Другий спосіб — це додати відділи до відповідної ролі в розділі керування ролями. -![](https://static-docs.nocobase.com/f2a77bb89aa1fb415c152a51a51cc23b.png) +![](https://static-docs.nocobase.com/f2a7bec937cf2f179ce868a92b98416d.png) Відділи, яким вже призначено цю роль, недоступні для вибору. diff --git a/docs/docs/uk/users-permissions/user.md b/docs/docs/uk/users-permissions/user.md index 7c0a177b1c7..4c479731afc 100644 --- a/docs/docs/uk/users-permissions/user.md +++ b/docs/docs/uk/users-permissions/user.md @@ -15,7 +15,7 @@ pkg: '@nocobase/plugin-users' Крім того, ви також можете додавати різні блоки з колекції Користувачі для керування користувачами, наприклад, табличні блоки: -![](https://static-docs.nocobase.com/76b59541a9e8f18a4568a7c9.png) +![](https://static-docs.nocobase.com/76b5a4652f869541a9e8f18a4568a7c9.png) ## Додати користувача diff --git a/docs/docs/uk/workflow/advanced/executions.md b/docs/docs/uk/workflow/advanced/executions.md index c4d3983744c..ce32b850665 100644 --- a/docs/docs/uk/workflow/advanced/executions.md +++ b/docs/docs/uk/workflow/advanced/executions.md @@ -25,7 +25,7 @@ У прикладі [Швидкий старт](../getting-started.md) ми вже знаємо, що перегляд деталей історії виконання робочого процесу дозволяє перевірити, чи всі вузли виконувалися нормально, а також стан виконання та дані результатів кожного виконаного вузла. У деяких складних робочих процесах і вузлах вузол може мати кілька результатів, наприклад, результат циклічного вузла: -![Node results from multiple executions](https://static-docs.nocobase.com/bbda259fa2ddf62b0fc0f928efbedae9.png) +![Node results from multiple executions](https://static-docs.nocobase.com/bbda259fa2ddf62b0fc0f982efbedae9.png) :::info{title=Підказка} Робочі процеси можуть запускатися одночасно, але виконуються вони послідовно в черзі. Навіть якщо кілька робочих процесів запускаються одночасно, вони будуть виконуватися один за одним, а не паралельно. Тому статус «У черзі» означає, що інші робочі процеси зараз виконуються, і потрібно зачекати. diff --git a/docs/docs/uk/workflow/nodes/calculation.md b/docs/docs/uk/workflow/nodes/calculation.md index 1db6b0c89d5..882e38af147 100644 --- a/docs/docs/uk/workflow/nodes/calculation.md +++ b/docs/docs/uk/workflow/nodes/calculation.md @@ -11,11 +11,11 @@ В інтерфейсі налаштування робочого процесу натисніть кнопку плюса («+»), щоб додати вузол «Обчислення»: -![Вузол обчислення_Додати](https://static-docs.nocobase.com/58a426945251cd143eb4b16579.png) +![Вузол обчислення_Додати](https://static-docs.nocobase.com/58a455540d26945251cd143eb4b16579.png) ## Налаштування вузла -![Вузол обчислення_Налаштування](https://static-docs.nocobase.com/6a155de3883d8cd1881b2d9c33874.png) +![Вузол обчислення_Налаштування](https://static-docs.nocobase.com/6a155de3f6a883d8cd1881b2d9c33874.png) ### Рушій обчислень diff --git a/docs/docs/uk/workflow/nodes/json-query.md b/docs/docs/uk/workflow/nodes/json-query.md index 98119a7eccc..3e9bb248042 100644 --- a/docs/docs/uk/workflow/nodes/json-query.md +++ b/docs/docs/uk/workflow/nodes/json-query.md @@ -15,7 +15,7 @@ pkg: '@nocobase/plugin-workflow-json-query' В інтерфейсі конфігурації робочого процесу натисніть кнопку плюса («+») у процесі, щоб додати вузол «Обчислення JSON»: -![Створення вузла](https://static-docs.nocobase.com/7de76517539ad9dfc88b7160f1d0dd7.png) +![Створення вузла](https://static-docs.nocobase.com/7de796517539ad9dfc88b7160f1d0dd7.png) :::info{title=Примітка} Зазвичай вузол «Обчислення JSON» створюється під іншими вузлами даних для їхнього аналізу. diff --git a/docs/docs/uk/workflow/nodes/loop.md b/docs/docs/uk/workflow/nodes/loop.md index 5ef63de847f..bed0873c656 100644 --- a/docs/docs/uk/workflow/nodes/loop.md +++ b/docs/docs/uk/workflow/nodes/loop.md @@ -108,7 +108,7 @@ pkg: '@nocobase/plugin-workflow-loop' ![Loop Node_Example_Calculation Node Configuration](https://static-docs.nocobase.com/8df3604c71f8f8705b1552d3ebfe3b50.png) - ![Loop Node_Example_Update Stock Node Configuration](https://static-docs.nocobase.com/2d84baa9b3b1bd85fccda9eec992378.png) + ![Loop Node_Example_Update Stock Node Configuration](https://static-docs.nocobase.com/2d84baa9b3b01bd85fccda9eec992378.png) 6. В іншому випадку, у гілці "Ні" створіть вузол "Оновити запис", щоб оновити статус деталі замовлення на "недійсний": diff --git a/docs/docs/uk/workflow/nodes/manual.md b/docs/docs/uk/workflow/nodes/manual.md index 492353417a3..ec23aa27523 100644 --- a/docs/docs/uk/workflow/nodes/manual.md +++ b/docs/docs/uk/workflow/nodes/manual.md @@ -31,7 +31,7 @@ pkg: '@nocobase/plugin-workflow-manual' Виберіть користувача або оберіть первинний чи зовнішній ключ даних користувача з контексту за допомогою змінної. -![Ручний вузол_Налаштування_Відповідальний_Вибір змінної](https://static-docs.nocobase.com/22fbca3b8e21fda3a8131019037001445.png) +![Ручний вузол_Налаштування_Відповідальний_Вибір змінної](https://static-docs.nocobase.com/22fbca3b8e21fda3a831019037001445.png) :::info{title=Примітка} Наразі опція «Відповідальний» для ручних вузлів не підтримує кількох користувачів. Це буде реалізовано в майбутніх версіях. @@ -103,7 +103,7 @@ pkg: '@nocobase/plugin-workflow-manual' Ви можете вибрати «Завдання робочого процесу» з блоків на сторінці, щоб додати блок списку завдань: -![Ручний вузол_Додавання блоку завдань](https://static-docs.nocobase.com/198b41754cd73b704267bf30fe5e647.png) +![Ручний вузол_Додавання блоку завдань](https://static-docs.nocobase.com/198b417454cd73b704267bf30fe5e647.png) Приклад блоку списку завдань: diff --git a/docs/docs/uk/workflow/nodes/parallel.md b/docs/docs/uk/workflow/nodes/parallel.md index 0bacf411baf..389c7df449e 100644 --- a/docs/docs/uk/workflow/nodes/parallel.md +++ b/docs/docs/uk/workflow/nodes/parallel.md @@ -17,7 +17,7 @@ pkg: '@nocobase/plugin-workflow-parallel' В інтерфейсі конфігурації робочого процесу натисніть кнопку плюса («+») у потоці, щоб додати вузол «Паралельна гілка»: -![Додати паралельну гілку](https://static-docs.nocobase.com/9e0f3faa0b9335270647a3047759eac.png) +![Додати паралельну гілку](https://static-docs.nocobase.com/9e0f3faa0b9335270647a30477559eac.png) Після додавання вузла паралельної гілки до робочого процесу за замовчуванням додаються дві підгілки. Ви також можете додати більше гілок, натиснувши кнопку додавання гілки. До кожної гілки можна додати будь-яку кількість вузлів. Непотрібні гілки можна видалити, натиснувши кнопку видалення на початку гілки. diff --git a/docs/docs/uk/workflow/nodes/request.md b/docs/docs/uk/workflow/nodes/request.md index 40ac8e2e5a0..f61a47eca49 100644 --- a/docs/docs/uk/workflow/nodes/request.md +++ b/docs/docs/uk/workflow/nodes/request.md @@ -25,7 +25,7 @@ pkg: '@nocobase/plugin-workflow-request' ## Налаштування вузла -![HTTP Запит_Налаштування вузла](https://static-docs.nocobase.com/2fcb29af66d869c80f8fbd362a54e644.png) +![HTTP Запит_Налаштування вузла](https://static-docs.nocobase.com/2fcb29af66b892fa704add52e2974a52.png) ### Метод запиту diff --git a/docs/docs/uk/workflow/nodes/variable.md b/docs/docs/uk/workflow/nodes/variable.md index 9570b59f436..235fee6efda 100644 --- a/docs/docs/uk/workflow/nodes/variable.md +++ b/docs/docs/uk/workflow/nodes/variable.md @@ -15,7 +15,7 @@ pkg: '@nocobase/plugin-workflow-variable' В інтерфейсі конфігурації робочого процесу натисніть кнопку плюса («+») у робочому процесі, щоб додати вузол «Змінна»: -![Додати вузол змінної](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![Додати вузол змінної](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## Налаштування вузла @@ -78,6 +78,6 @@ pkg: '@nocobase/plugin-workflow-variable' Таким чином, після завершення циклічного розгалуження змінна одержувача зберігатиме рядок одержувачів усіх авторів статті. Потім, після циклу, ви можете використовувати вузол HTTP-запиту для виклику API надсилання пошти, передаючи значення змінної одержувача як параметр одержувача до API: -![Надсилання пошти одержувачам через вузол запиту](https://static-docs.nocobase.com/37f714a1a63e172bcb2dce10a250947e.png) +![Надсилання пошти одержувачам через вузол запиту](https://static-docs.nocobase.com/37f71aa1a63e172bcb2dce10a250947e.png) Таким чином, проста функція масової розсилки електронних листів була реалізована за допомогою циклу та вузла змінної. \ No newline at end of file diff --git a/docs/docs/uk/workflow/triggers/post-action.md b/docs/docs/uk/workflow/triggers/post-action.md index 671f95eae76..aeb660d6636 100644 --- a/docs/docs/uk/workflow/triggers/post-action.md +++ b/docs/docs/uk/workflow/triggers/post-action.md @@ -177,7 +177,7 @@ curl -X POST -H 'Authorization: Bearer ' -H 'X-Role: ' -d Як показано на малюнку нижче: -![Action Execution Order](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![Action Execution Order](https://static-docs.nocobase.com/20251219234806.png) ### Відмінність від події колекції diff --git a/docs/docs/uk/workflow/triggers/pre-action.md b/docs/docs/uk/workflow/triggers/pre-action.md index 6dc7157caf1..4e7982a0d1b 100644 --- a/docs/docs/uk/workflow/triggers/pre-action.md +++ b/docs/docs/uk/workflow/triggers/pre-action.md @@ -110,7 +110,7 @@ pkg: '@nocobase/plugin-workflow-request-interceptor' Інші налаштування такі ж, як і в базовому використанні. Коли замовлення остаточно надсилається, якщо будь-який продукт має недостатній запас, надсилання замовлення буде перехоплено, і повернеться відповідне повідомлення. Під час тестування спробуйте надіслати замовлення з кількома продуктами, де один має недостатній запас, а інший — достатній. Ви побачите повернене повідомлення-відповідь: -![Приклад_Повідомлення-відповідь після надсилання](https://static-docs.nocobase.com/dd9e81084ac237bda0241d399ac19270.png) +![Приклад_Повідомлення-відповідь після надсилання](https://static-docs.nocobase.com/dd9e81084aa237bda0241d399ac19270.png) Як бачите, у повідомленні-відповіді не вказується, що перший продукт "iPhone 15 pro" відсутній на складі, а лише другий продукт "iPhone 14 pro". Це тому, що в циклі перший продукт має достатній запас, тому його не перехоплюють, тоді як другий продукт має недостатній запас, що призводить до перехоплення надсилання замовлення. diff --git a/docs/docs/vi/ai-employees/permission.md b/docs/docs/vi/ai-employees/permission.md index a6dfb9d1bf7..c206343fad7 100644 --- a/docs/docs/vi/ai-employees/permission.md +++ b/docs/docs/vi/ai-employees/permission.md @@ -73,7 +73,7 @@ Các công cụ này thường được sử dụng cho: #### Ví dụ 1: Overall Analytics (Phân tích nghiệp vụ tổng thể) -![05viz-configuration-2025-11-03-00-18-55](https://static-docs.nocobase.com/20251103001855.png) +![05viz-configuration-2025-11-03-00-18-55](https://static-docs.nocobase.com/05viz-configuration-2025-11-03-00-18-55.png) Trong CRM Demo, `Overall Analytics` là một công cụ phân tích nghiệp vụ dựa trên mẫu: @@ -103,7 +103,7 @@ flowchart TD #### Ví dụ 2: SQL Execution (Công cụ phân tích nâng cao) -![05viz-configuration-2025-11-03-00-17-13](https://static-docs.nocobase.com/20251103001713.png) +![05viz-configuration-2025-11-03-00-17-13](https://static-docs.nocobase.com/05viz-configuration-2025-11-03-00-17-13.png) Trong CRM Demo, `SQL Execution` là một công cụ linh hoạt hơn nhưng cần được kiểm soát chặt chẽ: diff --git a/docs/docs/vi/auth-verification/auth-saml/index.md b/docs/docs/vi/auth-verification/auth-saml/index.md index b92c484ee95..5d728c0fea8 100644 --- a/docs/docs/vi/auth-verification/auth-saml/index.md +++ b/docs/docs/vi/auth-verification/auth-saml/index.md @@ -58,4 +58,4 @@ Hiện tại không hỗ trợ ánh xạ tổ chức và vai trò của người Truy cập trang đăng nhập, sau đó nhấp vào nút bên dưới biểu mẫu đăng nhập để bắt đầu đăng nhập bằng bên thứ ba. -![](https://static-docs.nocobase.com/7496365c9d36a294948e6adeb5b24bc.png) \ No newline at end of file +![](https://static-docs.nocobase.com/74963865c9d36a294948e6adeb5b24bc.png) \ No newline at end of file diff --git a/docs/docs/vi/auth-verification/auth/password.md b/docs/docs/vi/auth-verification/auth/password.md index 125f9ffabc1..2fb741606da 100644 --- a/docs/docs/vi/auth-verification/auth/password.md +++ b/docs/docs/vi/auth-verification/auth/password.md @@ -27,7 +27,7 @@ Khi không cho phép đăng ký, trang đăng nhập sẽ không hiển thị li Khi không cho phép đăng ký, bạn không thể truy cập trang đăng ký. -![](https://static-docs.nocobase.com/09325c4b07e09f88f80a14dff8030556.png) +![](https://static-docs.nocobase.com/09325c4b07e09f88f80a14dff8430556.png) ## Cài đặt biểu mẫu đăng kýv1.4.0-beta.7+ diff --git a/docs/docs/vi/data-sources/data-modeling/collection-fields/associations/o2o/index.md b/docs/docs/vi/data-sources/data-modeling/collection-fields/associations/o2o/index.md index 960a2ef0b83..7802acf3c33 100644 --- a/docs/docs/vi/data-sources/data-modeling/collection-fields/associations/o2o/index.md +++ b/docs/docs/vi/data-sources/data-modeling/collection-fields/associations/o2o/index.md @@ -29,7 +29,7 @@ Cấu hình trường Mối quan hệ ER -![](https://static-docs.nocobase.com/31e7cc3e630220cf1e98573ca24ac72d.png) +![](https://static-docs.nocobase.com/31e7cc3e630220cf1e98753ca24ac72d.png) Cấu hình trường diff --git a/docs/docs/vi/data-sources/data-source-main/index.md b/docs/docs/vi/data-sources/data-source-main/index.md index 0d99740c180..32e5fb992c9 100644 --- a/docs/docs/vi/data-sources/data-source-main/index.md +++ b/docs/docs/vi/data-sources/data-source-main/index.md @@ -58,7 +58,7 @@ NocoBase hỗ trợ tạo và quản lý nhiều loại bộ sưu tập: ### Các loại trường phong phú -![nocobase_doc-2025-10-29-19-48-51](https://static-docs.nocobase.com/2025-10-29-19-48-51.png) +![nocobase_doc-2025-10-29-19-48-51](https://static-docs.nocobase.com/nocobase_doc-2025-10-29-19-48-51.png) #### Chuyển đổi loại trường linh hoạt diff --git a/docs/docs/vi/data-sources/field-encryption/index.md b/docs/docs/vi/data-sources/field-encryption/index.md index 411aef0563b..78140f54baa 100644 --- a/docs/docs/vi/data-sources/field-encryption/index.md +++ b/docs/docs/vi/data-sources/field-encryption/index.md @@ -29,7 +29,7 @@ Nếu plugin được kích hoạt bởi một ứng dụng con, thư mục lưu Sử dụng phương pháp mã hóa phong bì (Envelope Encryption). -![20251118151339](https://static-docs.nocobase.com/20251118151339.png) +![20251118151339](https://static-docs.nocobase.com/20251118151143.png) ### Quy trình tạo khóa 1. Khi tạo trường mã hóa lần đầu tiên, hệ thống sẽ tự động tạo một `khóa ứng dụng` 32 bit và lưu trữ nó dưới dạng mã hóa Base64 vào thư mục lưu trữ mặc định. diff --git a/docs/docs/vi/email-manager/advanced/batch-send.md b/docs/docs/vi/email-manager/advanced/batch-send.md index c11031d1522..a4824780df1 100644 --- a/docs/docs/vi/email-manager/advanced/batch-send.md +++ b/docs/docs/vi/email-manager/advanced/batch-send.md @@ -9,27 +9,27 @@ Tài liệu này được dịch bởi AI. Đối với bất kỳ thông tin kh ## Tổng quan về tính năng gửi hàng loạt Bạn có thể gửi email đến nhiều người cùng lúc (mỗi người nhận sẽ nhận được một email riêng biệt). -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_06_10_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_15_PM.png) ## Gửi hàng loạt qua bảng Bạn cũng có thể gửi email hàng loạt thông qua một bảng: 1. Thêm nút gửi email vào bảng - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_14_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_04_PM.png) 2. Cấu hình trường email trong bảng (dùng để phân tích địa chỉ email sau khi chọn các hàng trong bảng) - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_13_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_17_PM%20(1) 3. Chọn dữ liệu trong bảng để gửi email - ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_15_PM.png) + ![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) Nếu bạn cần gửi email đến tất cả các địa chỉ trong toàn bộ bảng, bạn có thể bật tính năng **Mặc định chọn tất cả bản ghi trong bảng hiện tại làm người nhận**: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_16_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_18_PM%20(1) Sau khi chỉnh sửa nội dung email, hãy nhấp vào nút gửi hàng loạt để gửi: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_06_17_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_19_PM.png) ## Theo dõi trạng thái gửi email Bạn có thể xem và theo dõi trạng thái gửi email cụ thể tại Trung tâm quản lý email: -![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM%20(1).png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_20_PM.png).png) ![](https://static-docs.nocobase.com/email-manager/Users-10-31-2025_08_24_PM.png) \ No newline at end of file diff --git a/docs/docs/vi/email-manager/usage/signature.md b/docs/docs/vi/email-manager/usage/signature.md index ad0644bc338..573a9b6a06e 100644 --- a/docs/docs/vi/email-manager/usage/signature.md +++ b/docs/docs/vi/email-manager/usage/signature.md @@ -10,15 +10,15 @@ Tài liệu này được dịch bởi AI. Đối với bất kỳ thông tin kh ## Cấu hình chữ ký Truy cập Trung tâm quản lý Email, sau đó nhấp vào nút cài đặt: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Chuyển sang bảng chữ ký: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_51_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM%20(1) Tại đây, bạn có thể quản lý chữ ký. Đánh dấu vào tùy chọn trước một chữ ký để đặt nó làm chữ ký mặc định: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_37_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_09_PM.png) ## Sử dụng chữ ký Trong khung nội dung email, nhấp vào biểu tượng chữ ký để chọn chữ ký mong muốn: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_40_PM.png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_11_PM.png) \ No newline at end of file diff --git a/docs/docs/vi/email-manager/usage/template.md b/docs/docs/vi/email-manager/usage/template.md index f872194c4eb..d6753026383 100644 --- a/docs/docs/vi/email-manager/usage/template.md +++ b/docs/docs/vi/email-manager/usage/template.md @@ -10,15 +10,15 @@ Tài liệu này được dịch bởi AI. Đối với bất kỳ thông tin kh ## Cấu hình Mẫu Truy cập Trung tâm Quản lý Email và nhấp vào nút cài đặt: -![](https://static-docs.nocobase.com/email-manager/Email-10-31-2025_05_34_PM.png) +![](https://static-docs.nocobase.com/email-manager/User-12-31-2025_10_08_PM.png) Chuyển sang bảng điều khiển mẫu: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_53_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_12_PM.png) Tại đây, bạn có thể quản lý các mẫu: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM.png) +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM.png) ## Sử dụng Mẫu Trong khung soạn thảo email, nhấp vào biểu tượng mẫu để chọn mẫu mong muốn: -![](https://static-docs.nocobase.com/email-manager/Loading--10-31-2025_05_54_PM%20(1).png) \ No newline at end of file +![](https://static-docs.nocobase.com/email-manager/Loading--12-31-2025_10_13_PM%20(1).png) \ No newline at end of file diff --git a/docs/docs/vi/flow-engine/learning-roadmap.md b/docs/docs/vi/flow-engine/learning-roadmap.md index 95700a1a4e9..42e9e79dbce 100644 --- a/docs/docs/vi/flow-engine/learning-roadmap.md +++ b/docs/docs/vi/flow-engine/learning-roadmap.md @@ -5,4 +5,4 @@ Tài liệu này được dịch bởi AI. Đối với bất kỳ thông tin kh # Lộ trình học tập -![20250915220745](https://static-docs.nocobase.com/20250915220745.png) \ No newline at end of file +![20250915220745](https://static-docs.nocobase.com/20251102202401.png) \ No newline at end of file diff --git a/docs/docs/vi/solution/ticket-system/design.md b/docs/docs/vi/solution/ticket-system/design.md index 5d4dcec7c31..38c8f5ea6b4 100755 --- a/docs/docs/vi/solution/ticket-system/design.md +++ b/docs/docs/vi/solution/ticket-system/design.md @@ -31,7 +31,7 @@ Mô hình này mượn ý tưởng từ khái niệm "nhân tài hình chữ T" - **Chiều ngang (Bảng chính)**: Bao quát các năng lực chung cho tất cả các loại nghiệp vụ — các trường cốt lõi như mã số, trạng thái, người xử lý, SLA, v.v. - **Chiều dọc (Bảng mở rộng)**: Các trường chuyên biệt đi sâu vào từng nghiệp vụ cụ thể — sửa chữa thiết bị có số sê-ri, khiếu nại có phương án bồi thường. -![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-50-45.png) +![ticketing-imgs-2025-12-31-22-50-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-18-25.png) **Tại sao lại thiết kế như vậy?** @@ -61,7 +61,7 @@ Không chỉ là "tính năng AI", mà là "nhân viên AI". Mỗi AI có vai tr #### Triết lý 3: Tự tuần hoàn kiến thức -![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-09.png) +![ticketing-imgs-2025-12-31-22-51-09](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-19-13.png) Điều này tạo thành một vòng lặp khép kín giữa **Tích lũy kiến thức - Ứng dụng kiến thức**. @@ -71,7 +71,7 @@ Không chỉ là "tính năng AI", mà là "nhân viên AI". Mỗi AI có vai tr ### 2.1 Tổng quan quan hệ thực thể -![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-23.png) +![ticketing-imgs-2025-12-31-22-51-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-20-02.png) ### 2.2 Chi tiết các bảng cốt lõi @@ -296,18 +296,18 @@ Không chỉ là "tính năng AI", mà là "nhân viên AI". Mỗi AI có vai tr **Quy trình chính (Từ trái sang phải)** -![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-51-45.png) +![ticketing-imgs-2025-12-31-22-51-45](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-21-01.png) **Quy trình nhánh** -![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-42.png) +![ticketing-imgs-2025-12-31-22-52-42](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-14.png) -![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-52-53.png) +![ticketing-imgs-2025-12-31-22-52-53](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-22-32.png) **Máy trạng thái đầy đủ** -![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-54-23.png) +![ticketing-imgs-2025-12-31-22-54-23](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-13.png) ### 3.3 Quy tắc chuyển đổi trạng thái quan trọng @@ -337,7 +337,7 @@ Không chỉ là "tính năng AI", mà là "nhân viên AI". Mỗi AI có vai tr ### 4.2 Logic tính toán SLA -![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-53-54.png) +![ticketing-imgs-2025-12-31-22-53-54](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-23-46.png) #### Khi tạo công đơn @@ -466,7 +466,7 @@ Mỗi nhân viên AI được cấu hình 4 nhiệm vụ cụ thể: ### 5.3 Nhân viên AI và Vòng đời công đơn -![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-04.png) +![ticketing-imgs-2025-12-31-22-55-04](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-22.png) ### 5.4 Ví dụ phản hồi của AI @@ -527,12 +527,12 @@ Việc kiểm duyệt chất lượng phản hồi do Grace phụ trách sẽ ng ### 6.1 Nguồn kiến thức -![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-20.png) +![ticketing-imgs-2025-12-31-22-55-20](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-24-57.png) ### 6.2 Quy trình chuyển đổi công đơn thành kiến thức -![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-38.png) +![ticketing-imgs-2025-12-31-22-55-38](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-18.png) **Các tiêu chí đánh giá**: - **Tính phổ biến**: Đây có phải là vấn đề thường gặp không? @@ -577,19 +577,19 @@ Khi nhân viên hỗ trợ mở chi tiết công đơn, Max sẽ tự động đ #### WF-T01: Quy trình tạo công đơn -![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-55-51.png) +![ticketing-imgs-2025-12-31-22-55-51](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-25-48.png) #### WF-AI01: Phân tích công đơn bằng AI -![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-03.png) +![ticketing-imgs-2025-12-31-22-56-03](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-14.png) #### WF-AI04: Dịch và kiểm duyệt bình luận -![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-19.png) +![ticketing-imgs-2025-12-31-22-56-19](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-38.png) #### WF-AI03: Tạo kiến thức -![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-56-37.png) +![ticketing-imgs-2025-12-31-22-56-37](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-26-54.png) ### 7.3 Nhiệm vụ định kỳ @@ -606,11 +606,11 @@ Khi nhân viên hỗ trợ mở chi tiết công đơn, Max sẽ tự động đ ### 8.1 Trang quản trị (Backend) -![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-10.png) +![ticketing-imgs-2025-12-31-22-59-10](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-19.png) ### 8.2 Cổng thông tin khách hàng (Customer Portal) -![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-2025-12-31-22-59-32.png) +![ticketing-imgs-2025-12-31-22-59-32](https://static-docs.nocobase.com/ticketing-imgs-en-2025-12-31-23-27-35.png) ### 8.3 Thiết kế bảng điều khiển (Dashboard) diff --git a/docs/docs/vi/users-permissions/acl/permissions.md b/docs/docs/vi/users-permissions/acl/permissions.md index 96c129c601f..b2bd482c559 100644 --- a/docs/docs/vi/users-permissions/acl/permissions.md +++ b/docs/docs/vi/users-permissions/acl/permissions.md @@ -25,7 +25,7 @@ Quyền hạn thao tác toàn cục áp dụng cho tất cả các **bộ sưu t ## Quyền hạn Thao tác Bộ sưu tập -![](https://static-docs.nocobase.com/6a6e028139cecdea5b5218e6173c5d7.png) +![](https://static-docs.nocobase.com/6a6e0281391cecdea5b5218e6173c5d7.png) ![](https://static-docs.nocobase.com/9814140434ff9e1bf028a6c282a5a165.png) diff --git a/docs/docs/vi/users-permissions/acl/ui.md b/docs/docs/vi/users-permissions/acl/ui.md index 60dbb29dc27..792cce408bd 100644 --- a/docs/docs/vi/users-permissions/acl/ui.md +++ b/docs/docs/vi/users-permissions/acl/ui.md @@ -22,13 +22,13 @@ Cấu hình quyền toàn cục: Cấu hình quyền riêng lẻ cho **bộ sưu tập** Đơn hàng: -![](https://static-docs.nocobase.com/a88c7a41247001c1610bf402a4a2c1.png) +![](https://static-docs.nocobase.com/a88caba1cad47001c1610bf402a4a2c1.png) Trên giao diện người dùng, tất cả các khối trong **bộ sưu tập** Đơn hàng đều không hiển thị. Quy trình cấu hình hoàn chỉnh như sau: -![](https://static-docs.nocobase.com/b283c004ffe0a746fddbffcf4f27b1df.gif) +![](https://static-docs.nocobase.com/b283c004ffe0b746fddbffcf4f27b1df.gif) ## Quyền của trường @@ -44,7 +44,7 @@ Trên giao diện người dùng, chỉ những trường có quyền được c Như hình minh họa, cấu hình quyền chỉnh sửa cho các trường của **bộ sưu tập** Đơn hàng (số lượng và các mặt hàng liên quan có quyền chỉnh sửa): - ![](https://static-docs.nocobase.com/6531ca4124887547b5719e2146ba93.png) + ![](https://static-docs.nocobase.com/6531ca4122f0887547b5719e2146ba93.png) Trên giao diện người dùng, trong khối biểu mẫu thao tác chỉnh sửa của khối **bộ sưu tập** Đơn hàng, chỉ hiển thị các trường có quyền chỉnh sửa. @@ -139,7 +139,7 @@ Như hình minh họa bên dưới, trường liên kết "Khách hàng" trong * Cấu hình quyền riêng lẻ cho **bộ sưu tập** Đơn hàng, trong đó trường liên kết "Khách hàng" có tất cả các quyền trường: -![](https://static-docs.nocobase.com/3a3ab972f14a7b3a35361219d67fa40.png) +![](https://static-docs.nocobase.com/3a3ab9722f14a7b3a35361219d67fa40.png) Cấu hình quyền riêng lẻ cho **bộ sưu tập** Khách hàng, trong đó các trường chỉ có quyền xem: diff --git a/docs/docs/vi/users-permissions/departments/index.md b/docs/docs/vi/users-permissions/departments/index.md index ade4e0b6c98..30b116065e4 100644 --- a/docs/docs/vi/users-permissions/departments/index.md +++ b/docs/docs/vi/users-permissions/departments/index.md @@ -35,7 +35,7 @@ Tài liệu này được dịch bởi AI. Đối với bất kỳ thông tin kh Trong biểu mẫu chỉnh sửa phòng ban, bạn có thể thay đổi trường phòng ban cấp trên. Lưu ý rằng phòng ban hiện tại và các phòng ban con của nó sẽ không thể chọn được. -![](https://static-docs.nocobase.com/9d80dd4f32c77186566ed8ada70128.png) +![](https://static-docs.nocobase.com/9d80ddf42f32c77186566ed8ada70128.png) ## Quản lý Thành viên Phòng Ban diff --git a/docs/docs/vi/users-permissions/user.md b/docs/docs/vi/users-permissions/user.md index 7bd94e265e5..68a0173c5e6 100644 --- a/docs/docs/vi/users-permissions/user.md +++ b/docs/docs/vi/users-permissions/user.md @@ -15,7 +15,7 @@ Plugin này cung cấp giao diện quản lý người dùng trong trung tâm c Ngoài ra, bạn cũng có thể sử dụng bảng người dùng trên trang để thêm nhiều khối khác nhau nhằm quản lý người dùng, ví dụ như khối bảng: -![](https://static-docs.nocobase.com/76b5d4dd96c424fb08082cf6.png) +![](https://static-docs.nocobase.com/76b5a4652f869541a9e8f18a4568a7c9.png) ## Thêm người dùng diff --git a/docs/docs/vi/workflow/advanced/variables.md b/docs/docs/vi/workflow/advanced/variables.md index e214dc28056..7f7106c6e5b 100644 --- a/docs/docs/vi/workflow/advanced/variables.md +++ b/docs/docs/vi/workflow/advanced/variables.md @@ -22,7 +22,7 @@ Chúng ta đã sử dụng tính năng biến nhiều lần trong [Bắt đầu Trong một nút cập nhật, sử dụng dữ liệu ngữ cảnh kích hoạt làm biến cho điều kiện lọc, và tham chiếu kết quả của nút tính toán làm biến cho giá trị trường dữ liệu cần cập nhật: -![Biến nút cập nhật dữ liệu](https://static-docs.nocobase.com/2e147c93642e7ebc709b9b7ab4f3af8c.png) +![Biến nút cập nhật dữ liệu](https://static-docs.nocobase.com/2e147c93643e7ebc709b9b7ab4f3af8c.png) ## Cấu trúc dữ liệu diff --git a/docs/docs/vi/workflow/nodes/calculation.md b/docs/docs/vi/workflow/nodes/calculation.md index 289dd5abab5..1c523b2c9c0 100644 --- a/docs/docs/vi/workflow/nodes/calculation.md +++ b/docs/docs/vi/workflow/nodes/calculation.md @@ -15,7 +15,7 @@ Trong giao diện cấu hình luồng công việc, hãy nhấp vào nút dấu ## Cấu hình nút -![Nút Tính toán_Cấu hình](https://static-docs.nocobase.com/6a155de3f883d8cd1881b2d9c33874.png) +![Nút Tính toán_Cấu hình](https://static-docs.nocobase.com/6a155de3f6a883d8cd1881b2d9c33874.png) ### Công cụ tính toán diff --git a/docs/docs/vi/workflow/nodes/end.md b/docs/docs/vi/workflow/nodes/end.md index c7f53d3a783..077c920355a 100644 --- a/docs/docs/vi/workflow/nodes/end.md +++ b/docs/docs/vi/workflow/nodes/end.md @@ -15,7 +15,7 @@ Trong giao diện cấu hình luồng công việc, nhấp vào nút dấu cộn ## Cấu hình nút -![Kết thúc luồng công việc_Cấu hình nút](https://static-docs.nocobase.com/bb6a57f25e9afb72836a14a0fe0683e.png) +![Kết thúc luồng công việc_Cấu hình nút](https://static-docs.nocobase.com/bb6a597f25e9afb72836a14a0fe0683e.png) ### Trạng thái kết thúc diff --git a/docs/docs/vi/workflow/nodes/manual.md b/docs/docs/vi/workflow/nodes/manual.md index 72da7d70d29..f598df33955 100644 --- a/docs/docs/vi/workflow/nodes/manual.md +++ b/docs/docs/vi/workflow/nodes/manual.md @@ -31,7 +31,7 @@ Nút thủ công cần chỉ định một người dùng làm người thực h Chọn một người dùng, hoặc chọn khóa chính hoặc khóa ngoại của dữ liệu người dùng từ ngữ cảnh thông qua một biến. -![Manual Node_Configure_Assignee_Select Variable](https://static-docs.nocobase.com/22fbca3b821fda31019037001445.png) +![Manual Node_Configure_Assignee_Select Variable](https://static-docs.nocobase.com/22fbca3b8e21fda3a831019037001445.png) :::info{title=Lưu ý} Hiện tại, tùy chọn người phụ trách cho nút thủ công chưa hỗ trợ xử lý cho nhiều người dùng. Tính năng này sẽ được hỗ trợ trong các phiên bản tương lai. @@ -103,7 +103,7 @@ Sau khi mở cửa sổ bật lên, bạn có thể gán giá trị cho bất k Bạn có thể chọn “Nhiệm vụ cần làm của `luồng công việc`” từ các khối trên trang để thêm khối danh sách nhiệm vụ cần làm: -![Manual Node_Add To-do Block](https://static-docs.nocobase.com/198b41754cd73b704267bf30fe5e647.png) +![Manual Node_Add To-do Block](https://static-docs.nocobase.com/198b417454cd73b704267bf30fe5e647.png) Ví dụ về khối danh sách nhiệm vụ cần làm: diff --git a/docs/docs/vi/workflow/nodes/variable.md b/docs/docs/vi/workflow/nodes/variable.md index 44ce88d16b9..d32d891eca2 100644 --- a/docs/docs/vi/workflow/nodes/variable.md +++ b/docs/docs/vi/workflow/nodes/variable.md @@ -15,7 +15,7 @@ Bạn có thể khai báo biến hoặc gán giá trị cho các biến đã kha Trong giao diện cấu hình luồng công việc, hãy nhấp vào nút dấu cộng (“+”) trong luồng để thêm nút "Biến": -![Add Variable Node](https://static-docs.nocobase.com/53b1e48e777bfff7f2a08271526ef3ee.png) +![Add Variable Node](https://static-docs.nocobase/53b1e48e777bfff7f2a08271526ef3ee.png) ## Cấu hình nút @@ -78,6 +78,6 @@ Sau nút tính toán, hãy tạo một nút biến khác. Chọn chế độ gá Bằng cách này, sau khi nhánh lặp kết thúc, biến người nhận sẽ lưu trữ chuỗi người nhận của tất cả các tác giả bài viết. Sau đó, bạn có thể sử dụng nút Yêu cầu HTTP để gọi API gửi email, truyền giá trị của biến người nhận làm tham số người nhận cho API: -![Send mail to recipients via the request node](https://static-docs.nocobase.com/37f71ae1a63e172bcb2dce10a250947e.png) +![Send mail to recipients via the request node](https://static-docs.nocobase.com/37f71aa1a63e172bcb2dce10a250947e.png) Đến đây, một tính năng gửi email hàng loạt đơn giản đã được triển khai bằng cách sử dụng vòng lặp và nút biến. \ No newline at end of file diff --git a/docs/docs/vi/workflow/triggers/post-action.md b/docs/docs/vi/workflow/triggers/post-action.md index c3b80ff9841..230632872fa 100644 --- a/docs/docs/vi/workflow/triggers/post-action.md +++ b/docs/docs/vi/workflow/triggers/post-action.md @@ -177,7 +177,7 @@ Nếu sự kiện được cấu hình ở chế độ toàn cục, bạn không Như được hiển thị trong hình dưới đây: -![Thứ tự thực thi thao tác](https://static-docs.nocobase.com/7c901be2282067d785205b70391332b7.png) +![Thứ tự thực thi thao tác](https://static-docs.nocobase.com/20251219234806.png) ### Sự khác biệt với sự kiện bộ sưu tập diff --git a/docs/docs/vi/workflow/triggers/schedule.md b/docs/docs/vi/workflow/triggers/schedule.md index d80a419df13..70c66811402 100644 --- a/docs/docs/vi/workflow/triggers/schedule.md +++ b/docs/docs/vi/workflow/triggers/schedule.md @@ -75,6 +75,6 @@ Tạo một luồng công việc dựa trên tác vụ định kỳ. Trong cấu Sau đó, cấu hình các nút khác theo logic của quy trình để cập nhật trạng thái của đơn hàng có ID dữ liệu kích hoạt và trạng thái "chưa thanh toán" thành đã hủy: -![Tác vụ định kỳ_Cấu hình kích hoạt_Chế độ trường thời gian của bộ sưu tập_Nút cập nhật](https://static-docs.nocobase.com/491dde9df7f41fb24a4e7baa1de6eb29.png) +![Tác vụ định kỳ_Cấu hình kích hoạt_Chế độ trường thời gian của bộ sưu tập_Nút cập nhật](https://static-docs.nocobase.com/491dde9df8f773f5b14a4fd8ceac9d3e.png) Khác với chế độ thời gian tùy chỉnh, ở đây không cần tính toán thời gian 30 phút trước đó, vì ngữ cảnh dữ liệu kích hoạt của luồng công việc đã bao gồm hàng dữ liệu tương ứng thỏa mãn điều kiện thời gian, do đó bạn có thể trực tiếp cập nhật trạng thái của đơn hàng đó. \ No newline at end of file