diff --git a/packages/twenty-docs/l/ar/user-guide/data-migration/how-tos/fix-import-errors.mdx b/packages/twenty-docs/l/ar/user-guide/data-migration/how-tos/fix-import-errors.mdx index fae13dff43..2586c39564 100644 --- a/packages/twenty-docs/l/ar/user-guide/data-migration/how-tos/fix-import-errors.mdx +++ b/packages/twenty-docs/l/ar/user-guide/data-migration/how-tos/fix-import-errors.mdx @@ -1,11 +1,11 @@ --- -title: Fix Import Errors -description: Complete troubleshooting guide for resolving CSV import errors. +title: إصلاح أخطاء الاستيراد +description: دليل شامل لاستكشاف أخطاء استيراد CSV وإصلاحها. --- ## نظرة عامة -Import not working? This guide helps you identify and fix common import errors step by step. +هل تواجه مشكلة في الاستيراد؟ This guide helps you identify and fix common import errors step by step. ## How Import Validation Works diff --git a/packages/twenty-docs/l/ar/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx b/packages/twenty-docs/l/ar/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx index 971474bb87..d24045196e 100644 --- a/packages/twenty-docs/l/ar/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx +++ b/packages/twenty-docs/l/ar/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx @@ -1,103 +1,103 @@ --- -title: Import Relations Between Objects via CSV -description: Complete step-by-step guide to linking records during CSV import. +title: استيراد العلاقات بين الكائنات عبر CSV +description: دليل كامل خطوة بخطوة لربط السجلات أثناء استيراد CSV. --- ## نظرة عامة -This guide walks you through importing relations between objects—for example, linking People to Companies, or Opportunities to People. +يأخذك هذا الدليل خلال استيراد العلاقات بين الكائنات—على سبيل المثال، ربط الأشخاص بالشركات، أو الفرص بالأشخاص. -**What can be imported:** Only one-to-many relations pointing to a single object type. Relations pointing to multiple object types (like Notes linking to People AND Companies) are not yet supported for import. +**ما الذي يمكن استيراده:** العلاقات من واحد إلى متعدد التي تشير إلى نوع كائن واحد فقط. العلاقات التي تشير إلى أنواع كائنات متعددة (مثل ملاحظات مرتبطة بالأشخاص والشركات معًا) غير مدعومة للاستيراد بعد. -## Understanding Relations +## فهم العلاقات -### What is a "One-to-Many" Relation? +### ما هي علاقة "واحد إلى متعدد"؟ -In a one-to-many relation: +في علاقة واحد إلى متعدد: -* **One** Company has **many** People (employees) -* **One** Company has **many** Opportunities -* **One** Person has **many** Tasks +* **شركة واحدة** لديها **العديد** من الأشخاص (الموظفين) +* **شركة واحدة** لديها **العديد** من الفرص +* **شخص واحد** لديه **العديد** من المهام -The "one" side is the **parent**. The "many" side is the **child**. +جانب "الواحد" هو **الأصل**. جانب "المتعدد" هو **التابع**. -### Common Relations in Twenty +### العلاقات الشائعة في Twenty -| علاقة | "One" Side (Parent) | "Many" Side (Child) | -| ------------------------- | ------------------- | ------------------- | -| Companies → People | الشركة | الأشخاص | -| Companies → Opportunities | الشركة | الفرص | -| People → Tasks | شخص | المهام | -| People → Notes | شخص | الملاحظات | +| علاقة | جانب "الواحد" (الأصل) | جانب "المتعدد" (التابع) | +| ------------------- | --------------------- | ----------------------- | +| الشركات → الأشخاص | الشركة | الأشخاص | +| الشركات → الفرص | الشركة | الفرص | +| الأشخاص → المهام | شخص | المهام | +| الأشخاص → الملاحظات | شخص | الملاحظات | -## Step 1: Identify the "One" and "Many" Sides +## الخطوة 1: تحديد جانبي "الواحد" و"المتعدد" -Before importing, determine which object is the parent and which is the child. +قبل الاستيراد، حدّد أي الكائنات هو الأصل وأيها التابع. -**Ask yourself:** "Does ONE [Object A] have MANY [Object B]?" +**اسأل نفسك:** "هل لدى كائن واحد من [Object A] العديد من [Object B]؟" -* One Company → Many People ✓ (Company is parent) -* One Person → Many Companies ✗ (This is wrong—a person belongs to one company) +* شركة واحدة → العديد من الأشخاص ✓ (الشركة هي الأصل) +* شخص واحد → العديد من الشركات ✗ (هذا خطأ — الشخص ينتمي إلى شركة واحدة) -## Step 2: Import the Parent Records First +## الخطوة 2: استيراد سجلات الأصل أولًا -The parent ("one" side) must exist in Twenty before you can reference it. +يجب أن يكون الأصل (جانب "الواحد") موجودًا في Twenty قبل أن تتمكّن من الإشارة إليه. -**Import order:** +**ترتيب الاستيراد:** -1. **Companies** first (no dependencies) -2. **People** second (link to Companies) -3. **Opportunities** third (link to Companies and/or People) -4. **Tasks/Notes** (link to any of the above) +1. **الشركات** أولًا (من دون تبعيات) +2. **الأشخاص** ثانيًا (مرتبطون بالشركات) +3. **الفرص** ثالثًا (مرتبطة بالشركات و/أو الأشخاص) +4. **المهام/الملاحظات** (مرتبطة بأي مما سبق) - **If the parent record doesn't exist, the import will fail.** + **إذا كان سجل الأصل غير موجود، فسيفشل الاستيراد.** - Always verify that Companies are imported before importing People with company references. + تحقّق دائمًا من استيراد الشركات قبل استيراد الأشخاص الذين لديهم مراجع للشركات. -## Step 3: Note the Parent's Unique Identifier +## الخطوة 3: تدوين المعرّف الفريد للأصل -You need to reference the parent record using a **unique identifier**. Available options: +تحتاج إلى الإشارة إلى سجل الأصل باستخدام **مُعرّف فريد**. الخيارات المتاحة: -| Parent Object | Available Unique Identifiers | -| --------------------- | --------------------------------------------------------------- | -| **الشركات** | `id` (UUID), `domain` (recommended), or any custom unique field | -| **People** | `id` (UUID), `email`, or any custom unique field | -| **أعضاء مساحة العمل** | `id` (UUID), `email` (not name) | -| **كائنات مخصصة** | `id` (UUID), or any field marked as unique | +| كائن الأصل | المُعرّفات الفريدة المتاحة | +| --------------------- | ---------------------------------------------------- | +| **الشركات** | `id` (UUID)، `domain` (موصى به)، أو أي حقل فريد مخصص | +| **الأشخاص** | `id` (UUID)، `email`، أو أي حقل فريد مخصص | +| **أعضاء مساحة العمل** | `id` (UUID)، `email` (ليس الاسم) | +| **كائنات مخصصة** | `id` (UUID)، أو أي حقل مميز كفريد | -**Recommended:** Use `domain` for Companies and `email` for People. These are human-readable and easy to verify in your spreadsheet. +**موصى به:** استخدم `domain` للشركات و`email` للأشخاص. هذه مقروءة للبشر وسهلة التحقّق منها في جدول البيانات الخاص بك. -### Finding the Identifier +### العثور على المعرّف -If you need the `id`: +إذا كنت تحتاج إلى `id`: -1. Export the parent records from Twenty -2. The export includes the `id` column -3. Use these IDs in your child records file +1. صدّر سجلات الأصل من Twenty +2. يتضمن التصدير عمود `id` +3. استخدم هذه المعرّفات في ملف سجلات التابع -## Step 4: Verify the Relation Field Exists +## الخطوة 4: التحقّق من وجود حقل العلاقة -Before importing, ensure the relation field exists between your objects. +قبل الاستيراد، تأكّد من وجود حقل العلاقة بين كائناتك. -**To check or create:** +**للتحقّق أو الإنشاء:** -1. Go to **Settings → Data Model** -2. Select your child object (e.g., People) -3. Look for a relation field pointing to the parent (e.g., Company) -4. If it doesn't exist, create it: - * Click **+ Add field** - * Select **Relation** type - * Choose the parent object +1. اذهب إلى **الإعدادات → نموذج البيانات** +2. اختر كائن التابع الخاص بك (مثلًا، الأشخاص) +3. ابحث عن حقل علاقة يشير إلى الأصل (مثلًا، الشركة) +4. إذا لم يكن موجودًا، فقم بإنشائه: + * انقر **+ إضافة حقل** + * اختر نوع **العلاقة** + * اختر كائن الأصل -## Step 5: Prepare Your CSV File +## الخطوة 5: جهّز ملف CSV الخاص بك -Add a column to your child CSV that references the parent using its unique identifier. +أضِف عمودًا إلى ملف CSV للتابع يشير إلى الأصل باستخدام مُعرّفه الفريد. -### Example: People Linking to Companies +### مثال: ربط الأشخاص بالشركات -**Your People CSV:** +**ملف CSV الخاص بالأشخاص لديك:** ```csv firstName,lastName,email,jobTitle,companyDomain @@ -106,66 +106,66 @@ Jane,Doe,jane@widgets.co,CTO,https://widgets.co Bob,Johnson,bob@techstart.io,Developer,https://techstart.io ``` -The `companyDomain` column references the Company's domain. +يشير عمود `companyDomain` إلى نطاق الشركة. -### Format Requirements +### متطلبات التنسيق -| معرّف | التنسيق | مثال | -| ----------------- | -------------- | -------------------------------------- | -| النطاق | URL format | `https://acme.com` | -| البريد الإلكتروني | Standard email | `john@acme.com` | -| المعرف | UUID | `c776ee49-f608-4a77-8cc8-6fe96ae1e43f` | +| معرّف | التنسيق | مثال | +| ----------------- | ------------------- | -------------------------------------- | +| النطاق | تنسيق عنوان URL | `https://acme.com` | +| البريد الإلكتروني | بريد إلكتروني قياسي | `john@acme.com` | +| المعرف | UUID | `c776ee49-f608-4a77-8cc8-6fe96ae1e43f` | - **Domain format matters!** + **تنسيق النطاق مهم!** - Use `https://domain.com` (not just `domain.com`). This matches how Twenty stores Company domains and prevents matching errors. + استخدم `https://domain.com` (وليس فقط `domain.com`). هذا يتوافق مع طريقة تخزين Twenty لنطاقات الشركات ويمنع أخطاء المطابقة. -### Important Rules +### قواعد مهمة -1. **Exact match required** — the value must exactly match the parent record -2. **Map only ONE unique identifier** — don't include both `companyId` AND `companyDomain` -3. **Case sensitive** — `Acme.com` ≠ `acme.com` +1. **تطابق تام مطلوب** — يجب أن تتطابق القيمة تمامًا مع سجل الأصل +2. **قم بتعيين مُعرّف فريد واحد فقط** — لا تُدرج كلًّا من `companyId` و`companyDomain` +3. **حسّاس لحالة الأحرف** — `Acme.com` ≠ `acme.com` -## Step 6: Upload and Map the Relation +## الخطوة 6: ارفع الملف وعيّن العلاقة -1. Navigate to the child object (e.g., People) -2. Click **⋮** → **Import records** -3. Upload your CSV file -4. In the field mapping step: - * Find your relation column (e.g., `companyDomain`) - * Map it to the **Company** relation field -5. Complete the remaining mapping -6. Review errors and confirm +1. انتقل إلى كائن التابع (مثلًا، الأشخاص) +2. انقر **⋮** → **Import records** +3. ارفع ملف CSV الخاص بك +4. في خطوة تعيين الحقول: + * اعثر على عمود العلاقة الخاص بك (مثلًا، `companyDomain`) + * طابقه مع حقل علاقة **Company** +5. أكمل التعيينات المتبقية +6. راجع الأخطاء وأكّد -Twenty will automatically link each child record to the matching parent. +سيقوم Twenty بربط كل سجل تابع تلقائيًا بالأصل المطابق. -## Step 7: Verify the Import +## الخطوة 7: التحقّق من الاستيراد -After importing: +بعد الاستيراد: -1. Open a few child records (e.g., People) -2. Verify the relation field shows the correct parent (e.g., Company) -3. Open a parent record and check the related records section +1. افتح عددًا قليلًا من سجلات التابع (مثلًا، الأشخاص) +2. تحقّق من أن حقل العلاقة يعرض الأصل الصحيح (مثلًا، الشركة) +3. افتح سجل الأصل وتفقّد قسم السجلات المرتبطة -## Common Mistakes to Avoid +## أخطاء شائعة يجب تجنّبها -| Mistake | Problem | Solution | -| -------------------------- | -------------------------------------------------- | ------------------------------------------------------- | -| **Wrong import order** | Importing People before Companies | Always import parents first, then children | -| **Wrong domain format** | Using `acme.com` instead of `https://acme.com` | Use full URL format with `https://` | -| **Multiple unique fields** | Mapping both `companyId` AND `companyDomain` | Map only ONE unique identifier | -| **Missing relation field** | The relation field doesn't exist in the data model | Create it in **Settings → Data Model** before importing | -| **Non-existent records** | The parent record doesn't exist in Twenty | Import parent records first, or check for typos | -| **Case mismatch** | `Acme.com` in file but `acme.com` in Twenty | Ensure exact case matching | +| الخطأ | المشكلة | الحل | +| ------------------------- | ---------------------------------------------- | ----------------------------------------------------------- | +| **ترتيب استيراد خاطئ** | استيراد الأشخاص قبل الشركات | استورد دائمًا الأصول أولًا، ثم التوابع | +| **تنسيق نطاق غير صحيح** | استخدام `acme.com` بدلًا من `https://acme.com` | استخدم تنسيق عنوان URL الكامل مع `https://` | +| **حقول فريدة متعددة** | تعيين كلٍّ من `companyId` و`companyDomain` | قم بتعيين مُعرّف فريد واحد فقط | +| **حقل علاقة مفقود** | حقل العلاقة غير موجود في نموذج البيانات | قم بإنشائه ضمن **الإعدادات → نموذج البيانات** قبل الاستيراد | +| **سجلات غير موجودة** | سجل الأصل غير موجود في Twenty | استورد سجلات الأصل أولًا، أو تحقّق من الأخطاء الإملائية | +| **عدم تطابق حالة الأحرف** | `Acme.com` في الملف ولكن `acme.com` في Twenty | تأكّد من تطابق حالة الأحرف تمامًا | -## Linking to Workspace Members +## الربط بأعضاء مساحة العمل -When linking to Workspace Members (your team): +عند الربط بأعضاء مساحة العمل (فريقك): -* Use their **email address**, not their name -* Example: `owner@yourcompany.com`, not "John Smith" +* استخدم **عنوان بريدهم الإلكتروني**، وليس اسمهم +* مثال: `owner@yourcompany.com`، وليس "John Smith" ```csv taskName,assignedTo @@ -173,56 +173,56 @@ Follow up with client,john@yourcompany.com Review proposal,jane@yourcompany.com ``` -## FAQ +## الأسئلة الشائعة - - You have two options: + + لديك خياران: - 1. Use the Twenty `id` (export parent records to get their IDs) - 2. Create a custom unique field in your data model to store an external ID from your previous system + 1. استخدم `id` الخاص بـ Twenty (صدّر سجلات الأصل للحصول على معرّفاتها) + 2. أنشئ حقلًا فريدًا مخصصًا في نموذج البيانات لتخزين معرّف خارجي من نظامك السابق - - نعم! Include the child record's unique identifier (e.g., `email` for People) and the new relation value. The import will update the relation. + + نعم! ضمّن المُعرّف الفريد لسجل التابع (مثلًا، `email` للأشخاص) وقيمة العلاقة الجديدة. سيقوم الاستيراد بتحديث العلاقة. - - Many-to-Many relations are not yet supported for import. This is planned for H1 2026. + + العلاقات عديدة-إلى-عدة غير مدعومة للاستيراد بعد. هذا مُخطّط للنصف الأول من عام 2026. - - Relations pointing to multiple object types are not yet supported for import/export. This is on our roadmap. + + العلاقات التي تشير إلى أنواع كائنات متعددة غير مدعومة للاستيراد/التصدير بعد. هذا على خارطة الطريق لدينا. - - The import will show an error for that row. يمكنك إما: + + سيعرض الاستيراد خطأً لذلك الصف. يمكنك إما: - * Import the parent record first, then re-import - * Fix the reference value - * Remove the row from import + * استورد سجل الأصل أولًا، ثم أعد الاستيراد + * أصلِح قيمة المرجع + * أزل الصف من الاستيراد - - Common causes: + + أسباب شائعة: - * Wrong format (use `https://domain.com` for domains) - * Case mismatch (check exact spelling) - * Parent doesn't exist (import parents first) - * Mapping multiple identifiers (use only one) + * تنسيق غير صحيح (استخدم `https://domain.com` للنطاقات) + * عدم تطابق حالة الأحرف (تحقّق من التهجئة الدقيقة) + * الأصل غير موجود (استورد الأصول أولًا) + * تعيين عدة مُعرّفات (استخدم واحدًا فقط) - **Remember: Soft-deleted records count toward uniqueness.** + **تذكير: السجلات المحذوفة حذفًا ناعمًا تُحتسب ضمن التفرد.** - If you're getting "not found" errors but the record seems to exist, check Command Menu → See deleted records. The parent may have been soft-deleted. + إذا كنت تتلقى أخطاء "not found" ولكن يبدو أن السجل موجود، فتحقّق من قائمة الأوامر → عرض السجلات المحذوفة. قد يكون السجل الأصل قد حُذِف حذفًا منطقيًا. ## استكشاف الأخطاء وإصلاحها -Having issues? Check: +هل تواجه مشكلات؟ اطّلع على: -* [How to Fix Import Errors](/l/ar/user-guide/data-migration/how-tos/fix-import-errors) -* [Import Relations Capabilities](/l/ar/user-guide/data-migration/capabilities/import-relations) -* [Uniqueness Constraints](/l/ar/user-guide/data-migration/capabilities/uniqueness-constraints) +* [كيفية إصلاح أخطاء الاستيراد](/l/ar/user-guide/data-migration/how-tos/fix-import-errors) +* [قدرات استيراد العلاقات](/l/ar/user-guide/data-migration/capabilities/import-relations) +* [قيود التفرد](/l/ar/user-guide/data-migration/capabilities/uniqueness-constraints) diff --git a/packages/twenty-docs/l/ar/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx b/packages/twenty-docs/l/ar/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx index 4a2ee2aadc..17a6e55bb7 100644 --- a/packages/twenty-docs/l/ar/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx +++ b/packages/twenty-docs/l/ar/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx @@ -1,73 +1,73 @@ --- title: التحويل من نظام ذاتي الاستضافة إلى السحابة -description: Step-by-step guide to migrate your Twenty self-hosted instance to Twenty Cloud. +description: دليل خطوة بخطوة لترحيل مثيل Twenty ذاتي الاستضافة الخاص بك إلى Twenty Cloud. --- ## نظرة عامة -This guide walks you through migrating your data from a Twenty self-hosted instance to Twenty Cloud. The process involves setting up your cloud workspace, exporting your data, and re-importing it. +يرشدك هذا الدليل خلال ترحيل بياناتك من مثيل Twenty ذاتي الاستضافة إلى Twenty Cloud. تتضمن العملية إعداد مساحة العمل السحابية الخاصة بك، وتصدير بياناتك، ثم إعادة استيرادها. -Views, workflows, and roles must be recreated manually after migration. Plan time for this configuration work. +يجب إعادة إنشاء العروض، وسير العمل، والأدوار يدويًا بعد الترحيل. خطط وقتًا لهذا العمل الخاص بالإعداد. -## Step 1: Create Your Cloud Workspace +## الخطوة 1: إنشاء مساحة العمل السحابية الخاصة بك -1. Go to [app.twenty.com](https://app.twenty.com) and create a new workspace -2. Complete the initial setup wizard -3. Note your new workspace URL +1. انتقل إلى [app.twenty.com](https://app.twenty.com) وأنشئ مساحة عمل جديدة +2. أكمل معالج الإعداد الأولي +3. دوّن عنوان URL لمساحة العمل الجديدة لديك -## Step 2: Recreate Your Data Model +## الخطوة 2: إعادة إنشاء نموذج البيانات الخاص بك -Before importing data, recreate your custom objects and fields: +قبل استيراد البيانات، أعد إنشاء الكائنات والحقول المخصّصة لديك: -1. Go to **Settings → Data Model** in your cloud instance -2. Create custom objects that match your self-hosted setup -3. Add custom fields to standard and custom objects -4. Configure field settings (unique, required, etc.) +1. انتقل إلى **الإعدادات → نموذج البيانات** في مثيلك السحابي +2. أنشئ كائنات مخصّصة تتطابق مع إعدادك ذاتي الاستضافة +3. أضف حقولًا مخصّصة إلى الكائنات القياسية والمخصّصة +4. قم بضبط إعدادات الحقول (فريد، مطلوب، إلخ.) -Take screenshots of your self-hosted data model for reference, or keep both instances open side by side. +التقط لقطات شاشة لنموذج البيانات ذاتي الاستضافة لديك كمرجع، أو اترك المثيلين مفتوحين جنبًا إلى جنب. -## Step 3: Invite All Users +## الخطوة 3: دعوة جميع المستخدمين - **Critical: Invite users BEFORE importing data.** + **هام: قم بدعوة المستخدمين قبل استيراد البيانات.** - Users must accept their invitations before you import any records that reference them (like Account Owner fields). If users don't exist yet, those relations cannot be mapped. + يجب على المستخدمين قبول دعواتهم قبل أن تستورد أي سجلات تُشير إليهم (مثل حقول مالك الحساب). إذا لم يكن المستخدمون موجودين بعد، فلن يمكن تعيين تلك العلاقات. -1. Go to **Settings → Members** in your cloud instance -2. Invite all team members who had accounts on self-hosted -3. **Wait for everyone to accept** their invitation -4. Verify all users appear in your Members list +1. انتقل إلى **الإعدادات → الأعضاء** في مثيلك السحابي +2. ادعُ جميع أعضاء الفريق الذين كانت لديهم حسابات على المثيل ذاتي الاستضافة +3. **انتظر أن يقبل الجميع** دعواتهم +4. تحقق من ظهور جميع المستخدمين في قائمة الأعضاء لديك -## Step 4: Export Data from Self-Hosted +## الخطوة 4: تصدير البيانات من المثيل ذاتي الاستضافة -Export each object from your self-hosted instance: +صدِّر كل كائن من مثيلك ذاتي الاستضافة: -1. Navigate to each object (Companies, People, Opportunities, etc.) -2. Configure the view to show **all columns** you want to migrate -3. Click **⋮ → Export view** -4. Save each CSV file with a clear name (e.g., `companies-export.csv`) +1. انتقل إلى كل كائن (الشركات، الأشخاص، الفرص، إلخ.) +2. قم بإعداد العرض ليُظهر **جميع الأعمدة** التي تريد ترحيلها +3. انقر **⋮ → Export view** +4. احفظ كل ملف CSV باسم واضح (مثلًا، `companies-export.csv`) -**Export in this order** (for reference when importing): +**صدِّر بالترتيب التالي** (للرجوع إليه عند الاستيراد): 1. الشركات 2. الأشخاص 3. الفرص -4. Custom objects (following their dependencies) -5. Tasks, Notes +4. الكائنات المخصّصة (وفقًا لتبعياتها) +5. المهام، الملاحظات -## Step 5: Update Workspace Member References +## الخطوة 5: تحديث مراجع أعضاء مساحة العمل -The exported CSVs contain user IDs from your self-hosted instance. These IDs won't match your cloud instance, so you need to replace them with emails. +تحتوي ملفات CSV المُصدَّرة على معرّفات المستخدمين من مثيلك ذاتي الاستضافة. هذه المعرّفات لن تتطابق مع مثيلك السحابي، لذا تحتاج إلى استبدالها بعناوين البريد الإلكتروني. -**For each CSV file with user references (Owner, Assignee, etc.):** +**لكل ملف CSV يحتوي على مراجع للمستخدمين (المالك، المسند إليه، إلخ.):** -1. Open the CSV in a spreadsheet application -2. Add a new column next to each user ID column (e.g., `accountOwnerEmail` next to `accountOwnerId`) -3. Fill in the **email address** of each user -4. You can delete the old ID column or leave it (it will be skipped during import) +1. افتح ملف CSV في تطبيق جداول بيانات +2. أضِف عمودًا جديدًا بجوار كل عمود لمعرّف المستخدم (مثلًا، `accountOwnerEmail` بجوار `accountOwnerId`) +3. املأ **عنوان البريد الإلكتروني** لكل مستخدم +4. يمكنك حذف عمود المعرّف القديم أو تركه (سيتم تخطيه أثناء الاستيراد) -**Example:** +**مثال:** قبل: @@ -83,89 +83,89 @@ name,domain,accountOwnerEmail Acme Corp,https://acme.com,john@yourcompany.com ``` -Use the same email addresses that users used to accept their cloud workspace invitation. +استخدم عناوين البريد الإلكتروني نفسها التي استخدمها المستخدمون لقبول دعوتهم إلى مساحة العمل السحابية. -## Step 6: Plan Your Import Order +## الخطوة 6: التخطيط لترتيب الاستيراد -Import files in the correct order to maintain relationships: +استورد الملفات بالترتيب الصحيح للحفاظ على العلاقات: -1. **Companies** first (no dependencies) -2. **People** second (link to Companies) -3. **Opportunities** third (link to Companies and People) -4. **Custom objects** (following their dependencies) -5. **Tasks and Notes** last (link to other records) +1. **الشركات** أولًا (من دون تبعيات) +2. **الأشخاص** ثانيًا (مرتبطون بالشركات) +3. **الفرص** ثالثًا (مرتبطة بالشركات والأشخاص) +4. **الكائنات المخصّصة** (وفقًا لتبعياتها) +5. **المهام والملاحظات** أخيرًا (مرتبطة بسجلات أخرى) -See [How to Import Relations](/l/ar/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv) for details on maintaining relationships. +اطّلع على [كيفية استيراد العلاقات](/l/ar/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv) لمعرفة تفاصيل الحفاظ على العلاقات. -## Step 7: Import to Cloud +## الخطوة 7: الاستيراد إلى السحابة -For each CSV file, in order: +لكل ملف CSV، بالتسلسل: -1. Navigate to the object in your cloud instance -2. Click **⋮ → Import records** -3. Upload the CSV file -4. Map columns to fields: - * Map user email columns to the appropriate relation fields - * Map other columns as usual -5. Review and fix any errors -6. Confirm the import -7. Verify a few records before proceeding to the next file +1. انتقل إلى الكائن في مثيلك السحابي +2. انقر **⋮ → Import records** +3. ارفع ملف CSV +4. طابق الأعمدة مع الحقول: + * طابِق أعمدة بريد المستخدم الإلكتروني مع حقول العلاقات المناسبة + * طابق الأعمدة الأخرى كالمعتاد +5. راجِع وأصلِح أي أخطاء +6. أكِّد عملية الاستيراد +7. تحقّق من عدد قليل من السجلات قبل المتابعة إلى الملف التالي -## Step 8: Recreate Configuration +## الخطوة 8: إعادة إنشاء الإعدادات -After importing data, manually recreate: +بعد استيراد البيانات، أعد إنشاء ما يلي يدويًا: ### العروض -* Recreate saved views with filters, sorts, and column configurations -* Set up any kanban or calendar views +* أعد إنشاء العروض المحفوظة مع عوامل التصفية والترتيب وتكوينات الأعمدة +* قم بإعداد أي عروض كانبان أو تقويم ### سير العمل -* Recreate automations in **Settings → Workflows** -* Test each workflow before relying on it +* أعد إنشاء الأتمتة في **الإعدادات → سير العمل** +* اختبر كل سير عمل قبل الاعتماد عليه -### Roles and Permissions +### الأدوار والصلاحيات -* Configure roles in **Settings → Roles** -* Assign users to appropriate roles +* قم بتكوين الأدوار في **الإعدادات → الأدوار** +* عيّن المستخدمين إلى الأدوار المناسبة ### التكاملات -* Reconnect email and calendar sync for each user -* Reconfigure any API integrations with new API keys +* أعد توصيل مزامنة البريد الإلكتروني والتقويم لكل مستخدم +* أعد تكوين أي تكاملات API بمفاتيح API جديدة ## قائمة التحقق بعد التحويل -All data imported successfully -Relations between objects working correctly -User assignments (Owner, Assignee) mapped correctly -Views recreated -Workflows recreated and tested -Roles and permissions configured -Email/calendar sync reconnected -API integrations updated with new keys +تم استيراد جميع البيانات بنجاح +العلاقات بين الكائنات تعمل بشكل صحيح +تعيينات المستخدمين (المالك، المسند إليه) تمت مطابقتها بشكل صحيح +تمت إعادة إنشاء العروض +تمت إعادة إنشاء سير العمل واختبارها +تم تكوين الأدوار والصلاحيات +تمت إعادة توصيل مزامنة البريد الإلكتروني/التقويم +تم تحديث تكاملات API بمفاتيح جديدة -## FAQ +## الأسئلة الشائعة - - Not currently. Workflows must be recreated manually in your cloud instance. + + ليس في الوقت الحالي. يجب إعادة إنشاء سير العمل يدويًا في مثيلك السحابي. - - File attachments are not included in CSV exports. You'll need to re-upload any attachments manually, migrate them via API or contact our team for assistance with large migrations. + + مرفقات الملفات غير متضمنة في صادرات CSV. ستحتاج إلى إعادة رفع أي مرفقات يدويًا، أو ترحيلها عبر API، أو التواصل مع فريقنا للحصول على المساعدة في عمليات الترحيل الكبيرة. - - Yes, we recommend keeping your self-hosted instance running until you've verified the cloud migration is complete. Just be careful not to create new data in both places. + + نعم، نوصي بإبقاء مثيلك ذاتي الاستضافة قيد التشغيل حتى تتحقق من اكتمال الترحيل إلى السحابة. فقط احرص على عدم إنشاء بيانات جديدة في كلا المكانين. - - Records referencing that user will fail to import or the relation will be empty. Ensure all users accept invitations before importing data. + + السجلات التي تُشير إلى ذلك المستخدم ستفشل في الاستيراد أو ستكون العلاقة فارغة. تأكّد من أن جميع المستخدمين يقبلون الدعوات قبل استيراد البيانات. ## هل تحتاج إلى مساعدة؟ -For complex migrations or large datasets, contact us at [contact@twenty.com](mailto:contact@twenty.com) or explore our [Implementation Services](/l/ar/user-guide/getting-started/capabilities/implementation-services). +بالنسبة لعمليات الترحيل المعقّدة أو مجموعات البيانات الكبيرة، تواصل معنا عبر [contact@twenty.com](mailto:contact@twenty.com) أو اطّلع على [خدمات التنفيذ](/l/ar/user-guide/getting-started/capabilities/implementation-services). diff --git a/packages/twenty-docs/l/ar/user-guide/settings/overview.mdx b/packages/twenty-docs/l/ar/user-guide/settings/overview.mdx index 04b4446b07..cab24cbe43 100644 --- a/packages/twenty-docs/l/ar/user-guide/settings/overview.mdx +++ b/packages/twenty-docs/l/ar/user-guide/settings/overview.mdx @@ -55,13 +55,13 @@ image: /images/user-guide/setup/settings.png ## قائمة التحقق لإعدادات مساحة العمل * تم تكوين اسم مساحة العمل والشعار -* Time zone and date format set -* Email and calendar connected -* Team members invited -* Roles and permissions configured +* تم ضبط المنطقة الزمنية وتنسيق التاريخ +* تم ربط البريد الإلكتروني والتقويم +* تمت دعوة أعضاء الفريق +* تم إعداد الأدوار والأذونات ## الخطوات التالية -* [Workspace settings](/l/ar/user-guide/settings/capabilities/workspace-settings) -* [Profile settings](/l/ar/user-guide/settings/capabilities/profile-settings) -* [Experience settings](/l/ar/user-guide/settings/capabilities/experience-settings) +* [إعدادات مساحة العمل](/l/ar/user-guide/settings/capabilities/workspace-settings) +* [إعدادات الملف الشخصي](/l/ar/user-guide/settings/capabilities/profile-settings) +* [إعدادات التجربة](/l/ar/user-guide/settings/capabilities/experience-settings) diff --git a/packages/twenty-docs/l/ar/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx b/packages/twenty-docs/l/ar/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx index 12a97e6239..eaf290c3d4 100644 --- a/packages/twenty-docs/l/ar/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx +++ b/packages/twenty-docs/l/ar/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx @@ -1,120 +1,120 @@ --- -title: Set Up a Sales Pipeline -description: Configure your sales pipeline to track opportunities through stages. +title: إعداد مسار المبيعات +description: قم بتهيئة مسار المبيعات لديك لتتبّع الفرص عبر المراحل. --- import { VimeoEmbed } from '/snippets/vimeo-embed.mdx'; -A sales pipeline in Twenty is a Kanban view of your Opportunities object, where each column represents a stage in your sales process. +يمثّل مسار المبيعات في Twenty عرض كانبان لكائن الفرص لديك، حيث يمثّل كل عمود مرحلة في عملية المبيعات الخاصة بك. -## Step 1: Configure Your Stages +## الخطوة 1: تهيئة المراحل الخاصة بك -Stages are defined in the Opportunities object's **Stage** field. +تُحدَّد المراحل في حقل **Stage** الخاص بكائن الفرص. -1. Go to **Settings → Data Model** -2. Select **Opportunities** -3. Find and click the **Stage** field -4. Add, remove, or rename stages to match your process +1. اذهب إلى **الإعدادات → نموذج البيانات** +2. حدّد **الفرص** +3. ابحث عن حقل **Stage** وانقر عليه +4. أضِف المراحل أو أزلها أو أعد تسميتها بما يتوافق مع عمليتك - + -### Recommended Stages +### المراحل الموصى بها -| المرحلة | Purpose | -| --------------- | ----------------------------------- | -| **New** | Fresh opportunities just identified | -| **Qualified** | Confirmed as a good fit | -| **Meeting** | Engaged in discussions | -| **Proposal** | Proposal sent | -| **Negotiation** | Working on terms | -| **Closed Won** | Deal successful | -| **Closed Lost** | Deal unsuccessful | +| المرحلة | الغرض | +| ----------------- | ----------------------------- | +| **جديد** | فرص جديدة تم تحديدها للتو | +| **مؤهل** | تم التأكّد من ملاءمتها الجيدة | +| **اجتماع** | تجري مناقشات | +| **عرض** | تم إرسال العرض | +| **تفاوض** | جارٍ العمل على الشروط | +| **مغلقة - رابحة** | صفقة ناجحة | +| **مغلقة - خاسرة** | صفقة غير ناجحة | - **5-7 stages is optimal.** Too many stages makes the pipeline hard to scan; too few loses visibility into deal progress. + **أفضل عدد هو 5–7 مراحل.** كثرة المراحل تجعل مسار المبيعات صعب الاستعراض؛ وقلّتها تُفقد الرؤية لتقدّم الصفقات. -## Step 2: Create a Pipeline View +## الخطوة 2: إنشاء عرض لمسار المبيعات -1. Go to **Opportunities** -2. Click the view dropdown → **+ Add view** -3. Name it "Sales Pipeline" -4. Click **Create** -5. Open **Options** and select **Kanban** as the layout +1. اذهب إلى **الفرص** +2. انقر على القائمة المنسدلة لطريقة العرض → **+ إضافة طريقة عرض** +3. سمِّه "مسار المبيعات" +4. انقر على **إنشاء** +5. افتح **الخيارات** واختر **Kanban** كتخطيط -The view automatically uses the Stage field for columns. +يستخدم العرض تلقائيًا حقل Stage للأعمدة. -## Step 3: Configure Your View +## الخطوة 3: تهيئة العرض الخاص بك -### Show Key Fields +### إظهار الحقول الرئيسية -1. Click **Options → Fields** -2. Look for fields in the "Hidden Fields" section -3. Click the **eye icon** to display: Company, Amount, Close Date, Owner +1. انقر على **الخيارات → الحقول** +2. ابحث عن الحقول في قسم "الحقول المخفية" +3. انقر على **أيقونة العين** لعرض: Company، Amount، Close Date، Owner -### Enable Aggregations +### تمكين عمليات التجميع -Show totals at the top of each column: +إظهار الإجماليات أعلى كل عمود: -1. Click the number displayed next to a Stage name at the top of a column -2. Select the aggregation type (Count, Sum, Average, etc.) -3. Choose the field to aggregate (e.g., Amount) +1. انقر على الرقم المعروض بجانب اسم Stage أعلى العمود +2. حدّد نوع التجميع (Count، Sum، Average، إلخ) +3. اختر الحقل المراد تجميعه (مثال: Amount) -**Example:** Show total deal value per stage by aggregating Amount with Sum. +**مثال:** اعرض إجمالي قيمة الصفقة لكل مرحلة من خلال تجميع Amount باستخدام Sum. -### Use Compact View (Optional) +### استخدم العرض المضغوط (اختياري) -For a high-level overview with minimal card content: +للحصول على نظرة عامة عالية المستوى مع أدنى قدر من محتوى البطاقات: -1. Click **Options** -2. Turn on the toggle for **Compact view** +1. انقر على **الخيارات** +2. فعِّل مفتاح التبديل لخيار **العرض المضغوط** -## Step 4: Create Personal and Team Views +## الخطوة 4: إنشاء عروض شخصية وعروض للفريق -### "My Pipeline" +### "مسار المبيعات الخاص بي" -* **Filter**: Owner = Me -* **Visibility**: Unlisted (personal view) +* **عامل التصفية**: Owner = Me +* **الظهور**: غير مُدرَج (عرض شخصي) -### "Team Pipeline" +### "مسار المبيعات للفريق" -* **Filter**: None (show all) -* **Visibility**: Workspace (shared view) +* **عامل التصفية**: None (عرض الكل) +* **الظهور**: Workspace (عرض مشترك) -### "Closing This Month" +### "الإغلاق هذا الشهر" -* **Type**: Table -* **Filter**: Close Date = This month, Stage ≠ Closed Won, Stage ≠ Closed Lost -* **Sort**: Close Date ascending +* **النوع**: Table +* **عامل التصفية**: Close Date = This month، Stage ≠ Closed Won، Stage ≠ Closed Lost +* **الفرز**: Close Date تصاعديًا -## Working with Opportunities +## العمل مع الفرص -### Creating Opportunities +### إنشاء الفرص -* Click **+ New** in the Opportunities view -* Or click **+** in a specific stage column +* انقر على **+ New** في عرض الفرص +* أو انقر على **+** في عمود مرحلة معيّنة -### Moving Through Stages +### الانتقال عبر المراحل -Drag and drop opportunity cards between columns to update their stage. +اسحب وأفلِت بطاقات الفرص بين الأعمدة لتحديث مرحلتها. - + ## أفضل الممارسات -### Pipeline Hygiene +### نظافة مسار المبيعات -* Update deals daily as they progress -* Move or close stale deals promptly -* Keep close dates realistic +* حدِّث الصفقات يوميًا مع تقدّمها +* انقل الصفقات الراكدة أو أغلِقها على الفور +* اجعل تواريخ الإقفال واقعية -### Stage Discipline +### الانضباط في المراحل -* Define clear criteria for each stage -* Move deals promptly when criteria are met -* Don't let deals sit in stages too long +* حدِّد معايير واضحة لكل مرحلة +* انقل الصفقات فور استيفاء المعايير +* لا تدَع الصفقات تبقى في المراحل لوقت طويل -## Related +## ذات صلة -* [Kanban Views](/l/ar/user-guide/views-pipelines/capabilities/kanban-views) — aggregations and compact view -* [Filters and Sorting](/l/ar/user-guide/views-pipelines/capabilities/filters-and-sorting) — creating filtered views +* [عروض كانبان](/l/ar/user-guide/views-pipelines/capabilities/kanban-views) — عمليات التجميع والعرض المضغوط +* [عوامل التصفية والفرز](/l/ar/user-guide/views-pipelines/capabilities/filters-and-sorting) — إنشاء عروض مُفلترة diff --git a/packages/twenty-docs/l/ar/user-guide/workflows/capabilities/use-branches-in-workflows.mdx b/packages/twenty-docs/l/ar/user-guide/workflows/capabilities/use-branches-in-workflows.mdx index eec8d14651..e53f3a8b7b 100644 --- a/packages/twenty-docs/l/ar/user-guide/workflows/capabilities/use-branches-in-workflows.mdx +++ b/packages/twenty-docs/l/ar/user-guide/workflows/capabilities/use-branches-in-workflows.mdx @@ -1,66 +1,66 @@ --- -title: Use Branches in Workflows -description: Understand how branches work and how to control which path is executed. +title: استخدام الفروع في سير العمل +description: افهم كيف تعمل الفروع وكيف تتحكم في المسار الذي يتم تنفيذه. --- -## How Branches Work +## كيف تعمل الفروع -In the workflow editor, you can create multiple paths (branches) going out from a single node. This allows you to build complex automations with different outcomes. +في محرر سير العمل، يمكنك إنشاء مسارات متعددة (فروع) تنطلق من عقدة واحدة. يُمكّنك هذا من إنشاء أتمتة معقدة بنتائج مختلفة. -**Important**: When a workflow runs, **all branches execute in parallel by default**. There is no built-in "if/else" logic to choose one branch over another—every path will run simultaneously. +**مهم**: عند تشغيل سير العمل، **تُنفَّذ جميع الفروع بالتوازي افتراضيًا**. لا توجد بنية منطقية مدمجة "if/else" لاختيار فرع على آخر — كل مسار سيعمل في الوقت نفسه. -## Controlling Which Branch Runs +## التحكم في الفرع الذي يعمل -To execute only one branch based on specific conditions, **add a Filter node at the beginning of each branch**. +لتنفيذ فرع واحد فقط بناءً على شروط محددة، **أضِف عقدة Filter في بداية كل فرع**. -### Example Setup +### مثال على الإعداد -1. Create your workflow with multiple branches from a single node -2. Add a **Filter** node as the first step in each branch -3. Set conditions on each Filter to determine when that branch should continue -4. Only the branch(es) whose Filter conditions are met will proceed +1. أنشئ سير العمل الخاص بك بفروع متعددة من عقدة واحدة +2. أضِف عقدة **Filter** كأول خطوة في كل فرع +3. عيِّن شروطًا على كل Filter لتحديد متى يجب أن يواصل ذلك الفرع +4. سيتابع فقط الفرع أو الفروع التي تستوفي شروط Filter -### How Filters Work +### كيف تعمل عُقد Filter -* If the Filter condition is **met**: The branch continues executing -* If the Filter condition is **not met**: The branch stops at the Filter node +* إذا كان شرط Filter **متحققًا**: يتابع الفرع التنفيذ +* إذا كان شرط Filter **غير متحقق**: يتوقف الفرع عند عقدة Filter -This effectively creates conditional logic where only the appropriate branch runs based on your data. +يُنشئ هذا عمليًا منطقًا شرطيًا بحيث لا يعمل إلا الفرع المناسب بناءً على بياناتك. -## Example: Route by Deal Size +## مثال: التوجيه حسب حجم الصفقة -**Scenario**: When a deal is closed, send different notifications based on deal size. +**السيناريو**: عند إغلاق صفقة، أرسِل إشعارات مختلفة حسب حجم الصفقة. -1. **Trigger**: Opportunity updated (Stage = Closed Won) -2. **Branch 1**: Filter for Amount > $10,000 → Send Slack message to #big-deals -3. **Branch 2**: Filter for Amount ≤ $10,000 → Send email to sales manager +1. **المشغّل**: تم تحديث الفرصة (المرحلة = Closed Won) +2. **الفرع 1**: شرط Filter للمبلغ > $10,000 → إرسال رسالة Slack إلى #big-deals +3. **الفرع 2**: شرط Filter للمبلغ ≤ $10,000 → إرسال بريد إلكتروني إلى مدير المبيعات -Both branches start, but only the one matching the deal amount will continue past its Filter. +يبدأ الفرعان، لكن الفرع الذي يطابق مبلغ الصفقة فقط سيستمر بعد عقدة Filter. -## Creating Branches +## إنشاء الفروع - To create a new branch from an existing step, click the **+** button on the step and add your action. You can add multiple branches by clicking **+** multiple times. + لإنشاء فرع جديد من خطوة موجودة، انقر زر **+** على الخطوة وأضِف الإجراء الخاص بك. يمكنك إضافة عدة فروع بالنقر على **+** عدة مرات. -1. In the workflow editor, select the step you want to branch from -2. Click the **+** button to add an action -3. This creates one branch -4. Click **+** again on the same step to create additional branches -5. Each branch can have its own sequence of actions +1. في محرر سير العمل، حدِّد الخطوة التي تريد التفريع منها +2. انقر **+** لإضافة إجراء +3. سيؤدي هذا إلى إنشاء فرع واحد +4. انقر **+** مرة أخرى على نفس الخطوة لإنشاء فروع إضافية +5. يمكن لكل فرع أن يكون له تسلسل إجراءات خاص به -## Merging Branches Back Together +## دمج الفروع معًا مرة أخرى -After parallel branches complete their work, you can merge them back into a single path: +بعد أن تُكمل الفروع المتوازية عملها، يمكنك دمجها مرة أخرى في مسار واحد: -1. Complete your branched actions -2. Add a new step that should run after all branches -3. Drag a connection from the last step of each branch to this new step -4. The merged step waits for all connected branches to complete before executing +1. أكمل إجراءات الفروع +2. أضِف خطوة جديدة ينبغي أن تعمل بعد جميع الفروع +3. اسحب اتصالًا من الخطوة الأخيرة لكل فرع إلى هذه الخطوة الجديدة +4. تنتظر الخطوة المدمجة اكتمال جميع الفروع المتصلة قبل التنفيذ -### Example: Process Then Notify +### مثال: المعالجة ثم الإشعار ``` Trigger @@ -74,17 +74,17 @@ Trigger Merged Step: Send Confirmation Email ``` -The confirmation email sends only after both the customer update and ticket creation are done. +لا يتم إرسال رسالة التأكيد عبر البريد الإلكتروني إلا بعد اكتمال تحديث العميل وإنشاء التذكرة. ## أفضل الممارسات -* Always use **Filter nodes** at the start of branches when you want conditional execution -* Keep branch conditions **mutually exclusive** to avoid duplicate actions -* Test your workflows with different data to ensure the correct branches run -* **Rename branch steps** descriptively so it's clear what each path does -* **Merge branches** when you need a final action after parallel processing +* استخدم دائمًا **عُقد Filter** في بداية الفروع عندما تريد تنفيذًا شرطيًا +* اجعل شروط الفروع **متبادلة الإقصاء** لتجنّب الإجراءات المكررة +* اختبر سير العمل لديك ببيانات مختلفة للتأكد من تشغيل الفروع الصحيحة +* **أعد تسمية خطوات الفروع** بطريقة وصفية ليكون واضحًا ما يفعله كل مسار +* **ادمج الفروع** عندما تحتاج إلى إجراء نهائي بعد المعالجة المتوازية -## Related +## ذات صلة -* [Workflows FAQ](/l/ar/user-guide/workflows/how-tos/need-more-help/workflows-faq) — answers about parallel execution -* [Workflow Actions](/l/ar/user-guide/workflows/capabilities/workflow-actions) — available actions for branches +* [الأسئلة الشائعة حول سير العمل](/l/ar/user-guide/workflows/how-tos/need-more-help/workflows-faq) — إجابات حول التنفيذ المتوازي +* [إجراءات سير العمل](/l/ar/user-guide/workflows/capabilities/workflow-actions) — الإجراءات المتاحة للفروع diff --git a/packages/twenty-docs/l/cs/user-guide/data-migration/how-tos/fix-import-errors.mdx b/packages/twenty-docs/l/cs/user-guide/data-migration/how-tos/fix-import-errors.mdx index e2c80aaa8b..b7e4a2f96f 100644 --- a/packages/twenty-docs/l/cs/user-guide/data-migration/how-tos/fix-import-errors.mdx +++ b/packages/twenty-docs/l/cs/user-guide/data-migration/how-tos/fix-import-errors.mdx @@ -1,11 +1,11 @@ --- -title: Fix Import Errors -description: Complete troubleshooting guide for resolving CSV import errors. +title: Oprava chyb importu +description: Kompletní průvodce odstraňováním chyb při importu CSV. --- ## Přehled -Import not working? This guide helps you identify and fix common import errors step by step. +Nefunguje import? This guide helps you identify and fix common import errors step by step. ## How Import Validation Works diff --git a/packages/twenty-docs/l/cs/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx b/packages/twenty-docs/l/cs/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx index c67f6a782f..23ab626d69 100644 --- a/packages/twenty-docs/l/cs/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx +++ b/packages/twenty-docs/l/cs/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx @@ -1,103 +1,103 @@ --- -title: Import Relations Between Objects via CSV -description: Complete step-by-step guide to linking records during CSV import. +title: Import relací mezi objekty pomocí CSV +description: Kompletní podrobný průvodce propojením záznamů během importu CSV. --- ## Přehled -This guide walks you through importing relations between objects—for example, linking People to Companies, or Opportunities to People. +Tento průvodce vás provede importem relací mezi objekty — například propojením lidí se společnostmi nebo příležitostí s lidmi. -**What can be imported:** Only one-to-many relations pointing to a single object type. Relations pointing to multiple object types (like Notes linking to People AND Companies) are not yet supported for import. +**Co lze importovat:** Pouze relace „jeden ku mnoha“ směřující k jednomu typu objektu. Relace směřující k více typům objektů (např. poznámky propojené s lidmi a společnostmi) zatím nejsou pro import podporovány. -## Understanding Relations +## Porozumění relacím -### What is a "One-to-Many" Relation? +### Co je to relace „jeden ku mnoha“? -In a one-to-many relation: +V relaci jeden ku mnoha: -* **One** Company has **many** People (employees) -* **One** Company has **many** Opportunities -* **One** Person has **many** Tasks +* **Jedna** společnost má **mnoho** lidí (zaměstnanců) +* **Jedna** společnost má **mnoho** příležitostí +* **Jedna** osoba má **mnoho** úkolů -The "one" side is the **parent**. The "many" side is the **child**. +Strana „jedna“ je **nadřazená**. Strana „mnoho“ je **podřízená**. -### Common Relations in Twenty +### Běžné relace v Twenty -| Vztah | "One" Side (Parent) | "Many" Side (Child) | -| ------------------------- | ------------------- | ------------------- | -| Companies → People | Společnost | Osoby | -| Companies → Opportunities | Společnost | Příležitosti | -| People → Tasks | Osoba | Úkoly | -| People → Notes | Osoba | Poznámky | +| Vztah | Strana „jedna“ (nadřazený) | Strana „mnoho“ (podřízený) | +| -------------------------- | -------------------------- | -------------------------- | +| Společnosti → Lidé | Společnost | Osoby | +| Společnosti → Příležitosti | Společnost | Příležitosti | +| Lidé → Úkoly | Osoba | Úkoly | +| Lidé → Poznámky | Osoba | Poznámky | -## Step 1: Identify the "One" and "Many" Sides +## Krok 1: Určete strany „jedna“ a „mnoho“ -Before importing, determine which object is the parent and which is the child. +Před importem určete, který objekt je nadřazený a který podřízený. -**Ask yourself:** "Does ONE [Object A] have MANY [Object B]?" +**Zeptejte se sami sebe:** "Má JEDEN [Objekt A] MNOHO [Objekt B]?" -* One Company → Many People ✓ (Company is parent) -* One Person → Many Companies ✗ (This is wrong—a person belongs to one company) +* Jedna společnost → Mnoho lidí ✓ (společnost je nadřazená) +* Jedna osoba → Mnoho společností ✗ (To je špatně — osoba patří k jedné společnosti) -## Step 2: Import the Parent Records First +## Krok 2: Nejprve importujte nadřazené záznamy -The parent ("one" side) must exist in Twenty before you can reference it. +Nadřazený („jedna“ strana) musí v Twenty existovat, než na něj budete moci odkazovat. -**Import order:** +**Pořadí importu:** -1. **Companies** first (no dependencies) -2. **People** second (link to Companies) -3. **Opportunities** third (link to Companies and/or People) -4. **Tasks/Notes** (link to any of the above) +1. **Společnosti** jako první (bez závislostí) +2. **Lidé** jako druzí (propojení se společnostmi) +3. **Příležitosti** jako třetí (propojené se společnostmi a/nebo lidmi) +4. **Úkoly/Poznámky** (propojené s jakýmkoli z výše uvedených) - **If the parent record doesn't exist, the import will fail.** + **Pokud nadřazený záznam neexistuje, import selže.** - Always verify that Companies are imported before importing People with company references. + Vždy ověřte, že společnosti jsou importovány dříve, než budete importovat lidi s odkazy na společnost. -## Step 3: Note the Parent's Unique Identifier +## Krok 3: Poznamenejte si jedinečný identifikátor nadřazeného objektu -You need to reference the parent record using a **unique identifier**. Available options: +Na nadřazený záznam musíte odkazovat pomocí **jedinečného identifikátoru**. Dostupné možnosti: -| Parent Object | Available Unique Identifiers | -| ------------------------------- | --------------------------------------------------------------- | -| **Společnosti** | `id` (UUID), `domain` (recommended), or any custom unique field | -| **People** | `id` (UUID), `email`, or any custom unique field | -| **Členové pracovního prostoru** | `id` (UUID), `email` (not name) | -| **Vlastní objekty** | `id` (UUID), or any field marked as unique | +| Nadřazený objekt | Dostupné jedinečné identifikátory | +| ------------------------------- | ----------------------------------------------------------------------- | +| **Společnosti** | `id` (UUID), `domain` (doporučeno) nebo jakékoli vlastní jedinečné pole | +| **Lidé** | `id` (UUID), `email` nebo jakékoli vlastní jedinečné pole | +| **Členové pracovního prostoru** | `id` (UUID), `email` (ne jméno) | +| **Vlastní objekty** | `id` (UUID) nebo jakékoli pole označené jako jedinečné | -**Recommended:** Use `domain` for Companies and `email` for People. These are human-readable and easy to verify in your spreadsheet. +**Doporučeno:** Pro společnosti použijte `domain` a pro lidi `email`. Jsou čitelné pro člověka a snadno ověřitelné ve vaší tabulce. -### Finding the Identifier +### Jak zjistit identifikátor -If you need the `id`: +Pokud potřebujete `id`: -1. Export the parent records from Twenty -2. The export includes the `id` column -3. Use these IDs in your child records file +1. Exportujte nadřazené záznamy z Twenty +2. Export obsahuje sloupec `id` +3. Použijte tato ID v souboru s podřízenými záznamy -## Step 4: Verify the Relation Field Exists +## Krok 4: Ověřte, že existuje relační pole -Before importing, ensure the relation field exists between your objects. +Před importem se ujistěte, že mezi vašimi objekty existuje relační pole. -**To check or create:** +**Jak ověřit nebo vytvořit:** -1. Go to **Settings → Data Model** -2. Select your child object (e.g., People) -3. Look for a relation field pointing to the parent (e.g., Company) -4. If it doesn't exist, create it: - * Click **+ Add field** - * Select **Relation** type - * Choose the parent object +1. Přejděte na **Nastavení → Datový model** +2. Vyberte svůj podřízený objekt (např. Lidé) +3. Vyhledejte relační pole směřující na nadřazený objekt (např. Společnost) +4. Pokud neexistuje, vytvořte jej: + * Klikněte na **+ Add field** + * Vyberte typ **Relation** + * Vyberte nadřazený objekt -## Step 5: Prepare Your CSV File +## Krok 5: Připravte svůj soubor CSV -Add a column to your child CSV that references the parent using its unique identifier. +Do podřízeného CSV přidejte sloupec, který odkazuje na nadřazený objekt pomocí jeho jedinečného identifikátoru. -### Example: People Linking to Companies +### Příklad: Propojení lidí se společnostmi -**Your People CSV:** +**Vaše CSV s lidmi:** ```csv firstName,lastName,email,jobTitle,companyDomain @@ -106,66 +106,66 @@ Jane,Doe,jane@widgets.co,CTO,https://widgets.co Bob,Johnson,bob@techstart.io,Developer,https://techstart.io ``` -The `companyDomain` column references the Company's domain. +Sloupec `companyDomain` odkazuje na doménu společnosti. -### Format Requirements +### Požadavky na formát -| Identifikátor | Formát | Příklad | -| ------------- | -------------- | -------------------------------------- | -| Doména | URL format | `https://acme.com` | -| Email | Standard email | `john@acme.com` | -| ID | UUID | `c776ee49-f608-4a77-8cc8-6fe96ae1e43f` | +| Identifikátor | Formát | Příklad | +| ------------- | ----------------- | -------------------------------------- | +| Doména | Formát URL | `https://acme.com` | +| Email | Standardní e-mail | `john@acme.com` | +| ID | UUID | `c776ee49-f608-4a77-8cc8-6fe96ae1e43f` | - **Domain format matters!** + **Na formátu domény záleží!** - Use `https://domain.com` (not just `domain.com`). This matches how Twenty stores Company domains and prevents matching errors. + Použijte `https://domain.com` (ne pouze `domain.com`). To odpovídá způsobu, jak Twenty ukládá domény společností, a předchází chybám při párování. -### Important Rules +### Důležitá pravidla -1. **Exact match required** — the value must exactly match the parent record -2. **Map only ONE unique identifier** — don't include both `companyId` AND `companyDomain` -3. **Case sensitive** — `Acme.com` ≠ `acme.com` +1. **Je vyžadována přesná shoda** — hodnota se musí přesně shodovat s nadřazeným záznamem +2. **Mapujte pouze JEDEN jedinečný identifikátor** — nezahrnujte současně `companyId` A `companyDomain` +3. **Rozlišuje se velikost písmen** — `Acme.com` ≠ `acme.com` -## Step 6: Upload and Map the Relation +## Krok 6: Nahrajte a namapujte relaci -1. Navigate to the child object (e.g., People) -2. Click **⋮** → **Import records** -3. Upload your CSV file -4. In the field mapping step: - * Find your relation column (e.g., `companyDomain`) - * Map it to the **Company** relation field -5. Complete the remaining mapping -6. Review errors and confirm +1. Přejděte k podřízenému objektu (např. Lidé) +2. Klikněte na **⋮** → **Import records** +3. Nahrajte svůj soubor CSV +4. V kroku mapování polí: + * Najděte svůj relační sloupec (např. `companyDomain`) + * Namapujte jej na relační pole **Společnost** +5. Dokončete zbývající mapování +6. Zkontrolujte chyby a potvrďte -Twenty will automatically link each child record to the matching parent. +Twenty automaticky propojí každý podřízený záznam s odpovídajícím nadřazeným. -## Step 7: Verify the Import +## Krok 7: Ověřte import -After importing: +Po importu: -1. Open a few child records (e.g., People) -2. Verify the relation field shows the correct parent (e.g., Company) -3. Open a parent record and check the related records section +1. Otevřete několik podřízených záznamů (např. Lidé) +2. Ověřte, že relační pole zobrazuje správný nadřazený objekt (např. Společnost) +3. Otevřete nadřazený záznam a zkontrolujte sekci souvisejících záznamů -## Common Mistakes to Avoid +## Časté chyby, kterým se vyhnout -| Mistake | Problem | Solution | -| -------------------------- | -------------------------------------------------- | ------------------------------------------------------- | -| **Wrong import order** | Importing People before Companies | Always import parents first, then children | -| **Wrong domain format** | Using `acme.com` instead of `https://acme.com` | Use full URL format with `https://` | -| **Multiple unique fields** | Mapping both `companyId` AND `companyDomain` | Map only ONE unique identifier | -| **Missing relation field** | The relation field doesn't exist in the data model | Create it in **Settings → Data Model** before importing | -| **Non-existent records** | The parent record doesn't exist in Twenty | Import parent records first, or check for typos | -| **Case mismatch** | `Acme.com` in file but `acme.com` in Twenty | Ensure exact case matching | +| Chyba | Problém | Řešení | +| ---------------------------- | ----------------------------------------------- | --------------------------------------------------------------- | +| **Chybné pořadí importu** | Importujete lidi před společnostmi | Vždy nejprve importujte nadřazené, poté podřízené | +| **Chybný formát domény** | Použití `acme.com` místo `https://acme.com` | Použijte plný formát URL s `https://` | +| **Více jedinečných polí** | Mapujete současně `companyId` A `companyDomain` | Mapujte pouze JEDEN jedinečný identifikátor | +| **Chybí relační pole** | Relační pole v datovém modelu neexistuje | Vytvořte jej v **Nastavení → Datový model** před importem | +| **Neexistující záznamy** | Nadřazený záznam v Twenty neexistuje | Nejprve importujte nadřazené záznamy nebo zkontrolujte překlepy | +| **Rozdílná velikost písmen** | `Acme.com` v souboru, ale v Twenty `acme.com` | Zajistěte přesnou shodu velikosti písmen | -## Linking to Workspace Members +## Propojování s členy pracovního prostoru -When linking to Workspace Members (your team): +Při propojování s členy pracovního prostoru (vaším týmem): -* Use their **email address**, not their name -* Example: `owner@yourcompany.com`, not "John Smith" +* Použijte jejich **e-mailovou adresu**, ne jméno +* Příklad: `owner@yourcompany.com`, ne "John Smith" ```csv taskName,assignedTo @@ -173,56 +173,56 @@ Follow up with client,john@yourcompany.com Review proposal,jane@yourcompany.com ``` -## FAQ +## Časté dotazy - - You have two options: + + Máte dvě možnosti: - 1. Use the Twenty `id` (export parent records to get their IDs) - 2. Create a custom unique field in your data model to store an external ID from your previous system + 1. Použijte Twenty `id` (exportujte nadřazené záznamy, abyste získali jejich ID) + 2. Vytvořte ve svém datovém modelu vlastní jedinečné pole pro uložení externího ID z vašeho předchozího systému - - Ano! Include the child record's unique identifier (e.g., `email` for People) and the new relation value. The import will update the relation. + + Ano! Zahrňte jedinečný identifikátor podřízeného záznamu (např. `email` u lidí) a novou hodnotu relace. Import relaci aktualizuje. - - Many-to-Many relations are not yet supported for import. This is planned for H1 2026. + + Vztahy mnoho k mnoha zatím nejsou pro import podporovány. To je plánováno na 1. pololetí 2026. - - Relations pointing to multiple object types are not yet supported for import/export. This is on our roadmap. + + Relace směřující k více typům objektů zatím nejsou pro import/export podporovány. Je to v našem plánu. - - The import will show an error for that row. Můžete buď: + + Import u daného řádku zobrazí chybu. Můžete buď: - * Import the parent record first, then re-import - * Fix the reference value - * Remove the row from import + * Nejprve importujte nadřazený záznam, poté znovu importujte + * Opravte referenční hodnotu + * Odstraňte řádek z importu - - Common causes: + + Časté příčiny: - * Wrong format (use `https://domain.com` for domains) - * Case mismatch (check exact spelling) - * Parent doesn't exist (import parents first) - * Mapping multiple identifiers (use only one) + * Nesprávný formát (pro domény použijte `https://domain.com`) + * Nesoulad ve velikosti písmen (zkontrolujte přesný zápis) + * Nadřazený neexistuje (nejprve importujte nadřazené) + * Mapujete více identifikátorů (použijte pouze jeden) - **Remember: Soft-deleted records count toward uniqueness.** + **Pamatujte: Záznamy „soft-deleted“ se započítávají do jedinečnosti.** - If you're getting "not found" errors but the record seems to exist, check Command Menu → See deleted records. The parent may have been soft-deleted. + Pokud dostáváte chyby "not found", ale záznam se zdá existovat, zkontrolujte Command Menu → See deleted records. Nadřazený mohl být „soft-deleted“. ## Řešení potíží -Having issues? Check: +Máte potíže? Podívejte se na: -* [How to Fix Import Errors](/l/cs/user-guide/data-migration/how-tos/fix-import-errors) -* [Import Relations Capabilities](/l/cs/user-guide/data-migration/capabilities/import-relations) -* [Uniqueness Constraints](/l/cs/user-guide/data-migration/capabilities/uniqueness-constraints) +* [Jak opravit chyby importu](/l/cs/user-guide/data-migration/how-tos/fix-import-errors) +* [Možnosti importu relací](/l/cs/user-guide/data-migration/capabilities/import-relations) +* [Omezení jedinečnosti](/l/cs/user-guide/data-migration/capabilities/uniqueness-constraints) diff --git a/packages/twenty-docs/l/cs/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx b/packages/twenty-docs/l/cs/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx index 1675ee6d08..533efd8296 100644 --- a/packages/twenty-docs/l/cs/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx +++ b/packages/twenty-docs/l/cs/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx @@ -1,71 +1,71 @@ --- title: Migrace z vlastních serverů do cloudu -description: Step-by-step guide to migrate your Twenty self-hosted instance to Twenty Cloud. +description: Podrobný průvodce krok za krokem pro migraci vaší instance Twenty hostované na vlastním serveru do Twenty Cloud. --- ## Přehled -This guide walks you through migrating your data from a Twenty self-hosted instance to Twenty Cloud. The process involves setting up your cloud workspace, exporting your data, and re-importing it. +Tento průvodce vás provede migrací vašich dat z instance Twenty hostované na vlastním serveru do Twenty Cloud. Proces zahrnuje zřízení vašeho cloudového pracovního prostoru, export dat a jejich opětovný import. -Views, workflows, and roles must be recreated manually after migration. Plan time for this configuration work. +Zobrazení, pracovní postupy a role je po migraci nutné vytvořit ručně. Naplánujte si čas na tuto konfigurační práci. -## Step 1: Create Your Cloud Workspace +## Krok 1: Vytvořte svůj cloudový pracovní prostor -1. Go to [app.twenty.com](https://app.twenty.com) and create a new workspace -2. Complete the initial setup wizard -3. Note your new workspace URL +1. Přejděte na [app.twenty.com](https://app.twenty.com) a vytvořte nový pracovní prostor +2. Dokončete úvodní nastavení pomocí průvodce +3. Poznamenejte si URL vašeho nového pracovního prostoru -## Step 2: Recreate Your Data Model +## Krok 2: Znovu vytvořte svůj datový model -Before importing data, recreate your custom objects and fields: +Před importem dat znovu vytvořte své vlastní objekty a pole: -1. Go to **Settings → Data Model** in your cloud instance -2. Create custom objects that match your self-hosted setup -3. Add custom fields to standard and custom objects -4. Configure field settings (unique, required, etc.) +1. Přejděte ve své cloudové instanci do **Settings → Data Model** +2. Vytvořte vlastní objekty, které odpovídají vašemu nastavení na vlastním serveru +3. Přidejte vlastní pole ke standardním i vlastním objektům +4. Nastavte vlastnosti polí (jedinečné, povinné apod.) -Take screenshots of your self-hosted data model for reference, or keep both instances open side by side. +Pořiďte si pro referenci snímky obrazovky vašeho datového modelu na vlastním serveru, nebo mějte obě instance otevřené vedle sebe. -## Step 3: Invite All Users +## Krok 3: Pozvěte všechny uživatele - **Critical: Invite users BEFORE importing data.** + **Důležité: Pozvěte uživatele PŘED importem dat.** - Users must accept their invitations before you import any records that reference them (like Account Owner fields). If users don't exist yet, those relations cannot be mapped. + Uživatelé musí přijmout své pozvánky, než importujete jakékoli záznamy, které na ně odkazují (například pole Account Owner). Pokud uživatelé ještě neexistují, tyto relace nelze namapovat. -1. Go to **Settings → Members** in your cloud instance -2. Invite all team members who had accounts on self-hosted -3. **Wait for everyone to accept** their invitation -4. Verify all users appear in your Members list +1. Přejděte ve své cloudové instanci do **Settings → Members** +2. Pozvěte všechny členy týmu, kteří měli účty v instanci hostované na vlastním serveru +3. **Počkejte, až všichni přijmou** své pozvání +4. Ověřte, že se všichni uživatelé zobrazují v seznamu Members -## Step 4: Export Data from Self-Hosted +## Krok 4: Export dat z instance hostované na vlastním serveru -Export each object from your self-hosted instance: +Exportujte každý objekt ze své instance hostované na vlastním serveru: -1. Navigate to each object (Companies, People, Opportunities, etc.) -2. Configure the view to show **all columns** you want to migrate -3. Click **⋮ → Export view** -4. Save each CSV file with a clear name (e.g., `companies-export.csv`) +1. Přejděte ke každému objektu (Společnosti, Lidé, Příležitosti atd.) +2. Nastavte zobrazení tak, aby zobrazovalo **všechny sloupce**, které chcete migrovat +3. Klikněte na **⋮ → Export view** +4. Uložte každý soubor CSV s jasným názvem (např. `companies-export.csv`) -**Export in this order** (for reference when importing): +**Exportujte v tomto pořadí** (pro referenci při importu): 1. Společnosti 2. Osoby 3. Příležitosti -4. Custom objects (following their dependencies) -5. Tasks, Notes +4. Vlastní objekty (podle jejich závislostí) +5. Úkoly, Poznámky -## Step 5: Update Workspace Member References +## Krok 5: Aktualizujte reference na členy pracovního prostoru -The exported CSVs contain user IDs from your self-hosted instance. These IDs won't match your cloud instance, so you need to replace them with emails. +Exportované soubory CSV obsahují ID uživatelů z vaší instance hostované na vlastním serveru. Tyto ID nebudou odpovídat vaší cloudové instanci, proto je musíte nahradit e-mailovými adresami. -**For each CSV file with user references (Owner, Assignee, etc.):** +**Pro každý soubor CSV s referencemi na uživatele (Owner, Assignee atd.):** -1. Open the CSV in a spreadsheet application -2. Add a new column next to each user ID column (e.g., `accountOwnerEmail` next to `accountOwnerId`) -3. Fill in the **email address** of each user -4. You can delete the old ID column or leave it (it will be skipped during import) +1. Otevřete soubor CSV v tabulkovém editoru +2. Přidejte nový sloupec vedle každého sloupce s ID uživatele (např. `accountOwnerEmail` vedle `accountOwnerId`) +3. Vyplňte **e-mailovou adresu** každého uživatele +4. Můžete starý sloupec s ID smazat, nebo ho ponechat (při importu bude přeskočen) **Příklad:** @@ -83,89 +83,89 @@ name,domain,accountOwnerEmail Acme Corp,https://acme.com,john@yourcompany.com ``` -Use the same email addresses that users used to accept their cloud workspace invitation. +Použijte stejné e-mailové adresy, které uživatelé použili k přijetí pozvánky do cloudového pracovního prostoru. -## Step 6: Plan Your Import Order +## Krok 6: Naplánujte pořadí importu -Import files in the correct order to maintain relationships: +Importujte soubory ve správném pořadí, abyste zachovali relace: -1. **Companies** first (no dependencies) -2. **People** second (link to Companies) -3. **Opportunities** third (link to Companies and People) -4. **Custom objects** (following their dependencies) -5. **Tasks and Notes** last (link to other records) +1. **Společnosti** jako první (bez závislostí) +2. **Lidé** jako druzí (propojení na společnosti) +3. **Příležitosti** jako třetí (propojené se společnostmi a lidmi) +4. **Vlastní objekty** (podle jejich závislostí) +5. **Úkoly a poznámky** nakonec (propojení na další záznamy) -See [How to Import Relations](/l/cs/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv) for details on maintaining relationships. +Viz [Jak importovat relace](/l/cs/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv) pro podrobnosti o zachování relací. -## Step 7: Import to Cloud +## Krok 7: Import do cloudu -For each CSV file, in order: +Pro každý soubor CSV, v daném pořadí: -1. Navigate to the object in your cloud instance -2. Click **⋮ → Import records** -3. Upload the CSV file -4. Map columns to fields: - * Map user email columns to the appropriate relation fields - * Map other columns as usual -5. Review and fix any errors -6. Confirm the import -7. Verify a few records before proceeding to the next file +1. Přejděte k objektu ve vaší cloudové instanci +2. Klikněte na **⋮ → Import records** +3. Nahrajte soubor CSV +4. Namapujte sloupce na pole: + * Namapujte sloupce s e-maily uživatelů na příslušná relační pole + * Ostatní sloupce namapujte obvyklým způsobem +5. Zkontrolujte a opravte případné chyby +6. Potvrďte import +7. Ověřte několik záznamů, než přejdete k dalšímu souboru -## Step 8: Recreate Configuration +## Krok 8: Znovu vytvořte konfiguraci -After importing data, manually recreate: +Po importu dat ručně znovu vytvořte: ### Zobrazení -* Recreate saved views with filters, sorts, and column configurations -* Set up any kanban or calendar views +* Znovu vytvořte uložená zobrazení s filtry, řazením a nastavením sloupců +* Nastavte případná kanbanová nebo kalendářová zobrazení ### Pracovní postupy -* Recreate automations in **Settings → Workflows** -* Test each workflow before relying on it +* Znovu vytvořte automatizace v **Settings → Workflows** +* Otestujte každý pracovní postup, než se na něj spolehnete -### Roles and Permissions +### Role a oprávnění -* Configure roles in **Settings → Roles** -* Assign users to appropriate roles +* Nakonfigurujte role v **Settings → Roles** +* Přiřaďte uživatele ke vhodným rolím ### Integrace -* Reconnect email and calendar sync for each user -* Reconfigure any API integrations with new API keys +* Znovu připojte synchronizaci e-mailu a kalendáře pro každého uživatele +* Znovu nakonfigurujte případné integrace API s novými klíči API ## Post-migrační kontrolní seznam -All data imported successfully -Relations between objects working correctly -User assignments (Owner, Assignee) mapped correctly -Views recreated -Workflows recreated and tested -Roles and permissions configured -Email/calendar sync reconnected -API integrations updated with new keys +Všechna data byla úspěšně importována +Relace mezi objekty fungují správně +Přiřazení uživatelů (Owner, Assignee) je namapováno správně +Zobrazení znovu vytvořena +Pracovní postupy znovu vytvořeny a otestovány +Role a oprávnění nakonfigurovány +Synchronizace e-mailu/kalendáře znovu připojena +Integrace API aktualizovány s novými klíči -## FAQ +## Časté dotazy - - Not currently. Workflows must be recreated manually in your cloud instance. + + V tuto chvíli ne. Pracovní postupy je nutné ve vaší cloudové instanci znovu vytvořit ručně. - - File attachments are not included in CSV exports. You'll need to re-upload any attachments manually, migrate them via API or contact our team for assistance with large migrations. + + Přílohy nejsou součástí exportů CSV. Přílohy budete muset nahrát znovu ručně, migrovat je přes API nebo kontaktovat náš tým pro pomoc s rozsáhlými migracemi. - - Yes, we recommend keeping your self-hosted instance running until you've verified the cloud migration is complete. Just be careful not to create new data in both places. + + Ano, doporučujeme ponechat vaši instanci na vlastním serveru v provozu, dokud neověříte, že migrace do cloudu je dokončena. Jen si dejte pozor, abyste nevytvářeli nová data na obou místech. - - Records referencing that user will fail to import or the relation will be empty. Ensure all users accept invitations before importing data. + + Záznamy, které na daného uživatele odkazují, se nepodaří importovat, nebo bude relace prázdná. Ujistěte se, že všichni uživatelé přijali pozvánky před importem dat. ## Potřebujete pomoc? -For complex migrations or large datasets, contact us at [contact@twenty.com](mailto:contact@twenty.com) or explore our [Implementation Services](/l/cs/user-guide/getting-started/capabilities/implementation-services). +U složitých migrací nebo velkých datových sad nás kontaktujte na [contact@twenty.com](mailto:contact@twenty.com) nebo si prohlédněte naše [Implementační služby](/l/cs/user-guide/getting-started/capabilities/implementation-services). diff --git a/packages/twenty-docs/l/cs/user-guide/settings/overview.mdx b/packages/twenty-docs/l/cs/user-guide/settings/overview.mdx index 21461cd38d..50f2631996 100644 --- a/packages/twenty-docs/l/cs/user-guide/settings/overview.mdx +++ b/packages/twenty-docs/l/cs/user-guide/settings/overview.mdx @@ -55,13 +55,13 @@ Přidejte členy týmu do svého pracovního prostoru: ## Kontrolní seznam nastavení pracovního prostoru * Název a logo pracovního prostoru nastaveny -* Time zone and date format set -* Email and calendar connected -* Team members invited -* Roles and permissions configured +* Časové pásmo a formát data nastaveny +* E-mail a kalendář propojeny +* Členové týmu pozváni +* Role a oprávnění nakonfigurovány ## Další kroky -* [Workspace settings](/l/cs/user-guide/settings/capabilities/workspace-settings) -* [Profile settings](/l/cs/user-guide/settings/capabilities/profile-settings) -* [Experience settings](/l/cs/user-guide/settings/capabilities/experience-settings) +* [Nastavení pracovního prostoru](/l/cs/user-guide/settings/capabilities/workspace-settings) +* [Nastavení profilu](/l/cs/user-guide/settings/capabilities/profile-settings) +* [Nastavení prostředí](/l/cs/user-guide/settings/capabilities/experience-settings) diff --git a/packages/twenty-docs/l/cs/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx b/packages/twenty-docs/l/cs/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx index e24b1ccdf9..68a8a02b5e 100644 --- a/packages/twenty-docs/l/cs/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx +++ b/packages/twenty-docs/l/cs/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx @@ -1,120 +1,120 @@ --- -title: Set Up a Sales Pipeline -description: Configure your sales pipeline to track opportunities through stages. +title: Nastavte prodejní pipeline +description: Nakonfigurujte svou prodejní pipeline pro sledování příležitostí napříč fázemi. --- import { VimeoEmbed } from '/snippets/vimeo-embed.mdx'; -A sales pipeline in Twenty is a Kanban view of your Opportunities object, where each column represents a stage in your sales process. +Prodejní pipeline v Twenty je kanbanové zobrazení vašeho objektu Příležitosti, kde každý sloupec představuje fázi ve vašem prodejním procesu. -## Step 1: Configure Your Stages +## Krok 1: Nakonfigurujte své fáze -Stages are defined in the Opportunities object's **Stage** field. +Fáze jsou definovány v objektu Příležitosti v poli **Stage**. -1. Go to **Settings → Data Model** -2. Select **Opportunities** -3. Find and click the **Stage** field -4. Add, remove, or rename stages to match your process +1. Přejděte na **Nastavení → Datový model** +2. Vyberte **Příležitosti** +3. Najděte a klikněte na pole **Stage** +4. Přidejte, odeberte nebo přejmenujte fáze tak, aby odpovídaly vašemu procesu - + -### Recommended Stages +### Doporučené fáze -| Fáze | Purpose | -| --------------- | ----------------------------------- | -| **New** | Fresh opportunities just identified | -| **Qualified** | Confirmed as a good fit | -| **Meeting** | Engaged in discussions | -| **Proposal** | Proposal sent | -| **Negotiation** | Working on terms | -| **Closed Won** | Deal successful | -| **Closed Lost** | Deal unsuccessful | +| Fáze | Účel | +| ----------------------- | -------------------------------- | +| **Nový** | Nově identifikované příležitosti | +| **Kvalifikovaný** | Potvrzeno jako vhodné | +| **Schůzka** | Probíhají jednání | +| **Nabídka** | Nabídka odeslána | +| **Vyjednávání** | Dolaďování podmínek | +| **Uzavřeno – vyhráno** | Obchod úspěšný | +| **Uzavřeno – prohráno** | Obchod neúspěšný | - **5-7 stages is optimal.** Too many stages makes the pipeline hard to scan; too few loses visibility into deal progress. + **5–7 fází je optimálních.** Příliš mnoho fází ztěžuje rychlé procházení pipeline; příliš málo snižuje přehled o postupu obchodu. -## Step 2: Create a Pipeline View +## Krok 2: Vytvořte zobrazení pipeline -1. Go to **Opportunities** -2. Click the view dropdown → **+ Add view** -3. Name it "Sales Pipeline" -4. Click **Create** -5. Open **Options** and select **Kanban** as the layout +1. Přejděte na **Příležitosti** +2. Klikněte na rozbalovací nabídku zobrazení → **+ Přidat zobrazení** +3. Pojmenujte jej "Sales Pipeline" +4. Klikněte na **Vytvořit** +5. Otevřete **Možnosti** a jako rozvržení vyberte **Kanban** -The view automatically uses the Stage field for columns. +Zobrazení automaticky používá pro sloupce pole Stage. -## Step 3: Configure Your View +## Krok 3: Nakonfigurujte své zobrazení -### Show Key Fields +### Zobrazte klíčová pole -1. Click **Options → Fields** -2. Look for fields in the "Hidden Fields" section -3. Click the **eye icon** to display: Company, Amount, Close Date, Owner +1. Klikněte na **Možnosti → Pole** +2. Vyhledejte pole v sekci "Skrytá pole" +3. Klikněte na **ikonu oka** a zobrazte: Společnost, Částka, Datum uzavření, Vlastník -### Enable Aggregations +### Povolte agregace -Show totals at the top of each column: +Zobrazte součty v horní části každého sloupce: -1. Click the number displayed next to a Stage name at the top of a column -2. Select the aggregation type (Count, Sum, Average, etc.) -3. Choose the field to aggregate (e.g., Amount) +1. Klikněte na číslo zobrazené vedle názvu fáze v horní části sloupce +2. Vyberte typ agregace (Počet, Součet, Průměr atd.) +3. Zvolte pole pro agregaci (např. Částka) -**Example:** Show total deal value per stage by aggregating Amount with Sum. +**Příklad:** Zobrazte celkovou hodnotu obchodu podle fází agregováním pole Částka pomocí Součtu. -### Use Compact View (Optional) +### Použijte kompaktní zobrazení (volitelné) -For a high-level overview with minimal card content: +Pro přehled na vysoké úrovni s minimálním obsahem karet: -1. Click **Options** -2. Turn on the toggle for **Compact view** +1. Klikněte na **Možnosti** +2. Zapněte přepínač **Kompaktní zobrazení** -## Step 4: Create Personal and Team Views +## Krok 4: Vytvořte osobní a týmová zobrazení -### "My Pipeline" +### "Moje pipeline" -* **Filter**: Owner = Me -* **Visibility**: Unlisted (personal view) +* **Filtr**: Vlastník = Já +* **Viditelnost**: Neveřejné (osobní zobrazení) -### "Team Pipeline" +### "Týmová pipeline" -* **Filter**: None (show all) -* **Visibility**: Workspace (shared view) +* **Filtr**: Žádný (zobrazit vše) +* **Viditelnost**: Workspace (sdílené zobrazení) -### "Closing This Month" +### "Uzavření tento měsíc" -* **Type**: Table -* **Filter**: Close Date = This month, Stage ≠ Closed Won, Stage ≠ Closed Lost -* **Sort**: Close Date ascending +* **Typ**: Tabulka +* **Filtr**: Datum uzavření = Tento měsíc, Stage ≠ Closed Won, Stage ≠ Closed Lost +* **Řazení**: Datum uzavření vzestupně -## Working with Opportunities +## Práce s příležitostmi -### Creating Opportunities +### Vytváření příležitostí -* Click **+ New** in the Opportunities view -* Or click **+** in a specific stage column +* Klikněte na **+ New** v zobrazení Příležitostí +* Nebo klikněte na **+** ve sloupci konkrétní fáze -### Moving Through Stages +### Přesun mezi fázemi -Drag and drop opportunity cards between columns to update their stage. +Přetažením karet příležitostí mezi sloupci aktualizujte jejich fázi. - + ## Osvědčené postupy -### Pipeline Hygiene +### Hygiena pipeline -* Update deals daily as they progress -* Move or close stale deals promptly -* Keep close dates realistic +* Denně aktualizujte obchody podle jejich postupu +* Zastaralé obchody rychle přesouvejte nebo uzavírejte +* Udržujte realistická data uzavření -### Stage Discipline +### Disciplína fází -* Define clear criteria for each stage -* Move deals promptly when criteria are met -* Don't let deals sit in stages too long +* Definujte jasná kritéria pro každou fázi +* Jakmile jsou kritéria splněna, obchody neprodleně přesouvejte +* Nenechávejte obchody ve fázích příliš dlouho -## Related +## Související -* [Kanban Views](/l/cs/user-guide/views-pipelines/capabilities/kanban-views) — aggregations and compact view -* [Filters and Sorting](/l/cs/user-guide/views-pipelines/capabilities/filters-and-sorting) — creating filtered views +* [Kanban zobrazení](/l/cs/user-guide/views-pipelines/capabilities/kanban-views) — agregace a kompaktní zobrazení +* [Filtry a řazení](/l/cs/user-guide/views-pipelines/capabilities/filters-and-sorting) — tvorba filtrovaných zobrazení diff --git a/packages/twenty-docs/l/cs/user-guide/workflows/capabilities/use-branches-in-workflows.mdx b/packages/twenty-docs/l/cs/user-guide/workflows/capabilities/use-branches-in-workflows.mdx index 09e2c9ca93..91ec286b27 100644 --- a/packages/twenty-docs/l/cs/user-guide/workflows/capabilities/use-branches-in-workflows.mdx +++ b/packages/twenty-docs/l/cs/user-guide/workflows/capabilities/use-branches-in-workflows.mdx @@ -1,90 +1,90 @@ --- -title: Use Branches in Workflows -description: Understand how branches work and how to control which path is executed. +title: Používání větví v pracovních postupech +description: Pochopte, jak větve fungují a jak řídit, která cesta se provede. --- -## How Branches Work +## Jak větve fungují -In the workflow editor, you can create multiple paths (branches) going out from a single node. This allows you to build complex automations with different outcomes. +V editoru pracovních postupů můžete vytvářet více cest (větví) vycházejících z jediného uzlu. To vám umožní vytvářet složité automatizace s různými výsledky. -**Important**: When a workflow runs, **all branches execute in parallel by default**. There is no built-in "if/else" logic to choose one branch over another—every path will run simultaneously. +**Důležité**: Když se pracovní postup spustí, **všechny větve se ve výchozím nastavení spouštějí paralelně**. Neexistuje žádná vestavěná "if/else" logika pro výběr jedné větve před jinou—každá cesta poběží současně. -## Controlling Which Branch Runs +## Řízení, která větev se spustí -To execute only one branch based on specific conditions, **add a Filter node at the beginning of each branch**. +Chcete-li provést pouze jednu větev na základě konkrétních podmínek, **přidejte na začátek každé větve uzel Filter**. -### Example Setup +### Ukázkové nastavení -1. Create your workflow with multiple branches from a single node -2. Add a **Filter** node as the first step in each branch -3. Set conditions on each Filter to determine when that branch should continue -4. Only the branch(es) whose Filter conditions are met will proceed +1. Vytvořte pracovní postup s více větvemi z jednoho uzlu +2. Přidejte uzel **Filter** jako první krok v každé větvi +3. Na každém uzlu Filter nastavte podmínky, které určují, kdy má daná větev pokračovat +4. Pokračovat bude pouze větev (případně větve), u níž jsou splněny podmínky uzlu Filter -### How Filters Work +### Jak fungují filtry -* If the Filter condition is **met**: The branch continues executing -* If the Filter condition is **not met**: The branch stops at the Filter node +* Pokud je podmínka Filter **splněna**: Větev pokračuje v provádění +* Pokud podmínka Filter **není splněna**: Větev se zastaví na uzlu Filter -This effectively creates conditional logic where only the appropriate branch runs based on your data. +Tím efektivně vytvoříte podmíněnou logiku, v níž se na základě vašich dat spustí pouze příslušná větev. -## Example: Route by Deal Size +## Příklad: Směrování podle výše obchodu -**Scenario**: When a deal is closed, send different notifications based on deal size. +**Scénář**: Když je obchod uzavřen, odešlete různé oznámení podle výše obchodu. -1. **Trigger**: Opportunity updated (Stage = Closed Won) -2. **Branch 1**: Filter for Amount > $10,000 → Send Slack message to #big-deals -3. **Branch 2**: Filter for Amount ≤ $10,000 → Send email to sales manager +1. **Spouštěč**: Příležitost aktualizována (Fáze = Uzavřeno/Vyhráno) +2. **Větev 1**: Filter pro částku > 10 000 $ → Odeslat zprávu na Slack do #big-deals +3. **Větev 2**: Filter pro částku ≤ 10 000 $ → Odeslat e-mail obchodnímu manažerovi -Both branches start, but only the one matching the deal amount will continue past its Filter. +Obě větve se spustí, ale za svým uzlem Filter bude pokračovat pouze ta, která odpovídá částce obchodu. -## Creating Branches +## Vytváření větví - To create a new branch from an existing step, click the **+** button on the step and add your action. You can add multiple branches by clicking **+** multiple times. + Chcete-li vytvořit novou větev z existujícího kroku, klikněte na tlačítko **+** u kroku a přidejte svou akci. Více větví můžete přidat opakovaným kliknutím na **+**. -1. In the workflow editor, select the step you want to branch from -2. Click the **+** button to add an action -3. This creates one branch -4. Click **+** again on the same step to create additional branches -5. Each branch can have its own sequence of actions +1. V editoru pracovních postupů vyberte krok, ze kterého chcete větvit +2. Klikněte na **+** pro přidání akce +3. Tím vytvoříte jednu větev +4. Pro vytvoření dalších větví klikněte znovu na **+** u stejného kroku +5. Každá větev může mít vlastní posloupnost akcí -## Merging Branches Back Together +## Sloučení větví zpět do jedné -After parallel branches complete their work, you can merge them back into a single path: +Po dokončení práce paralelních větví je můžete sloučit zpět do jedné cesty: -1. Complete your branched actions -2. Add a new step that should run after all branches -3. Drag a connection from the last step of each branch to this new step -4. The merged step waits for all connected branches to complete before executing +1. Dokončete akce ve větvích +2. Přidejte nový krok, který se má spustit po všech větvích +3. Přetáhněte spojení z posledního kroku každé větve do tohoto nového kroku +4. Sloučený krok před spuštěním počká na dokončení všech připojených větví -### Example: Process Then Notify +### Příklad: Zpracovat a poté upozornit ``` -Trigger +Spouštěč │ - ├── Branch A: Update Customer Record + ├── Větev A: Aktualizovat záznam zákazníka │ - └── Branch B: Create Support Ticket + └── Větev B: Vytvořit tiket podpory ↘ ↙ - Merged Step: Send Confirmation Email + Sloučený krok: Odeslat potvrzovací e-mail ``` -The confirmation email sends only after both the customer update and ticket creation are done. +Potvrzovací e-mail se odešle až po dokončení aktualizace zákazníka i vytvoření tiketu. ## Osvědčené postupy -* Always use **Filter nodes** at the start of branches when you want conditional execution -* Keep branch conditions **mutually exclusive** to avoid duplicate actions -* Test your workflows with different data to ensure the correct branches run -* **Rename branch steps** descriptively so it's clear what each path does -* **Merge branches** when you need a final action after parallel processing +* Na začátku větví vždy používejte **uzly Filter**, když chcete podmíněné spouštění +* Podmínky větví udržujte **vzájemně se vylučující**, abyste předešli duplicitním akcím +* Testujte své pracovní postupy s různými daty, abyste měli jistotu, že se spouštějí správné větve +* **Přejmenujte kroky ve větvích** popisně, aby bylo jasné, co která cesta dělá +* **Sloučte větve**, když po paralelním zpracování potřebujete závěrečnou akci -## Related +## Související -* [Workflows FAQ](/l/cs/user-guide/workflows/how-tos/need-more-help/workflows-faq) — answers about parallel execution -* [Workflow Actions](/l/cs/user-guide/workflows/capabilities/workflow-actions) — available actions for branches +* [Často kladené dotazy k pracovním postupům](/l/cs/user-guide/workflows/how-tos/need-more-help/workflows-faq) — odpovědi týkající se paralelního provádění +* [Akce pracovních postupů](/l/cs/user-guide/workflows/capabilities/workflow-actions) — dostupné akce pro větve diff --git a/packages/twenty-docs/l/de/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx b/packages/twenty-docs/l/de/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx index b7da106e63..ab5767bd56 100644 --- a/packages/twenty-docs/l/de/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx +++ b/packages/twenty-docs/l/de/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx @@ -1,73 +1,73 @@ --- title: Migration von Selbstgehostet zu Cloud -description: Step-by-step guide to migrate your Twenty self-hosted instance to Twenty Cloud. +description: Schritt-für-Schritt-Anleitung zur Migration Ihrer selbstgehosteten Twenty-Instanz zu Twenty Cloud. --- ## Übersicht -This guide walks you through migrating your data from a Twenty self-hosted instance to Twenty Cloud. The process involves setting up your cloud workspace, exporting your data, and re-importing it. +Diese Anleitung führt Sie durch die Migration Ihrer Daten von einer selbstgehosteten Twenty-Instanz zu Twenty Cloud. Der Prozess umfasst das Einrichten Ihres Cloud-Arbeitsbereichs, das Exportieren Ihrer Daten und deren erneutes Importieren. -Views, workflows, and roles must be recreated manually after migration. Plan time for this configuration work. +Ansichten, Workflows und Rollen müssen nach der Migration manuell neu erstellt werden. Planen Sie Zeit für diese Konfigurationsarbeiten ein. -## Step 1: Create Your Cloud Workspace +## Schritt 1: Erstellen Sie Ihren Cloud-Arbeitsbereich -1. Go to [app.twenty.com](https://app.twenty.com) and create a new workspace -2. Complete the initial setup wizard -3. Note your new workspace URL +1. Gehen Sie zu [app.twenty.com](https://app.twenty.com) und erstellen Sie einen neuen Arbeitsbereich +2. Schließen Sie den Einrichtungsassistenten ab +3. Notieren Sie sich die URL Ihres neuen Arbeitsbereichs -## Step 2: Recreate Your Data Model +## Schritt 2: Datenmodell neu erstellen -Before importing data, recreate your custom objects and fields: +Erstellen Sie vor dem Import der Daten Ihre benutzerdefinierten Objekte und Felder neu: -1. Go to **Settings → Data Model** in your cloud instance -2. Create custom objects that match your self-hosted setup -3. Add custom fields to standard and custom objects -4. Configure field settings (unique, required, etc.) +1. Gehen Sie in Ihrer Cloud-Instanz zu **Einstellungen → Datenmodell** +2. Erstellen Sie benutzerdefinierte Objekte, die Ihrer selbstgehosteten Konfiguration entsprechen +3. Fügen Sie Standard- und benutzerdefinierten Objekten benutzerdefinierte Felder hinzu +4. Konfigurieren Sie die Feldeinstellungen (eindeutig, erforderlich usw.) -Take screenshots of your self-hosted data model for reference, or keep both instances open side by side. +Machen Sie Screenshots Ihres selbstgehosteten Datenmodells als Referenz oder halten Sie beide Instanzen nebeneinander geöffnet. -## Step 3: Invite All Users +## Schritt 3: Alle Benutzer einladen - **Critical: Invite users BEFORE importing data.** + **Wichtig: Laden Sie Benutzer ein, BEVOR Sie Daten importieren.** - Users must accept their invitations before you import any records that reference them (like Account Owner fields). If users don't exist yet, those relations cannot be mapped. + Benutzer müssen ihre Einladungen annehmen, bevor Sie Datensätze importieren, die auf sie verweisen (z. B. das Feld 'Account Owner'). Wenn Benutzer noch nicht vorhanden sind, können diese Beziehungen nicht zugeordnet werden. -1. Go to **Settings → Members** in your cloud instance -2. Invite all team members who had accounts on self-hosted -3. **Wait for everyone to accept** their invitation -4. Verify all users appear in your Members list +1. Gehen Sie in Ihrer Cloud-Instanz zu **Einstellungen → Mitglieder** +2. Laden Sie alle Teammitglieder ein, die in der selbstgehosteten Instanz Konten hatten +3. **Warten Sie, bis alle** ihre Einladung angenommen haben +4. Überprüfen Sie, ob alle Benutzer in Ihrer Mitgliederliste erscheinen -## Step 4: Export Data from Self-Hosted +## Schritt 4: Daten aus der selbstgehosteten Instanz exportieren -Export each object from your self-hosted instance: +Exportieren Sie jedes Objekt aus Ihrer selbstgehosteten Instanz: -1. Navigate to each object (Companies, People, Opportunities, etc.) -2. Configure the view to show **all columns** you want to migrate -3. Click **⋮ → Export view** -4. Save each CSV file with a clear name (e.g., `companies-export.csv`) +1. Navigieren Sie zu jedem Objekt (Unternehmen, Personen, Opportunities usw.) +2. Konfigurieren Sie die Ansicht so, dass **alle Spalten** angezeigt werden, die Sie migrieren möchten +3. Klicken Sie auf **⋮ → Ansicht exportieren** +4. Speichern Sie jede CSV-Datei mit einem eindeutigen Namen (z. B. `companies-export.csv`) -**Export in this order** (for reference when importing): +**Exportieren Sie in dieser Reihenfolge** (als Referenz für den Import): 1. Unternehmen 2. Personen 3. Opportunities -4. Custom objects (following their dependencies) -5. Tasks, Notes +4. Benutzerdefinierte Objekte (entsprechend ihren Abhängigkeiten) +5. Aufgaben, Notizen -## Step 5: Update Workspace Member References +## Schritt 5: Verweise auf Arbeitsbereichsmitglieder aktualisieren -The exported CSVs contain user IDs from your self-hosted instance. These IDs won't match your cloud instance, so you need to replace them with emails. +Die exportierten CSVs enthalten Benutzer-IDs aus Ihrer selbstgehosteten Instanz. Diese IDs stimmen nicht mit Ihrer Cloud-Instanz überein, daher müssen Sie sie durch E-Mail-Adressen ersetzen. -**For each CSV file with user references (Owner, Assignee, etc.):** +**Für jede CSV-Datei mit Benutzerverweisen (Owner, Assignee usw.):** -1. Open the CSV in a spreadsheet application -2. Add a new column next to each user ID column (e.g., `accountOwnerEmail` next to `accountOwnerId`) -3. Fill in the **email address** of each user -4. You can delete the old ID column or leave it (it will be skipped during import) +1. Öffnen Sie die CSV-Datei in einem Tabellenkalkulationsprogramm +2. Fügen Sie neben jeder Benutzer-ID-Spalte eine neue Spalte hinzu (z. B. `accountOwnerEmail` neben `accountOwnerId`) +3. Tragen Sie die **E-Mail-Adresse** jedes Benutzers ein +4. Sie können die alte ID-Spalte löschen oder belassen (sie wird beim Import übersprungen) -**Example:** +**Beispiel:** Vor: @@ -83,89 +83,89 @@ name,domain,accountOwnerEmail Acme Corp,https://acme.com,john@yourcompany.com ``` -Use the same email addresses that users used to accept their cloud workspace invitation. +Verwenden Sie dieselben E-Mail-Adressen, mit denen die Benutzer die Einladung zu Ihrem Cloud-Arbeitsbereich angenommen haben. -## Step 6: Plan Your Import Order +## Schritt 6: Importreihenfolge planen -Import files in the correct order to maintain relationships: +Importieren Sie die Dateien in der richtigen Reihenfolge, um Beziehungen beizubehalten: -1. **Companies** first (no dependencies) -2. **People** second (link to Companies) -3. **Opportunities** third (link to Companies and People) -4. **Custom objects** (following their dependencies) -5. **Tasks and Notes** last (link to other records) +1. Zuerst **Unternehmen** (keine Abhängigkeiten) +2. **Personen** an zweiter Stelle (mit Unternehmen verknüpft) +3. **Opportunities** an dritter Stelle (mit Unternehmen und Personen verknüpft) +4. **Benutzerdefinierte Objekte** (entsprechend ihren Abhängigkeiten) +5. Zuletzt **Aufgaben und Notizen** (mit anderen Datensätzen verknüpft) -See [How to Import Relations](/l/de/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv) for details on maintaining relationships. +Siehe [So importieren Sie Beziehungen](/l/de/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv) für Details zum Beibehalten von Beziehungen. -## Step 7: Import to Cloud +## Schritt 7: In die Cloud importieren -For each CSV file, in order: +Führen Sie Folgendes der Reihe nach für jede CSV-Datei aus: -1. Navigate to the object in your cloud instance -2. Click **⋮ → Import records** -3. Upload the CSV file -4. Map columns to fields: - * Map user email columns to the appropriate relation fields - * Map other columns as usual -5. Review and fix any errors -6. Confirm the import -7. Verify a few records before proceeding to the next file +1. Navigieren Sie in Ihrer Cloud-Instanz zum Objekt +2. Klicken Sie auf **⋮ → Datensätze importieren** +3. Laden Sie die CSV-Datei hoch +4. Ordnen Sie die Spalten den Feldern zu: + * Ordnen Sie die E-Mail-Spalten der Benutzer den entsprechenden Beziehungsfeldern zu + * Ordnen Sie andere Spalten wie üblich zu +5. Überprüfen und beheben Sie eventuelle Fehler +6. Bestätigen Sie den Import +7. Überprüfen Sie einige Datensätze, bevor Sie mit der nächsten Datei fortfahren -## Step 8: Recreate Configuration +## Schritt 8: Konfiguration neu erstellen -After importing data, manually recreate: +Erstellen Sie nach dem Import der Daten manuell neu: ### Ansichten -* Recreate saved views with filters, sorts, and column configurations -* Set up any kanban or calendar views +* Erstellen Sie gespeicherte Ansichten mit Filtern, Sortierungen und Spaltenkonfigurationen neu +* Richten Sie ggf. Kanban- oder Kalenderansichten ein ### Workflows -* Recreate automations in **Settings → Workflows** -* Test each workflow before relying on it +* Erstellen Sie Automatisierungen in **Einstellungen → Workflows** neu +* Testen Sie jeden Workflow, bevor Sie sich darauf verlassen -### Roles and Permissions +### Rollen und Berechtigungen -* Configure roles in **Settings → Roles** -* Assign users to appropriate roles +* Konfigurieren Sie Rollen in **Einstellungen → Rollen** +* Weisen Sie Benutzer den entsprechenden Rollen zu ### Integrationen -* Reconnect email and calendar sync for each user -* Reconfigure any API integrations with new API keys +* Stellen Sie für jeden Benutzer die E-Mail- und Kalendersynchronisierung wieder her +* Konfigurieren Sie alle API-Integrationen mit neuen API-Schlüsseln neu ## Checkliste nach der Migration -All data imported successfully -Relations between objects working correctly -User assignments (Owner, Assignee) mapped correctly -Views recreated -Workflows recreated and tested -Roles and permissions configured -Email/calendar sync reconnected -API integrations updated with new keys +Alle Daten erfolgreich importiert +Beziehungen zwischen Objekten funktionieren korrekt +Benutzerzuweisungen (Owner, Assignee) korrekt zugeordnet +Ansichten neu erstellt +Workflows neu erstellt und getestet +Rollen und Berechtigungen konfiguriert +E-Mail-/Kalendersynchronisierung wiederhergestellt +API-Integrationen mit neuen Schlüsseln aktualisiert ## FAQ - - Not currently. Workflows must be recreated manually in your cloud instance. + + Derzeit nicht. Workflows müssen in Ihrer Cloud-Instanz manuell neu erstellt werden. - - File attachments are not included in CSV exports. You'll need to re-upload any attachments manually, migrate them via API or contact our team for assistance with large migrations. + + Dateianhänge sind in CSV-Exporten nicht enthalten. Sie müssen Anhänge manuell erneut hochladen, sie über die API migrieren oder unser Team für Unterstützung bei großen Migrationen kontaktieren. - - Yes, we recommend keeping your self-hosted instance running until you've verified the cloud migration is complete. Just be careful not to create new data in both places. + + Ja, wir empfehlen, Ihre selbstgehostete Instanz weiter auszuführen, bis Sie überprüft haben, dass die Cloud-Migration abgeschlossen ist. Achten Sie darauf, nicht an beiden Orten neue Daten zu erstellen. - - Records referencing that user will fail to import or the relation will be empty. Ensure all users accept invitations before importing data. + + Datensätze, die sich auf diesen Benutzer beziehen, werden nicht importiert oder die Beziehung bleibt leer. Stellen Sie sicher, dass alle Benutzer ihre Einladungen annehmen, bevor Sie Daten importieren. -## Need Help? +## Brauchen Sie Hilfe? -For complex migrations or large datasets, contact us at [contact@twenty.com](mailto:contact@twenty.com) or explore our [Implementation Services](/l/de/user-guide/getting-started/capabilities/implementation-services). +Bei komplexen Migrationen oder großen Datenmengen kontaktieren Sie uns unter [contact@twenty.com](mailto:contact@twenty.com) oder informieren Sie sich über unsere [Implementierungsservices](/l/de/user-guide/getting-started/capabilities/implementation-services). diff --git a/packages/twenty-docs/l/de/user-guide/settings/overview.mdx b/packages/twenty-docs/l/de/user-guide/settings/overview.mdx index bdd2c47de0..055601dd2b 100644 --- a/packages/twenty-docs/l/de/user-guide/settings/overview.mdx +++ b/packages/twenty-docs/l/de/user-guide/settings/overview.mdx @@ -55,13 +55,13 @@ Fügen Sie Ihrem Arbeitsbereich Teammitglieder hinzu: ## Checkliste für Arbeitsbereichseinstellungen * Arbeitsbereichsname und Logo konfiguriert -* Time zone and date format set -* Email and calendar connected -* Team members invited -* Roles and permissions configured +* Zeitzone und Datumsformat festgelegt +* E-Mail und Kalender verbunden +* Teammitglieder eingeladen +* Rollen und Berechtigungen konfiguriert ## Nächste Schritte -* [Workspace settings](/l/de/user-guide/settings/capabilities/workspace-settings) -* [Profile settings](/l/de/user-guide/settings/capabilities/profile-settings) -* [Experience settings](/l/de/user-guide/settings/capabilities/experience-settings) +* [Arbeitsbereichseinstellungen](/l/de/user-guide/settings/capabilities/workspace-settings) +* [Profileinstellungen](/l/de/user-guide/settings/capabilities/profile-settings) +* [Erlebniseinstellungen](/l/de/user-guide/settings/capabilities/experience-settings) diff --git a/packages/twenty-docs/l/de/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx b/packages/twenty-docs/l/de/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx index 45c725e37e..2a3b3ebf91 100644 --- a/packages/twenty-docs/l/de/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx +++ b/packages/twenty-docs/l/de/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx @@ -1,120 +1,120 @@ --- -title: Set Up a Sales Pipeline -description: Configure your sales pipeline to track opportunities through stages. +title: Vertriebspipeline einrichten +description: Konfigurieren Sie Ihre Vertriebspipeline, um Verkaufschancen durch die Phasen zu verfolgen. --- import { VimeoEmbed } from '/snippets/vimeo-embed.mdx'; -A sales pipeline in Twenty is a Kanban view of your Opportunities object, where each column represents a stage in your sales process. +Eine Vertriebspipeline in Twenty ist eine Kanban-Ansicht Ihres Objekts "Opportunities", in der jede Spalte eine Phase Ihres Vertriebsprozesses darstellt. -## Step 1: Configure Your Stages +## Schritt 1: Phasen konfigurieren -Stages are defined in the Opportunities object's **Stage** field. +Phasen werden im Feld **Phase** des Objekts "Opportunities" definiert. -1. Go to **Settings → Data Model** -2. Select **Opportunities** -3. Find and click the **Stage** field -4. Add, remove, or rename stages to match your process +1. Gehen Sie zu **Einstellungen → Datenmodell** +2. Wählen Sie **Opportunities** aus +3. Suchen Sie das Feld **Phase** und klicken Sie darauf +4. Fügen Sie Phasen hinzu, entfernen oder benennen Sie sie um, um Ihren Prozess abzubilden - + -### Recommended Stages +### Empfohlene Phasen -| Phase | Purpose | -| --------------- | ----------------------------------- | -| **New** | Fresh opportunities just identified | -| **Qualified** | Confirmed as a good fit | -| **Meeting** | Engaged in discussions | -| **Proposal** | Proposal sent | -| **Negotiation** | Working on terms | -| **Closed Won** | Deal successful | -| **Closed Lost** | Deal unsuccessful | +| Phase | Zweck | +| ---------------- | ---------------------------------- | +| **Neu** | Neu identifizierte Verkaufschancen | +| **Qualifiziert** | Als geeignet bestätigt | +| **Termin** | In Gesprächen | +| **Angebot** | Angebot gesendet | +| **Verhandlung** | Konditionen werden ausgehandelt | +| **Gewonnen** | Geschäft gewonnen | +| **Verloren** | Geschäft verloren | - **5-7 stages is optimal.** Too many stages makes the pipeline hard to scan; too few loses visibility into deal progress. + **5-7 Phasen sind optimal.** Zu viele Phasen erschweren das Erfassen der Pipeline; zu wenige verringern die Sichtbarkeit des Deal-Fortschritts. -## Step 2: Create a Pipeline View +## Schritt 2: Pipeline-Ansicht erstellen -1. Go to **Opportunities** -2. Click the view dropdown → **+ Add view** -3. Name it "Sales Pipeline" -4. Click **Create** -5. Open **Options** and select **Kanban** as the layout +1. Gehen Sie zu **Opportunities** +2. Klicken Sie auf das Ansichts-Dropdown → **+ Ansicht hinzufügen** +3. Nennen Sie sie "Vertriebspipeline" +4. Klicken Sie auf **Erstellen** +5. Öffnen Sie **Optionen** und wählen Sie **Kanban** als Layout -The view automatically uses the Stage field for columns. +Die Ansicht verwendet automatisch das Feld "Phase" für die Spalten. -## Step 3: Configure Your View +## Schritt 3: Ansicht konfigurieren -### Show Key Fields +### Wichtige Felder anzeigen -1. Click **Options → Fields** -2. Look for fields in the "Hidden Fields" section -3. Click the **eye icon** to display: Company, Amount, Close Date, Owner +1. Klicken Sie auf **Optionen → Felder** +2. Suchen Sie im Abschnitt "Ausgeblendete Felder" nach Feldern +3. Klicken Sie auf das **Augen-Symbol**, um Folgendes anzuzeigen: Unternehmen, Betrag, Abschlussdatum, Eigentümer -### Enable Aggregations +### Aggregationen aktivieren -Show totals at the top of each column: +Summen oben in jeder Spalte anzeigen: -1. Click the number displayed next to a Stage name at the top of a column -2. Select the aggregation type (Count, Sum, Average, etc.) -3. Choose the field to aggregate (e.g., Amount) +1. Klicken Sie auf die Zahl, die oben in einer Spalte neben einem Phasennamen angezeigt wird +2. Wählen Sie den Aggregationstyp (Anzahl, Summe, Durchschnitt usw.) +3. Wählen Sie das zu aggregierende Feld (z. B. Betrag) -**Example:** Show total deal value per stage by aggregating Amount with Sum. +**Beispiel:** Zeigen Sie den Gesamtwert der Geschäfte pro Phase an, indem Sie das Feld Betrag mit Summe aggregieren. -### Use Compact View (Optional) +### Kompaktansicht verwenden (optional) -For a high-level overview with minimal card content: +Für eine grobe Übersicht mit minimalem Karteninhalt: -1. Click **Options** -2. Turn on the toggle for **Compact view** +1. Klicken Sie auf **Optionen** +2. Aktivieren Sie den Schalter für **Kompaktansicht** -## Step 4: Create Personal and Team Views +## Schritt 4: Persönliche und Team-Ansichten erstellen -### "My Pipeline" +### "Meine Pipeline" -* **Filter**: Owner = Me -* **Visibility**: Unlisted (personal view) +* **Filter**: Eigentümer = Ich +* **Sichtbarkeit**: Nicht gelistet (persönliche Ansicht) -### "Team Pipeline" +### "Team-Pipeline" -* **Filter**: None (show all) -* **Visibility**: Workspace (shared view) +* **Filter**: Keiner (alle anzeigen) +* **Sichtbarkeit**: Arbeitsbereich (geteilte Ansicht) -### "Closing This Month" +### "Abschluss in diesem Monat" -* **Type**: Table -* **Filter**: Close Date = This month, Stage ≠ Closed Won, Stage ≠ Closed Lost -* **Sort**: Close Date ascending +* **Typ**: Tabelle +* **Filter**: Abschlussdatum = Dieser Monat, Phase ≠ Gewonnen, Phase ≠ Verloren +* **Sortierung**: Abschlussdatum aufsteigend -## Working with Opportunities +## Arbeiten mit Opportunities -### Creating Opportunities +### Opportunities erstellen -* Click **+ New** in the Opportunities view -* Or click **+** in a specific stage column +* Klicken Sie in der Opportunities-Ansicht auf **+ Neu** +* Oder klicken Sie in einer bestimmten Phasenspalte auf **+** -### Moving Through Stages +### Durch die Phasen wechseln -Drag and drop opportunity cards between columns to update their stage. +Ziehen Sie Opportunity-Karten per Drag & Drop zwischen die Spalten, um ihre Phase zu aktualisieren. - + ## Beste Praktiken -### Pipeline Hygiene +### Pipeline-Hygiene -* Update deals daily as they progress -* Move or close stale deals promptly -* Keep close dates realistic +* Aktualisieren Sie Geschäfte täglich entsprechend ihrem Fortschritt +* Verschieben oder schließen Sie ruhende Geschäfte umgehend +* Halten Sie Abschlussdaten realistisch -### Stage Discipline +### Phasendisziplin -* Define clear criteria for each stage -* Move deals promptly when criteria are met -* Don't let deals sit in stages too long +* Definieren Sie klare Kriterien für jede Phase +* Verschieben Sie Geschäfte umgehend, wenn Kriterien erfüllt sind +* Lassen Sie Geschäfte nicht zu lange in Phasen liegen -## Related +## Verwandt -* [Kanban Views](/l/de/user-guide/views-pipelines/capabilities/kanban-views) — aggregations and compact view -* [Filters and Sorting](/l/de/user-guide/views-pipelines/capabilities/filters-and-sorting) — creating filtered views +* [Kanban-Ansichten](/l/de/user-guide/views-pipelines/capabilities/kanban-views) — Aggregationen und Kompaktansicht +* [Filter und Sortierung](/l/de/user-guide/views-pipelines/capabilities/filters-and-sorting) — gefilterte Ansichten erstellen diff --git a/packages/twenty-docs/l/de/user-guide/workflows/capabilities/use-branches-in-workflows.mdx b/packages/twenty-docs/l/de/user-guide/workflows/capabilities/use-branches-in-workflows.mdx index 3c180a7985..dfefd1953f 100644 --- a/packages/twenty-docs/l/de/user-guide/workflows/capabilities/use-branches-in-workflows.mdx +++ b/packages/twenty-docs/l/de/user-guide/workflows/capabilities/use-branches-in-workflows.mdx @@ -1,90 +1,90 @@ --- -title: Use Branches in Workflows -description: Understand how branches work and how to control which path is executed. +title: Verzweigungen in Workflows verwenden +description: Verstehen Sie, wie Verzweigungen funktionieren und wie Sie steuern, welcher Pfad ausgeführt wird. --- -## How Branches Work +## Wie Verzweigungen funktionieren -In the workflow editor, you can create multiple paths (branches) going out from a single node. This allows you to build complex automations with different outcomes. +Im Workflow-Editor können Sie mehrere Pfade (Verzweigungen) erstellen, die von einem einzelnen Knoten ausgehen. So können Sie komplexe Automatisierungen mit unterschiedlichen Ergebnissen erstellen. -**Important**: When a workflow runs, **all branches execute in parallel by default**. There is no built-in "if/else" logic to choose one branch over another—every path will run simultaneously. +**Wichtig**: Wenn ein Workflow ausgeführt wird, **werden standardmäßig alle Verzweigungen parallel ausgeführt**. Es gibt keine integrierte "if/else"-Logik, um eine Verzweigung gegenüber einer anderen auszuwählen—jeder Pfad wird gleichzeitig ausgeführt. -## Controlling Which Branch Runs +## Steuern, welche Verzweigung ausgeführt wird -To execute only one branch based on specific conditions, **add a Filter node at the beginning of each branch**. +Um basierend auf bestimmten Bedingungen nur eine Verzweigung auszuführen, **fügen Sie am Anfang jeder Verzweigung einen Filter-Knoten hinzu**. -### Example Setup +### Beispiel-Setup -1. Create your workflow with multiple branches from a single node -2. Add a **Filter** node as the first step in each branch -3. Set conditions on each Filter to determine when that branch should continue -4. Only the branch(es) whose Filter conditions are met will proceed +1. Erstellen Sie Ihren Workflow mit mehreren Verzweigungen, die von einem einzelnen Knoten ausgehen +2. Fügen Sie in jeder Verzweigung als ersten Schritt einen **Filter**-Knoten hinzu +3. Legen Sie für jeden Filter Bedingungen fest, um zu bestimmen, wann diese Verzweigung fortgesetzt werden soll +4. Nur die Verzweigung(en), deren Filterbedingungen erfüllt sind, wird/werden weiter ausgeführt -### How Filters Work +### Wie Filter funktionieren -* If the Filter condition is **met**: The branch continues executing -* If the Filter condition is **not met**: The branch stops at the Filter node +* Wenn die Filterbedingung **erfüllt** ist: Die Verzweigung wird weiter ausgeführt +* Wenn die Filterbedingung **nicht erfüllt** ist: Die Verzweigung stoppt am Filter-Knoten -This effectively creates conditional logic where only the appropriate branch runs based on your data. +Dadurch entsteht effektiv eine bedingte Logik, bei der basierend auf Ihren Daten nur die passende Verzweigung ausgeführt wird. -## Example: Route by Deal Size +## Beispiel: Routing nach Dealgröße -**Scenario**: When a deal is closed, send different notifications based on deal size. +**Szenario**: Wenn ein Deal abgeschlossen wird, senden Sie je nach Dealgröße unterschiedliche Benachrichtigungen. -1. **Trigger**: Opportunity updated (Stage = Closed Won) -2. **Branch 1**: Filter for Amount > $10,000 → Send Slack message to #big-deals -3. **Branch 2**: Filter for Amount ≤ $10,000 → Send email to sales manager +1. **Auslöser**: Verkaufschance aktualisiert (Phase = Closed Won) +2. **Verzweigung 1**: Filter für Betrag > $10.000 → Slack-Nachricht an #big-deals senden +3. **Verzweigung 2**: Filter für Betrag ≤ $10.000 → E-Mail an den Vertriebsleiter senden -Both branches start, but only the one matching the deal amount will continue past its Filter. +Beide Verzweigungen starten, aber nur diejenige, die dem Dealbetrag entspricht, wird über ihren Filter hinaus fortgesetzt. -## Creating Branches +## Verzweigungen erstellen - To create a new branch from an existing step, click the **+** button on the step and add your action. You can add multiple branches by clicking **+** multiple times. + Um aus einem bestehenden Schritt eine neue Verzweigung zu erstellen, klicken Sie im Schritt auf die Schaltfläche **+** und fügen Sie Ihre Aktion hinzu. Sie können mehrere Verzweigungen hinzufügen, indem Sie **+** mehrmals klicken. -1. In the workflow editor, select the step you want to branch from -2. Click the **+** button to add an action -3. This creates one branch -4. Click **+** again on the same step to create additional branches -5. Each branch can have its own sequence of actions +1. Wählen Sie im Workflow-Editor den Schritt aus, von dem Sie verzweigen möchten +2. Klicken Sie auf **+**, um eine Aktion hinzuzufügen +3. Dadurch wird eine Verzweigung erstellt +4. Klicken Sie im selben Schritt erneut auf **+**, um weitere Verzweigungen zu erstellen +5. Jede Verzweigung kann ihre eigene Abfolge von Aktionen haben -## Merging Branches Back Together +## Verzweigungen wieder zusammenführen -After parallel branches complete their work, you can merge them back into a single path: +Nachdem parallele Verzweigungen ihre Arbeit abgeschlossen haben, können Sie sie wieder zu einem einzelnen Pfad zusammenführen: -1. Complete your branched actions -2. Add a new step that should run after all branches -3. Drag a connection from the last step of each branch to this new step -4. The merged step waits for all connected branches to complete before executing +1. Schließen Sie Ihre verzweigten Aktionen ab +2. Fügen Sie einen neuen Schritt hinzu, der nach allen Verzweigungen ausgeführt werden soll +3. Ziehen Sie eine Verbindung vom letzten Schritt jeder Verzweigung zu diesem neuen Schritt +4. Der zusammengeführte Schritt wartet, bis alle verbundenen Verzweigungen abgeschlossen sind, bevor er ausgeführt wird -### Example: Process Then Notify +### Beispiel: Erst verarbeiten, dann benachrichtigen ``` -Trigger +Auslöser │ - ├── Branch A: Update Customer Record + ├── Verzweigung A: Kundendatensatz aktualisieren │ - └── Branch B: Create Support Ticket + └── Verzweigung B: Support-Ticket erstellen ↘ ↙ - Merged Step: Send Confirmation Email + Zusammengeführter Schritt: Bestätigungs-E-Mail senden ``` -The confirmation email sends only after both the customer update and ticket creation are done. +Die Bestätigungs-E-Mail wird erst gesendet, nachdem sowohl die Aktualisierung des Kundendatensatzes als auch die Erstellung des Tickets abgeschlossen sind. ## Beste Praktiken -* Always use **Filter nodes** at the start of branches when you want conditional execution -* Keep branch conditions **mutually exclusive** to avoid duplicate actions -* Test your workflows with different data to ensure the correct branches run -* **Rename branch steps** descriptively so it's clear what each path does -* **Merge branches** when you need a final action after parallel processing +* Verwenden Sie am Anfang von Verzweigungen immer **Filter-Knoten**, wenn Sie eine bedingte Ausführung möchten +* Halten Sie Verzweigungsbedingungen **gegenseitig ausschließend**, um doppelte Aktionen zu vermeiden +* Testen Sie Ihre Workflows mit unterschiedlichen Daten, um sicherzustellen, dass die richtigen Verzweigungen ausgeführt werden +* **Benennen Sie Verzweigungsschritte um** und verwenden Sie aussagekräftige Bezeichnungen, damit klar ist, was jeder Pfad tut +* **Verzweigungen zusammenführen**, wenn Sie nach paralleler Verarbeitung eine abschließende Aktion benötigen -## Related +## Verwandt -* [Workflows FAQ](/l/de/user-guide/workflows/how-tos/need-more-help/workflows-faq) — answers about parallel execution -* [Workflow Actions](/l/de/user-guide/workflows/capabilities/workflow-actions) — available actions for branches +* [Workflows-FAQ](/l/de/user-guide/workflows/how-tos/need-more-help/workflows-faq) — Antworten zur parallelen Ausführung +* [Workflow-Aktionen](/l/de/user-guide/workflows/capabilities/workflow-actions) — verfügbare Aktionen für Verzweigungen diff --git a/packages/twenty-docs/l/it/user-guide/data-migration/how-tos/fix-import-errors.mdx b/packages/twenty-docs/l/it/user-guide/data-migration/how-tos/fix-import-errors.mdx index f05d0657c2..86da466444 100644 --- a/packages/twenty-docs/l/it/user-guide/data-migration/how-tos/fix-import-errors.mdx +++ b/packages/twenty-docs/l/it/user-guide/data-migration/how-tos/fix-import-errors.mdx @@ -1,11 +1,11 @@ --- -title: Fix Import Errors -description: Complete troubleshooting guide for resolving CSV import errors. +title: Correggere gli errori di importazione +description: Guida completa alla risoluzione degli errori di importazione CSV. --- ## Panoramica -Import not working? This guide helps you identify and fix common import errors step by step. +L'importazione non funziona? This guide helps you identify and fix common import errors step by step. ## How Import Validation Works diff --git a/packages/twenty-docs/l/it/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx b/packages/twenty-docs/l/it/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx index 8514e9306f..a563cc9d3f 100644 --- a/packages/twenty-docs/l/it/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx +++ b/packages/twenty-docs/l/it/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx @@ -1,103 +1,103 @@ --- -title: Import Relations Between Objects via CSV -description: Complete step-by-step guide to linking records during CSV import. +title: Importare le relazioni tra oggetti tramite CSV +description: Guida completa passo dopo passo per collegare i record durante l'importazione CSV. --- ## Panoramica -This guide walks you through importing relations between objects—for example, linking People to Companies, or Opportunities to People. +Questa guida ti accompagna nell'importazione delle relazioni tra oggetti — ad esempio, collegare Persone ad Aziende o Opportunità a Persone. -**What can be imported:** Only one-to-many relations pointing to a single object type. Relations pointing to multiple object types (like Notes linking to People AND Companies) are not yet supported for import. +**Cosa può essere importato:** Solo relazioni uno-a-molti che puntano a un singolo tipo di oggetto. Le relazioni che puntano a più tipi di oggetto (come Note collegate a Persone E Aziende) non sono ancora supportate per l'importazione. -## Understanding Relations +## Comprendere le relazioni -### What is a "One-to-Many" Relation? +### Che cos'è una relazione "uno-a-molti"? -In a one-to-many relation: +In una relazione uno-a-molti: -* **One** Company has **many** People (employees) -* **One** Company has **many** Opportunities -* **One** Person has **many** Tasks +* **Una** Azienda ha **molte** Persone (dipendenti) +* **Una** Azienda ha **molte** Opportunità +* **Una** Persona ha **molte** Attività -The "one" side is the **parent**. The "many" side is the **child**. +Il lato "uno" è il **genitore**. Il lato "molti" è il **figlio**. -### Common Relations in Twenty +### Relazioni comuni in Twenty -| Relazione | "One" Side (Parent) | "Many" Side (Child) | -| ------------------------- | ------------------- | ------------------- | -| Companies → People | Azienda | Persone | -| Companies → Opportunities | Azienda | Opportunità | -| People → Tasks | Persona | Attività | -| People → Notes | Persona | Note | +| Relazione | Lato "uno" (genitore) | Lato "molti" (figlio) | +| --------------------- | --------------------- | --------------------- | +| Aziende → Persone | Azienda | Persone | +| Aziende → Opportunità | Azienda | Opportunità | +| Persone → Attività | Persona | Attività | +| Persone → Note | Persona | Note | -## Step 1: Identify the "One" and "Many" Sides +## Passaggio 1: Identifica i lati "Uno" e "Molti" -Before importing, determine which object is the parent and which is the child. +Prima di importare, determina quale oggetto è il genitore e quale è il figlio. -**Ask yourself:** "Does ONE [Object A] have MANY [Object B]?" +**Chiediti:** "Un [Oggetto A] ha molti [Oggetto B]?" -* One Company → Many People ✓ (Company is parent) -* One Person → Many Companies ✗ (This is wrong—a person belongs to one company) +* Un'Azienda → Molte Persone ✓ (l'Azienda è il genitore) +* Una Persona → Molte Aziende ✗ (Questo è sbagliato: una persona appartiene a un'azienda) -## Step 2: Import the Parent Records First +## Passaggio 2: Importa prima i record genitore -The parent ("one" side) must exist in Twenty before you can reference it. +Il genitore (lato "uno") deve esistere in Twenty prima di potervi fare riferimento. -**Import order:** +**Ordine di importazione:** -1. **Companies** first (no dependencies) -2. **People** second (link to Companies) -3. **Opportunities** third (link to Companies and/or People) -4. **Tasks/Notes** (link to any of the above) +1. **Aziende** per prime (nessuna dipendenza) +2. **Persone** dopo (collegate alle Aziende) +3. **Opportunità** al terzo posto (collegate ad Aziende e/o Persone) +4. **Attività/Note** (collegate a uno qualsiasi dei precedenti) - **If the parent record doesn't exist, the import will fail.** + **Se il record genitore non esiste, l'importazione fallirà.** - Always verify that Companies are imported before importing People with company references. + Verifica sempre che le Aziende siano importate prima di importare le Persone con riferimenti all'Azienda. -## Step 3: Note the Parent's Unique Identifier +## Passaggio 3: Annota l'identificatore univoco del genitore -You need to reference the parent record using a **unique identifier**. Available options: +Devi fare riferimento al record genitore usando un **identificatore univoco**. Opzioni disponibili: -| Parent Object | Available Unique Identifiers | -| --------------------------------- | --------------------------------------------------------------- | -| **Aziende** | `id` (UUID), `domain` (recommended), or any custom unique field | -| **People** | `id` (UUID), `email`, or any custom unique field | -| **Membri dello spazio di lavoro** | `id` (UUID), `email` (not name) | -| **Oggetti personalizzati** | `id` (UUID), or any field marked as unique | +| Oggetto genitore | Identificatori univoci disponibili | +| --------------------------------- | ---------------------------------------------------------------------------- | +| **Aziende** | `id` (UUID), `domain` (consigliato) o qualsiasi campo univoco personalizzato | +| **Persone** | `id` (UUID), `email` o qualsiasi campo univoco personalizzato | +| **Membri dello spazio di lavoro** | `id` (UUID), `email` (non il nome) | +| **Oggetti personalizzati** | `id` (UUID) o qualsiasi campo contrassegnato come univoco | -**Recommended:** Use `domain` for Companies and `email` for People. These are human-readable and easy to verify in your spreadsheet. +**Consigliato:** Usa `domain` per le Aziende ed `email` per le Persone. Sono leggibili e facili da verificare nel tuo foglio di calcolo. -### Finding the Identifier +### Trovare l'identificatore -If you need the `id`: +Se ti serve l'`id`: -1. Export the parent records from Twenty -2. The export includes the `id` column -3. Use these IDs in your child records file +1. Esporta i record genitore da Twenty +2. L'esportazione include la colonna `id` +3. Usa questi ID nel file dei record figlio -## Step 4: Verify the Relation Field Exists +## Passaggio 4: Verifica che il campo di relazione esista -Before importing, ensure the relation field exists between your objects. +Prima di importare, assicurati che esista il campo di relazione tra i tuoi oggetti. -**To check or create:** +**Per verificare o creare:** -1. Go to **Settings → Data Model** -2. Select your child object (e.g., People) -3. Look for a relation field pointing to the parent (e.g., Company) -4. If it doesn't exist, create it: - * Click **+ Add field** - * Select **Relation** type - * Choose the parent object +1. Vai a **Impostazioni → Modello dati** +2. Seleziona il tuo oggetto figlio (ad es., Persone) +3. Cerca un campo di relazione che punti al genitore (ad es., Azienda) +4. Se non esiste, crealo: + * Fai clic su **+ Aggiungi campo** + * Seleziona il tipo **Relazione** + * Scegli l'oggetto genitore -## Step 5: Prepare Your CSV File +## Passaggio 5: Prepara il tuo file CSV -Add a column to your child CSV that references the parent using its unique identifier. +Aggiungi al CSV dei record figlio una colonna che faccia riferimento al genitore usando il suo identificatore univoco. -### Example: People Linking to Companies +### Esempio: Persone collegate ad Aziende -**Your People CSV:** +**Il tuo CSV delle Persone:** ```csv firstName,lastName,email,jobTitle,companyDomain @@ -106,66 +106,66 @@ Jane,Doe,jane@widgets.co,CTO,https://widgets.co Bob,Johnson,bob@techstart.io,Developer,https://techstart.io ``` -The `companyDomain` column references the Company's domain. +La colonna `companyDomain` fa riferimento al dominio dell'Azienda. -### Format Requirements +### Requisiti di formato | Identificatore | Formato | Esempio | | -------------- | -------------- | -------------------------------------- | -| Dominio | URL format | `https://acme.com` | -| Email | Standard email | `john@acme.com` | +| Dominio | Formato URL | `https://acme.com` | +| Email | Email standard | `john@acme.com` | | ID | UUID | `c776ee49-f608-4a77-8cc8-6fe96ae1e43f` | - **Domain format matters!** + **Il formato del dominio è importante!** - Use `https://domain.com` (not just `domain.com`). This matches how Twenty stores Company domains and prevents matching errors. + Usa `https://domain.com` (non solo `domain.com`). Questo corrisponde a come Twenty archivia i domini delle Aziende e previene errori di corrispondenza. -### Important Rules +### Regole importanti -1. **Exact match required** — the value must exactly match the parent record -2. **Map only ONE unique identifier** — don't include both `companyId` AND `companyDomain` -3. **Case sensitive** — `Acme.com` ≠ `acme.com` +1. **Corrispondenza esatta richiesta** — il valore deve corrispondere esattamente al record genitore +2. **Mappa un solo identificatore univoco** — non includere sia `companyId` che `companyDomain` +3. **Sensibile alle maiuscole/minuscole** — `Acme.com` ≠ `acme.com` -## Step 6: Upload and Map the Relation +## Passaggio 6: Carica e mappa la relazione -1. Navigate to the child object (e.g., People) -2. Click **⋮** → **Import records** -3. Upload your CSV file -4. In the field mapping step: - * Find your relation column (e.g., `companyDomain`) - * Map it to the **Company** relation field -5. Complete the remaining mapping -6. Review errors and confirm +1. Vai all'oggetto figlio (ad es., Persone) +2. Fai clic su **⋮** → **Importa record** +3. Carica il tuo file CSV +4. Nella fase di mappatura dei campi: + * Trova la tua colonna di relazione (ad es., `companyDomain`) + * Mappala al campo di relazione **Azienda** +5. Completa le restanti mappature +6. Controlla gli errori e conferma -Twenty will automatically link each child record to the matching parent. +Twenty collegherà automaticamente ogni record figlio al genitore corrispondente. -## Step 7: Verify the Import +## Passaggio 7: Verifica l'importazione -After importing: +Dopo l'importazione: -1. Open a few child records (e.g., People) -2. Verify the relation field shows the correct parent (e.g., Company) -3. Open a parent record and check the related records section +1. Apri alcuni record figlio (ad es., Persone) +2. Verifica che il campo di relazione mostri il genitore corretto (ad es., Azienda) +3. Apri un record genitore e controlla la sezione dei record correlati -## Common Mistakes to Avoid +## Errori comuni da evitare -| Mistake | Problem | Solution | -| -------------------------- | -------------------------------------------------- | ------------------------------------------------------- | -| **Wrong import order** | Importing People before Companies | Always import parents first, then children | -| **Wrong domain format** | Using `acme.com` instead of `https://acme.com` | Use full URL format with `https://` | -| **Multiple unique fields** | Mapping both `companyId` AND `companyDomain` | Map only ONE unique identifier | -| **Missing relation field** | The relation field doesn't exist in the data model | Create it in **Settings → Data Model** before importing | -| **Non-existent records** | The parent record doesn't exist in Twenty | Import parent records first, or check for typos | -| **Case mismatch** | `Acme.com` in file but `acme.com` in Twenty | Ensure exact case matching | +| Errore | Problema | Soluzione | +| ----------------------------------------- | ------------------------------------------------- | ---------------------------------------------------------------------------------- | +| **Ordine di importazione errato** | Importare le Persone prima delle Aziende | Importa sempre prima i genitori, poi i figli | +| **Formato del dominio errato** | Uso di `acme.com` invece di `https://acme.com` | Usa il formato URL completo con `https://` | +| **Più campi univoci** | Mappare sia `companyId` che `companyDomain` | Mappa un solo identificatore univoco | +| **Campo di relazione mancante** | Il campo di relazione non esiste nel modello dati | Crealo in **Impostazioni → Modello dati** prima dell'importazione | +| **Record inesistenti** | Il record genitore non esiste in Twenty | Importa prima i record genitore oppure verifica la presenza di errori di battitura | +| **Discrepanza tra maiuscole e minuscole** | `Acme.com` nel file ma `acme.com` in Twenty | Assicurati che le maiuscole/minuscole corrispondano esattamente | -## Linking to Workspace Members +## Collegamento ai membri del Workspace -When linking to Workspace Members (your team): +Quando colleghi i membri del Workspace (il tuo team): -* Use their **email address**, not their name -* Example: `owner@yourcompany.com`, not "John Smith" +* Usa il loro **indirizzo email**, non il nome +* Esempio: `owner@yourcompany.com`, non "John Smith" ```csv taskName,assignedTo @@ -176,53 +176,53 @@ Review proposal,jane@yourcompany.com ## FAQ - - You have two options: + + Hai due opzioni: - 1. Use the Twenty `id` (export parent records to get their IDs) - 2. Create a custom unique field in your data model to store an external ID from your previous system + 1. Usa l'`id` di Twenty (esporta i record genitore per ottenere i loro ID) + 2. Crea un campo univoco personalizzato nel tuo modello dati per archiviare un ID esterno dal sistema precedente - - Sì! Include the child record's unique identifier (e.g., `email` for People) and the new relation value. The import will update the relation. + + Sì! Includi l'identificatore univoco del record figlio (ad es., `email` per Persone) e il nuovo valore della relazione. L'importazione aggiornerà la relazione. - - Many-to-Many relations are not yet supported for import. This is planned for H1 2026. + + Le relazioni molti-a-molti non sono ancora supportate per l'importazione. È previsto per H1 2026. - - Relations pointing to multiple object types are not yet supported for import/export. This is on our roadmap. + + Le relazioni che puntano a più tipi di oggetto non sono ancora supportate per importazione/esportazione. È nella nostra roadmap. - - The import will show an error for that row. Puoi: + + L'importazione mostrerà un errore per quella riga. Puoi: - * Import the parent record first, then re-import - * Fix the reference value - * Remove the row from import + * Importa prima il record genitore, poi ripeti l'importazione + * Correggi il valore di riferimento + * Rimuovi la riga dall'importazione - - Common causes: + + Cause comuni: - * Wrong format (use `https://domain.com` for domains) - * Case mismatch (check exact spelling) - * Parent doesn't exist (import parents first) - * Mapping multiple identifiers (use only one) + * Formato errato (usa `https://domain.com` per i domini) + * Discrepanza tra maiuscole e minuscole (controlla l'ortografia esatta) + * Il genitore non esiste (importa prima i genitori) + * Mappatura di più identificatori (usane uno solo) - **Remember: Soft-deleted records count toward uniqueness.** + **Ricorda: i record eliminati in modo non definitivo contano ai fini dell'unicità.** - If you're getting "not found" errors but the record seems to exist, check Command Menu → See deleted records. The parent may have been soft-deleted. + Se ricevi errori "not found" ma il record sembra esistere, controlla Menu comandi → Visualizza record eliminati. Il genitore potrebbe essere stato eliminato in modo non definitivo. ## Risoluzione dei problemi -Having issues? Check: +Hai problemi? Controlla: -* [How to Fix Import Errors](/l/it/user-guide/data-migration/how-tos/fix-import-errors) -* [Import Relations Capabilities](/l/it/user-guide/data-migration/capabilities/import-relations) -* [Uniqueness Constraints](/l/it/user-guide/data-migration/capabilities/uniqueness-constraints) +* [Come correggere gli errori di importazione](/l/it/user-guide/data-migration/how-tos/fix-import-errors) +* [Capacità di importazione delle relazioni](/l/it/user-guide/data-migration/capabilities/import-relations) +* [Vincoli di unicità](/l/it/user-guide/data-migration/capabilities/uniqueness-constraints) diff --git a/packages/twenty-docs/l/it/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx b/packages/twenty-docs/l/it/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx index 9659f8d32e..a4d2797068 100644 --- a/packages/twenty-docs/l/it/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx +++ b/packages/twenty-docs/l/it/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx @@ -1,73 +1,73 @@ --- title: Migrazione da Soluzioni Self-Hosted a Cloud -description: Step-by-step guide to migrate your Twenty self-hosted instance to Twenty Cloud. +description: Guida passo-passo per migrare la tua istanza Twenty self-hosted verso Twenty Cloud. --- ## Panoramica -This guide walks you through migrating your data from a Twenty self-hosted instance to Twenty Cloud. The process involves setting up your cloud workspace, exporting your data, and re-importing it. +Questa guida ti accompagna nella migrazione dei tuoi dati da un'istanza Twenty self-hosted a Twenty Cloud. Il processo prevede la configurazione dello spazio di lavoro cloud, l'esportazione dei dati e la loro reimportazione. -Views, workflows, and roles must be recreated manually after migration. Plan time for this configuration work. +Le viste, i flussi di lavoro e i ruoli devono essere ricreati manualmente dopo la migrazione. Pianifica il tempo per questo lavoro di configurazione. -## Step 1: Create Your Cloud Workspace +## Passaggio 1: Crea il tuo spazio di lavoro cloud -1. Go to [app.twenty.com](https://app.twenty.com) and create a new workspace -2. Complete the initial setup wizard -3. Note your new workspace URL +1. Vai su [app.twenty.com](https://app.twenty.com) e crea un nuovo spazio di lavoro +2. Completa la procedura guidata iniziale +3. Annota l'URL del tuo nuovo spazio di lavoro -## Step 2: Recreate Your Data Model +## Passaggio 2: Ricrea il tuo modello dati -Before importing data, recreate your custom objects and fields: +Prima di importare i dati, ricrea i tuoi oggetti e campi personalizzati: -1. Go to **Settings → Data Model** in your cloud instance -2. Create custom objects that match your self-hosted setup -3. Add custom fields to standard and custom objects -4. Configure field settings (unique, required, etc.) +1. Vai a **Impostazioni → Modello dati** nella tua istanza cloud +2. Crea oggetti personalizzati che corrispondano alla tua configurazione self-hosted +3. Aggiungi campi personalizzati agli oggetti standard e personalizzati +4. Configura le impostazioni dei campi (univoche, obbligatorie, ecc.) -Take screenshots of your self-hosted data model for reference, or keep both instances open side by side. +Fai degli screenshot del tuo modello dati self-hosted come riferimento oppure tieni entrambe le istanze aperte affiancate. -## Step 3: Invite All Users +## Passaggio 3: Invita tutti gli utenti - **Critical: Invite users BEFORE importing data.** + **Critico: invita gli utenti PRIMA di importare i dati.** - Users must accept their invitations before you import any records that reference them (like Account Owner fields). If users don't exist yet, those relations cannot be mapped. + Gli utenti devono accettare i loro inviti prima di importare qualsiasi record che faccia riferimento a loro (come i campi Account Owner). Se gli utenti non esistono ancora, tali relazioni non possono essere mappate. -1. Go to **Settings → Members** in your cloud instance -2. Invite all team members who had accounts on self-hosted -3. **Wait for everyone to accept** their invitation -4. Verify all users appear in your Members list +1. Vai a **Impostazioni → Membri** nella tua istanza cloud +2. Invita tutti i membri del team che avevano account sull'istanza self-hosted +3. **Attendi che tutti accettino** il loro invito +4. Verifica che tutti gli utenti compaiano nell'elenco Membri -## Step 4: Export Data from Self-Hosted +## Passaggio 4: Esporta i dati dall'istanza self-hosted -Export each object from your self-hosted instance: +Esporta ogni oggetto dalla tua istanza self-hosted: -1. Navigate to each object (Companies, People, Opportunities, etc.) -2. Configure the view to show **all columns** you want to migrate -3. Click **⋮ → Export view** -4. Save each CSV file with a clear name (e.g., `companies-export.csv`) +1. Vai a ciascun oggetto (Aziende, Persone, Opportunità, ecc.) +2. Configura la vista per mostrare **tutte le colonne** che vuoi migrare +3. Fai clic su **⋮ → Esporta vista** +4. Salva ogni file CSV con un nome chiaro (ad es., `companies-export.csv`) -**Export in this order** (for reference when importing): +**Esporta in questo ordine** (come riferimento durante l'importazione): 1. Aziende 2. Persone 3. Opportunità -4. Custom objects (following their dependencies) -5. Tasks, Notes +4. Oggetti personalizzati (seguendo le loro dipendenze) +5. Attività, Note -## Step 5: Update Workspace Member References +## Passaggio 5: Aggiorna i riferimenti ai membri dello spazio di lavoro -The exported CSVs contain user IDs from your self-hosted instance. These IDs won't match your cloud instance, so you need to replace them with emails. +I CSV esportati contengono gli ID utente della tua istanza self-hosted. Questi ID non corrisponderanno alla tua istanza cloud, quindi devi sostituirli con le email. -**For each CSV file with user references (Owner, Assignee, etc.):** +**Per ogni file CSV con riferimenti utente (Owner, Assignee, ecc.):** -1. Open the CSV in a spreadsheet application -2. Add a new column next to each user ID column (e.g., `accountOwnerEmail` next to `accountOwnerId`) -3. Fill in the **email address** of each user -4. You can delete the old ID column or leave it (it will be skipped during import) +1. Apri il CSV in un'applicazione per fogli di calcolo +2. Aggiungi una nuova colonna accanto a ciascuna colonna di ID utente (ad es., `accountOwnerEmail` accanto a `accountOwnerId`) +3. Compila l'**indirizzo email** di ciascun utente +4. Puoi eliminare la vecchia colonna ID oppure lasciarla (verrà ignorata durante l'importazione) -**Example:** +**Esempio:** Prima: @@ -83,89 +83,89 @@ name,domain,accountOwnerEmail Acme Corp,https://acme.com,john@yourcompany.com ``` -Use the same email addresses that users used to accept their cloud workspace invitation. +Usa gli stessi indirizzi email che gli utenti hanno usato per accettare l'invito allo spazio di lavoro cloud. -## Step 6: Plan Your Import Order +## Passaggio 6: Pianifica l'ordine di importazione -Import files in the correct order to maintain relationships: +Importa i file nel giusto ordine per mantenere le relazioni: -1. **Companies** first (no dependencies) -2. **People** second (link to Companies) -3. **Opportunities** third (link to Companies and People) -4. **Custom objects** (following their dependencies) -5. **Tasks and Notes** last (link to other records) +1. **Aziende** per prime (nessuna dipendenza) +2. **Persone** dopo (collegate alle Aziende) +3. **Opportunità** al terzo posto (collegate ad Aziende e Persone) +4. **Oggetti personalizzati** (seguendo le loro dipendenze) +5. **Attività e Note** per ultime (collegate ad altri record) -See [How to Import Relations](/l/it/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv) for details on maintaining relationships. +Consulta [Come importare le relazioni](/l/it/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv) per i dettagli su come mantenere le relazioni. -## Step 7: Import to Cloud +## Passaggio 7: Importa nel cloud -For each CSV file, in order: +Per ogni file CSV, in ordine: -1. Navigate to the object in your cloud instance -2. Click **⋮ → Import records** -3. Upload the CSV file -4. Map columns to fields: - * Map user email columns to the appropriate relation fields - * Map other columns as usual -5. Review and fix any errors -6. Confirm the import -7. Verify a few records before proceeding to the next file +1. Vai all'oggetto nella tua istanza cloud +2. Fai clic su **⋮ → Importa record** +3. Carica il file CSV +4. Mappa le colonne ai campi: + * Mappa le colonne delle email degli utenti ai campi relazione appropriati + * Mappa le altre colonne come al solito +5. Controlla e correggi eventuali errori +6. Conferma l'importazione +7. Verifica alcuni record prima di passare al file successivo -## Step 8: Recreate Configuration +## Passaggio 8: Ricrea la configurazione -After importing data, manually recreate: +Dopo aver importato i dati, ricrea manualmente: ### Viste -* Recreate saved views with filters, sorts, and column configurations -* Set up any kanban or calendar views +* Ricrea le viste salvate con filtri, ordinamenti e configurazioni delle colonne +* Configura eventuali viste kanban o calendario ### Flussi di Lavoro -* Recreate automations in **Settings → Workflows** -* Test each workflow before relying on it +* Ricrea le automazioni in **Impostazioni → Flussi di lavoro** +* Testa ogni flusso di lavoro prima di farci affidamento -### Roles and Permissions +### Ruoli e permessi -* Configure roles in **Settings → Roles** -* Assign users to appropriate roles +* Configura i ruoli in **Impostazioni → Ruoli** +* Assegna gli utenti ai ruoli appropriati ### Integrazioni -* Reconnect email and calendar sync for each user -* Reconfigure any API integrations with new API keys +* Riconnetti la sincronizzazione di email e calendario per ogni utente +* Riconfigura eventuali integrazioni API con nuove chiavi API ## Lista di Verifica Post-Migrazione -All data imported successfully -Relations between objects working correctly -User assignments (Owner, Assignee) mapped correctly -Views recreated -Workflows recreated and tested -Roles and permissions configured -Email/calendar sync reconnected -API integrations updated with new keys +Tutti i dati importati correttamente +Relazioni tra oggetti funzionanti correttamente +Assegnazioni utente (Owner, Assignee) mappate correttamente +Viste ricreate +Flussi di lavoro ricreati e testati +Ruoli e permessi configurati +Sincronizzazione email/calendario riconnessa +Integrazioni API aggiornate con nuove chiavi ## FAQ - - Not currently. Workflows must be recreated manually in your cloud instance. + + Al momento no. I flussi di lavoro devono essere ricreati manualmente nella tua istanza cloud. - - File attachments are not included in CSV exports. You'll need to re-upload any attachments manually, migrate them via API or contact our team for assistance with large migrations. + + Gli allegati non sono inclusi nelle esportazioni CSV. Dovrai ricaricare manualmente gli allegati, migrarli tramite API oppure contattare il nostro team per assistenza con migrazioni di grandi dimensioni. - - Yes, we recommend keeping your self-hosted instance running until you've verified the cloud migration is complete. Just be careful not to create new data in both places. + + Sì, consigliamo di mantenere attiva la tua istanza self-hosted finché non avrai verificato che la migrazione al cloud sia completa. Fai solo attenzione a non creare nuovi dati in entrambi gli ambienti. - - Records referencing that user will fail to import or the relation will be empty. Ensure all users accept invitations before importing data. + + I record che fanno riferimento a quell'utente non verranno importati oppure la relazione risulterà vuota. Assicurati che tutti gli utenti accettino gli inviti prima di importare i dati. ## Hai Bisogno di Aiuto? -For complex migrations or large datasets, contact us at [contact@twenty.com](mailto:contact@twenty.com) or explore our [Implementation Services](/l/it/user-guide/getting-started/capabilities/implementation-services). +Per migrazioni complesse o set di dati di grandi dimensioni, contattaci all'indirizzo [contact@twenty.com](mailto:contact@twenty.com) oppure scopri i nostri [Servizi di Implementazione](/l/it/user-guide/getting-started/capabilities/implementation-services). diff --git a/packages/twenty-docs/l/it/user-guide/settings/overview.mdx b/packages/twenty-docs/l/it/user-guide/settings/overview.mdx index fc86627958..cf9dd018bd 100644 --- a/packages/twenty-docs/l/it/user-guide/settings/overview.mdx +++ b/packages/twenty-docs/l/it/user-guide/settings/overview.mdx @@ -54,14 +54,14 @@ Aggiungi membri del team al tuo spazio di lavoro: ## Elenco di controllo delle impostazioni dello spazio di lavoro -* Workspace name and logo configured -* Time zone and date format set -* Email and calendar connected -* Team members invited -* Roles and permissions configured +* Nome e logo dello spazio di lavoro configurati +* Fuso orario e formato della data impostati +* Email e calendario collegati +* Membri del team invitati +* Ruoli e permessi configurati ## Prossimi Passi -* [Workspace settings](/l/it/user-guide/settings/capabilities/workspace-settings) -* [Profile settings](/l/it/user-guide/settings/capabilities/profile-settings) -* [Experience settings](/l/it/user-guide/settings/capabilities/experience-settings) +* [Impostazioni dello spazio di lavoro](/l/it/user-guide/settings/capabilities/workspace-settings) +* [Impostazioni del profilo](/l/it/user-guide/settings/capabilities/profile-settings) +* [Impostazioni dell'esperienza](/l/it/user-guide/settings/capabilities/experience-settings) diff --git a/packages/twenty-docs/l/it/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx b/packages/twenty-docs/l/it/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx index 18cbc091e1..2f4d147faf 100644 --- a/packages/twenty-docs/l/it/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx +++ b/packages/twenty-docs/l/it/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx @@ -1,120 +1,120 @@ --- -title: Set Up a Sales Pipeline -description: Configure your sales pipeline to track opportunities through stages. +title: Configura una pipeline di vendita +description: Configura la tua pipeline di vendita per tracciare le opportunità attraverso le fasi. --- import { VimeoEmbed } from '/snippets/vimeo-embed.mdx'; -A sales pipeline in Twenty is a Kanban view of your Opportunities object, where each column represents a stage in your sales process. +Una pipeline di vendita in Twenty è una vista Kanban del tuo oggetto Opportunità, in cui ogni colonna rappresenta una fase del tuo processo di vendita. -## Step 1: Configure Your Stages +## Passaggio 1: Configura le tue fasi -Stages are defined in the Opportunities object's **Stage** field. +Le fasi sono definite nel campo **Fase** dell'oggetto Opportunità. -1. Go to **Settings → Data Model** -2. Select **Opportunities** -3. Find and click the **Stage** field -4. Add, remove, or rename stages to match your process +1. Vai a **Impostazioni → Modello dati** +2. Seleziona **Opportunità** +3. Trova e fai clic sul campo **Fase** +4. Aggiungi, rimuovi o rinomina le fasi per allinearle al tuo processo - + -### Recommended Stages +### Fasi consigliate -| Fase | Purpose | -| --------------- | ----------------------------------- | -| **New** | Fresh opportunities just identified | -| **Qualified** | Confirmed as a good fit | -| **Meeting** | Engaged in discussions | -| **Proposal** | Proposal sent | -| **Negotiation** | Working on terms | -| **Closed Won** | Deal successful | -| **Closed Lost** | Deal unsuccessful | +| Fase | Scopo | +| ------------------ | ------------------------------ | +| **Nuovo** | Opportunità appena individuate | +| **Qualificato** | Confermate come idonee | +| **Incontro** | In fase di discussione | +| **Proposta** | Proposta inviata | +| **Negoziazione** | Definizione dei termini | +| **Chiuso - Vinta** | Trattativa vinta | +| **Chiuso - Persa** | Trattativa persa | - **5-7 stages is optimal.** Too many stages makes the pipeline hard to scan; too few loses visibility into deal progress. + **5-7 fasi sono ottimali.** Troppe fasi rendono la pipeline difficile da consultare; troppo poche riducono la visibilità sull'avanzamento delle trattative. -## Step 2: Create a Pipeline View +## Passaggio 2: Crea una vista pipeline -1. Go to **Opportunities** -2. Click the view dropdown → **+ Add view** -3. Name it "Sales Pipeline" -4. Click **Create** -5. Open **Options** and select **Kanban** as the layout +1. Vai a **Opportunità** +2. Clicca sul menu a discesa della vista → **+ Aggiungi vista** +3. Chiamala "Pipeline di vendita" +4. Clicca **Crea** +5. Apri **Opzioni** e seleziona **Kanban** come layout -The view automatically uses the Stage field for columns. +La vista utilizza automaticamente il campo Fase per le colonne. -## Step 3: Configure Your View +## Passaggio 3: Configura la tua vista -### Show Key Fields +### Mostra i campi chiave -1. Click **Options → Fields** -2. Look for fields in the "Hidden Fields" section -3. Click the **eye icon** to display: Company, Amount, Close Date, Owner +1. Clicca su **Opzioni → Campi** +2. Cerca i campi nella sezione "Campi nascosti" +3. Clicca sull'**icona a forma di occhio** per visualizzare: Azienda, Importo, Data di chiusura, Proprietario -### Enable Aggregations +### Abilita le aggregazioni -Show totals at the top of each column: +Mostra i totali nella parte superiore di ogni colonna: -1. Click the number displayed next to a Stage name at the top of a column -2. Select the aggregation type (Count, Sum, Average, etc.) -3. Choose the field to aggregate (e.g., Amount) +1. Clicca sul numero visualizzato accanto al nome di una fase nella parte superiore di una colonna +2. Seleziona il tipo di aggregazione (Conteggio, Somma, Media, ecc.) +3. Scegli il campo da aggregare (ad es., Importo) -**Example:** Show total deal value per stage by aggregating Amount with Sum. +**Esempio:** Mostra il valore totale delle trattative per fase aggregando Importo con Somma. -### Use Compact View (Optional) +### Usa la vista compatta (opzionale) -For a high-level overview with minimal card content: +Per una panoramica di alto livello con contenuto della scheda minimo: -1. Click **Options** -2. Turn on the toggle for **Compact view** +1. Clicca su **Opzioni** +2. Attiva l'interruttore per **Vista compatta** -## Step 4: Create Personal and Team Views +## Passaggio 4: Crea viste personali e di team -### "My Pipeline" +### "La mia pipeline" -* **Filter**: Owner = Me -* **Visibility**: Unlisted (personal view) +* **Filtro**: Proprietario = Io +* **Visibilità**: Non in elenco (vista personale) -### "Team Pipeline" +### "Pipeline del team" -* **Filter**: None (show all) -* **Visibility**: Workspace (shared view) +* **Filtro**: Nessuno (mostra tutto) +* **Visibilità**: Spazio di lavoro (vista condivisa) -### "Closing This Month" +### "In chiusura questo mese" -* **Type**: Table -* **Filter**: Close Date = This month, Stage ≠ Closed Won, Stage ≠ Closed Lost -* **Sort**: Close Date ascending +* **Tipo**: Tabella +* **Filtro**: Data di chiusura = Questo mese, Fase ≠ Chiuso - Vinta, Fase ≠ Chiuso - Persa +* **Ordina**: Data di chiusura crescente -## Working with Opportunities +## Lavorare con le opportunità -### Creating Opportunities +### Creazione di opportunità -* Click **+ New** in the Opportunities view -* Or click **+** in a specific stage column +* Clicca su **+ Nuovo** nella vista Opportunità +* Oppure clicca su **+** nella colonna di una specifica fase -### Moving Through Stages +### Passare tra le fasi -Drag and drop opportunity cards between columns to update their stage. +Trascina e rilascia le schede delle opportunità tra le colonne per aggiornarne la fase. - + ## Migliori Pratiche -### Pipeline Hygiene +### Igiene della pipeline -* Update deals daily as they progress -* Move or close stale deals promptly -* Keep close dates realistic +* Aggiorna quotidianamente le trattative man mano che avanzano +* Sposta o chiudi tempestivamente le trattative stagnanti +* Mantieni realistiche le date di chiusura -### Stage Discipline +### Disciplina delle fasi -* Define clear criteria for each stage -* Move deals promptly when criteria are met -* Don't let deals sit in stages too long +* Definisci criteri chiari per ogni fase +* Sposta le trattative tempestivamente quando i criteri sono soddisfatti +* Non lasciare le trattative troppo a lungo nelle fasi -## Related +## Correlati -* [Kanban Views](/l/it/user-guide/views-pipelines/capabilities/kanban-views) — aggregations and compact view -* [Filters and Sorting](/l/it/user-guide/views-pipelines/capabilities/filters-and-sorting) — creating filtered views +* [Viste Kanban](/l/it/user-guide/views-pipelines/capabilities/kanban-views) — aggregazioni e vista compatta +* [Filtri e ordinamento](/l/it/user-guide/views-pipelines/capabilities/filters-and-sorting) — creazione di viste filtrate diff --git a/packages/twenty-docs/l/it/user-guide/workflows/capabilities/use-branches-in-workflows.mdx b/packages/twenty-docs/l/it/user-guide/workflows/capabilities/use-branches-in-workflows.mdx index 52ca03363b..3e9462eaf6 100644 --- a/packages/twenty-docs/l/it/user-guide/workflows/capabilities/use-branches-in-workflows.mdx +++ b/packages/twenty-docs/l/it/user-guide/workflows/capabilities/use-branches-in-workflows.mdx @@ -1,90 +1,90 @@ --- -title: Use Branches in Workflows -description: Understand how branches work and how to control which path is executed. +title: Usare le diramazioni nei flussi di lavoro +description: Comprendi come funzionano le diramazioni e come controllare quale percorso viene eseguito. --- -## How Branches Work +## Come funzionano le diramazioni -In the workflow editor, you can create multiple paths (branches) going out from a single node. This allows you to build complex automations with different outcomes. +Nell'editor dei flussi di lavoro, puoi creare più percorsi (diramazioni) che partono da un singolo nodo. Questo ti consente di creare automazioni complesse con risultati diversi. -**Important**: When a workflow runs, **all branches execute in parallel by default**. There is no built-in "if/else" logic to choose one branch over another—every path will run simultaneously. +**Importante**: Quando viene eseguito un flusso di lavoro, **tutte le diramazioni vengono eseguite in parallelo per impostazione predefinita**. Non esiste una logica "if/else" integrata per scegliere una diramazione rispetto a un'altra — ogni percorso verrà eseguito simultaneamente. -## Controlling Which Branch Runs +## Controllare quale diramazione viene eseguita -To execute only one branch based on specific conditions, **add a Filter node at the beginning of each branch**. +Per eseguire una sola diramazione in base a condizioni specifiche, **aggiungi un nodo Filtro all'inizio di ogni diramazione**. -### Example Setup +### Esempio di configurazione -1. Create your workflow with multiple branches from a single node -2. Add a **Filter** node as the first step in each branch -3. Set conditions on each Filter to determine when that branch should continue -4. Only the branch(es) whose Filter conditions are met will proceed +1. Crea il tuo flusso di lavoro con più diramazioni da un singolo nodo +2. Aggiungi un nodo **Filtro** come primo passaggio in ogni diramazione +3. Imposta le condizioni su ciascun Filtro per determinare quando quella diramazione deve continuare +4. Procederanno solo le diramazioni per cui le condizioni del Filtro sono soddisfatte -### How Filters Work +### Come funzionano i filtri -* If the Filter condition is **met**: The branch continues executing -* If the Filter condition is **not met**: The branch stops at the Filter node +* Se la condizione del Filtro è **soddisfatta**: la diramazione continua l'esecuzione +* Se la condizione del Filtro **non è soddisfatta**: la diramazione si ferma al nodo Filtro -This effectively creates conditional logic where only the appropriate branch runs based on your data. +Questo crea di fatto una logica condizionale in cui, in base ai tuoi dati, viene eseguita solo la diramazione appropriata. -## Example: Route by Deal Size +## Esempio: instradare in base al valore dell'opportunità -**Scenario**: When a deal is closed, send different notifications based on deal size. +**Scenario**: Quando un'opportunità viene chiusa, invia notifiche diverse in base al valore dell'opportunità. -1. **Trigger**: Opportunity updated (Stage = Closed Won) -2. **Branch 1**: Filter for Amount > $10,000 → Send Slack message to #big-deals -3. **Branch 2**: Filter for Amount ≤ $10,000 → Send email to sales manager +1. **Trigger**: Opportunità aggiornata (Fase = Chiusa vinta) +2. **Diramazione 1**: Filtro per Importo > $10.000 → Invia un messaggio Slack a #big-deals +3. **Diramazione 2**: Filtro per Importo ≤ $10.000 → Invia un'email al responsabile vendite -Both branches start, but only the one matching the deal amount will continue past its Filter. +Entrambe le diramazioni iniziano, ma solo quella che corrisponde all'importo dell'opportunità continuerà oltre il suo Filtro. -## Creating Branches +## Creare le diramazioni - To create a new branch from an existing step, click the **+** button on the step and add your action. You can add multiple branches by clicking **+** multiple times. + Per creare una nuova diramazione da un passaggio esistente, fai clic sul pulsante **+** nel passaggio e aggiungi la tua azione. Puoi aggiungere più diramazioni facendo clic su **+** più volte. -1. In the workflow editor, select the step you want to branch from -2. Click the **+** button to add an action -3. This creates one branch -4. Click **+** again on the same step to create additional branches -5. Each branch can have its own sequence of actions +1. Nell'editor dei flussi di lavoro, seleziona il passaggio da cui vuoi creare la diramazione +2. Fai clic su **+** per aggiungere un'azione +3. Questo crea una diramazione +4. Fai di nuovo clic su **+** sullo stesso passaggio per creare diramazioni aggiuntive +5. Ogni diramazione può avere la propria sequenza di azioni -## Merging Branches Back Together +## Riunire le diramazioni -After parallel branches complete their work, you can merge them back into a single path: +Dopo che le diramazioni parallele hanno completato il loro lavoro, puoi riunirle in un unico percorso: -1. Complete your branched actions -2. Add a new step that should run after all branches -3. Drag a connection from the last step of each branch to this new step -4. The merged step waits for all connected branches to complete before executing +1. Completa le azioni nelle diramazioni +2. Aggiungi un nuovo passaggio che deve essere eseguito dopo tutte le diramazioni +3. Trascina una connessione dall'ultimo passaggio di ciascuna diramazione verso questo nuovo passaggio +4. Il passaggio riunito attende il completamento di tutte le diramazioni collegate prima di essere eseguito -### Example: Process Then Notify +### Esempio: elabora quindi notifica ``` Trigger │ - ├── Branch A: Update Customer Record + ├── Diramazione A: Aggiorna il record cliente │ - └── Branch B: Create Support Ticket + └── Diramazione B: Crea ticket di assistenza ↘ ↙ - Merged Step: Send Confirmation Email + Passaggio riunito: Invia email di conferma ``` -The confirmation email sends only after both the customer update and ticket creation are done. +L'email di conferma viene inviata solo dopo che sia l'aggiornamento del cliente sia la creazione del ticket sono stati completati. ## Migliori Pratiche -* Always use **Filter nodes** at the start of branches when you want conditional execution -* Keep branch conditions **mutually exclusive** to avoid duplicate actions -* Test your workflows with different data to ensure the correct branches run -* **Rename branch steps** descriptively so it's clear what each path does -* **Merge branches** when you need a final action after parallel processing +* Usa sempre i **nodi Filtro** all'inizio delle diramazioni quando desideri un'esecuzione condizionale +* Mantieni le condizioni delle diramazioni **mutuamente esclusive** per evitare azioni duplicate +* Testa i tuoi flussi di lavoro con dati diversi per assicurarti che vengano eseguite le diramazioni corrette +* **Rinomina i passaggi delle diramazioni** in modo descrittivo, così è chiaro cosa fa ogni percorso +* **Riunisci le diramazioni** quando ti serve un'azione finale dopo l'elaborazione parallela -## Related +## Correlati -* [Workflows FAQ](/l/it/user-guide/workflows/how-tos/need-more-help/workflows-faq) — answers about parallel execution -* [Workflow Actions](/l/it/user-guide/workflows/capabilities/workflow-actions) — available actions for branches +* [Domande frequenti sui flussi di lavoro](/l/it/user-guide/workflows/how-tos/need-more-help/workflows-faq) — risposte sull'esecuzione parallela +* [Azioni dei flussi di lavoro](/l/it/user-guide/workflows/capabilities/workflow-actions) — azioni disponibili per le diramazioni diff --git a/packages/twenty-docs/l/ro/user-guide/data-migration/how-tos/fix-import-errors.mdx b/packages/twenty-docs/l/ro/user-guide/data-migration/how-tos/fix-import-errors.mdx index 96b28f7d3d..f5cc9ab66c 100644 --- a/packages/twenty-docs/l/ro/user-guide/data-migration/how-tos/fix-import-errors.mdx +++ b/packages/twenty-docs/l/ro/user-guide/data-migration/how-tos/fix-import-errors.mdx @@ -1,11 +1,11 @@ --- -title: Fix Import Errors -description: Complete troubleshooting guide for resolving CSV import errors. +title: Remediați erorile de import +description: Ghid complet de depanare pentru remedierea erorilor de import CSV. --- ## Prezentare generală -Import not working? This guide helps you identify and fix common import errors step by step. +Importul nu funcționează? Acest ghid vă ajută să identificați și să remediați, pas cu pas, erorile comune de import. ## How Import Validation Works diff --git a/packages/twenty-docs/l/ro/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx b/packages/twenty-docs/l/ro/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx index 82e4a07c58..77628cea7b 100644 --- a/packages/twenty-docs/l/ro/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx +++ b/packages/twenty-docs/l/ro/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx @@ -1,103 +1,103 @@ --- -title: Import Relations Between Objects via CSV -description: Complete step-by-step guide to linking records during CSV import. +title: Importați relațiile dintre obiecte prin CSV +description: Ghid complet, pas cu pas, pentru asocierea înregistrărilor în timpul importului CSV. --- ## Prezentare generală -This guide walks you through importing relations between objects—for example, linking People to Companies, or Opportunities to People. +Acest ghid vă arată cum să importați relațiile dintre obiecte — de exemplu, să asociați Persoane la Companii sau Oportunități la Persoane. -**What can be imported:** Only one-to-many relations pointing to a single object type. Relations pointing to multiple object types (like Notes linking to People AND Companies) are not yet supported for import. +**Ce poate fi importat:** Doar relații de tip unu-la-mulți care indică către un singur tip de obiect. Relațiile care indică către mai multe tipuri de obiect (cum ar fi Notele care se leagă de Persoane ȘI Companii) nu sunt încă acceptate pentru import. -## Understanding Relations +## Înțelegerea relațiilor -### What is a "One-to-Many" Relation? +### Ce este o relație "unu-la-mulți"? -In a one-to-many relation: +Într-o relație unu-la-mulți: -* **One** Company has **many** People (employees) -* **One** Company has **many** Opportunities -* **One** Person has **many** Tasks +* **O** companie are **multe** persoane (angajați) +* **O** companie are **multe** oportunități +* **O** persoană are **multe** sarcini -The "one" side is the **parent**. The "many" side is the **child**. +Partea "unu" este **părintele**. Partea "mulți" este **copilul**. -### Common Relations in Twenty +### Relații obișnuite în Twenty -| Relație | "One" Side (Parent) | "Many" Side (Child) | -| ------------------------- | ------------------- | ------------------- | -| Companies → People | Companie | Persoane | -| Companies → Opportunities | Companie | Oportunități | -| People → Tasks | Persoană | Sarcini | -| People → Notes | Persoană | Notițe | +| Relație | Partea "unu" (părinte) | Partea "mulți" (copil) | +| ----------------------- | ---------------------- | ---------------------- | +| Companii → Persoane | Companie | Persoane | +| Companii → Oportunități | Companie | Oportunități | +| Persoane → Sarcini | Persoană | Sarcini | +| Persoane → Note | Persoană | Notițe | -## Step 1: Identify the "One" and "Many" Sides +## Pasul 1: Identificați părțile „unu” și „mulți” -Before importing, determine which object is the parent and which is the child. +Înainte de import, stabiliți care obiect este părinte și care este copil. -**Ask yourself:** "Does ONE [Object A] have MANY [Object B]?" +**Întrebați-vă:** "Are UN [Obiect A] MULTE [Obiect B]?" -* One Company → Many People ✓ (Company is parent) -* One Person → Many Companies ✗ (This is wrong—a person belongs to one company) +* O companie → Multe persoane ✓ (Compania este părinte) +* O persoană → Multe companii ✗ (Greșit — o persoană aparține unei singure companii) -## Step 2: Import the Parent Records First +## Pasul 2: Importați mai întâi înregistrările părinte -The parent ("one" side) must exist in Twenty before you can reference it. +Înregistrarea părinte (partea „unu”) trebuie să existe în Twenty înainte de a o putea referi. -**Import order:** +**Ordinea importului:** -1. **Companies** first (no dependencies) -2. **People** second (link to Companies) -3. **Opportunities** third (link to Companies and/or People) -4. **Tasks/Notes** (link to any of the above) +1. **Companii** mai întâi (fără dependențe) +2. **Persoane** în al doilea rând (legate de Companii) +3. **Oportunități** în al treilea rând (legate de Companii și/sau Persoane) +4. **Sarcini/Note** (legate de oricare dintre cele de mai sus) - **If the parent record doesn't exist, the import will fail.** + **Dacă înregistrarea părinte nu există, importul va eșua.** - Always verify that Companies are imported before importing People with company references. + Verificați întotdeauna că companiile au fost importate înainte de a importa persoane cu referințe la companie. -## Step 3: Note the Parent's Unique Identifier +## Pasul 3: Notați identificatorul unic al părintelui -You need to reference the parent record using a **unique identifier**. Available options: +Trebuie să faceți referire la înregistrarea părinte folosind un **identificator unic**. Opțiuni disponibile: -| Parent Object | Available Unique Identifiers | -| -------------------------------- | --------------------------------------------------------------- | -| **Companii** | `id` (UUID), `domain` (recommended), or any custom unique field | -| **People** | `id` (UUID), `email`, or any custom unique field | -| **Membri ai Spațiului de Lucru** | `id` (UUID), `email` (not name) | -| **Obiecte personalizate** | `id` (UUID), or any field marked as unique | +| Obiect părinte | Identificatori unici disponibili | +| -------------------------------- | ------------------------------------------------------------------- | +| **Companii** | `id` (UUID), `domain` (recomandat) sau orice câmp unic personalizat | +| **Persoane** | `id` (UUID), `email` sau orice câmp unic personalizat | +| **Membri ai Spațiului de Lucru** | `id` (UUID), `email` (nu numele) | +| **Obiecte personalizate** | `id` (UUID) sau orice câmp marcat ca unic | -**Recommended:** Use `domain` for Companies and `email` for People. These are human-readable and easy to verify in your spreadsheet. +**Recomandat:** Folosiți `domain` pentru Companii și `email` pentru Persoane. Acestea sunt ușor de citit de către oameni și ușor de verificat în foaia de calcul. -### Finding the Identifier +### Găsirea identificatorului -If you need the `id`: +Dacă aveți nevoie de `id`: -1. Export the parent records from Twenty -2. The export includes the `id` column -3. Use these IDs in your child records file +1. Exportați înregistrările părinte din Twenty +2. Exportul include coloana `id` +3. Folosiți aceste ID-uri în fișierul cu înregistrări copil -## Step 4: Verify the Relation Field Exists +## Pasul 4: Verificați existența câmpului de relație -Before importing, ensure the relation field exists between your objects. +Înainte de import, asigurați-vă că există câmpul de relație între obiectele dvs. -**To check or create:** +**Pentru a verifica sau crea:** -1. Go to **Settings → Data Model** -2. Select your child object (e.g., People) -3. Look for a relation field pointing to the parent (e.g., Company) -4. If it doesn't exist, create it: - * Click **+ Add field** - * Select **Relation** type - * Choose the parent object +1. Accesați **Setări → Model de date** +2. Selectați obiectul copil (de ex., Persoane) +3. Căutați un câmp de relație care indică către părinte (de ex., Companie) +4. Dacă nu există, creați-l: + * Faceți clic pe **+ Adaugă câmp** + * Selectați tipul **Relație** + * Alegeți obiectul părinte -## Step 5: Prepare Your CSV File +## Pasul 5: Pregătiți fișierul CSV -Add a column to your child CSV that references the parent using its unique identifier. +Adăugați o coloană în CSV-ul obiectului copil care face referire la părinte folosind identificatorul său unic. -### Example: People Linking to Companies +### Exemplu: Persoane asociate cu Companii -**Your People CSV:** +**CSV-ul dvs. cu Persoane:** ```csv firstName,lastName,email,jobTitle,companyDomain @@ -106,66 +106,66 @@ Jane,Doe,jane@widgets.co,CTO,https://widgets.co Bob,Johnson,bob@techstart.io,Developer,https://techstart.io ``` -The `companyDomain` column references the Company's domain. +Coloana `companyDomain` face referire la domeniul companiei. -### Format Requirements +### Cerințe de format | Identificator | Format | Exemplu | | ------------- | -------------- | -------------------------------------- | -| Domeniu | URL format | `https://acme.com` | -| Email | Standard email | `john@acme.com` | +| Domeniu | Format URL | `https://acme.com` | +| Email | Email standard | `john@acme.com` | | ID | UUID | `c776ee49-f608-4a77-8cc8-6fe96ae1e43f` | - **Domain format matters!** + **Formatul domeniului contează!** - Use `https://domain.com` (not just `domain.com`). This matches how Twenty stores Company domains and prevents matching errors. + Folosiți `https://domain.com` (nu doar `domain.com`). Acest lucru corespunde modului în care Twenty stochează domeniile companiilor și previne erorile de potrivire. -### Important Rules +### Reguli importante -1. **Exact match required** — the value must exactly match the parent record -2. **Map only ONE unique identifier** — don't include both `companyId` AND `companyDomain` -3. **Case sensitive** — `Acme.com` ≠ `acme.com` +1. **Potrivire exactă necesară** — valoarea trebuie să corespundă exact înregistrării părinte +2. **Mapați doar UN identificator unic** — nu includeți atât `companyId`, cât și `companyDomain` +3. **Sensibil la majuscule/minuscule** — `Acme.com` ≠ `acme.com` -## Step 6: Upload and Map the Relation +## Pasul 6: Încărcați și mapați relația -1. Navigate to the child object (e.g., People) -2. Click **⋮** → **Import records** -3. Upload your CSV file -4. In the field mapping step: - * Find your relation column (e.g., `companyDomain`) - * Map it to the **Company** relation field -5. Complete the remaining mapping -6. Review errors and confirm +1. Navigați la obiectul copil (de ex., Persoane) +2. Faceți clic pe **⋮** → **Import records** +3. Încărcați fișierul CSV +4. În etapa de mapare a câmpurilor: + * Găsiți coloana relației (de ex., `companyDomain`) + * Mapați-o la câmpul de relație **Company** +5. Finalizați maparea rămasă +6. Revizuiți erorile și confirmați -Twenty will automatically link each child record to the matching parent. +Twenty va lega automat fiecare înregistrare copil de părintele corespunzător. -## Step 7: Verify the Import +## Pasul 7: Verificați importul -After importing: +După import: -1. Open a few child records (e.g., People) -2. Verify the relation field shows the correct parent (e.g., Company) -3. Open a parent record and check the related records section +1. Deschideți câteva înregistrări copil (de ex., Persoane) +2. Verificați că câmpul de relație arată părintele corect (de ex., Companie) +3. Deschideți o înregistrare părinte și verificați secțiunea de înregistrări asociate -## Common Mistakes to Avoid +## Greșeli comune de evitat -| Mistake | Problem | Solution | -| -------------------------- | -------------------------------------------------- | ------------------------------------------------------- | -| **Wrong import order** | Importing People before Companies | Always import parents first, then children | -| **Wrong domain format** | Using `acme.com` instead of `https://acme.com` | Use full URL format with `https://` | -| **Multiple unique fields** | Mapping both `companyId` AND `companyDomain` | Map only ONE unique identifier | -| **Missing relation field** | The relation field doesn't exist in the data model | Create it in **Settings → Data Model** before importing | -| **Non-existent records** | The parent record doesn't exist in Twenty | Import parent records first, or check for typos | -| **Case mismatch** | `Acme.com` in file but `acme.com` in Twenty | Ensure exact case matching | +| Greșeală | Problemă | Soluție | +| -------------------------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------------ | +| **Ordine greșită a importului** | Importarea Persoanelor înaintea Companiilor | Importați întotdeauna mai întâi părinții, apoi copiii | +| **Format de domeniu greșit** | Folosirea `acme.com` în loc de `https://acme.com` | Folosiți formatul URL complet cu `https://` | +| **Câmpuri unice multiple** | Maparea atât a `companyId`, cât și a `companyDomain` | Mapați un singur identificator unic | +| **Câmp de relație lipsă** | Câmpul de relație nu există în modelul de date | Creați-l în **Setări → Model de date** înainte de import | +| **Înregistrări inexistente** | Înregistrarea părinte nu există în Twenty | Importați mai întâi înregistrările părinte sau verificați greșelile de tastare | +| **Nepotrivire de majuscule/minuscule** | `Acme.com` în fișier, dar `acme.com` în Twenty | Asigurați potrivirea exactă a majusculelor/minusculelor | -## Linking to Workspace Members +## Legarea la membrii spațiului de lucru -When linking to Workspace Members (your team): +Când legați la membrii spațiului de lucru (echipa dvs.): -* Use their **email address**, not their name -* Example: `owner@yourcompany.com`, not "John Smith" +* Folosiți **adresa de email**, nu numele +* Exemplu: `owner@yourcompany.com`, nu "John Smith" ```csv taskName,assignedTo @@ -173,56 +173,56 @@ Follow up with client,john@yourcompany.com Review proposal,jane@yourcompany.com ``` -## FAQ +## Întrebări frecvente - - You have two options: + + Aveți două opțiuni: - 1. Use the Twenty `id` (export parent records to get their IDs) - 2. Create a custom unique field in your data model to store an external ID from your previous system + 1. Folosiți `id`-ul Twenty (exportați înregistrările părinte pentru a obține ID-urile lor) + 2. Creați un câmp unic personalizat în modelul dvs. de date pentru a stoca un ID extern din sistemul anterior - - Da! Include the child record's unique identifier (e.g., `email` for People) and the new relation value. The import will update the relation. + + Da! Includeți identificatorul unic al înregistrării copil (de ex., `email` pentru Persoane) și noua valoare a relației. Importul va actualiza relația. - - Many-to-Many relations are not yet supported for import. This is planned for H1 2026. + + Relațiile mulți-la-mulți nu sunt încă acceptate pentru import. Aceasta este planificată pentru S1 2026. - - Relations pointing to multiple object types are not yet supported for import/export. This is on our roadmap. + + Relațiile care indică către mai multe tipuri de obiecte nu sunt încă acceptate pentru import/export. Această funcționalitate este în planul nostru de dezvoltare. - - The import will show an error for that row. Puteți fie să: + + Importul va afișa o eroare pentru acel rând. Puteți fie să: - * Import the parent record first, then re-import - * Fix the reference value - * Remove the row from import + * Importați mai întâi înregistrarea părinte, apoi reimportați + * Corectați valoarea de referință + * Eliminați rândul din import - - Common causes: + + Cauze comune: - * Wrong format (use `https://domain.com` for domains) - * Case mismatch (check exact spelling) - * Parent doesn't exist (import parents first) - * Mapping multiple identifiers (use only one) + * Format greșit (folosiți `https://domain.com` pentru domenii) + * Nepotrivire de majuscule/minuscule (verificați ortografia exactă) + * Părintele nu există (importați mai întâi părinții) + * Maparea mai multor identificatori (folosiți doar unul) - **Remember: Soft-deleted records count toward uniqueness.** + **Rețineți: Înregistrările șterse logic se iau în calcul pentru unicitate.** - If you're getting "not found" errors but the record seems to exist, check Command Menu → See deleted records. The parent may have been soft-deleted. + Dacă primiți erori „not found”, dar înregistrarea pare să existe, verificați Command Menu → See deleted records. Este posibil ca părintele să fi fost șters logic. ## Depanare -Having issues? Check: +Aveți probleme? Verificați: -* [How to Fix Import Errors](/l/ro/user-guide/data-migration/how-tos/fix-import-errors) -* [Import Relations Capabilities](/l/ro/user-guide/data-migration/capabilities/import-relations) -* [Uniqueness Constraints](/l/ro/user-guide/data-migration/capabilities/uniqueness-constraints) +* [Cum să remediați erorile de import](/l/ro/user-guide/data-migration/how-tos/fix-import-errors) +* [Capabilități de import al relațiilor](/l/ro/user-guide/data-migration/capabilities/import-relations) +* [Constrângeri de unicitate](/l/ro/user-guide/data-migration/capabilities/uniqueness-constraints) diff --git a/packages/twenty-docs/l/ro/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx b/packages/twenty-docs/l/ro/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx index 49e120b119..cbe9546b9d 100644 --- a/packages/twenty-docs/l/ro/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx +++ b/packages/twenty-docs/l/ro/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx @@ -1,73 +1,73 @@ --- title: Migrarea de la Self-Hosted la Cloud -description: Step-by-step guide to migrate your Twenty self-hosted instance to Twenty Cloud. +description: Ghid pas cu pas pentru migrarea instanței Twenty auto-găzduite la Twenty Cloud. --- ## Prezentare generală -This guide walks you through migrating your data from a Twenty self-hosted instance to Twenty Cloud. The process involves setting up your cloud workspace, exporting your data, and re-importing it. +Acest ghid vă ghidează prin migrarea datelor dvs. dintr-o instanță Twenty auto-găzduită către Twenty Cloud. Procesul presupune configurarea spațiului dvs. de lucru în cloud, exportarea datelor și reimportarea acestora. -Views, workflows, and roles must be recreated manually after migration. Plan time for this configuration work. +Vizualizările, fluxurile de lucru și rolurile trebuie recreate manual după migrare. Planificați timp pentru această muncă de configurare. -## Step 1: Create Your Cloud Workspace +## Pasul 1: Creați spațiul dvs. de lucru în cloud -1. Go to [app.twenty.com](https://app.twenty.com) and create a new workspace -2. Complete the initial setup wizard -3. Note your new workspace URL +1. Accesați [app.twenty.com](https://app.twenty.com) și creați un nou spațiu de lucru +2. Finalizați asistentul de configurare inițială +3. Notați URL-ul noului spațiu de lucru -## Step 2: Recreate Your Data Model +## Pasul 2: Recreați modelul de date -Before importing data, recreate your custom objects and fields: +Înainte de a importa datele, recreați obiectele și câmpurile personalizate: -1. Go to **Settings → Data Model** in your cloud instance -2. Create custom objects that match your self-hosted setup -3. Add custom fields to standard and custom objects -4. Configure field settings (unique, required, etc.) +1. Accesați **Setări → Model de date** în instanța dvs. din cloud +2. Creați obiecte personalizate care corespund configurației dvs. auto-găzduite +3. Adăugați câmpuri personalizate la obiectele standard și personalizate +4. Configurați setările câmpurilor (unic, obligatoriu etc.) -Take screenshots of your self-hosted data model for reference, or keep both instances open side by side. +Faceți capturi de ecran ale modelului de date auto-găzduit pentru referință sau păstrați ambele instanțe deschise una lângă alta. -## Step 3: Invite All Users +## Pasul 3: Invitați toți utilizatorii - **Critical: Invite users BEFORE importing data.** + **Important: Invitați utilizatorii ÎNAINTE de a importa datele.** - Users must accept their invitations before you import any records that reference them (like Account Owner fields). If users don't exist yet, those relations cannot be mapped. + Utilizatorii trebuie să accepte invitațiile înainte de a importa orice înregistrări care îi referențiază (cum ar fi câmpurile Account Owner). Dacă utilizatorii nu există încă, acele relații nu pot fi mapate. -1. Go to **Settings → Members** in your cloud instance -2. Invite all team members who had accounts on self-hosted -3. **Wait for everyone to accept** their invitation -4. Verify all users appear in your Members list +1. Accesați **Setări → Membri** în instanța dvs. din cloud +2. Invitați toți membrii echipei care aveau conturi pe instanța auto-găzduită +3. **Așteptați ca toți să accepte** invitațiile +4. Verificați că toți utilizatorii apar în lista de Membri -## Step 4: Export Data from Self-Hosted +## Pasul 4: Exportați date din instanța auto-găzduită -Export each object from your self-hosted instance: +Exportați fiecare obiect din instanța auto-găzduită: -1. Navigate to each object (Companies, People, Opportunities, etc.) -2. Configure the view to show **all columns** you want to migrate -3. Click **⋮ → Export view** -4. Save each CSV file with a clear name (e.g., `companies-export.csv`) +1. Navigați la fiecare obiect (Companii, Persoane, Oportunități etc.) +2. Configurați vizualizarea pentru a afișa **toate coloanele** pe care doriți să le migrați +3. Faceți clic pe **⋮ → Export view** +4. Salvați fiecare fișier CSV cu un nume clar (de ex., `companies-export.csv`) -**Export in this order** (for reference when importing): +**Exportați în această ordine** (pentru referință la importare): 1. Companii 2. Persoane 3. Oportunități -4. Custom objects (following their dependencies) -5. Tasks, Notes +4. Obiecte personalizate (urmând dependențele lor) +5. Sarcini, Note -## Step 5: Update Workspace Member References +## Pasul 5: Actualizați referințele la membrii spațiului de lucru -The exported CSVs contain user IDs from your self-hosted instance. These IDs won't match your cloud instance, so you need to replace them with emails. +CSV-urile exportate conțin ID-uri de utilizator din instanța dvs. auto-găzduită. Aceste ID-uri nu vor corespunde cu instanța din cloud, deci trebuie să le înlocuiți cu adrese de e-mail. -**For each CSV file with user references (Owner, Assignee, etc.):** +**Pentru fiecare fișier CSV cu referințe la utilizatori (Owner, Assignee etc.):** -1. Open the CSV in a spreadsheet application -2. Add a new column next to each user ID column (e.g., `accountOwnerEmail` next to `accountOwnerId`) -3. Fill in the **email address** of each user -4. You can delete the old ID column or leave it (it will be skipped during import) +1. Deschideți fișierul CSV într-o aplicație de foi de calcul +2. Adăugați o coloană nouă lângă fiecare coloană cu ID de utilizator (de ex., `accountOwnerEmail` lângă `accountOwnerId`) +3. Completați **adresa de e-mail** a fiecărui utilizator +4. Puteți șterge coloana veche de ID sau o puteți lăsa (va fi omisă în timpul importului) -**Example:** +**Exemplu:** Înainte: @@ -83,89 +83,89 @@ name,domain,accountOwnerEmail Acme Corp,https://acme.com,john@yourcompany.com ``` -Use the same email addresses that users used to accept their cloud workspace invitation. +Folosiți aceleași adrese de e-mail pe care utilizatorii le-au folosit pentru a accepta invitația la spațiul de lucru din cloud. -## Step 6: Plan Your Import Order +## Pasul 6: Planificați ordinea de import -Import files in the correct order to maintain relationships: +Importați fișierele în ordinea corectă pentru a păstra relațiile: -1. **Companies** first (no dependencies) -2. **People** second (link to Companies) -3. **Opportunities** third (link to Companies and People) -4. **Custom objects** (following their dependencies) -5. **Tasks and Notes** last (link to other records) +1. **Companii** mai întâi (fără dependențe) +2. **Persoane** în al doilea rând (legate de Companii) +3. **Oportunități** în al treilea rând (legate de Companii și Persoane) +4. **Obiecte personalizate** (urmând dependențele lor) +5. **Sarcini și Note** la final (legate de alte înregistrări) -See [How to Import Relations](/l/ro/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv) for details on maintaining relationships. +Consultați [Cum să importați relații](/l/ro/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv) pentru detalii despre menținerea relațiilor. -## Step 7: Import to Cloud +## Pasul 7: Importați în cloud -For each CSV file, in order: +Pentru fiecare fișier CSV, în ordine: -1. Navigate to the object in your cloud instance -2. Click **⋮ → Import records** -3. Upload the CSV file -4. Map columns to fields: - * Map user email columns to the appropriate relation fields - * Map other columns as usual -5. Review and fix any errors -6. Confirm the import -7. Verify a few records before proceeding to the next file +1. Navigați la obiectul din instanța dvs. din cloud +2. Faceți clic pe **⋮ → Import records** +3. Încărcați fișierul CSV +4. Mapați coloanele la câmpuri: + * Mapați coloanele de e-mail ale utilizatorilor la câmpurile de relație corespunzătoare + * Mapați celelalte coloane ca de obicei +5. Revizuiți și remediați eventualele erori +6. Confirmați importul +7. Verificați câteva înregistrări înainte de a trece la următorul fișier -## Step 8: Recreate Configuration +## Pasul 8: Recreați configurația -After importing data, manually recreate: +După importarea datelor, recreați manual: ### Vizualizări -* Recreate saved views with filters, sorts, and column configurations -* Set up any kanban or calendar views +* Recreați vizualizările salvate cu filtre, sortări și configurații de coloane +* Configurați orice vizualizări kanban sau calendar ### Fluxuri de lucru -* Recreate automations in **Settings → Workflows** -* Test each workflow before relying on it +* Recreați automatizările în **Setări → Fluxuri de lucru** +* Testați fiecare flux de lucru înainte de a vă baza pe el -### Roles and Permissions +### Roluri și permisiuni -* Configure roles in **Settings → Roles** -* Assign users to appropriate roles +* Configurați rolurile în **Setări → Roluri** +* Atribuiți utilizatorilor rolurile corespunzătoare ### Integrări -* Reconnect email and calendar sync for each user -* Reconfigure any API integrations with new API keys +* Reconectați sincronizarea e-mailului și a calendarului pentru fiecare utilizator +* Reconfigurați orice integrări API cu chei API noi ## Lista de Verificare Post-Migrare -All data imported successfully -Relations between objects working correctly -User assignments (Owner, Assignee) mapped correctly -Views recreated -Workflows recreated and tested -Roles and permissions configured -Email/calendar sync reconnected -API integrations updated with new keys +Toate datele importate cu succes +Relațiile dintre obiecte funcționează corect +Atribuirile utilizatorilor (Owner, Assignee) mapate corect +Vizualizări recreate +Fluxuri de lucru recreate și testate +Roluri și permisiuni configurate +Sincronizarea e-mailului/calendarului reconectată +Integrările API actualizate cu chei noi -## FAQ +## Întrebări frecvente - - Not currently. Workflows must be recreated manually in your cloud instance. + + Momentan, nu. Fluxurile de lucru trebuie recreate manual în instanța dvs. din cloud. - - File attachments are not included in CSV exports. You'll need to re-upload any attachments manually, migrate them via API or contact our team for assistance with large migrations. + + Atașamentele de fișiere nu sunt incluse în exporturile CSV. Va trebui să reîncărcați manual orice atașamente, să le migrați prin API sau să contactați echipa noastră pentru asistență la migrarea de volum mare. - - Yes, we recommend keeping your self-hosted instance running until you've verified the cloud migration is complete. Just be careful not to create new data in both places. + + Da, recomandăm să păstrați instanța auto-găzduită în funcțiune până când ați verificat că migrarea în cloud este completă. Aveți doar grijă să nu creați date noi în ambele locuri. - - Records referencing that user will fail to import or the relation will be empty. Ensure all users accept invitations before importing data. + + Înregistrările care fac referire la acel utilizator nu se vor importa sau relația va fi goală. Asigurați-vă că toți utilizatorii acceptă invitațiile înainte de a importa datele. ## Ai nevoie de ajutor? -For complex migrations or large datasets, contact us at [contact@twenty.com](mailto:contact@twenty.com) or explore our [Implementation Services](/l/ro/user-guide/getting-started/capabilities/implementation-services). +Pentru migrarea complexă sau seturi mari de date, contactați-ne la [contact@twenty.com](mailto:contact@twenty.com) sau explorați [Serviciile noastre de implementare](/l/ro/user-guide/getting-started/capabilities/implementation-services). diff --git a/packages/twenty-docs/l/ro/user-guide/introduction.mdx b/packages/twenty-docs/l/ro/user-guide/introduction.mdx index 387917727b..734ac933a3 100644 --- a/packages/twenty-docs/l/ro/user-guide/introduction.mdx +++ b/packages/twenty-docs/l/ro/user-guide/introduction.mdx @@ -1,63 +1,63 @@ --- -title: Discover Twenty -description: Welcome to Twenty User Guide, your resources for advanced configurations and best practices. +title: Descoperiți Twenty +description: Bine ați venit în Ghidul utilizatorului Twenty, resursa dvs. pentru configurări avansate și bune practici. --- import { CardTitle } from "/snippets/card-title.mdx" - Discover Twenty - Learn what Twenty is and how it can help your business. + Descoperiți Twenty + Aflați ce este Twenty și cum vă poate ajuta afacerea. - Data Model - Customize your data model to fit your business processes. + Model de date + Personalizați modelul de date pentru a se potrivi proceselor dvs. de afaceri. - Data Migration - Import and export your data via CSV or API. + Migrarea datelor + Importați și exportați datele prin CSV sau API. - Calendar & Emails - Centralize your team's meetings and emails. + Calendar și e-mailuri + Centralizați întâlnirile și e-mailurile echipei. - Workflows - Automate processes and integrate with external tools. + Fluxuri de lucru + Automatizați procesele și integrați cu instrumente externe. - AI - Enhance your team with AI agents. + IA + Îmbunătățiți-vă echipa cu agenți IA. - Views & Pipelines - Organize your data with actionable views and pipelines. + Vizualizări și pipeline-uri + Organizați-vă datele cu vizualizări acționabile și pipeline-uri. - Dashboards - Real-time insights to track performance. + Tablouri de bord + Perspective în timp real pentru a urmări performanța. - Permissions & Access - Manage roles and access to Twenty. + Permisiuni și acces + Gestionați rolurile și accesul la Twenty. - Billing - Understand how Twenty pricing and billing works. + Facturare + Înțelegeți cum funcționează prețurile și facturarea în Twenty. - Settings - Configure your workspace preferences. + Setări + Configurați preferințele spațiului de lucru. diff --git a/packages/twenty-docs/l/ro/user-guide/permissions-access/how-tos/permissions-faq.mdx b/packages/twenty-docs/l/ro/user-guide/permissions-access/how-tos/permissions-faq.mdx index d6751ca09e..193544ace6 100644 --- a/packages/twenty-docs/l/ro/user-guide/permissions-access/how-tos/permissions-faq.mdx +++ b/packages/twenty-docs/l/ro/user-guide/permissions-access/how-tos/permissions-faq.mdx @@ -1,126 +1,126 @@ --- -title: Permissions FAQ -description: Frequently asked questions about roles and permissions. +title: Întrebări frecvente despre permisiuni +description: Întrebări frecvente despre roluri și permisiuni. --- ## Roluri - - Twenty comes with an **Admin** and **Member** roles by default. You can create additional custom roles based on your team's needs (e.g., Sales Rep, Manager, Read-Only User). + + Twenty include în mod implicit rolurile **Admin** și **Member**. Puteți crea roluri personalizate suplimentare în funcție de nevoile echipei dvs. (de exemplu, Reprezentant de vânzări, Manager, Utilizator doar pentru citire). - - No, the Admin role cannot be deleted. There must always be at least one member assigned to the Admin role. + + Nu, rolul Admin nu poate fi șters. Trebuie să existe întotdeauna cel puțin un membru atribuit rolului Admin. - - Any workspace member assigned to that role will be automatically reassigned to the default role. + + Orice membru al spațiului de lucru atribuit acelui rol va fi reatribuit automat rolului implicit. - - Go to **Settings → Roles**, find the **Default Role** option, and select which role new members should automatically receive when they join. + + Accesați **Settings → Roles**, găsiți opțiunea **Default Role** și selectați ce rol ar trebui să primească automat noii membri când se alătură. - - No, each user can only have one role at a time. Create a custom role if you need a combination of permissions. + + Nu, fiecare utilizator poate avea un singur rol la un moment dat. Creați un rol personalizat dacă aveți nevoie de o combinație de permisiuni. ## Permisiuni - - * **Object permissions**: Control access to entire records (e.g., can see/edit/delete People records) - * **Field permissions**: Control access to specific fields within an object (e.g., can see but not edit the Salary field) + + * **Permisiuni pentru obiecte**: Controlează accesul la înregistrări întregi (de exemplu, pot vedea/edita/șterge înregistrări People) + * **Permisiuni pentru câmpuri**: Controlează accesul la câmpuri specifice dintr-un obiect (de exemplu, pot vedea, dar nu pot edita câmpul Salary) - Field permissions allow more granular control over sensitive data. + Permisiunile pentru câmpuri permit un control mai granular asupra datelor sensibile. - - Permissions cascade from global to specific: + + Permisiunile se propagă în cascadă de la global la specific: - 1. **All Objects** sets the baseline for all objects - 2. **Object-Level Permissions** can override the global setting for specific objects - 3. **Field-Level Permissions** can override the object setting for specific fields + 1. **All Objects** stabilește configurația de bază pentru toate obiectele + 2. **Object-Level Permissions** pot suprascrie setarea globală pentru anumite obiecte + 3. **Field-Level Permissions** pot suprascrie setarea la nivel de obiect pentru anumite câmpuri - More specific settings always take precedence. + Setările mai specifice au întotdeauna prioritate. - - For objects: + + Pentru obiecte: - * **See Records**: View records in lists and detail pages - * **Edit Records**: Modify existing records - * **Delete Records**: Soft-delete records (can be restored) - * **Destroy Records**: Permanently delete records + * **See Records**: Vizualizați înregistrările în liste și în paginile de detaliu + * **Edit Records**: Modificați înregistrările existente + * **Delete Records**: Ștergeți temporar înregistrările (pot fi restaurate) + * **Destroy Records**: Ștergeți definitiv înregistrările - For fields: + Pentru câmpuri: - * **See Field**: View the field value - * **Edit Field**: Modify the field value - * **No Access**: Field is completely hidden + * **See Field**: Vizualizați valoarea câmpului + * **Edit Field**: Modificați valoarea câmpului + * **No Access**: Câmpul este complet ascuns - - Row-level permissions will be available on the **Organization** plan by Q1 2026. This allows you to restrict access to specific records based on criteria (e.g., only see your own opportunities). + + Permisiunile la nivel de rând vor fi disponibile în planul **Organization** până în trimestrul I 2026. Acest lucru vă permite să restricționați accesul la anumite înregistrări pe baza unor criterii (de exemplu, să vedeți doar propriile oportunități). - + 1. Accesați **Setări → Roluri** - 2. Select the role - 3. Navigate to the object containing the field - 4. Set the field permission to **See Field** (without Edit Field) + 2. Selectați rolul + 3. Navigați la obiectul care conține câmpul + 4. Setați permisiunea câmpului la **See Field** (fără Edit Field) -## Settings & Actions +## Setări și acțiuni - - You can control access to: + + Puteți controla accesul la: - * API key generation - * Workspace preferences - * Role assignment - * Data model configuration - * Security settings - * Workflow management + * Generarea cheilor API + * Preferințe ale spațiului de lucru + * Atribuirea rolurilor + * Configurarea modelului de date + * Setări de securitate + * Gestionarea fluxurilor de lucru - Use **Settings All Access** to grant full access, or enable specific permissions. + Folosiți **Settings All Access** pentru a acorda acces complet, sau activați permisiuni specifice. - - You can control: + + Puteți controla: - * **Send Email**: Ability to send emails from Twenty - * **Import CSV**: Ability to import data via CSV - * **Export CSV**: Ability to export data to CSV + * **Send Email**: Posibilitatea de a trimite e-mailuri din Twenty + * **Import CSV**: Posibilitatea de a importa date prin CSV + * **Export CSV**: Posibilitatea de a exporta date în CSV - Use **Application All Access** to grant all actions, or enable specific ones. + Folosiți **Application All Access** pentru a permite toate acțiunile, sau activați doar pe cele specifice. ## Autentificare Unică - - No, SSO is a Premium feature available on the **Organization** plan only. + + Nu, SSO este o funcționalitate Premium disponibilă doar în planul **Organization**. - - Twenty supports: + + Twenty acceptă: - * **SAML 2.0** (works with most enterprise identity providers) + * **SAML 2.0** (funcționează cu majoritatea furnizorilor de identitate pentru întreprinderi) * **Google Workspace** - * **Microsoft Entra ID** (formerly Azure AD) + * **Microsoft Entra ID** (fostul Azure AD) - - With JIT provisioning, user accounts are automatically created in Twenty when someone logs in via SSO for the first time. They're assigned the default role automatically. + + Cu provisionarea JIT, conturile de utilizator sunt create automat în Twenty atunci când cineva se autentifică prin SSO pentru prima dată. Li se atribuie automat rolul implicit. - - Yes, once SSO is configured, you can disable password login for SSO users to enforce authentication through your identity provider. + + Da, odată ce SSO este configurat, puteți dezactiva autentificarea cu parolă pentru utilizatorii SSO, pentru a impune autentificarea prin furnizorul dvs. de identitate. diff --git a/packages/twenty-docs/l/ro/user-guide/settings/how-tos/settings-faq.mdx b/packages/twenty-docs/l/ro/user-guide/settings/how-tos/settings-faq.mdx index 42c9aebdfd..8738dfa197 100644 --- a/packages/twenty-docs/l/ro/user-guide/settings/how-tos/settings-faq.mdx +++ b/packages/twenty-docs/l/ro/user-guide/settings/how-tos/settings-faq.mdx @@ -1,136 +1,136 @@ --- title: Întrebări frecvente privind setările -description: Frequently asked questions about Twenty settings. +description: Întrebări frecvente despre setările Twenty. image: /images/user-guide/setup/settings.png --- ## Setări Spațiu de Lucru - - 1. Go to **Settings → General** - 2. Find the Workspace Name field - 3. Enter your new name - 4. Changes save automatically + + 1. Accesați **Setări → General** + 2. Găsiți câmpul „Numele spațiului de lucru” + 3. Introduceți noul nume + 4. Modificările sunt salvate automat - - 1. Go to **Settings → General** - 2. Click on the current logo or upload area - 3. Select an image file (PNG, JPEG, or GIF under 10MB) - 4. The logo updates immediately + + 1. Accesați **Setări → General** + 2. Faceți clic pe sigla actuală sau pe zona de încărcare + 3. Selectați un fișier imagine (PNG, JPEG sau GIF sub 10 MB) + 4. Sigla se actualizează imediat - - Yes, you can create and be a member of multiple workspaces. Each workspace has its own data, settings, and subscription. + + Da, puteți crea și să faceți parte din mai multe spații de lucru. Fiecare spațiu de lucru are propriile date, setări și abonament. - - 1. Go to **Settings → General** - 2. Scroll to Danger Zone - 3. Click **Delete workspace** - 4. Confirm the deletion + + 1. Accesați **Setări → General** + 2. Derulați până la Zona de pericol + 3. Faceți clic pe **Șterge spațiul de lucru** + 4. Confirmați ștergerea - Note: This permanently deletes all data and cannot be undone. + Notă: Aceasta șterge definitiv toate datele și nu poate fi anulată. - - Delete the workspaces you no longer need under **Settings → General → Delete workspace**. + + Ștergeți spațiile de lucru de care nu mai aveți nevoie în **Setări → General → Șterge spațiul de lucru**. - Do not delete your **account** (accessible under Settings → Profile): your account is shared among all your workspaces. Deleting your account removes access to ALL workspaces. + Nu vă ștergeți **contul** (accesibil la Setări → Profil): contul dvs. este partajat între toate spațiile de lucru. Ștergerea contului vă elimină accesul la TOATE spațiile de lucru. - - If you want to temporarily disable your workspace (not permanently delete it), go to **Settings → Billing** and click **Cancel Plan**. Your data will be preserved for a grace period. + + Dacă doriți să dezactivați temporar spațiul de lucru (nu să îl ștergeți definitiv), accesați **Setări → Facturare** și faceți clic pe **Anulează planul**. Datele dvs. vor fi păstrate pentru o perioadă de grație. ## Setări profil - - 1. Go to **Settings → Profile** - 2. Find the Password section - 3. Enter your current password - 4. Enter your new password - 5. Save changes + + 1. Accesați **Setări → Profil** + 2. Găsiți secțiunea Parolă + 3. Introduceți parola curentă + 4. Introduceți noua parolă + 5. Salvați modificările - - 1. Go to **Settings → Profile** - 2. Find the 2FA section + + 1. Accesați **Setări → Profil** + 2. Găsiți secțiunea 2FA 3. Apasă pe **Activează 2FA** 4. Scanează codul QR cu aplicația ta de autentificare - 5. Enter the verification code + 5. Introduceți codul de verificare - - To change your email address, please reach out to [contact@twenty.com](mailto:contact@twenty.com). + + Pentru a vă schimba adresa de e-mail, vă rugăm să ne contactați la [contact@twenty.com](mailto:contact@twenty.com). - - 1. Go to **Settings → Profile** - 2. Scroll to Danger Zone + + 1. Accesați **Setări → Profil** + 2. Derulați până la Zona de pericol 3. Apasă pe **Șterge contul** - 4. Confirm by typing your email + 4. Confirmați tastând adresa de e-mail - Note: This removes your access to all workspaces and deletes all emails synced from your connected accounts. + Notă: Aceasta vă retrage accesul la toate spațiile de lucru și șterge toate e-mailurile sincronizate din conturile conectate. ## Setări Experiență - - 1. Go to **Settings → Experience** - 2. Find the Theme section - 3. Select Light, Dark, or System + + 1. Accesați **Setări → Experiență** + 2. Găsiți secțiunea Temă + 3. Selectați Deschis, Întunecat sau Sistem - - 1. Go to **Settings → Experience** - 2. Find Date Format - 3. Select your preferred format - 4. Changes apply immediately + + 1. Accesați **Setări → Experiență** + 2. Găsiți Formatul datei + 3. Selectați formatul preferat + 4. Modificările se aplică imediat - - 1. Go to **Settings → Experience** - 2. Find Time Zone - 3. Select your local time zone - 4. All timestamps will adjust + + 1. Accesați **Setări → Experiență** + 2. Găsiți secțiunea „Fus orar” + 3. Selectați fusul orar local + 4. Toate marcajele de timp vor fi ajustate - - 1. Go to **Settings → Experience** - 2. Find Language - 3. Select from available languages - 4. The interface updates to your selection + + 1. Accesați **Setări → Experiență** + 2. Găsiți secțiunea „Limbă” + 3. Selectați dintre limbile disponibile + 4. Interfața se actualizează în funcție de selecția dvs. -## Account Settings +## Setările contului - + 1. Mergeți la **Setări → Conturi** 2. Faceți clic pe **Adăugați cont** - 3. Choose Google or Microsoft - 4. Authorize access - 5. Configure sync settings + 3. Alegeți Google sau Microsoft + 4. Autorizați accesul + 5. Configurați setările de sincronizare - - Yes, you can connect multiple email accounts. Go to **Settings → Accounts** and add additional accounts as needed. + + Da, puteți conecta mai multe conturi de e-mail. Accesați **Setări → Conturi** și adăugați conturi suplimentare după cum este necesar. - + 1. Mergeți la **Setări → Conturi** - 2. Find the account to remove - 3. Click **Disconnect** - 4. Confirm the action + 2. Găsiți contul pe care doriți să îl eliminați + 3. Faceți clic pe **Deconectează** + 4. Confirmați acțiunea @@ -138,16 +138,16 @@ image: /images/user-guide/setup/settings.png - Da! Go to **Settings → Domains** and click **Customize Domain**. You have two options: + Da! Accesați **Setări → Domenii** și faceți clic pe **Personalizează domeniul**. Aveți două opțiuni: - * **Subdomain**: Use a Twenty subdomain like `yourcompany.twenty.com` - * **Custom domain**: Use your own domain like `crm.yourcompany.com` (requires DNS configuration) + * **Subdomeniu**: Folosiți un subdomeniu Twenty, de exemplu `yourcompany.twenty.com` + * **Domeniu personalizat**: Folosiți propriul domeniu, de exemplu `crm.yourcompany.com` (necesită configurarea DNS) - A subdomain is quick to set up, while a custom domain provides a fully branded experience for your team. + Un subdomeniu se configurează rapid, în timp ce un domeniu personalizat oferă o experiență complet personalizată pentru brandul echipei dvs. - - You can configure approved access domains so team members with company email addresses can automatically join your workspace. Go to **Settings → Domains** and add your company domain (e.g., `yourcompany.com`). + + Puteți configura domenii de acces aprobate astfel încât membrii echipei cu adrese de e-mail ale companiei să se poată alătura automat spațiului dvs. de lucru. Accesați **Setări → Domenii** și adăugați domeniul companiei (de ex., `yourcompany.com`). @@ -164,8 +164,8 @@ image: /images/user-guide/setup/settings.png 1. Go to **Settings → Updates → Early Access** - 2. Find the feature you want - 3. Toggle it on - 4. The feature becomes available immediately + 2. Găsiți funcția dorită + 3. Activați-o + 4. Funcția devine disponibilă imediat diff --git a/packages/twenty-docs/l/ro/user-guide/settings/overview.mdx b/packages/twenty-docs/l/ro/user-guide/settings/overview.mdx index 58ae353db9..3796227165 100644 --- a/packages/twenty-docs/l/ro/user-guide/settings/overview.mdx +++ b/packages/twenty-docs/l/ro/user-guide/settings/overview.mdx @@ -1,6 +1,6 @@ --- title: Setări -description: Set up your Twenty workspace with essential configurations. +description: Configurați spațiul de lucru Twenty cu configurările esențiale. image: /images/user-guide/setup/settings.png --- @@ -8,60 +8,60 @@ image: /images/user-guide/setup/settings.png Setări -## Initial Setup +## Configurare inițială -When you first create your workspace, there are several key settings to configure. +Când creați pentru prima dată spațiul de lucru, există câteva setări cheie de configurat. -### Workspace Name and Logo +### Numele și sigla spațiului de lucru -1. Go to **Settings → General** -2. Update your workspace name -3. Upload your company logo -4. Save your changes +1. Accesați **Setări → General** +2. Actualizați numele spațiului de lucru +3. Încărcați sigla companiei +4. Salvați modificările -### Time Zone and Date Format +### Fusul orar și formatul datei -1. Go to **Settings → Experience** -2. Select your time zone -3. Choose your preferred date format -4. Save your changes +1. Accesați **Setări → Experiență** +2. Selectați fusul orar +3. Alegeți formatul de dată preferat +4. Salvați modificările -## Essential Configurations +## Configurări esențiale -### Connect Email and Calendar +### Conectați e-mailul și calendarul -Set up email and calendar sync: +Configurați sincronizarea e-mailului și a calendarului: 1. Mergeți la **Setări → Conturi** 2. Faceți clic pe **Adăugați cont** -3. Connect your Google or Microsoft account -4. Configure sync settings +3. Conectați contul Google sau Microsoft +4. Configurați setările de sincronizare -→ [Complete email & calendar setup guide](/l/ro/user-guide/calendar-emails/overview) +→ [Ghid complet de configurare a e-mailului și a calendarului](/l/ro/user-guide/calendar-emails/overview) -### Invite Your Team +### Invitați-vă echipa -Add team members to your workspace: +Adăugați membri ai echipei în spațiul de lucru: 1. Mergi la **Setări → Membri** -2. Click **+ Invite** -3. Enter email addresses -4. Assign appropriate roles +2. Faceți clic pe **+ Invită** +3. Introduceți adresele de e-mail +4. Atribuiți rolurile corespunzătoare - Before inviting your team, check the default role under **Settings → Roles**. New members are automatically assigned this role when they join. + Înainte de a vă invita echipa, verificați rolul implicit în **Setări → Roluri**. Noilor membri li se atribuie automat acest rol când se alătură. -## Workspace Settings Checklist +## Listă de verificare pentru setările spațiului de lucru -* Workspace name and logo configured -* Time zone and date format set -* Email and calendar connected -* Team members invited -* Roles and permissions configured +* Numele și sigla spațiului de lucru configurate +* Fusul orar și formatul datei configurate +* Emailul și calendarul conectate +* Membrii echipei invitați +* Rolurile și permisiunile configurate ## Pașii următori -* [Workspace settings](/l/ro/user-guide/settings/capabilities/workspace-settings) -* [Profile settings](/l/ro/user-guide/settings/capabilities/profile-settings) -* [Experience settings](/l/ro/user-guide/settings/capabilities/experience-settings) +* [Setări ale spațiului de lucru](/l/ro/user-guide/settings/capabilities/workspace-settings) +* [Setări ale profilului](/l/ro/user-guide/settings/capabilities/profile-settings) +* [Setări ale experienței](/l/ro/user-guide/settings/capabilities/experience-settings) diff --git a/packages/twenty-docs/l/ro/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx b/packages/twenty-docs/l/ro/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx index 44f789cb1a..e1ad50e02d 100644 --- a/packages/twenty-docs/l/ro/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx +++ b/packages/twenty-docs/l/ro/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx @@ -1,120 +1,120 @@ --- -title: Set Up a Sales Pipeline -description: Configure your sales pipeline to track opportunities through stages. +title: Configurați un pipeline de vânzări +description: Configurați-vă pipeline-ul de vânzări pentru a urmări oportunitățile prin etape. --- import { VimeoEmbed } from '/snippets/vimeo-embed.mdx'; -A sales pipeline in Twenty is a Kanban view of your Opportunities object, where each column represents a stage in your sales process. +Un pipeline de vânzări în Twenty este o vizualizare Kanban a obiectului Oportunități, în care fiecare coloană reprezintă o etapă în procesul dvs. de vânzări. -## Step 1: Configure Your Stages +## Pasul 1: Configurați etapele -Stages are defined in the Opportunities object's **Stage** field. +Etapele sunt definite în câmpul **Etapă** al obiectului Oportunități. -1. Go to **Settings → Data Model** -2. Select **Opportunities** -3. Find and click the **Stage** field -4. Add, remove, or rename stages to match your process +1. Accesați **Setări → Model de date** +2. Selectați **Oportunități** +3. Găsiți și faceți clic pe câmpul **Etapă** +4. Adăugați, eliminați sau redenumiți etapele pentru a se potrivi procesului dvs. -### Recommended Stages +### Etape recomandate -| Etapa | Purpose | -| --------------- | ----------------------------------- | -| **New** | Fresh opportunities just identified | -| **Qualified** | Confirmed as a good fit | -| **Meeting** | Engaged in discussions | -| **Proposal** | Proposal sent | -| **Negotiation** | Working on terms | -| **Closed Won** | Deal successful | -| **Closed Lost** | Deal unsuccessful | +| Etapa | Scop | +| ------------------- | ------------------------------------ | +| **Nou** | Oportunități noi tocmai identificate | +| **Calificat** | Confirmată ca o potrivire bună | +| **Întâlnire** | Se poartă discuții | +| **Propunere** | Propunere trimisă | +| **Negociere** | Se negociază termenii | +| **Închis câștigat** | Tranzacție reușită | +| **Închis pierdut** | Tranzacție nereușită | - **5-7 stages is optimal.** Too many stages makes the pipeline hard to scan; too few loses visibility into deal progress. + **5-7 etape sunt optime.** Prea multe etape fac pipeline-ul greu de parcurs; prea puține reduc vizibilitatea asupra progresului tranzacțiilor. -## Step 2: Create a Pipeline View +## Pasul 2: Creați o vizualizare pentru pipeline -1. Go to **Opportunities** -2. Click the view dropdown → **+ Add view** -3. Name it "Sales Pipeline" -4. Click **Create** -5. Open **Options** and select **Kanban** as the layout +1. Accesați **Oportunități** +2. Faceți clic pe meniul derulant al vizualizării → **+ Adaugă vizualizare** +3. Denumiți-o "Sales Pipeline" +4. Faceți clic pe **Creare** +5. Deschideți **Opțiuni** și selectați **Kanban** ca tip de afișare -The view automatically uses the Stage field for columns. +Vizualizarea folosește automat câmpul **Etapă** pentru coloane. -## Step 3: Configure Your View +## Pasul 3: Configurați vizualizarea -### Show Key Fields +### Afișați câmpurile cheie -1. Click **Options → Fields** -2. Look for fields in the "Hidden Fields" section -3. Click the **eye icon** to display: Company, Amount, Close Date, Owner +1. Faceți clic pe **Opțiuni → Câmpuri** +2. Căutați câmpurile în secțiunea "Câmpuri ascunse" +3. Faceți clic pe **pictograma ochi** pentru a afișa: Companie, Sumă, Data închiderii, Proprietar -### Enable Aggregations +### Activați agregările -Show totals at the top of each column: +Afișați totalurile în partea de sus a fiecărei coloane: -1. Click the number displayed next to a Stage name at the top of a column -2. Select the aggregation type (Count, Sum, Average, etc.) -3. Choose the field to aggregate (e.g., Amount) +1. Faceți clic pe numărul afișat lângă numele unei etape în partea de sus a unei coloane +2. Selectați tipul de agregare (Număr, Sumă, Medie etc.) +3. Alegeți câmpul pe care să îl agregați (de ex., Sumă) -**Example:** Show total deal value per stage by aggregating Amount with Sum. +**Exemplu:** Afișați valoarea totală a tranzacțiilor pe etapă prin agregarea câmpului Sumă cu operația Sumă. -### Use Compact View (Optional) +### Utilizați vizualizarea compactă (opțional) -For a high-level overview with minimal card content: +Pentru o privire de ansamblu la nivel înalt, cu conținut minim pe card: -1. Click **Options** -2. Turn on the toggle for **Compact view** +1. Faceți clic pe **Opțiuni** +2. Activați comutatorul pentru **Vizualizare compactă** -## Step 4: Create Personal and Team Views +## Pasul 4: Creați vizualizări personale și de echipă -### "My Pipeline" +### "Pipeline-ul meu" -* **Filter**: Owner = Me -* **Visibility**: Unlisted (personal view) +* **Filtru**: Proprietar = Eu +* **Vizibilitate**: Nelistată (vizualizare personală) -### "Team Pipeline" +### "Pipeline-ul echipei" -* **Filter**: None (show all) -* **Visibility**: Workspace (shared view) +* **Filtru**: Niciunul (afișează tot) +* **Vizibilitate**: Workspace (vizualizare partajată) -### "Closing This Month" +### "Se închid luna aceasta" -* **Type**: Table -* **Filter**: Close Date = This month, Stage ≠ Closed Won, Stage ≠ Closed Lost -* **Sort**: Close Date ascending +* **Tip**: Tabel +* **Filtru**: Data închiderii = Luna aceasta, Etapa ≠ Închis câștigat, Etapa ≠ Închis pierdut +* **Sortare**: Data închiderii crescător -## Working with Opportunities +## Lucrul cu oportunitățile -### Creating Opportunities +### Crearea oportunităților -* Click **+ New** in the Opportunities view -* Or click **+** in a specific stage column +* Faceți clic pe **+ Nou** în vizualizarea Oportunități +* Sau faceți clic pe **+** într-o coloană a unei etape specifice -### Moving Through Stages +### Trecerea prin etape -Drag and drop opportunity cards between columns to update their stage. +Trageți și plasați cardurile oportunităților între coloane pentru a le actualiza etapa. ## Cele mai bune practici -### Pipeline Hygiene +### Igiena pipeline-ului -* Update deals daily as they progress -* Move or close stale deals promptly -* Keep close dates realistic +* Actualizați zilnic tranzacțiile pe măsură ce progresează +* Mutați sau închideți prompt tranzacțiile stagnante +* Mențineți datele de închidere realiste -### Stage Discipline +### Disciplina etapelor -* Define clear criteria for each stage -* Move deals promptly when criteria are met -* Don't let deals sit in stages too long +* Definiți criterii clare pentru fiecare etapă +* Mutați tranzacțiile prompt atunci când criteriile sunt îndeplinite +* Nu lăsați tranzacțiile să stea prea mult timp în etape -## Related +## Conexe -* [Kanban Views](/l/ro/user-guide/views-pipelines/capabilities/kanban-views) — aggregations and compact view -* [Filters and Sorting](/l/ro/user-guide/views-pipelines/capabilities/filters-and-sorting) — creating filtered views +* [Vizualizări Kanban](/l/ro/user-guide/views-pipelines/capabilities/kanban-views) — agregări și vizualizare compactă +* [Filtre și sortare](/l/ro/user-guide/views-pipelines/capabilities/filters-and-sorting) — crearea vizualizărilor filtrate diff --git a/packages/twenty-docs/l/ro/user-guide/workflows/capabilities/use-branches-in-workflows.mdx b/packages/twenty-docs/l/ro/user-guide/workflows/capabilities/use-branches-in-workflows.mdx index 3f0a13061c..1dd9529498 100644 --- a/packages/twenty-docs/l/ro/user-guide/workflows/capabilities/use-branches-in-workflows.mdx +++ b/packages/twenty-docs/l/ro/user-guide/workflows/capabilities/use-branches-in-workflows.mdx @@ -1,90 +1,90 @@ --- -title: Use Branches in Workflows -description: Understand how branches work and how to control which path is executed. +title: Utilizați ramuri în fluxuri de lucru +description: Înțelegeți cum funcționează ramurile și cum să controlați care cale este executată. --- -## How Branches Work +## Cum funcționează ramurile -In the workflow editor, you can create multiple paths (branches) going out from a single node. This allows you to build complex automations with different outcomes. +În editorul de fluxuri de lucru, puteți crea mai multe căi (ramuri) care pornesc dintr-un singur nod. Acest lucru vă permite să creați automatizări complexe cu rezultate diferite. -**Important**: When a workflow runs, **all branches execute in parallel by default**. There is no built-in "if/else" logic to choose one branch over another—every path will run simultaneously. +**Important**: Când rulează un flux de lucru, **toate ramurile se execută în paralel în mod implicit**. Nu există o logică "if/else" integrată pentru a alege o ramură în locul alteia — fiecare cale va rula simultan. -## Controlling Which Branch Runs +## Controlul ramurii care se execută -To execute only one branch based on specific conditions, **add a Filter node at the beginning of each branch**. +Pentru a executa doar o singură ramură pe baza unor condiții specifice, **adăugați un nod Filter la începutul fiecărei ramuri**. -### Example Setup +### Exemplu de configurare -1. Create your workflow with multiple branches from a single node -2. Add a **Filter** node as the first step in each branch -3. Set conditions on each Filter to determine when that branch should continue -4. Only the branch(es) whose Filter conditions are met will proceed +1. Creați fluxul de lucru cu mai multe ramuri dintr-un singur nod +2. Adăugați un nod **Filter** ca primul pas în fiecare ramură +3. Setați condiții în fiecare nod Filter pentru a determina când ar trebui să continue acea ramură +4. Vor continua doar ramurile pentru care condițiile din Filter sunt îndeplinite -### How Filters Work +### Cum funcționează nodurile Filter -* If the Filter condition is **met**: The branch continues executing -* If the Filter condition is **not met**: The branch stops at the Filter node +* Dacă condiția din Filter este **îndeplinită**: Ramura își continuă execuția +* Dacă condiția din Filter **nu este îndeplinită**: Ramura se oprește la nodul Filter -This effectively creates conditional logic where only the appropriate branch runs based on your data. +Acest lucru creează, în mod eficient, o logică condițională în care rulează doar ramura potrivită, pe baza datelor dvs. -## Example: Route by Deal Size +## Exemplu: Rutare după valoarea tranzacției -**Scenario**: When a deal is closed, send different notifications based on deal size. +**Scenariu**: Când o tranzacție este închisă, trimiteți notificări diferite în funcție de valoarea tranzacției. -1. **Trigger**: Opportunity updated (Stage = Closed Won) -2. **Branch 1**: Filter for Amount > $10,000 → Send Slack message to #big-deals -3. **Branch 2**: Filter for Amount ≤ $10,000 → Send email to sales manager +1. **Declanșator**: Opportunity updated (Stage = Closed Won) +2. **Ramura 1**: Filter pentru Amount > $10,000 → Trimiteți mesaj Slack către #big-deals +3. **Ramura 2**: Filter pentru Amount ≤ $10,000 → Trimiteți e-mail managerului de vânzări -Both branches start, but only the one matching the deal amount will continue past its Filter. +Ambele ramuri pornesc, dar doar cea care corespunde sumei tranzacției va continua dincolo de propriul Filter. -## Creating Branches +## Crearea ramurilor - To create a new branch from an existing step, click the **+** button on the step and add your action. You can add multiple branches by clicking **+** multiple times. + Pentru a crea o ramură nouă dintr-un pas existent, faceți clic pe butonul **+** al acelui pas și adăugați acțiunea. Puteți adăuga mai multe ramuri făcând clic pe **+** de mai multe ori. -1. In the workflow editor, select the step you want to branch from -2. Click the **+** button to add an action -3. This creates one branch -4. Click **+** again on the same step to create additional branches -5. Each branch can have its own sequence of actions +1. În editorul de fluxuri de lucru, selectați pasul din care doriți să creați o ramură +2. Faceți clic pe butonul **+** pentru a adăuga o acțiune +3. Aceasta creează o ramură +4. Faceți clic din nou pe **+** la același pas pentru a crea ramuri suplimentare +5. Fiecare ramură poate avea propria secvență de acțiuni -## Merging Branches Back Together +## Îmbinarea ramurilor la loc -After parallel branches complete their work, you can merge them back into a single path: +După ce ramurile paralele își finalizează activitatea, le puteți îmbina la loc într-o singură cale: -1. Complete your branched actions -2. Add a new step that should run after all branches -3. Drag a connection from the last step of each branch to this new step -4. The merged step waits for all connected branches to complete before executing +1. Finalizați acțiunile din ramuri +2. Adăugați un pas nou care ar trebui să ruleze după toate ramurile +3. Trageți o conexiune de la ultimul pas al fiecărei ramuri către acest pas nou +4. Pasul îmbinat așteaptă ca toate ramurile conectate să se finalizeze înainte de a se executa -### Example: Process Then Notify +### Exemplu: Procesare, apoi notificare ``` -Trigger +Declanșator │ - ├── Branch A: Update Customer Record + ├── Ramura A: Actualizați înregistrarea clientului │ - └── Branch B: Create Support Ticket + └── Ramura B: Creați tichet de suport ↘ ↙ - Merged Step: Send Confirmation Email + Pas îmbinat: Trimiteți e-mail de confirmare ``` -The confirmation email sends only after both the customer update and ticket creation are done. +E-mailul de confirmare se trimite doar după ce atât actualizarea clientului, cât și crearea tichetului sunt finalizate. ## Cele mai bune practici -* Always use **Filter nodes** at the start of branches when you want conditional execution -* Keep branch conditions **mutually exclusive** to avoid duplicate actions -* Test your workflows with different data to ensure the correct branches run -* **Rename branch steps** descriptively so it's clear what each path does -* **Merge branches** when you need a final action after parallel processing +* Folosiți întotdeauna **noduri Filter** la începutul ramurilor atunci când doriți execuție condițională +* Mențineți condițiile ramurilor **reciproc exclusive** pentru a evita acțiunile duplicate +* Testați fluxurile de lucru cu date diferite pentru a vă asigura că rulează ramurile corecte +* **Redenumiți pașii ramurilor** într-un mod descriptiv pentru a fi clar ce face fiecare cale +* **Îmbinați ramurile** când aveți nevoie de o acțiune finală după procesare în paralel -## Related +## Conexe -* [Workflows FAQ](/l/ro/user-guide/workflows/how-tos/need-more-help/workflows-faq) — answers about parallel execution -* [Workflow Actions](/l/ro/user-guide/workflows/capabilities/workflow-actions) — available actions for branches +* [Întrebări frecvente despre fluxuri de lucru](/l/ro/user-guide/workflows/how-tos/need-more-help/workflows-faq) — răspunsuri despre execuția în paralel +* [Acțiuni ale fluxurilor de lucru](/l/ro/user-guide/workflows/capabilities/workflow-actions) — acțiuni disponibile pentru ramuri diff --git a/packages/twenty-docs/l/ro/user-guide/workflows/capabilities/workflow-actions.mdx b/packages/twenty-docs/l/ro/user-guide/workflows/capabilities/workflow-actions.mdx index fd05005339..629cd9cf50 100644 --- a/packages/twenty-docs/l/ro/user-guide/workflows/capabilities/workflow-actions.mdx +++ b/packages/twenty-docs/l/ro/user-guide/workflows/capabilities/workflow-actions.mdx @@ -96,150 +96,150 @@ Creează o înregistrare nouă sau actualizează una existentă pe baza criterii * Folosiți datele din pașii anteriori pentru a completa câmpurile -**How it works**: +**Cum funcționează**: -1. Searches for a record matching your criteria -2. If found → updates the existing record -3. If not found → creates a new record +1. Caută o înregistrare care corespunde condițiilor specificate +2. Dacă este găsită → actualizează înregistrarea existentă +3. Dacă nu este găsită → creează o înregistrare nouă -**Output**: The created or updated record data is available for use in subsequent steps. +**Output**: Datele înregistrării create sau actualizate sunt disponibile pentru utilizare în pașii următori. -## Flow Actions +## Acțiuni de flux ### Iterator -**Loops through an array of records** returned from a previous step, allowing you to perform actions on each record individually. +**Parcurge un array de înregistrări** returnat de un pas anterior, permițându-vă să efectuați acțiuni pe fiecare înregistrare individual. **Configurare**: -* Select the array of records from a previous step (e.g., results from Search Records, from a Manual trigger with Bulk availability, from a code node) -* Define the actions to perform on each record in the loop. +* Selectați array-ul de înregistrări dintr-un pas anterior (de ex., rezultate din Search Records, dintr-un declanșator Manual cu disponibilitate Bulk, dintr-un nod de cod) +* Definiți acțiunile de efectuat pe fiecare înregistrare în buclă. - - You can add several actions within an iterator. - - When using branches inside an iterator, make sure the last step of each branch connects back to the iterator to close the loop. + - Puteți adăuga mai multe acțiuni în cadrul unui iterator. + - Când folosiți ramuri în interiorul unui iterator, asigurați-vă că ultimul pas al fiecărei ramuri se conectează înapoi la iterator pentru a închide bucla. -* Access `Current Item` Fields: to use fields from the record currently being processed, click on the **Iterator** step, then select **Current item**. The list of available fields from that record will be displayed and can be selected for use in subsequent actions. +* Accesați câmpurile `Current Item`: pentru a utiliza câmpuri din înregistrarea procesată în prezent, faceți clic pe pasul **Iterator**, apoi selectați **Current item**. Lista câmpurilor disponibile din acea înregistrare va fi afișată și poate fi selectată pentru utilizare în acțiunile ulterioare. -### Filter +### Filtru -Filters records based on specified conditions, allowing only records that meet the criteria to pass through. +Filtrează înregistrările pe baza condițiilor specificate, permițând trecerea doar a înregistrărilor care îndeplinesc criteriile. **Configurare**: -* Select the record to filter +* Selectați înregistrarea de filtrat * Definiți condițiile și criteriile de filtrare * Configurați care înregistrări ar trebui să treacă la pașii următori - 1. **Output**: Filter nodes don't return data—they act as gates. If the conditions are met, the workflow continues. If not, the workflow stops at that branch. - 2. The `IS` operator can be used with numeric fields. It performs as an `EQUAL`. + 1. **Output**: Nodurile Filter nu returnează date — acționează ca porți. Dacă condițiile sunt îndeplinite, fluxul de lucru continuă. Dacă nu, fluxul de lucru se oprește pe acea ramură. + 2. Operatorul `IS` poate fi utilizat cu câmpuri numerice. Se comportă ca un `EQUAL`. -### Delay +### Întârziere -Pauses workflow execution for a specified duration or until a specific date/time. +Pauzează execuția fluxului de lucru pentru o durată specificată sau până la o anumită dată/oră. -**Delay Types**: +**Tipuri de întârziere**: -| Tip | Descriere | -| ------------------ | ------------------------------------------------------------------ | -| **Duration** | Wait for a specific amount of time (days, hours, minutes, seconds) | -| **Scheduled Date** | Wait until a specific date and time | +| Tip | Descriere | +| ------------------- | -------------------------------------------------------------------- | +| **Durată** | Așteaptă o perioadă de timp specificată (zile, ore, minute, secunde) | +| **Dată programată** | Așteaptă până la o dată și o oră specifice | -**Configuration for Duration**: +**Configurare pentru durată**: -* Set days, hours, minutes, and/or seconds -* Combine multiple units (e.g., 2 days and 4 hours) +* Setați zile, ore, minute și/sau secunde +* Combinați mai multe unități (de ex., 2 zile și 4 ore) -**Configuration for Scheduled Date**: +**Configurare pentru dată programată**: -* Select a date and time -* Can reference a date field from a previous step (e.g., follow up 3 days after a meeting) +* Selectați o dată și o oră +* Poate face referire la un câmp de tip dată dintr-un pas anterior (de ex., un follow-up la 3 zile după o întâlnire) **Cazuri de utilizare**: -* Wait 24 hours before sending a follow-up email -* Pause until an opportunity's close date -* Schedule actions for business hours +* Așteaptă 24 de ore înainte de a trimite un email de follow-up +* Pauzează până la data de închidere a unei oportunități +* Programează acțiuni pentru programul de lucru - The scheduled date cannot be in the past. If a date field from a previous step is used and the date has already passed, the workflow will fail. + Data programată nu poate fi în trecut. Dacă este utilizat un câmp de tip dată dintr-un pas anterior și data a trecut deja, fluxul de lucru va eșua. -**Limits & Credits**: +**Limitări și credite**: -* **No maximum duration limit**—you can set delays of minutes, days, weeks, or longer -* **1 credit consumed** when the Delay node executes, regardless of duration -* **No credits consumed** while waiting—a 5-minute delay costs the same as a 5-day delay +* **Fără limită maximă de durată** — puteți seta întârzieri de minute, zile, săptămâni sau mai mult +* Se consumă **1 credit** la executarea nodului Delay, indiferent de durată +* **Nu se consumă credite** în timpul așteptării — o întârziere de 5 minute costă la fel ca o întârziere de 5 zile -## Communication Actions +## Acțiuni de comunicare -### Send Email +### Trimite email -Trimite un email din fluxul dumneavoastră de lucru. This is great for templated group emails. Emails will look like the ones you send from your mailbox. -Not suited for newsletters (which require richer formatting) or automated email sequences. +Trimite un email din fluxul dumneavoastră de lucru. Este excelent pentru emailuri de grup bazate pe șabloane. Emailurile vor arăta ca cele pe care le trimiteți din căsuța de e-mail. +Nu este potrivit pentru newslettere (care necesită o formatare mai bogată) sau pentru secvențe automate de emailuri. -**Prerequisites**: Add an email account in Settings → Accounts +**Cerințe prealabile**: Adăugați un cont de email în Settings → Accounts **Configurare**: -* Select the sender email account +* Selectați contul de email expeditor - You can only send emails from mailboxes synced to your own Twenty account. Sending from other team members' mailboxes (e.g., the account owner's email) is on the roadmap. + Puteți trimite emailuri doar din căsuțele poștale sincronizate cu propriul dvs. cont Twenty. Trimiterea din căsuțele poștale ale altor membri ai echipei (de ex., emailul proprietarului contului) este pe roadmap. -For all the following steps, you can reference variables from previous steps for personalization. +Pentru toți pașii următori, puteți face referire la variabile din pașii anteriori pentru personalizare. * Introduceți adresa de email a destinatarului. - Only one recipient is possible at the moment. + În acest moment este posibil un singur destinatar. * Setați linia de subiect. -* Compuneți corpul mesajului. You can format links, create numbered list, bullet point lists, add attachments. +* Compuneți corpul mesajului. Puteți formata linkuri, crea liste numerotate, liste cu puncte, adăuga atașamente. - Adding HTML signatures is not possible at the moment. + Adăugarea semnăturilor HTML nu este posibilă în acest moment. ### Formular -Solicită un formular în timpul execuției fluxului de lucru pentru a colecta intrarea utilizatorului. The responses can then be used in subsequent steps to create records, send emails, or execute any other action based on the input. +Solicită un formular în timpul execuției fluxului de lucru pentru a colecta intrarea utilizatorului. Răspunsurile pot fi apoi folosite în pașii următori pentru a crea înregistrări, a trimite emailuri sau a executa orice altă acțiune pe baza datelor introduse. - **Forms are designed for manual triggers only**. Pentru fluxurile de lucru cu alte declanșatoare (Înregistrare creată, actualizată, etc.), formularele sunt accesibile doar prin interfața de execuție a fluxului de lucru, ceea ce nu este experiența de utilizator așteptată. Un centru de notificări va fi lansat în 2026 pentru a sprijini corespunzător formularele în fluxurile de lucru automatizate. + **Formularele sunt concepute doar pentru declanșatoare manuale**. Pentru fluxurile de lucru cu alte declanșatoare (Înregistrare creată, actualizată, etc.), formularele sunt accesibile doar prin interfața de execuție a fluxului de lucru, ceea ce nu este experiența de utilizator așteptată. Un centru de notificări va fi lansat în 2026 pentru a sprijini corespunzător formularele în fluxurile de lucru automatizate. **Configurare**: -* Configure the fields that users will be asked to fill. For each field, choose - * a type among text, number, date, a given record, a select field. Select fields from all objects are available. - * a label - * a default value under `Placeholder` (optional) -* Edit the form title +* Configurați câmpurile pe care utilizatorii vor fi solicitați să le completeze. Pentru fiecare câmp, alegeți + * un tip dintre text, număr, dată, o anumită înregistrare, un câmp select. Câmpurile de tip select din toate obiectele sunt disponibile. + * o etichetă + * o valoare implicită la `Placeholder` (opțional) +* Editați titlul formularului **Output**: Răspunsurile formularului sunt disponibile pentru utilizare în pașii următori. -**Example**: The "Quick Lead" workflow is available by default in all workspaces, available anywhere in the Command Menu `Cmd + K`. +**Exemplu**: Fluxul de lucru "Quick Lead" este disponibil implicit în toate spațiile de lucru, disponibil oriunde în Command Menu `Cmd + K`. -**How to fill the form**: +**Cum să completați formularul**: -* Trigger your manual workflow from the command menu `Cmd K` -* Fill the form that is displayed in the side panel and click `Submit`. +* Declanșați fluxul de lucru manual din meniul de comandă `Cmd K` +* Completați formularul afișat în panoul lateral și faceți clic pe `Submit`. - The fields cannot be made mandatory. + Câmpurile nu pot fi făcute obligatorii. -## Integration Actions +## Acțiuni de integrare ### Cod @@ -247,7 +247,7 @@ Rulați JavaScript personalizat în cadrul fluxului dumneavoastră de lucru. **Configurare**: -* Accesați variabilele din pașii anteriori. You can edit the variables names dynamically. +* Accesați variabilele din pașii anteriori. Puteți edita dinamic numele variabilelor. @@ -256,15 +256,15 @@ Rulați JavaScript personalizat în cadrul fluxului dumneavoastră de lucru. * Testați codul direct în pas - If you need to use external API keys in your code, you must input them directly in the function body. You cannot configure API keys elsewhere and reference them in the serverless function. + Dacă trebuie să utilizați chei API externe în codul dvs., trebuie să le introduceți direct în corpul funcției. Nu puteți configura cheile API în altă parte și face referire la ele în funcția serverless. - **Working with arrays?** Arrays from external systems or previous steps may come as strings. See [How to handle arrays in Code actions](/l/ro/user-guide/workflows/how-tos/advanced-configurations/handle-arrays-in-code-actions) for the solution. + **Lucrați cu array-uri?** Array-urile din sisteme externe sau din pași anteriori pot veni ca stringuri. Consultați [Cum să gestionați array-urile în acțiunile Code](/l/ro/user-guide/workflows/how-tos/advanced-configurations/handle-arrays-in-code-actions) pentru soluție. - Click the square icon at the top right of the code editor to display it in full screen — helpful since the default editor width is limited. + Faceți clic pe pictograma pătrată din dreapta sus a editorului de cod pentru a-l afișa pe tot ecranul — util, deoarece lățimea implicită a editorului este limitată. ### Solicitare HTTP @@ -275,37 +275,37 @@ Trimite o cerere la un API extern ca parte a fluxului dumneavoastră de lucru. **Configurare**: -* Introduceți URL-ul punctului final API. Using parameters from previous steps is possible. +* Introduceți URL-ul punctului final API. Puteți utiliza parametri din pașii anteriori. * Selectați metoda HTTP (GET, POST, PUT, PATCH, DELETE) * Adăugați anteturile și valorile necesare * Oferiți un exemplu de răspuns pentru previzualizarea structurii -## AI Actions +## Acțiuni AI -### AI Agent - Coming Soon +### Agent AI - În curând -Runs an AI agent within your workflow to perform intelligent tasks. +Rulează un agent AI în cadrul fluxului dvs. de lucru pentru a efectua sarcini inteligente. **Configurare**: -* **Agent**: Select an existing AI agent or use the default agent -* **Prompt**: Write the instruction for the AI agent -* Reference variables from previous steps in the prompt +* **Agent**: Selectați un agent AI existent sau folosiți agentul implicit +* **Prompt**: Scrieți instrucțiunea pentru agentul AI +* Faceți referire la variabile din pașii anteriori în prompt -**What AI Agents can do**: +**Ce pot face agenții AI**: -* Analyze and summarize data -* Classify or categorize records -* Generate text content -* Make decisions based on data -* Interact with your CRM data using tools +* Analizează și rezumă date +* Clasifică sau categorizează înregistrări +* Generează conținut text +* Ia decizii pe baza datelor +* Interacționează cu datele CRM folosind instrumente -**Output**: The AI agent's response is available for use in subsequent steps. If the agent has a structured output schema, the response will follow that format. +**Output**: Răspunsul agentului AI este disponibil pentru utilizare în pașii următori. Dacă agentul are o schemă de ieșire structurată, răspunsul va urma acel format. - AI Agent actions consume workflow credits based on the AI model used. See [Workflow Credits](/l/ro/user-guide/workflows/capabilities/workflow-credits) for details. + Acțiunile agentului AI consumă credite ale fluxului de lucru în funcție de modelul AI utilizat. Consultați [Credite pentru fluxuri de lucru](/l/ro/user-guide/workflows/capabilities/workflow-credits) pentru detalii. - AI agents respect role-based permissions. You can assign specific roles to agents under **Settings → Roles** to control what data they can access. See [Permissions](/l/ro/user-guide/permissions-access/capabilities/permissions) for details. + Agenții AI respectă permisiunile bazate pe roluri. Puteți atribui roluri specifice agenților în **Settings → Roles** pentru a controla la ce date pot avea acces. Consultați [Permisiuni](/l/ro/user-guide/permissions-access/capabilities/permissions) pentru detalii. diff --git a/packages/twenty-docs/l/ro/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities.mdx b/packages/twenty-docs/l/ro/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities.mdx index 350332ee57..a0eea228f6 100644 --- a/packages/twenty-docs/l/ro/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities.mdx +++ b/packages/twenty-docs/l/ro/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities.mdx @@ -1,56 +1,56 @@ --- -title: Detect Stale Opportunities -description: Automatically notify managers when opportunities haven't been updated. +title: Detectați oportunitățile stagnante +description: Notificați automat managerii când oportunitățile nu au fost actualizate. --- -Keep your pipeline healthy by alerting managers when opportunities go stale. This workflow checks for opportunities that haven't been updated in a specified number of days. +Mențineți pipeline-ul sănătos alertând managerii când oportunitățile devin stagnante. Acest flux de lucru verifică oportunitățile care nu au fost actualizate într-un număr specificat de zile. -## The Problem +## Problema -Opportunities sitting without updates lead to: +Oportunitățile lăsate fără actualizări duc la: -* Deals going cold -* Unreliable forecasts -* Lost revenue +* Tranzacții care se răcesc +* Previziuni nesigure +* Venituri pierdute -## The Solution +## Soluția -Create a scheduled workflow that finds stale opportunities and emails their managers. +Creați un flux de lucru programat care găsește oportunități stagnante și le trimite prin e-mail managerilor lor. -## Step-by-Step Setup +## Configurare pas cu pas -### Step 1: Create the Workflow +### Pasul 1: Creați fluxul de lucru -1. Go to **Settings → Workflows** -2. Click **+ New Workflow** -3. Name it "Stale Opportunity Alert" +1. Accesați **Setări → Fluxuri de lucru** +2. Faceți clic pe **+ Flux de lucru nou** +3. Denumiți-l "Alertă pentru oportunități stagnante" -### Step 2: Configure the Trigger +### Pasul 2: Configurați declanșatorul -1. Select **On a Schedule** -2. Set to run daily (e.g., every day at 8 AM) +1. Selectați **On a Schedule** +2. Setați să ruleze zilnic (de exemplu, în fiecare zi la 8 AM) -### Step 3: Search for Stale Opportunities +### Pasul 3: Căutați oportunități stagnante -1. Add **Search Records** action +1. Adăugați acțiunea **Search Records** 2. Configurați: -| Câmp | Valoare | -| ---------- | ----------------------------------------------- | -| **Object** | Oportunități | -| **Filter** | Updated At is before (today - 7 days) | -| **Filter** | Stage is not "Closed Won" AND not "Closed Lost" | -| **Limit** | 100 | +| Câmp | Valoare | +| ---------- | --------------------------------------------------- | +| **Obiect** | Oportunități | +| **Filtru** | Updated At este înainte de (astăzi - 7 zile) | +| **Filtru** | Stage nu este "Closed Won" ȘI nu este "Closed Lost" | +| **Limită** | 100 | -### Step 4: Check If Any Found +### Pasul 4: Verificați dacă s-au găsit rezultate -1. Add **Filter** action -2. Condition: `{{searchRecords.length}}` is greater than 0 -3. If no stale opportunities, the workflow stops here +1. Adăugați acțiunea **Filter** +2. Condiție: `{{searchRecords.length}}` este mai mare decât 0 +3. Dacă nu există oportunități stagnante, fluxul de lucru se oprește aici -### Step 5: Format the Alert (Code Action) +### Pasul 5: Formatați alerta (acțiune Code) -Add a **Code** action to format the email: +Adăugați o acțiune **Code** pentru a formata e-mailul: ```javascript export const main = async (params) => { @@ -88,49 +88,49 @@ export const main = async (params) => { }; ``` -### Step 6: Send Alert Email +### Pasul 6: Trimiteți e-mailul de alertă -Add **Send Email** action: +Adăugați acțiunea **Send Email**: -| Câmp | Valoare | -| ----------- | ----------------------------------------------------------- | -| **To** | sales-manager@yourcompany.com | -| **Subject** | `🚨 {{code.totalCount}} Stale Opportunities Need Attention` | -| **Body** | `{{code.summary}}` | +| Câmp | Valoare | +| ----------- | ---------------------------------------------------------------- | +| **Către** | sales-manager@yourcompany.com | +| **Subiect** | `🚨 {{code.totalCount}} oportunități stagnante necesită atenție` | +| **Corp** | `{{code.summary}}` | -### Step 7: Test and Activate +### Pasul 7: Testați și activați -1. Click **Test** to run the workflow -2. Check that the email contains the right data -3. Activate when ready +1. Faceți clic pe **Test** pentru a rula fluxul de lucru +2. Verificați că e-mailul conține datele corecte +3. Activați când sunteți gata -## Customization Options +## Opțiuni de personalizare -### Change Staleness Threshold +### Modificați pragul de stagnare -Modify the Search Records filter to change from 7 days to your preferred period: +Modificați filtrul Search Records pentru a schimba de la 7 zile la perioada preferată: -* 3 days for high-velocity sales -* 14 days for enterprise deals -* 30 days for long sales cycles +* 3 zile pentru vânzări cu ritm ridicat +* 14 zile pentru tranzacții enterprise +* 30 de zile pentru cicluri de vânzări lungi -### Alert Individual Reps +### Alerte pentru reprezentanți individuali -Instead of one manager email, use **Iterator** to send personalized emails to each rep about their own stale deals. +În loc de un singur e-mail către manager, folosiți **Iterator** pentru a trimite e-mailuri personalizate fiecărui reprezentant despre tranzacțiile lor stagnante. -### Add Escalation +### Adăugați escaladare -Create multiple workflows with increasing severity: +Creați mai multe fluxuri de lucru cu severitate în creștere: -1. Day 7: Email to rep -2. Day 14: Email to rep + manager -3. Day 21: Create task for manager to intervene +1. Ziua 7: E-mail către reprezentant +2. Ziua 14: E-mail către reprezentant + manager +3. Ziua 21: Creați o sarcină pentru ca managerul să intervină -### Include in Slack +### Includeți în Slack -Use **HTTP Request** to post to a Slack webhook instead of or in addition to email. +Utilizați **HTTP Request** pentru a posta către un webhook Slack în locul sau pe lângă e-mail. -## Related +## Conexe -* [Workflow Actions](/l/ro/user-guide/workflows/capabilities/workflow-actions) -* [Send Emails from Workflows](/l/ro/user-guide/workflows/capabilities/send-emails-from-workflows) +* [Acțiuni ale fluxurilor de lucru](/l/ro/user-guide/workflows/capabilities/workflow-actions) +* [Trimiteți e-mailuri din fluxuri de lucru](/l/ro/user-guide/workflows/capabilities/send-emails-from-workflows) diff --git a/packages/twenty-docs/l/ru/user-guide/data-migration/how-tos/fix-import-errors.mdx b/packages/twenty-docs/l/ru/user-guide/data-migration/how-tos/fix-import-errors.mdx index 2b036f8c93..b76c587df6 100644 --- a/packages/twenty-docs/l/ru/user-guide/data-migration/how-tos/fix-import-errors.mdx +++ b/packages/twenty-docs/l/ru/user-guide/data-migration/how-tos/fix-import-errors.mdx @@ -1,11 +1,11 @@ --- -title: Fix Import Errors -description: Complete troubleshooting guide for resolving CSV import errors. +title: Устранение ошибок импорта +description: Полное руководство по устранению ошибок импорта CSV. --- ## Обзор -Import not working? This guide helps you identify and fix common import errors step by step. +Импорт не работает? This guide helps you identify and fix common import errors step by step. ## How Import Validation Works diff --git a/packages/twenty-docs/l/ru/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx b/packages/twenty-docs/l/ru/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx index 45ae22b978..4de984f9b0 100644 --- a/packages/twenty-docs/l/ru/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx +++ b/packages/twenty-docs/l/ru/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx @@ -1,103 +1,103 @@ --- -title: Import Relations Between Objects via CSV -description: Complete step-by-step guide to linking records during CSV import. +title: Импорт связей между объектами с помощью CSV +description: Полное пошаговое руководство по связыванию записей при импорте CSV. --- ## Обзор -This guide walks you through importing relations between objects—for example, linking People to Companies, or Opportunities to People. +В этом руководстве показано, как импортировать связи между объектами — например, связывать Людей с Компаниями, или Возможности с Людьми. -**What can be imported:** Only one-to-many relations pointing to a single object type. Relations pointing to multiple object types (like Notes linking to People AND Companies) are not yet supported for import. +**Что можно импортировать:** Только связи типа «один-ко-многим», указывающие на один тип объекта. Связи, указывающие на несколько типов объектов (например, Заметки, связанные с Людьми И Компаниями), пока не поддерживаются для импорта. -## Understanding Relations +## Понимание связей -### What is a "One-to-Many" Relation? +### Что такое связь «один-ко-многим»? -In a one-to-many relation: +В связи «один-ко-многим»: -* **One** Company has **many** People (employees) -* **One** Company has **many** Opportunities -* **One** Person has **many** Tasks +* **Одна** компания имеет **много** людей (сотрудников) +* **Одна** компания имеет **много** возможностей +* **Один** человек имеет **много** задач -The "one" side is the **parent**. The "many" side is the **child**. +Сторона «один» — это **родитель**. Сторона «многие» — это **дочерняя** сторона. -### Common Relations in Twenty +### Типичные связи в Twenty -| Связь | "One" Side (Parent) | "Many" Side (Child) | -| ------------------------- | ------------------- | ------------------- | -| Companies → People | Компания | Люди | -| Companies → Opportunities | Компания | Возможности | -| People → Tasks | Person | Задачи | -| People → Notes | Person | Заметки | +| Связь | Сторона «один» (родитель) | Сторона «многие» (дочерняя) | +| ---------------------- | ------------------------- | --------------------------- | +| Компании → Люди | Компания | Люди | +| Компании → Возможности | Компания | Возможности | +| Люди → Задачи | Человек | Задачи | +| Люди → Заметки | Человек | Заметки | -## Step 1: Identify the "One" and "Many" Sides +## Шаг 1: Определите стороны «один» и «многие» -Before importing, determine which object is the parent and which is the child. +Перед импортом определите, какой объект является родительским, а какой — дочерним. -**Ask yourself:** "Does ONE [Object A] have MANY [Object B]?" +**Спросите себя:** «У одного [Объект A] есть много [Объект B]?» -* One Company → Many People ✓ (Company is parent) -* One Person → Many Companies ✗ (This is wrong—a person belongs to one company) +* Одна Компания → Много Людей ✓ (Компания — родитель) +* Один Человек → Много Компаний ✗ (Это неверно — человек принадлежит одной компании) -## Step 2: Import the Parent Records First +## Шаг 2: Сначала импортируйте родительские записи -The parent ("one" side) must exist in Twenty before you can reference it. +Родительская запись (сторона «один») должна существовать в Twenty, прежде чем вы сможете на неё сослаться. -**Import order:** +**Порядок импорта:** -1. **Companies** first (no dependencies) -2. **People** second (link to Companies) -3. **Opportunities** third (link to Companies and/or People) -4. **Tasks/Notes** (link to any of the above) +1. **Компании** в первую очередь (без зависимостей) +2. **Люди** во вторую очередь (связь с компаниями) +3. **Возможности** в третью очередь (связь с компаниями и/или людьми) +4. **Задачи/Заметки** (связь с любым из вышеперечисленных) - **If the parent record doesn't exist, the import will fail.** + **Если родительская запись не существует, импорт завершится с ошибкой.** - Always verify that Companies are imported before importing People with company references. + Всегда проверяйте, что Компании импортированы до импорта Людей со ссылками на компании. -## Step 3: Note the Parent's Unique Identifier +## Шаг 3: Запишите уникальный идентификатор родительской записи -You need to reference the parent record using a **unique identifier**. Available options: +Вам нужно ссылаться на родительскую запись с помощью **уникального идентификатора**. Доступные варианты: -| Parent Object | Available Unique Identifiers | -| ----------------------------------- | --------------------------------------------------------------- | -| **Компании** | `id` (UUID), `domain` (recommended), or any custom unique field | -| **People** | `id` (UUID), `email`, or any custom unique field | -| **Участники рабочего пространства** | `id` (UUID), `email` (not name) | -| **Пользовательские объекты** | `id` (UUID), or any field marked as unique | +| Родительский объект | Доступные уникальные идентификаторы | +| ----------------------------------- | -------------------------------------------------------------------------------- | +| **Компании** | `id` (UUID), `domain` (рекомендуется) или любое пользовательское уникальное поле | +| **Люди** | `id` (UUID), `email` или любое пользовательское уникальное поле | +| **Участники рабочего пространства** | `id` (UUID), `email` (не имя) | +| **Пользовательские объекты** | `id` (UUID) или любое поле, отмеченное как уникальное | -**Recommended:** Use `domain` for Companies and `email` for People. These are human-readable and easy to verify in your spreadsheet. +**Рекомендуется:** Используйте `domain` для Компаний и `email` для Людей. Они удобочитаемы и их легко проверить в вашей таблице. -### Finding the Identifier +### Поиск идентификатора -If you need the `id`: +Если вам нужен `id`: -1. Export the parent records from Twenty -2. The export includes the `id` column -3. Use these IDs in your child records file +1. Экспортируйте родительские записи из Twenty +2. Экспорт включает столбец `id` +3. Используйте эти ID в файле дочерних записей -## Step 4: Verify the Relation Field Exists +## Шаг 4: Убедитесь, что поле связи существует -Before importing, ensure the relation field exists between your objects. +Перед импортом убедитесь, что между вашими объектами существует поле связи. -**To check or create:** +**Чтобы проверить или создать:** -1. Go to **Settings → Data Model** -2. Select your child object (e.g., People) -3. Look for a relation field pointing to the parent (e.g., Company) -4. If it doesn't exist, create it: - * Click **+ Add field** - * Select **Relation** type - * Choose the parent object +1. Перейдите в **Настройки → Модель данных** +2. Выберите ваш дочерний объект (например, Люди) +3. Найдите поле связи, указывающее на родителя (например, Компания) +4. Если его нет, создайте его: + * Нажмите **+ Добавить поле** + * Выберите тип **Связь** + * Выберите родительский объект -## Step 5: Prepare Your CSV File +## Шаг 5: Подготовьте ваш файл CSV -Add a column to your child CSV that references the parent using its unique identifier. +Добавьте в ваш дочерний CSV столбец, который ссылается на родителя по его уникальному идентификатору. -### Example: People Linking to Companies +### Пример: Связывание Людей с Компаниями -**Your People CSV:** +**Ваш CSV-файл для Людей:** ```csv firstName,lastName,email,jobTitle,companyDomain @@ -106,66 +106,66 @@ Jane,Doe,jane@widgets.co,CTO,https://widgets.co Bob,Johnson,bob@techstart.io,Developer,https://techstart.io ``` -The `companyDomain` column references the Company's domain. +Столбец `companyDomain` ссылается на домен Компании. -### Format Requirements +### Требования к формату -| Идентификатор | Формат | Пример | -| ----------------- | -------------- | -------------------------------------- | -| Домен | URL format | `https://acme.com` | -| Электронная почта | Standard email | `john@acme.com` | -| ID | UUID | `c776ee49-f608-4a77-8cc8-6fe96ae1e43f` | +| Идентификатор | Формат | Пример | +| ----------------- | ----------------------------------- | -------------------------------------- | +| Домен | Формат URL | `https://acme.com` | +| Электронная почта | Стандартный адрес электронной почты | `john@acme.com` | +| ID | UUID | `c776ee49-f608-4a77-8cc8-6fe96ae1e43f` | - **Domain format matters!** + **Формат домена имеет значение!** - Use `https://domain.com` (not just `domain.com`). This matches how Twenty stores Company domains and prevents matching errors. + Используйте `https://domain.com` (не просто `domain.com`). Это соответствует тому, как Twenty хранит домены Компаний, и предотвращает ошибки сопоставления. -### Important Rules +### Важные правила -1. **Exact match required** — the value must exactly match the parent record -2. **Map only ONE unique identifier** — don't include both `companyId` AND `companyDomain` -3. **Case sensitive** — `Acme.com` ≠ `acme.com` +1. **Требуется точное совпадение** — значение должно в точности соответствовать родительской записи +2. **Сопоставляйте только ОДИН уникальный идентификатор** — не указывайте одновременно `companyId` И `companyDomain` +3. **С учётом регистра** — `Acme.com` ≠ `acme.com` -## Step 6: Upload and Map the Relation +## Шаг 6: Загрузите и сопоставьте связь -1. Navigate to the child object (e.g., People) -2. Click **⋮** → **Import records** -3. Upload your CSV file -4. In the field mapping step: - * Find your relation column (e.g., `companyDomain`) - * Map it to the **Company** relation field -5. Complete the remaining mapping -6. Review errors and confirm +1. Перейдите к дочернему объекту (например, Люди) +2. Нажмите **⋮** → **Импорт записей** +3. Загрузите ваш CSV-файл +4. На шаге сопоставления полей: + * Найдите столбец связи (например, `companyDomain`) + * Сопоставьте его с полем связи **Компания** +5. Завершите оставшееся сопоставление +6. Проверьте ошибки и подтвердите -Twenty will automatically link each child record to the matching parent. +Twenty автоматически свяжет каждую дочернюю запись с соответствующим родителем. -## Step 7: Verify the Import +## Шаг 7: Проверьте импорт -After importing: +После импорта: -1. Open a few child records (e.g., People) -2. Verify the relation field shows the correct parent (e.g., Company) -3. Open a parent record and check the related records section +1. Откройте несколько дочерних записей (например, Люди) +2. Убедитесь, что в поле связи указан правильный родитель (например, Компания) +3. Откройте родительскую запись и проверьте раздел связанных записей -## Common Mistakes to Avoid +## Распространённые ошибки, которых следует избегать -| Mistake | Problem | Solution | -| -------------------------- | -------------------------------------------------- | ------------------------------------------------------- | -| **Wrong import order** | Importing People before Companies | Always import parents first, then children | -| **Wrong domain format** | Using `acme.com` instead of `https://acme.com` | Use full URL format with `https://` | -| **Multiple unique fields** | Mapping both `companyId` AND `companyDomain` | Map only ONE unique identifier | -| **Missing relation field** | The relation field doesn't exist in the data model | Create it in **Settings → Data Model** before importing | -| **Non-existent records** | The parent record doesn't exist in Twenty | Import parent records first, or check for typos | -| **Case mismatch** | `Acme.com` in file but `acme.com` in Twenty | Ensure exact case matching | +| Ошибка | Проблема | Решение | +| -------------------------------- | -------------------------------------------------------- | --------------------------------------------------------------- | +| **Неправильный порядок импорта** | Импорт Людей раньше Компаний | Всегда сначала импортируйте родительские записи, затем дочерние | +| **Неверный формат домена** | Использование `acme.com` вместо `https://acme.com` | Используйте полный формат URL с `https://` | +| **Несколько уникальных полей** | Сопоставление одновременно `companyId` И `companyDomain` | Сопоставляйте только ОДИН уникальный идентификатор | +| **Отсутствует поле связи** | Поля связи нет в модели данных | Создайте его в **Настройки → Модель данных** перед импортом | +| **Несуществующие записи** | Родительская запись не существует в Twenty | Сначала импортируйте родительские записи или проверьте опечатки | +| **Несовпадение регистра** | `Acme.com` в файле, но `acme.com` в Twenty | Обеспечьте точное совпадение регистра | -## Linking to Workspace Members +## Связь с участниками рабочего пространства -When linking to Workspace Members (your team): +При связывании с участниками рабочего пространства (вашей командой): -* Use their **email address**, not their name -* Example: `owner@yourcompany.com`, not "John Smith" +* Используйте их **адрес электронной почты**, а не имя +* Пример: `owner@yourcompany.com`, а не «John Smith» ```csv taskName,assignedTo @@ -173,56 +173,56 @@ Follow up with client,john@yourcompany.com Review proposal,jane@yourcompany.com ``` -## FAQ +## Часто задаваемые вопросы - - You have two options: + + У вас есть два варианта: - 1. Use the Twenty `id` (export parent records to get their IDs) - 2. Create a custom unique field in your data model to store an external ID from your previous system + 1. Используйте Twenty `id` (экспортируйте родительские записи, чтобы получить их ID) + 2. Создайте пользовательское уникальное поле в вашей модели данных для хранения внешнего ID из вашей предыдущей системы - - Да! Include the child record's unique identifier (e.g., `email` for People) and the new relation value. The import will update the relation. + + Да! Укажите уникальный идентификатор дочерней записи (например, `email` для Людей) и новое значение связи. Импорт обновит связь. - - Many-to-Many relations are not yet supported for import. This is planned for H1 2026. + + Связи многие-ко-многим пока не поддерживаются для импорта. Это запланировано на первое полугодие 2026 года. - - Relations pointing to multiple object types are not yet supported for import/export. This is on our roadmap. + + Связи, указывающие на несколько типов объектов, пока не поддерживаются для импорта/экспорта. Это запланировано в нашей дорожной карте. - - The import will show an error for that row. Вы можете либо: + + Импорт покажет ошибку для этой строки. Вы можете либо: - * Import the parent record first, then re-import - * Fix the reference value - * Remove the row from import + * Сначала импортируйте родительскую запись, затем повторите импорт + * Исправьте ссылочное значение + * Исключите строку из импорта - - Common causes: + + Распространённые причины: - * Wrong format (use `https://domain.com` for domains) - * Case mismatch (check exact spelling) - * Parent doesn't exist (import parents first) - * Mapping multiple identifiers (use only one) + * Неверный формат (для доменов используйте `https://domain.com`) + * Несовпадение регистра (проверьте точное написание) + * Родитель не существует (сначала импортируйте родителей) + * Сопоставление нескольких идентификаторов (используйте только один) - **Remember: Soft-deleted records count toward uniqueness.** + **Помните: записи, помеченные как удалённые, учитываются при проверке уникальности.** - If you're getting "not found" errors but the record seems to exist, check Command Menu → See deleted records. The parent may have been soft-deleted. + Если вы получаете ошибки «not found», но запись, кажется, существует, проверьте Command Menu → See deleted records. Возможно, родитель был помечен как удалённый. ## Устранение неполадок -Having issues? Check: +Возникли проблемы? Проверьте: -* [How to Fix Import Errors](/l/ru/user-guide/data-migration/how-tos/fix-import-errors) -* [Import Relations Capabilities](/l/ru/user-guide/data-migration/capabilities/import-relations) -* [Uniqueness Constraints](/l/ru/user-guide/data-migration/capabilities/uniqueness-constraints) +* [Как исправить ошибки импорта](/l/ru/user-guide/data-migration/how-tos/fix-import-errors) +* [Возможности импорта связей](/l/ru/user-guide/data-migration/capabilities/import-relations) +* [Ограничения уникальности](/l/ru/user-guide/data-migration/capabilities/uniqueness-constraints) diff --git a/packages/twenty-docs/l/ru/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx b/packages/twenty-docs/l/ru/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx index 5a14b3a7fd..03908fc604 100644 --- a/packages/twenty-docs/l/ru/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx +++ b/packages/twenty-docs/l/ru/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx @@ -1,71 +1,71 @@ --- title: Миграция с локального на облако -description: Step-by-step guide to migrate your Twenty self-hosted instance to Twenty Cloud. +description: Пошаговое руководство по миграции вашего самостоятельно размещённого экземпляра Twenty в Twenty Cloud. --- ## Обзор -This guide walks you through migrating your data from a Twenty self-hosted instance to Twenty Cloud. The process involves setting up your cloud workspace, exporting your data, and re-importing it. +В этом руководстве описан процесс переноса ваших данных из самостоятельно размещённого экземпляра Twenty в Twenty Cloud. Процесс включает настройку облачного рабочего пространства, экспорт данных и их повторный импорт. -Views, workflows, and roles must be recreated manually after migration. Plan time for this configuration work. +Представления, рабочие процессы и роли необходимо воссоздать вручную после миграции. Запланируйте время на эту настройку. -## Step 1: Create Your Cloud Workspace +## Шаг 1: Создайте облачное рабочее пространство -1. Go to [app.twenty.com](https://app.twenty.com) and create a new workspace -2. Complete the initial setup wizard -3. Note your new workspace URL +1. Перейдите на [app.twenty.com](https://app.twenty.com) и создайте новое рабочее пространство +2. Пройдите начальный мастер настройки +3. Запишите URL нового рабочего пространства -## Step 2: Recreate Your Data Model +## Шаг 2: Воссоздайте модель данных -Before importing data, recreate your custom objects and fields: +Перед импортом данных воссоздайте ваши пользовательские объекты и поля: -1. Go to **Settings → Data Model** in your cloud instance -2. Create custom objects that match your self-hosted setup -3. Add custom fields to standard and custom objects -4. Configure field settings (unique, required, etc.) +1. Перейдите в **Настройки → Модель данных** в вашем облачном экземпляре +2. Создайте пользовательские объекты, соответствующие вашей конфигурации в самостоятельно размещённом экземпляре +3. Добавьте пользовательские поля к стандартным и пользовательским объектам +4. Настройте параметры полей (уникальность, обязательность и т. д.) -Take screenshots of your self-hosted data model for reference, or keep both instances open side by side. +Сделайте скриншоты модели данных вашего самостоятельно размещённого экземпляра для справки или держите оба экземпляра открытыми рядом. -## Step 3: Invite All Users +## Шаг 3: Пригласите всех пользователей - **Critical: Invite users BEFORE importing data.** + **Важно: Пригласите пользователей ПЕРЕД импортом данных.** - Users must accept their invitations before you import any records that reference them (like Account Owner fields). If users don't exist yet, those relations cannot be mapped. + Пользователи должны принять приглашения до импорта любых записей, которые на них ссылаются (например, поля владельца аккаунта). Если пользователи ещё не существуют, эти связи нельзя будет сопоставить. -1. Go to **Settings → Members** in your cloud instance -2. Invite all team members who had accounts on self-hosted -3. **Wait for everyone to accept** their invitation -4. Verify all users appear in your Members list +1. Перейдите в **Настройки → Участники** в вашем облачном экземпляре +2. Пригласите всех участников команды, у которых были аккаунты в самостоятельно размещённой версии +3. **Дождитесь, пока все примут** приглашения +4. Проверьте, что все пользователи отображаются в списке «Участники» -## Step 4: Export Data from Self-Hosted +## Шаг 4: Экспортируйте данные из самостоятельно размещённой версии -Export each object from your self-hosted instance: +Экспортируйте каждый объект из вашего самостоятельно размещённого экземпляра: -1. Navigate to each object (Companies, People, Opportunities, etc.) -2. Configure the view to show **all columns** you want to migrate -3. Click **⋮ → Export view** -4. Save each CSV file with a clear name (e.g., `companies-export.csv`) +1. Перейдите к каждому объекту (Компании, Люди, Возможности и т. д.) +2. Настройте представление так, чтобы отображались **все столбцы**, которые вы хотите перенести +3. Нажмите **⋮ → Экспорт представления** +4. Сохраните каждый CSV-файл с понятным именем (например, `companies-export.csv`) -**Export in this order** (for reference when importing): +**Экспортируйте в следующем порядке** (для справки при импорте): 1. Компании 2. Люди 3. Возможности -4. Custom objects (following their dependencies) -5. Tasks, Notes +4. Пользовательские объекты (с учётом зависимостей) +5. Задачи, заметки -## Step 5: Update Workspace Member References +## Шаг 5: Обновите ссылки на участников рабочего пространства -The exported CSVs contain user IDs from your self-hosted instance. These IDs won't match your cloud instance, so you need to replace them with emails. +Экспортированные CSV-файлы содержат идентификаторы пользователей из вашего самостоятельно размещённого экземпляра. Эти идентификаторы не совпадут с облачным экземпляром, поэтому их нужно заменить на адреса электронной почты. -**For each CSV file with user references (Owner, Assignee, etc.):** +**Для каждого CSV-файла со ссылками на пользователей (владелец, исполнитель и т. д.):** -1. Open the CSV in a spreadsheet application -2. Add a new column next to each user ID column (e.g., `accountOwnerEmail` next to `accountOwnerId`) -3. Fill in the **email address** of each user -4. You can delete the old ID column or leave it (it will be skipped during import) +1. Откройте CSV в табличном редакторе +2. Добавьте новый столбец рядом с каждым столбцом идентификатора пользователя (например, `accountOwnerEmail` рядом с `accountOwnerId`) +3. Укажите **адрес электронной почты** каждого пользователя +4. Вы можете удалить старый столбец с идентификатором или оставить его (при импорте он будет пропущен) **Пример:** @@ -83,89 +83,89 @@ name,domain,accountOwnerEmail Acme Corp,https://acme.com,john@yourcompany.com ``` -Use the same email addresses that users used to accept their cloud workspace invitation. +Используйте те же адреса электронной почты, которые пользователи использовали для принятия приглашения в облачное рабочее пространство. -## Step 6: Plan Your Import Order +## Шаг 6: Спланируйте порядок импорта -Import files in the correct order to maintain relationships: +Импортируйте файлы в правильном порядке, чтобы сохранить связи: -1. **Companies** first (no dependencies) -2. **People** second (link to Companies) -3. **Opportunities** third (link to Companies and People) -4. **Custom objects** (following their dependencies) -5. **Tasks and Notes** last (link to other records) +1. **Компании** в первую очередь (без зависимостей) +2. **Люди** во вторую очередь (связь с компаниями) +3. **Возможности** в третью очередь (связь с компаниями и людьми) +4. **Пользовательские объекты** (с учётом зависимостей) +5. **Задачи и заметки** в последнюю очередь (связь с другими записями) -See [How to Import Relations](/l/ru/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv) for details on maintaining relationships. +См. [как импортировать связи](/l/ru/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv) для подробностей о сохранении связей. -## Step 7: Import to Cloud +## Шаг 7: Импорт в облако -For each CSV file, in order: +Для каждого CSV-файла, по порядку: -1. Navigate to the object in your cloud instance -2. Click **⋮ → Import records** -3. Upload the CSV file -4. Map columns to fields: - * Map user email columns to the appropriate relation fields - * Map other columns as usual -5. Review and fix any errors -6. Confirm the import -7. Verify a few records before proceeding to the next file +1. Перейдите к объекту в вашем облачном экземпляре +2. Нажмите **⋮ → Импорт записей** +3. Загрузите файл CSV +4. Сопоставьте столбцы с полями: + * Сопоставьте столбцы с адресами электронной почты пользователей соответствующим полям связей + * Сопоставьте остальные столбцы как обычно +5. Проверьте и исправьте любые ошибки +6. Подтвердите импорт +7. Проверьте несколько записей, прежде чем переходить к следующему файлу -## Step 8: Recreate Configuration +## Шаг 8: Воссоздайте конфигурацию -After importing data, manually recreate: +После импорта данных вручную воссоздайте: ### Представления -* Recreate saved views with filters, sorts, and column configurations -* Set up any kanban or calendar views +* Воссоздайте сохранённые представления с фильтрами, сортировками и настройками столбцов +* Настройте канбан- и календарные представления ### Рабочие процессы -* Recreate automations in **Settings → Workflows** -* Test each workflow before relying on it +* Воссоздайте автоматизации в **Настройки → Рабочие процессы** +* Протестируйте каждый рабочий процесс, прежде чем полагаться на него -### Roles and Permissions +### Роли и разрешения -* Configure roles in **Settings → Roles** -* Assign users to appropriate roles +* Настройте роли в **Настройки → Роли** +* Назначьте пользователям соответствующие роли ### Интеграции -* Reconnect email and calendar sync for each user -* Reconfigure any API integrations with new API keys +* Подключите заново синхронизацию почты и календаря для каждого пользователя +* Перенастройте любые интеграции API с новыми ключами API ## Послемиграционный контрольный список -All data imported successfully -Relations between objects working correctly -User assignments (Owner, Assignee) mapped correctly -Views recreated -Workflows recreated and tested -Roles and permissions configured -Email/calendar sync reconnected -API integrations updated with new keys +Все данные успешно импортированы +Связи между объектами работают корректно +Назначения пользователей (владелец, исполнитель) сопоставлены корректно +Представления воссозданы +Рабочие процессы воссозданы и протестированы +Роли и разрешения настроены +Синхронизация почты/календаря восстановлена +Интеграции API обновлены новыми ключами -## FAQ +## Часто задаваемые вопросы - - Not currently. Workflows must be recreated manually in your cloud instance. + + Пока нет. Рабочие процессы необходимо воссоздать вручную в вашем облачном экземпляре. - - File attachments are not included in CSV exports. You'll need to re-upload any attachments manually, migrate them via API or contact our team for assistance with large migrations. + + Вложения не включаются в экспорт CSV. Вам потребуется повторно загрузить все вложения вручную, перенести их через API или связаться с нашей командой для помощи при крупных миграциях. - - Yes, we recommend keeping your self-hosted instance running until you've verified the cloud migration is complete. Just be careful not to create new data in both places. + + Да, мы рекомендуем оставлять самостоятельно размещённый экземпляр запущенным, пока вы не убедитесь, что миграция в облако завершена. Просто следите, чтобы не создавать новые данные в обеих системах. - - Records referencing that user will fail to import or the relation will be empty. Ensure all users accept invitations before importing data. + + Записи, ссылающиеся на этого пользователя, не будут импортированы, либо связь останется пустой. Убедитесь, что все пользователи приняли приглашения перед импортом данных. ## Нужна Помощь? -For complex migrations or large datasets, contact us at [contact@twenty.com](mailto:contact@twenty.com) or explore our [Implementation Services](/l/ru/user-guide/getting-started/capabilities/implementation-services). +Для сложных миграций или больших наборов данных свяжитесь с нами по адресу [contact@twenty.com](mailto:contact@twenty.com) или изучите наши [услуги по внедрению](/l/ru/user-guide/getting-started/capabilities/implementation-services). diff --git a/packages/twenty-docs/l/ru/user-guide/settings/how-tos/settings-faq.mdx b/packages/twenty-docs/l/ru/user-guide/settings/how-tos/settings-faq.mdx index 6c17dc9bfb..4ae8d068f1 100644 --- a/packages/twenty-docs/l/ru/user-guide/settings/how-tos/settings-faq.mdx +++ b/packages/twenty-docs/l/ru/user-guide/settings/how-tos/settings-faq.mdx @@ -86,7 +86,7 @@ image: /images/user-guide/setup/settings.png 1. Перейдите в **Настройки → Опыт** 2. Найдите раздел "Тема" - 3. Выберите Светлая, Темная или Системная + 3. Выберите «Светлая», «Тёмная» или «Системная» diff --git a/packages/twenty-docs/l/ru/user-guide/settings/overview.mdx b/packages/twenty-docs/l/ru/user-guide/settings/overview.mdx index 7a037fb57c..38fa57bcf9 100644 --- a/packages/twenty-docs/l/ru/user-guide/settings/overview.mdx +++ b/packages/twenty-docs/l/ru/user-guide/settings/overview.mdx @@ -1,6 +1,6 @@ --- title: Настройки -description: Set up your Twenty workspace with essential configurations. +description: Настройте рабочее пространство Twenty с основными настройками. image: /images/user-guide/setup/settings.png --- @@ -8,60 +8,60 @@ image: /images/user-guide/setup/settings.png Настройки -## Initial Setup +## Начальная настройка -When you first create your workspace, there are several key settings to configure. +Когда вы впервые создаете рабочее пространство, необходимо настроить несколько ключевых параметров. -### Workspace Name and Logo +### Название рабочего пространства и логотип -1. Go to **Settings → General** -2. Update your workspace name -3. Upload your company logo -4. Save your changes +1. Перейдите в **Настройки → Общие** +2. Обновите название рабочего пространства +3. Загрузите логотип вашей компании +4. Сохраните изменения -### Time Zone and Date Format +### Часовой пояс и формат даты 1. Перейдите в **Настройки → Опыт** -2. Select your time zone -3. Choose your preferred date format -4. Save your changes +2. Выберите часовой пояс +3. Выберите предпочитаемый формат даты +4. Сохраните изменения -## Essential Configurations +## Основные настройки -### Connect Email and Calendar +### Подключите электронную почту и календарь -Set up email and calendar sync: +Настройте синхронизацию электронной почты и календаря: 1. Перейдите в **Настройки → Аккаунты** 2. Нажмите **Добавить аккаунт** -3. Connect your Google or Microsoft account -4. Configure sync settings +3. Подключите учетную запись Google или Microsoft +4. Настройте параметры синхронизации -→ [Complete email & calendar setup guide](/l/ru/user-guide/calendar-emails/overview) +→ [Полное руководство по настройке электронной почты и календаря](/l/ru/user-guide/calendar-emails/overview) -### Invite Your Team +### Пригласите свою команду -Add team members to your workspace: +Добавьте участников команды в ваше рабочее пространство: -1. Go to **Settings → Members** -2. Click **+ Invite** -3. Enter email addresses -4. Assign appropriate roles +1. Перейдите в **Настройки → Участники** +2. Нажмите **+ Пригласить** +3. Введите адреса электронной почты +4. Назначьте соответствующие роли - Before inviting your team, check the default role under **Settings → Roles**. New members are automatically assigned this role when they join. + Прежде чем приглашать команду, проверьте роль по умолчанию в разделе **Настройки → Роли**. Новые участники автоматически получают эту роль при присоединении. -## Workspace Settings Checklist +## Контрольный список настроек рабочего пространства -* Workspace name and logo configured -* Time zone and date format set -* Email and calendar connected -* Team members invited -* Roles and permissions configured +* Название рабочего пространства и логотип настроены +* Часовой пояс и формат даты установлены +* Почта и календарь подключены +* Участники команды приглашены +* Роли и разрешения настроены ## Следующие шаги -* [Workspace settings](/l/ru/user-guide/settings/capabilities/workspace-settings) -* [Profile settings](/l/ru/user-guide/settings/capabilities/profile-settings) -* [Experience settings](/l/ru/user-guide/settings/capabilities/experience-settings) +* [Настройки рабочего пространства](/l/ru/user-guide/settings/capabilities/workspace-settings) +* [Настройки профиля](/l/ru/user-guide/settings/capabilities/profile-settings) +* [Настройки интерфейса](/l/ru/user-guide/settings/capabilities/experience-settings) diff --git a/packages/twenty-docs/l/ru/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx b/packages/twenty-docs/l/ru/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx index 01aae3e9af..97adb56623 100644 --- a/packages/twenty-docs/l/ru/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx +++ b/packages/twenty-docs/l/ru/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx @@ -1,120 +1,120 @@ --- -title: Set Up a Sales Pipeline -description: Configure your sales pipeline to track opportunities through stages. +title: Настройка воронки продаж +description: Настройте воронку продаж для отслеживания возможностей по стадиям. --- import { VimeoEmbed } from '/snippets/vimeo-embed.mdx'; -A sales pipeline in Twenty is a Kanban view of your Opportunities object, where each column represents a stage in your sales process. +В Twenty воронка продаж — это представление Канбан объекта «Возможности», где каждый столбец соответствует стадии вашего процесса продаж. -## Step 1: Configure Your Stages +## Шаг 1: Настройте стадии -Stages are defined in the Opportunities object's **Stage** field. +Стадии задаются в поле **Stage** объекта «Возможности». -1. Go to **Settings → Data Model** -2. Select **Opportunities** -3. Find and click the **Stage** field -4. Add, remove, or rename stages to match your process +1. Перейдите в **Настройки → Модель данных** +2. Выберите **Возможности** +3. Найдите и нажмите поле **Stage** +4. Добавьте, удалите или переименуйте стадии в соответствии с вашим процессом -### Recommended Stages +### Рекомендуемые стадии -| Этап | Purpose | -| --------------- | ----------------------------------- | -| **New** | Fresh opportunities just identified | -| **Qualified** | Confirmed as a good fit | -| **Meeting** | Engaged in discussions | -| **Proposal** | Proposal sent | -| **Negotiation** | Working on terms | -| **Closed Won** | Deal successful | -| **Closed Lost** | Deal unsuccessful | +| Этап | Назначение | +| ----------------------- | --------------------------------- | +| **Новый** | Только что выявленные возможности | +| **Квалифицированные** | Подтверждённое соответствие | +| **Встреча** | Ведутся обсуждения | +| **Предложение** | Предложение отправлено | +| **Переговоры** | Обсуждение условий | +| **Закрыта — выиграно** | Сделка успешно завершена | +| **Закрыта — проиграно** | Сделка неуспешна | - **5-7 stages is optimal.** Too many stages makes the pipeline hard to scan; too few loses visibility into deal progress. + **Оптимально 5–7 стадий.** Слишком много стадий усложняет просмотр воронки; слишком мало — снижает прозрачность прогресса по сделкам. -## Step 2: Create a Pipeline View +## Шаг 2: Создайте представление воронки -1. Go to **Opportunities** -2. Click the view dropdown → **+ Add view** -3. Name it "Sales Pipeline" -4. Click **Create** -5. Open **Options** and select **Kanban** as the layout +1. Перейдите в **Возможности** +2. Откройте выпадающее меню представления → **+ Добавить представление** +3. Назовите его «Воронка продаж» +4. Нажмите **Создать** +5. Откройте **Параметры** и выберите **Канбан** в качестве макета -The view automatically uses the Stage field for columns. +Представление автоматически использует поле Stage для столбцов. -## Step 3: Configure Your View +## Шаг 3: Настройте ваше представление -### Show Key Fields +### Отображение ключевых полей -1. Click **Options → Fields** -2. Look for fields in the "Hidden Fields" section -3. Click the **eye icon** to display: Company, Amount, Close Date, Owner +1. Нажмите **Параметры → Поля** +2. Найдите поля в разделе «Скрытые поля» +3. Нажмите **значок глаза**, чтобы отобразить: Company, Amount, Close Date, Owner -### Enable Aggregations +### Включите агрегирование -Show totals at the top of each column: +Показывайте итоги вверху каждого столбца: -1. Click the number displayed next to a Stage name at the top of a column -2. Select the aggregation type (Count, Sum, Average, etc.) -3. Choose the field to aggregate (e.g., Amount) +1. Щёлкните по числу, отображаемому рядом с названием стадии вверху столбца +2. Выберите тип агрегации (Count, Sum, Average и т. д.) +3. Выберите поле для агрегации (например, Amount) -**Example:** Show total deal value per stage by aggregating Amount with Sum. +**Пример:** Показать общую стоимость сделок по стадиям, агрегируя Amount с помощью Sum. -### Use Compact View (Optional) +### Используйте компактный вид (необязательно) -For a high-level overview with minimal card content: +Для обзорного вида с минимальным содержимым карточек: -1. Click **Options** -2. Turn on the toggle for **Compact view** +1. Нажмите **Параметры** +2. Включите переключатель **Компактный вид** -## Step 4: Create Personal and Team Views +## Шаг 4: Создайте личные и командные представления -### "My Pipeline" +### "Моя воронка" -* **Filter**: Owner = Me -* **Visibility**: Unlisted (personal view) +* **Фильтр**: Owner = Me +* **Видимость**: Unlisted (личное представление) -### "Team Pipeline" +### "Командная воронка" -* **Filter**: None (show all) -* **Visibility**: Workspace (shared view) +* **Фильтр**: None (показать всё) +* **Видимость**: Workspace (общее представление) -### "Closing This Month" +### "Закрытия в этом месяце" -* **Type**: Table -* **Filter**: Close Date = This month, Stage ≠ Closed Won, Stage ≠ Closed Lost -* **Sort**: Close Date ascending +* **Тип**: Table +* **Фильтр**: Close Date = This month, Stage ≠ Closed Won, Stage ≠ Closed Lost +* **Сортировка**: Close Date по возрастанию -## Working with Opportunities +## Работа с возможностями -### Creating Opportunities +### Создание возможностей -* Click **+ New** in the Opportunities view -* Or click **+** in a specific stage column +* Нажмите **+ New** в представлении «Возможности» +* Либо нажмите **+** в столбце нужной стадии -### Moving Through Stages +### Переход между стадиями -Drag and drop opportunity cards between columns to update their stage. +Перетаскивайте карточки возможностей между столбцами, чтобы обновить их стадию. ## Лучшие практики -### Pipeline Hygiene +### Гигиена воронки -* Update deals daily as they progress -* Move or close stale deals promptly -* Keep close dates realistic +* Ежедневно обновляйте сделки по мере их продвижения +* Своевременно перемещайте или закрывайте «застоявшиеся» сделки +* Поддерживайте реалистичные даты закрытия -### Stage Discipline +### Дисциплина стадий -* Define clear criteria for each stage -* Move deals promptly when criteria are met -* Don't let deals sit in stages too long +* Определите чёткие критерии для каждой стадии +* Своевременно переводите сделки при выполнении критериев +* Не допускайте, чтобы сделки слишком долго застревали на стадиях -## Related +## Связанные материалы -* [Kanban Views](/l/ru/user-guide/views-pipelines/capabilities/kanban-views) — aggregations and compact view -* [Filters and Sorting](/l/ru/user-guide/views-pipelines/capabilities/filters-and-sorting) — creating filtered views +* [Канбан-представления](/l/ru/user-guide/views-pipelines/capabilities/kanban-views) — агрегации и компактный вид +* [Фильтры и сортировка](/l/ru/user-guide/views-pipelines/capabilities/filters-and-sorting) — создание отфильтрованных представлений diff --git a/packages/twenty-docs/l/ru/user-guide/workflows/capabilities/use-branches-in-workflows.mdx b/packages/twenty-docs/l/ru/user-guide/workflows/capabilities/use-branches-in-workflows.mdx index da489cae8e..e09c98ad14 100644 --- a/packages/twenty-docs/l/ru/user-guide/workflows/capabilities/use-branches-in-workflows.mdx +++ b/packages/twenty-docs/l/ru/user-guide/workflows/capabilities/use-branches-in-workflows.mdx @@ -1,90 +1,90 @@ --- -title: Use Branches in Workflows -description: Understand how branches work and how to control which path is executed. +title: Использование веток в рабочих процессах +description: Разберитесь, как работают ветки и как управлять тем, какой путь выполняется. --- -## How Branches Work +## Как работают ветки -In the workflow editor, you can create multiple paths (branches) going out from a single node. This allows you to build complex automations with different outcomes. +В редакторе рабочего процесса вы можете создавать несколько путей (веток), выходящих из одного узла. Это позволяет строить сложные автоматизации с разными результатами. -**Important**: When a workflow runs, **all branches execute in parallel by default**. There is no built-in "if/else" logic to choose one branch over another—every path will run simultaneously. +**Важно**: при запуске рабочего процесса **все ветки по умолчанию выполняются параллельно**. Нет встроенной логики "if/else" для выбора одной ветки вместо другой — каждый путь будет запускаться одновременно. -## Controlling Which Branch Runs +## Управление тем, какая ветка запускается -To execute only one branch based on specific conditions, **add a Filter node at the beginning of each branch**. +Чтобы выполнять только одну ветку на основании определённых условий, **добавьте узел Filter в начале каждой ветки**. -### Example Setup +### Пример настройки -1. Create your workflow with multiple branches from a single node -2. Add a **Filter** node as the first step in each branch -3. Set conditions on each Filter to determine when that branch should continue -4. Only the branch(es) whose Filter conditions are met will proceed +1. Создайте рабочий процесс с несколькими ветками от одного узла +2. Добавьте узел **Filter** в качестве первого шага в каждой ветке +3. Задайте условия на каждом узле Filter, чтобы определить, когда эта ветка должна продолжить выполнение +4. Продолжат выполнение только те ветки, для которых выполнены условия узла Filter -### How Filters Work +### Как работают фильтры -* If the Filter condition is **met**: The branch continues executing -* If the Filter condition is **not met**: The branch stops at the Filter node +* Если условие Filter выполнено: ветка продолжает выполнение +* Если условие Filter не выполнено: ветка останавливается на узле Filter -This effectively creates conditional logic where only the appropriate branch runs based on your data. +Это фактически создаёт условную логику, при которой на основе ваших данных выполняется только соответствующая ветка. -## Example: Route by Deal Size +## Пример: маршрутизация по размеру сделки -**Scenario**: When a deal is closed, send different notifications based on deal size. +**Сценарий**: когда сделка закрывается, отправляйте разные уведомления в зависимости от её размера. -1. **Trigger**: Opportunity updated (Stage = Closed Won) -2. **Branch 1**: Filter for Amount > $10,000 → Send Slack message to #big-deals -3. **Branch 2**: Filter for Amount ≤ $10,000 → Send email to sales manager +1. **Триггер**: сделка обновлена (стадия = «Закрыта — выиграна») +2. **Ветка 1**: фильтр по сумме > $10,000 → отправить сообщение в Slack в #big-deals +3. **Ветка 2**: фильтр по сумме ≤ $10,000 → отправить письмо менеджеру по продажам -Both branches start, but only the one matching the deal amount will continue past its Filter. +Обе ветки запускаются, но продолжит выполнение после своего Filter только та, что соответствует сумме сделки. -## Creating Branches +## Создание веток - To create a new branch from an existing step, click the **+** button on the step and add your action. You can add multiple branches by clicking **+** multiple times. + Чтобы создать новую ветку из существующего шага, нажмите кнопку **+** на этом шаге и добавьте действие. Вы можете добавить несколько веток, нажав **+** несколько раз. -1. In the workflow editor, select the step you want to branch from -2. Click the **+** button to add an action -3. This creates one branch -4. Click **+** again on the same step to create additional branches -5. Each branch can have its own sequence of actions +1. В редакторе рабочего процесса выберите шаг, от которого вы хотите создать ветку +2. Нажмите **+**, чтобы добавить действие +3. Будет создана одна ветка +4. Нажмите **+** ещё раз на том же шаге, чтобы создать дополнительные ветки +5. Каждая ветка может иметь собственную последовательность действий -## Merging Branches Back Together +## Объединение веток -After parallel branches complete their work, you can merge them back into a single path: +После того как параллельные ветки завершат работу, вы можете объединить их обратно в один путь: -1. Complete your branched actions -2. Add a new step that should run after all branches -3. Drag a connection from the last step of each branch to this new step -4. The merged step waits for all connected branches to complete before executing +1. Завершите действия в ветках +2. Добавьте новый шаг, который должен выполняться после всех веток +3. Перетащите соединение с последнего шага каждой ветки к этому новому шагу +4. Объединенный шаг ожидает завершения всех подключенных веток перед выполнением -### Example: Process Then Notify +### Пример: обработка, затем уведомление ``` -Trigger +Триггер │ - ├── Branch A: Update Customer Record + ├── Ветка A: Обновить запись клиента │ - └── Branch B: Create Support Ticket + └── Ветка B: Создать заявку в поддержку ↘ ↙ - Merged Step: Send Confirmation Email + Объединённый шаг: Отправить подтверждающее письмо ``` -The confirmation email sends only after both the customer update and ticket creation are done. +Подтверждающее письмо отправится только после завершения обновления клиента и создания заявки. ## Лучшие практики -* Always use **Filter nodes** at the start of branches when you want conditional execution -* Keep branch conditions **mutually exclusive** to avoid duplicate actions -* Test your workflows with different data to ensure the correct branches run -* **Rename branch steps** descriptively so it's clear what each path does -* **Merge branches** when you need a final action after parallel processing +* Всегда используйте **узлы Filter** в начале веток, когда требуется условное выполнение +* Делайте условия веток **взаимно исключающимися**, чтобы избежать дублирования действий +* Тестируйте рабочие процессы с разными данными, чтобы убедиться, что запускаются правильные ветки +* **Переименовывайте шаги веток** так, чтобы было ясно, что делает каждая ветка +* **Объединяйте ветки**, когда нужно финальное действие после параллельной обработки -## Related +## Связанные материалы -* [Workflows FAQ](/l/ru/user-guide/workflows/how-tos/need-more-help/workflows-faq) — answers about parallel execution -* [Workflow Actions](/l/ru/user-guide/workflows/capabilities/workflow-actions) — available actions for branches +* [FAQ по рабочим процессам](/l/ru/user-guide/workflows/how-tos/need-more-help/workflows-faq) — ответы о параллельном выполнении +* [Действия рабочего процесса](/l/ru/user-guide/workflows/capabilities/workflow-actions) — доступные действия для веток diff --git a/packages/twenty-docs/l/ru/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities.mdx b/packages/twenty-docs/l/ru/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities.mdx index d93499f0a1..2fbf56f10c 100644 --- a/packages/twenty-docs/l/ru/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities.mdx +++ b/packages/twenty-docs/l/ru/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities.mdx @@ -1,56 +1,56 @@ --- -title: Detect Stale Opportunities -description: Automatically notify managers when opportunities haven't been updated. +title: Выявление застойных возможностей +description: Автоматически уведомляйте менеджеров, когда возможности не обновлялись. --- -Keep your pipeline healthy by alerting managers when opportunities go stale. This workflow checks for opportunities that haven't been updated in a specified number of days. +Поддерживайте воронку продаж в порядке, уведомляя менеджеров, когда возможности застаиваются. Этот рабочий процесс проверяет возможности, которые не обновлялись в течение указанного числа дней. -## The Problem +## Проблема -Opportunities sitting without updates lead to: +Возможности без обновлений приводят к: -* Deals going cold -* Unreliable forecasts -* Lost revenue +* Остывающие сделки +* Ненадежные прогнозы +* Потеря выручки -## The Solution +## Решение -Create a scheduled workflow that finds stale opportunities and emails their managers. +Создайте запланированный рабочий процесс, который находит застойные возможности и отправляет их менеджерам электронные письма. -## Step-by-Step Setup +## Пошаговая настройка -### Step 1: Create the Workflow +### Шаг 1: Создайте рабочий процесс -1. Go to **Settings → Workflows** -2. Click **+ New Workflow** -3. Name it "Stale Opportunity Alert" +1. Перейдите в **Настройки → Рабочие процессы** +2. Нажмите **+ Новый рабочий процесс** +3. Назовите его «Оповещение о застойных возможностях» -### Step 2: Configure the Trigger +### Шаг 2: Настройте триггер -1. Select **On a Schedule** -2. Set to run daily (e.g., every day at 8 AM) +1. Выберите **On a Schedule** +2. Установите ежедневный запуск (например, каждый день в 8:00) -### Step 3: Search for Stale Opportunities +### Шаг 3: Поиск застойных возможностей -1. Add **Search Records** action +1. Добавьте действие **Search Records** 2. Настроить: -| Поле | Значение | -| ---------- | ----------------------------------------------- | -| **Object** | Возможности | -| **Filter** | Updated At is before (today - 7 days) | -| **Filter** | Stage is not "Closed Won" AND not "Closed Lost" | -| **Limit** | 100 | +| Поле | Значение | +| ---------- | ------------------------------------------ | +| **Объект** | Возможности | +| **Фильтр** | Updated At раньше, чем (сегодня - 7 дней) | +| **Фильтр** | Stage не "Closed Won" AND не "Closed Lost" | +| **Лимит** | 100 | -### Step 4: Check If Any Found +### Шаг 4: Проверьте, есть ли найденные записи -1. Add **Filter** action -2. Condition: `{{searchRecords.length}}` is greater than 0 -3. If no stale opportunities, the workflow stops here +1. Добавьте действие **Фильтр** +2. Условие: `{{searchRecords.length}}` больше 0 +3. Если застойных возможностей нет, рабочий процесс останавливается здесь -### Step 5: Format the Alert (Code Action) +### Шаг 5: Сформатируйте оповещение (действие Code) -Add a **Code** action to format the email: +Добавьте действие **Code** для форматирования письма: ```javascript export const main = async (params) => { @@ -88,49 +88,49 @@ export const main = async (params) => { }; ``` -### Step 6: Send Alert Email +### Шаг 6: Отправьте письмо с оповещением -Add **Send Email** action: +Добавьте действие **Send Email**: -| Поле | Значение | -| ----------- | ----------------------------------------------------------- | -| **To** | sales-manager@yourcompany.com | -| **Subject** | `🚨 {{code.totalCount}} Stale Opportunities Need Attention` | -| **Body** | `{{code.summary}}` | +| Поле | Значение | +| --------- | ---------------------------------------------------------------- | +| **Кому** | sales-manager@yourcompany.com | +| **Тема** | `🚨 {{code.totalCount}} застойных возможностей требуют внимания` | +| **Текст** | `{{code.summary}}` | -### Step 7: Test and Activate +### Шаг 7: Протестируйте и активируйте -1. Click **Test** to run the workflow -2. Check that the email contains the right data -3. Activate when ready +1. Нажмите **Test** для запуска рабочего процесса +2. Проверьте, что письмо содержит корректные данные +3. Активируйте, когда будете готовы -## Customization Options +## Варианты настройки -### Change Staleness Threshold +### Измените порог застоя -Modify the Search Records filter to change from 7 days to your preferred period: +Измените фильтр Search Records, чтобы заменить 7 дней на предпочитаемый вами период: -* 3 days for high-velocity sales -* 14 days for enterprise deals -* 30 days for long sales cycles +* 3 дня для быстрых продаж +* 14 дней для корпоративных сделок +* 30 дней для длинных циклов продаж -### Alert Individual Reps +### Оповещайте отдельных менеджеров по продажам -Instead of one manager email, use **Iterator** to send personalized emails to each rep about their own stale deals. +Вместо одного письма менеджеру используйте **Iterator** для отправки персонализированных писем каждому менеджеру по продажам о его застойных сделках. -### Add Escalation +### Добавьте эскалацию -Create multiple workflows with increasing severity: +Создайте несколько рабочих процессов с возрастающим уровнем серьезности: -1. Day 7: Email to rep -2. Day 14: Email to rep + manager -3. Day 21: Create task for manager to intervene +1. День 7: письмо менеджеру по продажам +2. День 14: письмо менеджеру по продажам и руководителю +3. День 21: создать задачу для руководителя о необходимости вмешаться -### Include in Slack +### Добавьте в Slack -Use **HTTP Request** to post to a Slack webhook instead of or in addition to email. +Используйте **HTTP Request**, чтобы отправлять сообщения в Slack через вебхук вместо электронной почты или в дополнение к ней. -## Related +## Связанные материалы -* [Workflow Actions](/l/ru/user-guide/workflows/capabilities/workflow-actions) -* [Send Emails from Workflows](/l/ru/user-guide/workflows/capabilities/send-emails-from-workflows) +* [Действия рабочего процесса](/l/ru/user-guide/workflows/capabilities/workflow-actions) +* [Отправка писем из рабочих процессов](/l/ru/user-guide/workflows/capabilities/send-emails-from-workflows) diff --git a/packages/twenty-docs/l/tr/user-guide/data-migration/how-tos/fix-import-errors.mdx b/packages/twenty-docs/l/tr/user-guide/data-migration/how-tos/fix-import-errors.mdx index 1a8d464487..0bb36292ec 100644 --- a/packages/twenty-docs/l/tr/user-guide/data-migration/how-tos/fix-import-errors.mdx +++ b/packages/twenty-docs/l/tr/user-guide/data-migration/how-tos/fix-import-errors.mdx @@ -1,11 +1,11 @@ --- -title: Fix Import Errors -description: Complete troubleshooting guide for resolving CSV import errors. +title: İçe aktarma hatalarını düzeltin +description: CSV içe aktarma hatalarını çözmeye yönelik eksiksiz bir sorun giderme kılavuzu. --- ## Genel Bakış -Import not working? This guide helps you identify and fix common import errors step by step. +İçe aktarma çalışmıyor mu? This guide helps you identify and fix common import errors step by step. ## How Import Validation Works diff --git a/packages/twenty-docs/l/tr/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx b/packages/twenty-docs/l/tr/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx index 5ede693434..5831eb6f3f 100644 --- a/packages/twenty-docs/l/tr/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx +++ b/packages/twenty-docs/l/tr/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv.mdx @@ -1,103 +1,103 @@ --- -title: Import Relations Between Objects via CSV -description: Complete step-by-step guide to linking records during CSV import. +title: CSV ile Nesneler Arasındaki İlişkileri İçe Aktarma +description: CSV içe aktarma sırasında kayıtları bağlamaya yönelik eksiksiz adım adım kılavuz. --- ## Genel Bakış -This guide walks you through importing relations between objects—for example, linking People to Companies, or Opportunities to People. +Bu kılavuz, nesneler arasındaki ilişkileri içe aktarma konusunda size yol gösterir—örneğin, Kişileri Şirketlere ya da Fırsatları Kişilere bağlama. -**What can be imported:** Only one-to-many relations pointing to a single object type. Relations pointing to multiple object types (like Notes linking to People AND Companies) are not yet supported for import. +**İçe aktarılabilecekler:** Yalnızca tek bir nesne türüne işaret eden bire-çoğa ilişkiler. Birden fazla nesne türüne işaret eden ilişkiler (ör. Notların Kişilere VE Şirketlere bağlanması) henüz içe aktarmada desteklenmiyor. -## Understanding Relations +## İlişkileri Anlama -### What is a "One-to-Many" Relation? +### "Bire-Çoğa" İlişki Nedir? -In a one-to-many relation: +Bir bire-çoğa ilişkide: -* **One** Company has **many** People (employees) -* **One** Company has **many** Opportunities -* **One** Person has **many** Tasks +* **Bir** Şirketin **birçok** Kişisi (çalışanı) vardır +* **Bir** Şirketin **birçok** Fırsatı vardır +* **Bir** Kişinin **birçok** Görevi vardır -The "one" side is the **parent**. The "many" side is the **child**. +"Bir" taraf **ana** taraftır. "Çok" taraf **alt** taraftır. -### Common Relations in Twenty +### Twenty'de Yaygın İlişkiler -| İlişki | "One" Side (Parent) | "Many" Side (Child) | -| ------------------------- | ------------------- | ------------------- | -| Companies → People | Şirket | İnsanlar | -| Companies → Opportunities | Şirket | Fırsatlar | -| People → Tasks | Kişi | Görevler | -| People → Notes | Kişi | Notlar | +| İlişki | "Bir" Taraf (Ana) | "Çok" Taraf (Alt) | +| --------------------- | ----------------- | ----------------- | +| Şirketler → Kişiler | Şirket | İnsanlar | +| Şirketler → Fırsatlar | Şirket | Fırsatlar | +| Kişiler → Görevler | Kişi | Görevler | +| Kişiler → Notlar | Kişi | Notlar | -## Step 1: Identify the "One" and "Many" Sides +## Adım 1: "Bir" ve "Çok" Tarafları Belirleyin -Before importing, determine which object is the parent and which is the child. +İçe aktarmadan önce hangi nesnenin ana, hangisinin alt olduğunu belirleyin. -**Ask yourself:** "Does ONE [Object A] have MANY [Object B]?" +**Kendinize sorun:** "BİR [Nesne A]'nın ÇOK [Nesne B]'si var mı?" -* One Company → Many People ✓ (Company is parent) -* One Person → Many Companies ✗ (This is wrong—a person belongs to one company) +* Bir Şirket → Çok Kişi ✓ (Şirket ana taraftır) +* Bir Kişi → Çok Şirket ✗ (Bu yanlıştır—bir kişi bir şirkete aittir) -## Step 2: Import the Parent Records First +## Adım 2: Önce Ana Kayıtları İçe Aktarın -The parent ("one" side) must exist in Twenty before you can reference it. +Ana ("bir" taraf) kaydı, ona referans verebilmeden önce Twenty'de mevcut olmalıdır. -**Import order:** +**İçe aktarma sırası:** -1. **Companies** first (no dependencies) -2. **People** second (link to Companies) -3. **Opportunities** third (link to Companies and/or People) -4. **Tasks/Notes** (link to any of the above) +1. Önce **Şirketler** (bağımlılık yok) +2. İkinci olarak **Kişiler** (Şirketlere bağlanır) +3. Üçüncü olarak **Fırsatlar** (Şirketlere ve/veya Kişilere bağlanır) +4. **Görevler/Notlar** (yukarıdakilerin herhangi birine bağlanır) - **If the parent record doesn't exist, the import will fail.** + **Ana kayıt mevcut değilse içe aktarma başarısız olur.** - Always verify that Companies are imported before importing People with company references. + Şirket referansları olan Kişileri içe aktarmadan önce, Şirketlerin içe aktarılmış olduğunu her zaman doğrulayın. -## Step 3: Note the Parent's Unique Identifier +## Adım 3: Ana kaydın benzersiz tanımlayıcısını not edin -You need to reference the parent record using a **unique identifier**. Available options: +Ana kayda **benzersiz bir tanımlayıcı** kullanarak referans vermeniz gerekir. Kullanılabilir seçenekler: -| Parent Object | Available Unique Identifiers | -| ------------------------- | --------------------------------------------------------------- | -| **Şirketler** | `id` (UUID), `domain` (recommended), or any custom unique field | -| **People** | `id` (UUID), `email`, or any custom unique field | -| **Çalışma Alanı Üyeleri** | `id` (UUID), `email` (not name) | -| **Özel Nesneler** | `id` (UUID), or any field marked as unique | +| Ana Nesne | Kullanılabilir Benzersiz Tanımlayıcılar | +| ------------------------- | ---------------------------------------------------------------------- | +| **Şirketler** | `id` (UUID), `domain` (önerilir) veya herhangi bir özel benzersiz alan | +| **Kişiler** | `id` (UUID), `email` veya herhangi bir özel benzersiz alan | +| **Çalışma Alanı Üyeleri** | `id` (UUID), `email` (isim değil) | +| **Özel Nesneler** | `id` (UUID) veya benzersiz olarak işaretlenmiş herhangi bir alan | -**Recommended:** Use `domain` for Companies and `email` for People. These are human-readable and easy to verify in your spreadsheet. +**Önerilir:** Şirketler için `domain`, Kişiler için `email` kullanın. Bunlar insan tarafından okunabilirdir ve e-tablonuzda doğrulanması kolaydır. -### Finding the Identifier +### Tanımlayıcıyı Bulma -If you need the `id`: +`id` gerekiyorsa: -1. Export the parent records from Twenty -2. The export includes the `id` column -3. Use these IDs in your child records file +1. Ana kayıtları Twenty'den dışa aktarın +2. Dışa aktarma `id` sütununu içerir +3. Bu kimlikleri alt kayıtlar dosyanızda kullanın -## Step 4: Verify the Relation Field Exists +## Adım 4: İlişki Alanının Var Olduğunu Doğrulayın -Before importing, ensure the relation field exists between your objects. +İçe aktarmadan önce, nesneleriniz arasında ilişki alanının mevcut olduğundan emin olun. -**To check or create:** +**Kontrol etmek veya oluşturmak için:** -1. Go to **Settings → Data Model** -2. Select your child object (e.g., People) -3. Look for a relation field pointing to the parent (e.g., Company) -4. If it doesn't exist, create it: - * Click **+ Add field** - * Select **Relation** type - * Choose the parent object +1. **Ayarlar → Veri Modeli** bölümüne gidin +2. Alt nesnenizi seçin (ör. Kişiler) +3. Ana tarafa işaret eden bir ilişki alanı olup olmadığına bakın (ör. Şirket) +4. Yoksa oluşturun: + * **+ Alan Ekle**'ye tıklayın + * **İlişki** türünü seçin + * Ana nesneyi seçin -## Step 5: Prepare Your CSV File +## Adım 5: CSV Dosyanızı Hazırlayın -Add a column to your child CSV that references the parent using its unique identifier. +Alt CSV'nize, ana tarafa benzersiz tanımlayıcısıyla referans veren bir sütun ekleyin. -### Example: People Linking to Companies +### Örnek: Kişilerin Şirketlere Bağlanması -**Your People CSV:** +**Kişiler CSV'niz:** ```csv firstName,lastName,email,jobTitle,companyDomain @@ -106,66 +106,66 @@ Jane,Doe,jane@widgets.co,CTO,https://widgets.co Bob,Johnson,bob@techstart.io,Developer,https://techstart.io ``` -The `companyDomain` column references the Company's domain. +`companyDomain` sütunu, Şirketin alan adına referans verir. -### Format Requirements +### Biçim Gereksinimleri -| Tanımlayıcı | Biçim | Örnek | -| ----------- | -------------- | -------------------------------------- | -| Alan Adı | URL format | `https://acme.com` | -| E-posta | Standard email | `john@acme.com` | -| Kimlik | UUID | `c776ee49-f608-4a77-8cc8-6fe96ae1e43f` | +| Tanımlayıcı | Biçim | Örnek | +| ----------- | ---------------- | -------------------------------------- | +| Alan Adı | URL biçimi | `https://acme.com` | +| E-posta | Standart e-posta | `john@acme.com` | +| Kimlik | UUID | `c776ee49-f608-4a77-8cc8-6fe96ae1e43f` | - **Domain format matters!** + **Alan adı biçimi önemlidir!** - Use `https://domain.com` (not just `domain.com`). This matches how Twenty stores Company domains and prevents matching errors. + `https://domain.com` kullanın (yalnızca `domain.com` değil). Bu, Twenty'nin Şirket alan adlarını saklama biçimiyle eşleşir ve eşleştirme hatalarını önler. -### Important Rules +### Önemli Kurallar -1. **Exact match required** — the value must exactly match the parent record -2. **Map only ONE unique identifier** — don't include both `companyId` AND `companyDomain` -3. **Case sensitive** — `Acme.com` ≠ `acme.com` +1. **Bire bir eşleşme gerekir** — değer ana kayda tam olarak uymalıdır +2. **Yalnızca TEK bir benzersiz tanımlayıcıyı eşleyin** — hem `companyId` HEM DE `companyDomain` eklemeyin +3. **Büyük/küçük harf duyarlı** — `Acme.com` ≠ `acme.com` -## Step 6: Upload and Map the Relation +## Adım 6: İlişkiyi Yükleyin ve Eşleyin -1. Navigate to the child object (e.g., People) -2. Click **⋮** → **Import records** -3. Upload your CSV file -4. In the field mapping step: - * Find your relation column (e.g., `companyDomain`) - * Map it to the **Company** relation field -5. Complete the remaining mapping -6. Review errors and confirm +1. Alt nesneye gidin (ör. Kişiler) +2. **⋮** → **Kayıtları içe aktar**'ı tıklayın +3. CSV dosyanızı yükleyin +4. Alan eşleme adımında: + * İlişki sütununuzu bulun (ör. `companyDomain`) + * Bunu **Şirket** ilişki alanına eşleyin +5. Kalan eşlemeleri tamamlayın +6. Hataları gözden geçirin ve onaylayın -Twenty will automatically link each child record to the matching parent. +Twenty, her alt kaydı otomatik olarak eşleşen ana kayda bağlar. -## Step 7: Verify the Import +## Adım 7: İçe Aktarmayı Doğrulayın -After importing: +İçe aktardıktan sonra: -1. Open a few child records (e.g., People) -2. Verify the relation field shows the correct parent (e.g., Company) -3. Open a parent record and check the related records section +1. Birkaç alt kaydı açın (ör. Kişiler) +2. İlişki alanının doğru ana kaydı gösterdiğini doğrulayın (ör. Şirket) +3. Bir ana kaydı açın ve ilişkili kayıtlar bölümünü kontrol edin -## Common Mistakes to Avoid +## Kaçınılması Gereken Yaygın Hatalar -| Mistake | Problem | Solution | -| -------------------------- | -------------------------------------------------- | ------------------------------------------------------- | -| **Wrong import order** | Importing People before Companies | Always import parents first, then children | -| **Wrong domain format** | Using `acme.com` instead of `https://acme.com` | Use full URL format with `https://` | -| **Multiple unique fields** | Mapping both `companyId` AND `companyDomain` | Map only ONE unique identifier | -| **Missing relation field** | The relation field doesn't exist in the data model | Create it in **Settings → Data Model** before importing | -| **Non-existent records** | The parent record doesn't exist in Twenty | Import parent records first, or check for typos | -| **Case mismatch** | `Acme.com` in file but `acme.com` in Twenty | Ensure exact case matching | +| Hata | Sorun | Çözüm | +| -------------------------------- | ---------------------------------------------- | ----------------------------------------------------------------- | +| **Yanlış içe aktarma sırası** | Şirketlerden önce Kişileri içe aktarmak | Her zaman önce ana kayıtları, sonra alt kayıtları içe aktarın | +| **Yanlış alan adı biçimi** | `https://acme.com` yerine `acme.com` kullanmak | `https://` ile tam URL biçimini kullanın | +| **Birden fazla benzersiz alan** | Hem `companyId` HEM DE `companyDomain` eşlemek | Yalnızca TEK bir benzersiz tanımlayıcıyı eşleyin | +| **İlişki alanı eksik** | İlişki alanı veri modelinde yok | İçe aktarmadan önce **Ayarlar → Veri Modeli** içinde oluşturun | +| **Mevcut olmayan kayıtlar** | Ana kayıt Twenty'de mevcut değil | Önce ana kayıtları içe aktarın veya yazım hatalarını kontrol edin | +| **Büyük/küçük harf uyumsuzluğu** | Dosyada `Acme.com`, Twenty'de ise `acme.com` | Bire bir büyük/küçük harf eşleşmesini sağlayın | -## Linking to Workspace Members +## İş Alanı Üyelerine Bağlama -When linking to Workspace Members (your team): +İş Alanı Üyelerine (ekibiniz) bağlarken: -* Use their **email address**, not their name -* Example: `owner@yourcompany.com`, not "John Smith" +* Adları yerine **e-posta adreslerini** kullanın +* Örnek: `owner@yourcompany.com`, "John Smith" değil ```csv taskName,assignedTo @@ -173,56 +173,56 @@ Follow up with client,john@yourcompany.com Review proposal,jane@yourcompany.com ``` -## FAQ +## SSS - - You have two options: + + İki seçeneğiniz var: - 1. Use the Twenty `id` (export parent records to get their IDs) - 2. Create a custom unique field in your data model to store an external ID from your previous system + 1. Twenty `id` değerini kullanın (kimlikleri almak için ana kayıtları dışa aktarın) + 2. Önceki sisteminizden gelen harici bir kimliği saklamak için veri modelinizde özel bir benzersiz alan oluşturun - - Evet! Include the child record's unique identifier (e.g., `email` for People) and the new relation value. The import will update the relation. + + Evet! Alt kaydın benzersiz tanımlayıcısını (ör. Kişiler için `email`) ve yeni ilişki değerini ekleyin. İçe aktarma ilişkiyi günceller. - - Many-to-Many relations are not yet supported for import. This is planned for H1 2026. + + Çoktan-çoka ilişkiler henüz içe aktarmada desteklenmiyor. Bu, 2026'nın ilk yarısı için planlanıyor. - - Relations pointing to multiple object types are not yet supported for import/export. This is on our roadmap. + + Birden fazla nesne türüne işaret eden ilişkiler henüz içe/dışa aktarma için desteklenmiyor. Bu özellik yol haritamızda. - - The import will show an error for that row. Aşağıdakileri yapabilirsiniz: + + İçe aktarma, o satır için bir hata gösterir. Aşağıdakileri yapabilirsiniz: - * Import the parent record first, then re-import - * Fix the reference value - * Remove the row from import + * Önce ana kaydı içe aktarın, ardından yeniden içe aktarın + * Referans değerini düzeltin + * Satırı içe aktarmadan çıkarın - - Common causes: + + Yaygın nedenler: - * Wrong format (use `https://domain.com` for domains) - * Case mismatch (check exact spelling) - * Parent doesn't exist (import parents first) - * Mapping multiple identifiers (use only one) + * Yanlış biçim (alan adları için `https://domain.com` kullanın) + * Büyük/küçük harf uyumsuzluğu (yazımı tam olarak kontrol edin) + * Ana kayıt mevcut değil (önce ana kayıtları içe aktarın) + * Birden fazla tanımlayıcıyı eşleme (yalnızca birini kullanın) - **Remember: Soft-deleted records count toward uniqueness.** + **Unutmayın: Yumuşak silinmiş kayıtlar benzersizliğe dahildir.** - If you're getting "not found" errors but the record seems to exist, check Command Menu → See deleted records. The parent may have been soft-deleted. + "bulunamadı" hataları alıyorsanız ancak kayıt var gibi görünüyorsa, Komut Menüsü → Silinen kayıtları göster'i kontrol edin. Ana kayıt yumuşak silinmiş olabilir. ## Sorun Giderme -Having issues? Check: +Sorun mu yaşıyorsunuz? Şunları kontrol edin: -* [How to Fix Import Errors](/l/tr/user-guide/data-migration/how-tos/fix-import-errors) -* [Import Relations Capabilities](/l/tr/user-guide/data-migration/capabilities/import-relations) -* [Uniqueness Constraints](/l/tr/user-guide/data-migration/capabilities/uniqueness-constraints) +* [İçe Aktarma Hataları Nasıl Düzeltilir](/l/tr/user-guide/data-migration/how-tos/fix-import-errors) +* [İlişkileri İçe Aktarma Yetenekleri](/l/tr/user-guide/data-migration/capabilities/import-relations) +* [Benzersizlik Kısıtlamaları](/l/tr/user-guide/data-migration/capabilities/uniqueness-constraints) diff --git a/packages/twenty-docs/l/tr/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx b/packages/twenty-docs/l/tr/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx index f667a180d6..e49b68ab01 100644 --- a/packages/twenty-docs/l/tr/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx +++ b/packages/twenty-docs/l/tr/user-guide/data-migration/how-tos/migrating-from-self-hosted-to-cloud.mdx @@ -1,73 +1,73 @@ --- title: Kendi Barındırma'dan Bulut'a Geçiş -description: Step-by-step guide to migrate your Twenty self-hosted instance to Twenty Cloud. +description: Twenty kendi barındırmalı örneğinizi Twenty Cloud’a taşımak için adım adım kılavuz. --- ## Genel Bakış -This guide walks you through migrating your data from a Twenty self-hosted instance to Twenty Cloud. The process involves setting up your cloud workspace, exporting your data, and re-importing it. +Bu kılavuz, verilerinizi Twenty kendi barındırmalı örneğinizden Twenty Cloud’a taşıma sürecinde size adım adım yol gösterir. Süreç; bulut çalışma alanınızı kurmayı, verilerinizi dışa aktarmayı ve yeniden içe aktarmayı içerir. -Views, workflows, and roles must be recreated manually after migration. Plan time for this configuration work. +Görünümler, iş akışları ve roller geçişten sonra manuel olarak yeniden oluşturulmalıdır. Bu yapılandırma çalışması için zaman planlayın. -## Step 1: Create Your Cloud Workspace +## Adım 1: Bulut Çalışma Alanınızı Oluşturun -1. Go to [app.twenty.com](https://app.twenty.com) and create a new workspace -2. Complete the initial setup wizard -3. Note your new workspace URL +1. [app.twenty.com](https://app.twenty.com) adresine gidin ve yeni bir çalışma alanı oluşturun +2. İlk kurulum sihirbazını tamamlayın +3. Yeni çalışma alanı URL’nizi not edin -## Step 2: Recreate Your Data Model +## Adım 2: Veri Modelinizi Yeniden Oluşturun -Before importing data, recreate your custom objects and fields: +Verileri içe aktarmadan önce özel nesnelerinizi ve alanlarınızı yeniden oluşturun: -1. Go to **Settings → Data Model** in your cloud instance -2. Create custom objects that match your self-hosted setup -3. Add custom fields to standard and custom objects -4. Configure field settings (unique, required, etc.) +1. Bulut örneğinizde **Ayarlar → Veri Modeli**’ne gidin +2. Kendi barındırmalı kurulumunuzla eşleşen özel nesneler oluşturun +3. Standart ve özel nesnelere özel alanlar ekleyin +4. Alan ayarlarını yapılandırın (benzersiz, zorunlu vb.) -Take screenshots of your self-hosted data model for reference, or keep both instances open side by side. +Referans için kendi barındırmalı veri modelinizin ekran görüntülerini alın veya her iki örneği yan yana açık tutun. -## Step 3: Invite All Users +## Adım 3: Tüm Kullanıcıları Davet Edin - **Critical: Invite users BEFORE importing data.** + **Kritik: Kullanıcıları verileri içe aktarmadan ÖNCE davet edin.** - Users must accept their invitations before you import any records that reference them (like Account Owner fields). If users don't exist yet, those relations cannot be mapped. + Kullanıcılar, onları referans alan (ör. Hesap Sahibi alanları) herhangi bir kaydı içe aktarmadan önce davetlerini kabul etmelidir. Eğer kullanıcılar henüz mevcut değilse bu ilişkiler eşleştirilemez. -1. Go to **Settings → Members** in your cloud instance -2. Invite all team members who had accounts on self-hosted -3. **Wait for everyone to accept** their invitation -4. Verify all users appear in your Members list +1. Bulut örneğinizde **Ayarlar → Üyeler**’e gidin +2. Kendi barındırmalı sistemde hesabı olan tüm ekip üyelerini davet edin +3. **Herkesin daveti kabul etmesini bekleyin** +4. Tüm kullanıcıların Üyeler listenizde göründüğünü doğrulayın -## Step 4: Export Data from Self-Hosted +## Adım 4: Verileri Kendi Barındırmalı Sistemden Dışa Aktarın -Export each object from your self-hosted instance: +Kendi barındırmalı örneğinizden her bir nesneyi dışa aktarın: -1. Navigate to each object (Companies, People, Opportunities, etc.) -2. Configure the view to show **all columns** you want to migrate -3. Click **⋮ → Export view** -4. Save each CSV file with a clear name (e.g., `companies-export.csv`) +1. Her bir nesneye gidin (Şirketler, Kişiler, Fırsatlar vb.) +2. Görünümü, taşımak istediğiniz **tüm sütunları** gösterecek şekilde yapılandırın +3. **⋮ → Görünümü Dışa Aktar**’a tıklayın +4. Her CSV dosyasını anlaşılır bir adla kaydedin (ör. `companies-export.csv`) -**Export in this order** (for reference when importing): +**Bu sırayla dışa aktarın** (içe aktarım sırasında referans için): 1. Şirketler 2. İnsanlar 3. Fırsatlar -4. Custom objects (following their dependencies) -5. Tasks, Notes +4. Özel nesneler (bağımlılıklarına uyarak) +5. Görevler, Notlar -## Step 5: Update Workspace Member References +## Adım 5: Çalışma Alanı Üyesi Referanslarını Güncelleyin -The exported CSVs contain user IDs from your self-hosted instance. These IDs won't match your cloud instance, so you need to replace them with emails. +Dışa aktarılan CSV’ler, kendi barındırmalı örneğinizden kullanıcı kimliklerini (ID) içerir. Bu kimlikler bulut örneğinizle eşleşmeyeceğinden, bunları e-postalarla değiştirmeniz gerekir. -**For each CSV file with user references (Owner, Assignee, etc.):** +**Kullanıcı referansları (Sahip, Atanan vb.) içeren her CSV dosyası için:** -1. Open the CSV in a spreadsheet application -2. Add a new column next to each user ID column (e.g., `accountOwnerEmail` next to `accountOwnerId`) -3. Fill in the **email address** of each user -4. You can delete the old ID column or leave it (it will be skipped during import) +1. CSV’yi bir elektronik tablo uygulamasında açın +2. Her kullanıcı ID sütununun yanına yeni bir sütun ekleyin (ör. `accountOwnerId` yanına `accountOwnerEmail`) +3. Her kullanıcının **e-posta adresini** doldurun +4. Eski ID sütununu silebilir veya bırakabilirsiniz (içe aktarma sırasında atlanacaktır) -**Example:** +**Örnek:** Önce: @@ -83,89 +83,89 @@ name,domain,accountOwnerEmail Acme Corp,https://acme.com,john@yourcompany.com ``` -Use the same email addresses that users used to accept their cloud workspace invitation. +Kullanıcıların bulut çalışma alanı davetini kabul etmek için kullandıklarıyla aynı e-posta adreslerini kullanın. -## Step 6: Plan Your Import Order +## Adım 6: İçe Aktarma Sıralamanızı Planlayın -Import files in the correct order to maintain relationships: +İlişkileri korumak için dosyaları doğru sırayla içe aktarın: -1. **Companies** first (no dependencies) -2. **People** second (link to Companies) -3. **Opportunities** third (link to Companies and People) -4. **Custom objects** (following their dependencies) -5. **Tasks and Notes** last (link to other records) +1. Önce **Şirketler** (bağımlılık yok) +2. İkinci olarak **Kişiler** (Şirketlere bağlı) +3. Üçüncü olarak **Fırsatlar** (Şirketler ve Kişilere bağlı) +4. **Özel nesneler** (bağımlılıklarına uyarak) +5. Son olarak **Görevler ve Notlar** (diğer kayıtlara bağlı) -See [How to Import Relations](/l/tr/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv) for details on maintaining relationships. +İlişkileri korumaya ilişkin ayrıntılar için [İlişkileri Nasıl İçe Aktarırız](/l/tr/user-guide/data-migration/how-tos/import-relations-between-objects-via-csv) bölümüne bakın. -## Step 7: Import to Cloud +## Adım 7: Buluta İçe Aktarın -For each CSV file, in order: +Her CSV dosyası için, sırayla: -1. Navigate to the object in your cloud instance -2. Click **⋮ → Import records** -3. Upload the CSV file -4. Map columns to fields: - * Map user email columns to the appropriate relation fields - * Map other columns as usual -5. Review and fix any errors -6. Confirm the import -7. Verify a few records before proceeding to the next file +1. Bulut örneğinizde ilgili nesneye gidin +2. **⋮ → Kayıtları içe aktar**’ı tıklayın +3. CSV dosyasını yükleyin +4. Sütunları alanlarla eşleyin: + * Kullanıcı e-posta sütunlarını uygun ilişki alanlarına eşleyin + * Diğer sütunları her zamanki gibi eşleyin +5. Herhangi bir hatayı gözden geçirin ve düzeltin +6. İçe aktarmayı onaylayın +7. Sonraki dosyaya geçmeden önce birkaç kaydı doğrulayın -## Step 8: Recreate Configuration +## Adım 8: Yapılandırmayı Yeniden Oluşturun -After importing data, manually recreate: +Verileri içe aktardıktan sonra, aşağıdakileri manuel olarak yeniden oluşturun: ### Görünümler -* Recreate saved views with filters, sorts, and column configurations -* Set up any kanban or calendar views +* Kaydedilmiş görünümleri filtreler, sıralamalar ve sütun yapılandırmalarıyla yeniden oluşturun +* Herhangi bir kanban veya takvim görünümünü ayarlayın ### İş Akışları -* Recreate automations in **Settings → Workflows** -* Test each workflow before relying on it +* **Ayarlar → İş Akışları** içinde otomasyonları yeniden oluşturun +* Her iş akışını kullanmadan önce test edin -### Roles and Permissions +### Roller ve İzinler -* Configure roles in **Settings → Roles** -* Assign users to appropriate roles +* Rolleri **Ayarlar → Roller** bölümünde yapılandırın +* Kullanıcıları uygun rollere atayın ### Entegrasyonlar -* Reconnect email and calendar sync for each user -* Reconfigure any API integrations with new API keys +* Her kullanıcı için e-posta ve takvim eşzamanlamasını yeniden bağlayın +* Herhangi bir API entegrasyonunu yeni API anahtarlarıyla yeniden yapılandırın ## Taşındıktan Sonra Kontrol Listesi -All data imported successfully -Relations between objects working correctly -User assignments (Owner, Assignee) mapped correctly -Views recreated -Workflows recreated and tested -Roles and permissions configured -Email/calendar sync reconnected -API integrations updated with new keys +Tüm veriler başarıyla içe aktarıldı +Nesneler arasındaki ilişkiler doğru çalışıyor +Kullanıcı atamaları (Sahip, Atanan) doğru şekilde eşlendi +Görünümler yeniden oluşturuldu +İş akışları yeniden oluşturuldu ve test edildi +Roller ve izinler yapılandırıldı +E-posta/takvim eşzamanlaması yeniden bağlandı +API entegrasyonları yeni anahtarlarla güncellendi -## FAQ +## SSS - - Not currently. Workflows must be recreated manually in your cloud instance. + + Şu anda mümkün değil. İş akışları bulut örneğinizde manuel olarak yeniden oluşturulmalıdır. - - File attachments are not included in CSV exports. You'll need to re-upload any attachments manually, migrate them via API or contact our team for assistance with large migrations. + + Dosya ekleri CSV dışa aktarmalarına dahil edilmez. Herhangi bir eki manuel olarak yeniden yüklemeniz, API aracılığıyla taşımanız ya da büyük geçişlerde yardım için ekibimizle iletişime geçmeniz gerekecek. - - Yes, we recommend keeping your self-hosted instance running until you've verified the cloud migration is complete. Just be careful not to create new data in both places. + + Evet, buluta geçişin tamamlandığını doğrulayana kadar kendi barındırmalı örneğinizi çalışır durumda tutmanızı öneririz. Sadece her iki yerde de yeni veriler oluşturmamaya dikkat edin. - - Records referencing that user will fail to import or the relation will be empty. Ensure all users accept invitations before importing data. + + O kullanıcıya referans veren kayıtların içe aktarımı başarısız olur veya ilişki boş kalır. Verileri içe aktarmadan önce tüm kullanıcıların davetleri kabul ettiğinden emin olun. ## Yardıma mı ihtiyacınız var? -For complex migrations or large datasets, contact us at [contact@twenty.com](mailto:contact@twenty.com) or explore our [Implementation Services](/l/tr/user-guide/getting-started/capabilities/implementation-services). +Karmaşık geçişler veya büyük veri kümeleri için [contact@twenty.com](mailto:contact@twenty.com) adresinden bize ulaşın veya [Uygulama Hizmetlerimizi](/l/tr/user-guide/getting-started/capabilities/implementation-services) inceleyin. diff --git a/packages/twenty-docs/l/tr/user-guide/introduction.mdx b/packages/twenty-docs/l/tr/user-guide/introduction.mdx index f4b8e222d1..57ba26aed0 100644 --- a/packages/twenty-docs/l/tr/user-guide/introduction.mdx +++ b/packages/twenty-docs/l/tr/user-guide/introduction.mdx @@ -1,63 +1,63 @@ --- -title: Discover Twenty -description: Welcome to Twenty User Guide, your resources for advanced configurations and best practices. +title: Twenty'yi Keşfedin +description: Twenty Kullanıcı Kılavuzu'na hoş geldiniz; gelişmiş yapılandırmalar ve en iyi uygulamalar için başvuru kaynağınız. --- import { CardTitle } from "/snippets/card-title.mdx" - Discover Twenty - Learn what Twenty is and how it can help your business. + Twenty'yi Keşfedin + Twenty'nin ne olduğunu ve işletmenize nasıl yardımcı olabileceğini öğrenin. - Data Model - Customize your data model to fit your business processes. + Veri Modeli + Veri modelinizi iş süreçlerinize uyacak şekilde özelleştirin. - Data Migration - Import and export your data via CSV or API. + Veri Geçişi + Verilerinizi CSV veya API aracılığıyla içe ve dışa aktarın. - Calendar & Emails - Centralize your team's meetings and emails. + Takvim ve E-postalar + Ekibinizin toplantılarını ve e-postalarını merkezileştirin. - Workflows - Automate processes and integrate with external tools. + İş Akışları + Süreçleri otomatikleştirin ve harici araçlarla entegre edin. - AI - Enhance your team with AI agents. + Yapay Zekâ + Yapay zekâ ajanlarıyla ekibinizi güçlendirin. - Views & Pipelines - Organize your data with actionable views and pipelines. + Görünümler ve Boru Hatları + Eyleme dönüştürülebilir görünümler ve boru hatlarıyla verilerinizi düzenleyin. - Dashboards - Real-time insights to track performance. + Panolar + Performansı izlemek için gerçek zamanlı içgörüler. - Permissions & Access - Manage roles and access to Twenty. + İzinler ve Erişim + Rolleri ve Twenty'ye erişimi yönetin. - Billing - Understand how Twenty pricing and billing works. + Faturalandırma + Twenty'nin fiyatlandırmasının ve faturalandırmasının nasıl çalıştığını anlayın. - Settings - Configure your workspace preferences. + Ayarlar + Çalışma alanı tercihlerinizi yapılandırın. diff --git a/packages/twenty-docs/l/tr/user-guide/settings/how-tos/settings-faq.mdx b/packages/twenty-docs/l/tr/user-guide/settings/how-tos/settings-faq.mdx index 3749868f8c..eebf9c479a 100644 --- a/packages/twenty-docs/l/tr/user-guide/settings/how-tos/settings-faq.mdx +++ b/packages/twenty-docs/l/tr/user-guide/settings/how-tos/settings-faq.mdx @@ -1,136 +1,136 @@ --- title: Ayarlar SSS -description: Frequently asked questions about Twenty settings. +description: Twenty ayarları hakkında sıkça sorulan sorular. image: /images/user-guide/setup/settings.png --- ## Çalışma Alanı Ayarları - - 1. Go to **Settings → General** - 2. Find the Workspace Name field - 3. Enter your new name - 4. Changes save automatically + + 1. **Ayarlar → Genel** bölümüne gidin + 2. Çalışma Alanı Adı alanını bulun + 3. Yeni adınızı girin + 4. Değişiklikler otomatik olarak kaydedilir - - 1. Go to **Settings → General** - 2. Click on the current logo or upload area - 3. Select an image file (PNG, JPEG, or GIF under 10MB) - 4. The logo updates immediately + + 1. **Ayarlar → Genel** bölümüne gidin + 2. Mevcut logoya veya yükleme alanına tıklayın + 3. Bir görsel dosyası seçin (10 MB'den küçük PNG, JPEG veya GIF) + 4. Logo anında güncellenir - - Yes, you can create and be a member of multiple workspaces. Each workspace has its own data, settings, and subscription. + + Evet, birden fazla çalışma alanı oluşturabilir ve üyesi olabilirsiniz. Her çalışma alanının kendi verileri, ayarları ve aboneliği vardır. - - 1. Go to **Settings → General** - 2. Scroll to Danger Zone - 3. Click **Delete workspace** - 4. Confirm the deletion + + 1. **Ayarlar → Genel** bölümüne gidin + 2. Tehlike Bölgesi'ne kadar kaydırın + 3. **Çalışma alanını sil** düğmesine tıklayın + 4. Silmeyi onaylayın - Note: This permanently deletes all data and cannot be undone. + Not: Bu işlem tüm verileri kalıcı olarak siler ve geri alınamaz. - - Delete the workspaces you no longer need under **Settings → General → Delete workspace**. + + Artık ihtiyaç duymadığınız çalışma alanlarını **Ayarlar → Genel → Çalışma alanını sil** altında silin. - Do not delete your **account** (accessible under Settings → Profile): your account is shared among all your workspaces. Deleting your account removes access to ALL workspaces. + **Hesabınızı** silmeyin (Ayarlar → Profil altından erişilebilir): hesabınız tüm çalışma alanlarınız arasında paylaşılır. Hesabınızı silmek TÜM çalışma alanlarına erişiminizi kaldırır. - - If you want to temporarily disable your workspace (not permanently delete it), go to **Settings → Billing** and click **Cancel Plan**. Your data will be preserved for a grace period. + + Çalışma alanınızı geçici olarak devre dışı bırakmak istiyorsanız (kalıcı olarak silmek değil), **Ayarlar → Faturalandırma**'ya gidin ve **Planı İptal Et**'e tıklayın. Verileriniz bir ek süre boyunca korunacaktır. ## Profil Ayarları - - 1. Go to **Settings → Profile** - 2. Find the Password section - 3. Enter your current password - 4. Enter your new password - 5. Save changes + + 1. **Ayarlar → Profil** bölümüne gidin + 2. Şifre bölümünü bulun + 3. Mevcut şifrenizi girin + 4. Yeni şifrenizi girin + 5. Değişiklikleri kaydedin - - 1. Go to **Settings → Profile** - 2. Find the 2FA section + + 1. **Ayarlar → Profil** bölümüne gidin + 2. 2FA bölümünü bulun 3. **2FA Etkinleştir**'e tıklayın 4. QR kodunu yetkilendirme uygulamanızla tarayın - 5. Enter the verification code + 5. Doğrulama kodunu girin - - To change your email address, please reach out to [contact@twenty.com](mailto:contact@twenty.com). + + E-posta adresinizi değiştirmek için lütfen [contact@twenty.com](mailto:contact@twenty.com) ile iletişime geçin. - - 1. Go to **Settings → Profile** - 2. Scroll to Danger Zone + + 1. **Ayarlar → Profil** bölümüne gidin + 2. Tehlike Bölgesi'ne kadar kaydırın 3. **Hesabı Sil**'e tıklayın - 4. Confirm by typing your email + 4. E-posta adresinizi yazarak onaylayın - Note: This removes your access to all workspaces and deletes all emails synced from your connected accounts. + Not: Bu, tüm çalışma alanlarına erişiminizi kaldırır ve bağlı hesaplarınızdan eşitlenmiş tüm e-postaları siler. ## Deneyim Ayarları - - 1. Go to **Settings → Experience** - 2. Find the Theme section - 3. Select Light, Dark, or System + + 1. **Ayarlar → Deneyim** bölümüne gidin + 2. Tema bölümünü bulun + 3. Açık, Koyu veya Sistem'i seçin - - 1. Go to **Settings → Experience** - 2. Find Date Format - 3. Select your preferred format - 4. Changes apply immediately + + 1. **Ayarlar → Deneyim** bölümüne gidin + 2. Tarih Biçimi'ni bulun + 3. Tercih ettiğiniz biçimi seçin + 4. Değişiklikler anında uygulanır - - 1. Go to **Settings → Experience** - 2. Find Time Zone - 3. Select your local time zone - 4. All timestamps will adjust + + 1. **Ayarlar → Deneyim** bölümüne gidin + 2. Saat Dilimi'ni bulun + 3. Yerel saat diliminizi seçin + 4. Tüm zaman damgaları ayarlanır - - 1. Go to **Settings → Experience** - 2. Find Language - 3. Select from available languages - 4. The interface updates to your selection + + 1. **Ayarlar → Deneyim** bölümüne gidin + 2. Dil'i bulun + 3. Mevcut diller arasından seçin + 4. Arayüz seçiminize göre güncellenir -## Account Settings +## Hesap Ayarları - + 1. **Ayarlar → Hesaplar** sekmesine gidin. 2. **Hesap ekle** butonuna tıklayın. - 3. Choose Google or Microsoft - 4. Authorize access - 5. Configure sync settings + 3. Google veya Microsoft'u seçin + 4. Erişimi yetkilendirin + 5. Senkronizasyon ayarlarını yapılandırın - - Yes, you can connect multiple email accounts. Go to **Settings → Accounts** and add additional accounts as needed. + + Evet, birden fazla e-posta hesabını bağlayabilirsiniz. **Ayarlar → Hesaplar**'a gidin ve gerektiğinde ek hesaplar ekleyin. - + 1. **Ayarlar → Hesaplar** sekmesine gidin. - 2. Find the account to remove - 3. Click **Disconnect** - 4. Confirm the action + 2. Kaldırmak istediğiniz hesabı bulun + 3. **Bağlantıyı Kes**'e tıklayın + 4. İşlemi onaylayın @@ -138,16 +138,16 @@ image: /images/user-guide/setup/settings.png - Evet! Go to **Settings → Domains** and click **Customize Domain**. You have two options: + Evet! **Ayarlar → Alanlar**'a gidin ve **Alan Adını Özelleştir**'e tıklayın. İki seçeneğiniz var: - * **Subdomain**: Use a Twenty subdomain like `yourcompany.twenty.com` - * **Custom domain**: Use your own domain like `crm.yourcompany.com` (requires DNS configuration) + * **Alt alan adı**: `yourcompany.twenty.com` gibi bir Twenty alt alan adı kullanın + * **Özel alan adı**: `crm.yourcompany.com` gibi kendi alan adınızı kullanın (DNS yapılandırması gerektirir) - A subdomain is quick to set up, while a custom domain provides a fully branded experience for your team. + Alt alan adı kurmak hızlıdır; özel alan adı ise ekibiniz için tam markalı bir deneyim sağlar. - - You can configure approved access domains so team members with company email addresses can automatically join your workspace. Go to **Settings → Domains** and add your company domain (e.g., `yourcompany.com`). + + Şirket e-posta adreslerine sahip ekip üyelerinin çalışma alanınıza otomatik olarak katılabilmeleri için onaylı erişim alan adlarını yapılandırabilirsiniz. **Ayarlar → Alanlar**'a gidin ve şirket alan adınızı ekleyin (ör. `yourcompany.com`). @@ -164,8 +164,8 @@ image: /images/user-guide/setup/settings.png 1. Go to **Settings → Updates → Early Access** - 2. Find the feature you want - 3. Toggle it on - 4. The feature becomes available immediately + 2. İstediğiniz özelliği bulun + 3. Açık konuma getirin + 4. Özellik hemen kullanılabilir hale gelir diff --git a/packages/twenty-docs/l/tr/user-guide/settings/overview.mdx b/packages/twenty-docs/l/tr/user-guide/settings/overview.mdx index 6624eb1274..5a77dac0b0 100644 --- a/packages/twenty-docs/l/tr/user-guide/settings/overview.mdx +++ b/packages/twenty-docs/l/tr/user-guide/settings/overview.mdx @@ -1,6 +1,6 @@ --- title: Ayarlar -description: Set up your Twenty workspace with essential configurations. +description: Twenty çalışma alanınızı temel yapılandırmalarla kurun. image: /images/user-guide/setup/settings.png --- @@ -8,60 +8,60 @@ image: /images/user-guide/setup/settings.png Ayarlar -## Initial Setup +## İlk Kurulum -When you first create your workspace, there are several key settings to configure. +Çalışma alanınızı ilk oluşturduğunuzda yapılandırmanız gereken birkaç temel ayar vardır. -### Workspace Name and Logo +### Çalışma Alanı Adı ve Logo -1. Go to **Settings → General** -2. Update your workspace name -3. Upload your company logo -4. Save your changes +1. **Ayarlar → Genel** bölümüne gidin +2. Çalışma alanınızın adını güncelleyin +3. Şirket logonuzu yükleyin +4. Değişikliklerinizi kaydedin -### Time Zone and Date Format +### Saat Dilimi ve Tarih Biçimi -1. Go to **Settings → Experience** -2. Select your time zone -3. Choose your preferred date format -4. Save your changes +1. **Ayarlar → Deneyim** bölümüne gidin +2. Saat diliminizi seçin +3. Tercih ettiğiniz tarih biçimini seçin +4. Değişikliklerinizi kaydedin -## Essential Configurations +## Temel Yapılandırmalar -### Connect Email and Calendar +### E-posta ve Takvimi Bağlayın -Set up email and calendar sync: +E-posta ve takvim senkronizasyonunu ayarlayın: 1. **Ayarlar → Hesaplar** sekmesine gidin. 2. **Hesap ekle** butonuna tıklayın. -3. Connect your Google or Microsoft account -4. Configure sync settings +3. Google veya Microsoft hesabınızı bağlayın +4. Senkronizasyon ayarlarını yapılandırın -→ [Complete email & calendar setup guide](/l/tr/user-guide/calendar-emails/overview) +→ [Tam e-posta ve takvim kurulum kılavuzu](/l/tr/user-guide/calendar-emails/overview) -### Invite Your Team +### Ekibinizi Davet Edin -Add team members to your workspace: +Çalışma alanınıza ekip üyeleri ekleyin: 1. **Ayarlar → Üyeler** bölümüne gidin -2. Click **+ Invite** -3. Enter email addresses -4. Assign appropriate roles +2. **+ Davet Et**'e tıklayın +3. E-posta adreslerini girin +4. Uygun rolleri atayın - Before inviting your team, check the default role under **Settings → Roles**. New members are automatically assigned this role when they join. + Ekibinizi davet etmeden önce, **Ayarlar → Roller** altında varsayılan rolü kontrol edin. Yeni üyeler katıldıklarında otomatik olarak bu role atanır. -## Workspace Settings Checklist +## Çalışma Alanı Ayarları Kontrol Listesi -* Workspace name and logo configured -* Time zone and date format set -* Email and calendar connected -* Team members invited -* Roles and permissions configured +* Çalışma alanı adı ve logosu yapılandırıldı +* Saat dilimi ve tarih biçimi ayarlandı +* E-posta ve takvim bağlandı +* Ekip üyeleri davet edildi +* Roller ve izinler yapılandırıldı ## Sonraki Adımlar -* [Workspace settings](/l/tr/user-guide/settings/capabilities/workspace-settings) -* [Profile settings](/l/tr/user-guide/settings/capabilities/profile-settings) -* [Experience settings](/l/tr/user-guide/settings/capabilities/experience-settings) +* [Çalışma alanı ayarları](/l/tr/user-guide/settings/capabilities/workspace-settings) +* [Profil ayarları](/l/tr/user-guide/settings/capabilities/profile-settings) +* [Deneyim ayarları](/l/tr/user-guide/settings/capabilities/experience-settings) diff --git a/packages/twenty-docs/l/tr/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx b/packages/twenty-docs/l/tr/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx index 66f4182a88..ef0d967fe9 100644 --- a/packages/twenty-docs/l/tr/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx +++ b/packages/twenty-docs/l/tr/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline.mdx @@ -1,120 +1,120 @@ --- -title: Set Up a Sales Pipeline -description: Configure your sales pipeline to track opportunities through stages. +title: Bir Satış Boru Hattı Kurun +description: Fırsatları aşamalar boyunca izlemek için satış boru hattınızı yapılandırın --- import { VimeoEmbed } from '/snippets/vimeo-embed.mdx'; -A sales pipeline in Twenty is a Kanban view of your Opportunities object, where each column represents a stage in your sales process. +Twenty'deki satış boru hattı, her sütunun satış sürecinizdeki bir aşamayı temsil ettiği Fırsatlar nesnenizin bir Kanban görünümüdür. -## Step 1: Configure Your Stages +## Adım 1: Aşamalarınızı yapılandırın -Stages are defined in the Opportunities object's **Stage** field. +Aşamalar, Fırsatlar nesnesinin **Aşama** alanında tanımlanır. -1. Go to **Settings → Data Model** -2. Select **Opportunities** -3. Find and click the **Stage** field -4. Add, remove, or rename stages to match your process +1. **Ayarlar → Veri Modeli** bölümüne gidin +2. **Fırsatlar**'ı seçin +3. **Aşama** alanını bulun ve tıklayın +4. Sürecinize uyması için aşama ekleyin, kaldırın veya yeniden adlandırın - + -### Recommended Stages +### Önerilen Aşamalar -| Aşama | Purpose | -| --------------- | ----------------------------------- | -| **New** | Fresh opportunities just identified | -| **Qualified** | Confirmed as a good fit | -| **Meeting** | Engaged in discussions | -| **Proposal** | Proposal sent | -| **Negotiation** | Working on terms | -| **Closed Won** | Deal successful | -| **Closed Lost** | Deal unsuccessful | +| Aşama | Amaç | +| -------------- | ----------------------------- | +| **Yeni** | Yeni belirlenen fırsatlar | +| **Nitelikli** | Uygun olduğu doğrulandı | +| **Toplantı** | Görüşmeler yapılıyor | +| **Teklif** | Teklif gönderildi | +| **Müzakere** | Koşullar üzerinde çalışılıyor | +| **Kazanıldı** | Anlaşma başarıyla sonuçlandı | +| **Kaybedildi** | Anlaşma olumsuz sonuçlandı | - **5-7 stages is optimal.** Too many stages makes the pipeline hard to scan; too few loses visibility into deal progress. + **5-7 aşama idealdir.** Çok fazla aşama, boru hattının hızlı taranmasını zorlaştırır; çok az aşama ise anlaşma ilerleyişine ilişkin görünürlüğü azaltır. -## Step 2: Create a Pipeline View +## Adım 2: Boru Hattı Görünümü oluşturun -1. Go to **Opportunities** -2. Click the view dropdown → **+ Add view** -3. Name it "Sales Pipeline" -4. Click **Create** -5. Open **Options** and select **Kanban** as the layout +1. **Fırsatlar**'a gidin +2. Görünüm açılır menüsüne tıklayın → **+ Görünüm ekle** +3. Adını "Satış Boru Hattı" koyun +4. **Oluştur**'a tıklayın +5. **Seçenekler**'i açın ve düzen olarak **Kanban**'ı seçin -The view automatically uses the Stage field for columns. +Görünüm, sütunlar için otomatik olarak Aşama alanını kullanır. -## Step 3: Configure Your View +## Adım 3: Görünümünüzü yapılandırın -### Show Key Fields +### Önemli Alanları Göster -1. Click **Options → Fields** -2. Look for fields in the "Hidden Fields" section -3. Click the **eye icon** to display: Company, Amount, Close Date, Owner +1. **Seçenekler → Alanlar**'a tıklayın +2. "Gizli Alanlar" bölümünde alanlara bakın +3. Görüntülemek için **göz simgesine** tıklayın: Şirket, Tutar, Kapanış Tarihi, Sahip -### Enable Aggregations +### Toplamaları Etkinleştir -Show totals at the top of each column: +Her sütunun üstünde toplamları gösterin: -1. Click the number displayed next to a Stage name at the top of a column -2. Select the aggregation type (Count, Sum, Average, etc.) -3. Choose the field to aggregate (e.g., Amount) +1. Bir sütunun üst kısmında bir Aşama adının yanında gösterilen sayıya tıklayın +2. Toplama türünü seçin (Adet, Toplam, Ortalama vb.) +3. Toplanacak alanı seçin (ör. Tutar) -**Example:** Show total deal value per stage by aggregating Amount with Sum. +**Örnek:** Tutar'ı Toplam ile toplayarak aşama başına toplam anlaşma değerini gösterin. -### Use Compact View (Optional) +### Kompakt Görünümü Kullanın (İsteğe bağlı) -For a high-level overview with minimal card content: +Kart içeriğini en aza indirerek genel bir görünüm için: -1. Click **Options** -2. Turn on the toggle for **Compact view** +1. **Seçenekler**'e tıklayın +2. **Kompakt görünüm** için anahtarı açın -## Step 4: Create Personal and Team Views +## Adım 4: Kişisel ve Ekip Görünümleri oluşturun -### "My Pipeline" +### "Boru Hattım" -* **Filter**: Owner = Me -* **Visibility**: Unlisted (personal view) +* **Filtre**: Sahip = Ben +* **Görünürlük**: Liste dışı (kişisel görünüm) -### "Team Pipeline" +### "Ekip Boru Hattı" -* **Filter**: None (show all) -* **Visibility**: Workspace (shared view) +* **Filtre**: Yok (tümünü göster) +* **Görünürlük**: Çalışma alanı (paylaşılan görünüm) -### "Closing This Month" +### "Bu Ay Kapanacaklar" -* **Type**: Table -* **Filter**: Close Date = This month, Stage ≠ Closed Won, Stage ≠ Closed Lost -* **Sort**: Close Date ascending +* **Tür**: Tablo +* **Filtre**: Kapanış Tarihi = Bu ay, Aşama ≠ Kazanıldı, Aşama ≠ Kaybedildi +* **Sırala**: Kapanış Tarihi artan -## Working with Opportunities +## Fırsatlarla Çalışma -### Creating Opportunities +### Fırsat Oluşturma -* Click **+ New** in the Opportunities view -* Or click **+** in a specific stage column +* Fırsatlar görünümünde **+ Yeni**'ye tıklayın +* Ya da belirli bir aşama sütununda **+**'a tıklayın -### Moving Through Stages +### Aşamalar Arasında İlerleme -Drag and drop opportunity cards between columns to update their stage. +Aşamalarını güncellemek için fırsat kartlarını sütunlar arasında sürükleyip bırakın. - + ## En İyi Uygulamalar -### Pipeline Hygiene +### Boru Hattı Hijyeni -* Update deals daily as they progress -* Move or close stale deals promptly -* Keep close dates realistic +* Anlaşmaları ilerledikçe günlük olarak güncelleyin +* Durağan anlaşmaları hızlıca taşıyın veya kapatın +* Kapanış tarihlerini gerçekçi tutun -### Stage Discipline +### Aşama Disiplini -* Define clear criteria for each stage -* Move deals promptly when criteria are met -* Don't let deals sit in stages too long +* Her aşama için net kriterler tanımlayın +* Kriterler karşılandığında anlaşmaları hızla taşıyın +* Anlaşmaların aşamalarda çok uzun süre beklemesine izin vermeyin -## Related +## İlgili -* [Kanban Views](/l/tr/user-guide/views-pipelines/capabilities/kanban-views) — aggregations and compact view -* [Filters and Sorting](/l/tr/user-guide/views-pipelines/capabilities/filters-and-sorting) — creating filtered views +* [Kanban Görünümleri](/l/tr/user-guide/views-pipelines/capabilities/kanban-views) — toplamalar ve kompakt görünüm +* [Filtreler ve Sıralama](/l/tr/user-guide/views-pipelines/capabilities/filters-and-sorting) — filtrelenmiş görünümler oluşturma diff --git a/packages/twenty-docs/l/tr/user-guide/workflows/capabilities/use-branches-in-workflows.mdx b/packages/twenty-docs/l/tr/user-guide/workflows/capabilities/use-branches-in-workflows.mdx index 993c3e3d54..63c2cedd4f 100644 --- a/packages/twenty-docs/l/tr/user-guide/workflows/capabilities/use-branches-in-workflows.mdx +++ b/packages/twenty-docs/l/tr/user-guide/workflows/capabilities/use-branches-in-workflows.mdx @@ -1,90 +1,90 @@ --- -title: Use Branches in Workflows -description: Understand how branches work and how to control which path is executed. +title: İş Akışlarında Dalları Kullanın +description: Dalların nasıl çalıştığını ve hangi yolun çalıştırılacağını nasıl kontrol edeceğinizi anlayın. --- -## How Branches Work +## Dallar Nasıl Çalışır -In the workflow editor, you can create multiple paths (branches) going out from a single node. This allows you to build complex automations with different outcomes. +İş akışı düzenleyicisinde, tek bir düğümden çıkan birden çok yol (dallar) oluşturabilirsiniz. Bu, farklı sonuçlara sahip karmaşık otomasyonlar oluşturmanıza olanak tanır. -**Important**: When a workflow runs, **all branches execute in parallel by default**. There is no built-in "if/else" logic to choose one branch over another—every path will run simultaneously. +**Önemli**: Bir iş akışı çalıştığında, **varsayılan olarak tüm dallar paralel olarak yürütülür**. Bir dalı diğerine tercih etmek için yerleşik bir "if/else" mantığı yoktur—her yol eşzamanlı olarak çalışır. -## Controlling Which Branch Runs +## Hangi Dalın Çalıştırılacağını Kontrol Etme -To execute only one branch based on specific conditions, **add a Filter node at the beginning of each branch**. +Belirli koşullara göre yalnızca bir dalı çalıştırmak için, **her dalın başına bir Filter düğümü ekleyin**. -### Example Setup +### Örnek Kurulum -1. Create your workflow with multiple branches from a single node -2. Add a **Filter** node as the first step in each branch -3. Set conditions on each Filter to determine when that branch should continue -4. Only the branch(es) whose Filter conditions are met will proceed +1. İş akışınızı, tek bir düğümden birden çok dal çıkaracak şekilde oluşturun +2. Her dalda ilk adım olarak bir **Filter** düğümü ekleyin +3. Her Filter üzerinde, o dalın ne zaman devam etmesi gerektiğini belirlemek için koşullar ayarlayın +4. Yalnızca Filter koşulları sağlanan dal(lar) devam edecektir -### How Filters Work +### Filter'lar Nasıl Çalışır -* If the Filter condition is **met**: The branch continues executing -* If the Filter condition is **not met**: The branch stops at the Filter node +* Filter koşulu **sağlanırsa**: Dal çalışmaya devam eder +* Filter koşulu **sağlanmazsa**: Dal, Filter düğümünde durur -This effectively creates conditional logic where only the appropriate branch runs based on your data. +Bu, verilerinize bağlı olarak yalnızca uygun dalın çalıştığı bir koşullu mantık oluşturur. -## Example: Route by Deal Size +## Örnek: Anlaşma Büyüklüğüne Göre Yönlendirme -**Scenario**: When a deal is closed, send different notifications based on deal size. +**Senaryo**: Bir anlaşma kapandığında, anlaşma büyüklüğüne göre farklı bildirimler gönderin. -1. **Trigger**: Opportunity updated (Stage = Closed Won) -2. **Branch 1**: Filter for Amount > $10,000 → Send Slack message to #big-deals -3. **Branch 2**: Filter for Amount ≤ $10,000 → Send email to sales manager +1. **Tetikleyici**: Fırsat güncellendi (Aşama = Closed Won) +2. **Dal 1**: Miktar > $10.000 için Filter → #big-deals kanalına Slack mesajı gönderin +3. **Dal 2**: Miktar ≤ $10.000 için Filter → satış müdürüne e-posta gönderin -Both branches start, but only the one matching the deal amount will continue past its Filter. +Her iki dal da başlar, ancak yalnızca anlaşma tutarıyla eşleşen dal, Filter'ını geçerek devam eder. -## Creating Branches +## Dallar Oluşturma - To create a new branch from an existing step, click the **+** button on the step and add your action. You can add multiple branches by clicking **+** multiple times. + Mevcut bir adımdan yeni bir dal oluşturmak için, adım üzerindeki **+** düğmesine tıklayın ve eyleminizi ekleyin. **+**'ı birden çok kez tıklayarak birden fazla dal ekleyebilirsiniz. -1. In the workflow editor, select the step you want to branch from -2. Click the **+** button to add an action -3. This creates one branch -4. Click **+** again on the same step to create additional branches -5. Each branch can have its own sequence of actions +1. İş akışı düzenleyicisinde, dallandırmak istediğiniz adımı seçin +2. Bir eylem eklemek için **+** düğmesine tıklayın +3. Bu, bir dal oluşturur +4. Ek dallar oluşturmak için aynı adımda **+** düğmesine tekrar tıklayın +5. Her dalın kendi eylem dizisi olabilir -## Merging Branches Back Together +## Dalları Yeniden Birleştirme -After parallel branches complete their work, you can merge them back into a single path: +Paralel dallar işlerini tamamladıktan sonra, onları yeniden tek bir yolda birleştirebilirsiniz: -1. Complete your branched actions -2. Add a new step that should run after all branches -3. Drag a connection from the last step of each branch to this new step -4. The merged step waits for all connected branches to complete before executing +1. Dallanmış eylemlerinizi tamamlayın +2. Tüm dallardan sonra çalışması gereken yeni bir adım ekleyin +3. Her dalın son adımından bu yeni adıma bir bağlantı sürükleyin +4. Birleştirilen adım, çalıştırılmadan önce bağlı tüm dalların tamamlanmasını bekler -### Example: Process Then Notify +### Örnek: Önce İşle Sonra Bildir ``` Trigger │ - ├── Branch A: Update Customer Record + ├── Dal A: Müşteri Kaydını Güncelle │ - └── Branch B: Create Support Ticket + └── Dal B: Destek Talebi Oluştur ↘ ↙ - Merged Step: Send Confirmation Email + Birleştirilen Adım: Onay E-postası Gönder ``` -The confirmation email sends only after both the customer update and ticket creation are done. +Onay e-postası, hem müşteri güncellemesi hem de talep oluşturma tamamlandıktan sonra gönderilir. ## En İyi Uygulamalar -* Always use **Filter nodes** at the start of branches when you want conditional execution -* Keep branch conditions **mutually exclusive** to avoid duplicate actions -* Test your workflows with different data to ensure the correct branches run -* **Rename branch steps** descriptively so it's clear what each path does -* **Merge branches** when you need a final action after parallel processing +* Koşullu yürütme istediğiniz durumlarda dalların başlangıcında her zaman **Filter düğümlerini** kullanın +* Yinelenen eylemleri önlemek için dal koşullarını **birbirini dışlayıcı** tutun +* Doğru dalların çalıştığından emin olmak için iş akışlarınızı farklı verilerle test edin +* Her yolun ne yaptığının açık olması için dal adımlarını açıklayıcı şekilde **yeniden adlandırın** +* Paralel işlemden sonra son bir eyleme ihtiyaç duyduğunuzda **dalları birleştirin** -## Related +## İlgili -* [Workflows FAQ](/l/tr/user-guide/workflows/how-tos/need-more-help/workflows-faq) — answers about parallel execution -* [Workflow Actions](/l/tr/user-guide/workflows/capabilities/workflow-actions) — available actions for branches +* [İş Akışları SSS](/l/tr/user-guide/workflows/how-tos/need-more-help/workflows-faq) — paralel yürütme hakkında yanıtlar +* [İş Akışı Eylemleri](/l/tr/user-guide/workflows/capabilities/workflow-actions) — dallar için kullanılabilir eylemler diff --git a/packages/twenty-docs/l/tr/user-guide/workflows/capabilities/workflow-actions.mdx b/packages/twenty-docs/l/tr/user-guide/workflows/capabilities/workflow-actions.mdx index 5b8de9a6e2..262f8c74ee 100644 --- a/packages/twenty-docs/l/tr/user-guide/workflows/capabilities/workflow-actions.mdx +++ b/packages/twenty-docs/l/tr/user-guide/workflows/capabilities/workflow-actions.mdx @@ -96,150 +96,150 @@ Eşleştirme ölçütlerine göre yeni bir kayıt oluşturur veya mevcut bir kay * Alanları doldurmak için önceki adımlardan gelen verileri kullanın -**How it works**: +**Nasıl Çalışır**: -1. Searches for a record matching your criteria -2. If found → updates the existing record -3. If not found → creates a new record +1. Kriterlerinize uyan bir kaydı arar +2. Bulunursa → mevcut kaydı günceller +3. Bulunamazsa → yeni bir kayıt oluşturur -**Output**: The created or updated record data is available for use in subsequent steps. +**Çıktı**: Oluşturulan veya güncellenen kayıt verileri, sonraki adımlarda kullanılmak üzere mevcuttur. -## Flow Actions +## Akış Eylemleri ### Yineleyici -**Loops through an array of records** returned from a previous step, allowing you to perform actions on each record individually. +**Önceki bir adımdan dönen kayıt dizisi üzerinde döngü oluşturur**, her kayıt üzerinde ayrı ayrı işlem yapmanıza olanak tanır. **Yapılandırma**: -* Select the array of records from a previous step (e.g., results from Search Records, from a Manual trigger with Bulk availability, from a code node) +* Önceki bir adımdan gelen kayıt dizisini seçin (ör. Kayıt Ara sonuçları, Toplu kullanılabilirliğe sahip bir Manuel tetikleyici, bir kod düğümü) * Döngüde her kayıt üzerinde gerçekleştireceğiniz işlemleri tanımlayın. - - You can add several actions within an iterator. - - When using branches inside an iterator, make sure the last step of each branch connects back to the iterator to close the loop. + - Bir yineleyici içinde birden fazla eylem ekleyebilirsiniz. + - Bir yineleyici içinde dallar kullanırken, her dalın son adımının döngüyü kapatmak için yineleyiciye geri bağlandığından emin olun. -* Access `Current Item` Fields: to use fields from the record currently being processed, click on the **Iterator** step, then select **Current item**. The list of available fields from that record will be displayed and can be selected for use in subsequent actions. +* `Current Item` Alanlarına Erişim: şu anda işlenen kayıttaki alanları kullanmak için **Iterator** adımına tıklayın, ardından **Current item** seçin. Bu kayıttan kullanılabilir alanların listesi görüntülenir ve sonraki eylemlerde kullanılmak üzere seçilebilir. - + ### Filtre -Filters records based on specified conditions, allowing only records that meet the criteria to pass through. +Belirtilen koşullara göre kayıtları filtreler ve yalnızca kriterleri karşılayan kayıtların geçmesine izin verir. **Yapılandırma**: -* Select the record to filter +* Filtrelenecek kaydı seçin * Filtre koşullarını ve kriterlerini tanımlayın * Sonraki adımlara geçmesi gereken kayıtları yapılandırın - 1. **Output**: Filter nodes don't return data—they act as gates. If the conditions are met, the workflow continues. If not, the workflow stops at that branch. - 2. The `IS` operator can be used with numeric fields. It performs as an `EQUAL`. + 1. **Çıktı**: Filtre düğümleri veri döndürmez—geçit görevi görürler. Koşullar karşılanırsa iş akışı devam eder. Karşılanmazsa iş akışı o dalda durur. + 2. `IS` işleci sayısal alanlarla kullanılabilir. Bir `EQUAL` gibi çalışır. -### Delay +### Gecikme -Pauses workflow execution for a specified duration or until a specific date/time. +İş akışının yürütülmesini belirtilen bir süre boyunca veya belirli bir tarih/saate kadar duraklatır. -**Delay Types**: +**Gecikme Türleri**: -| Tür | Açıklama | -| ------------------ | ------------------------------------------------------------------ | -| **Duration** | Wait for a specific amount of time (days, hours, minutes, seconds) | -| **Scheduled Date** | Wait until a specific date and time | +| Tür | Açıklama | +| --------------------- | ----------------------------------------------------- | +| **Süre** | Belirli bir süre bekleyin (gün, saat, dakika, saniye) | +| **Zamanlanmış Tarih** | Belirli bir tarih ve saate kadar bekleyin | -**Configuration for Duration**: +**Süre için yapılandırma**: -* Set days, hours, minutes, and/or seconds -* Combine multiple units (e.g., 2 days and 4 hours) +* Gün, saat, dakika ve/veya saniye ayarlayın +* Birden fazla birimi birleştirin (ör. 2 gün ve 4 saat) -**Configuration for Scheduled Date**: +**Zamanlanmış Tarih için yapılandırma**: -* Select a date and time -* Can reference a date field from a previous step (e.g., follow up 3 days after a meeting) +* Bir tarih ve saat seçin +* Önceki bir adımdaki bir tarih alanına referans verebilir (ör. bir toplantıdan 3 gün sonra takip) **Kullanım alanları**: -* Wait 24 hours before sending a follow-up email -* Pause until an opportunity's close date -* Schedule actions for business hours +* Takip e-postası göndermeden önce 24 saat bekleyin +* Bir fırsatın kapanış tarihine kadar duraklatın +* Eylemleri mesai saatlerine göre zamanlayın - The scheduled date cannot be in the past. If a date field from a previous step is used and the date has already passed, the workflow will fail. + Planlanan tarih geçmişte olamaz. Önceki bir adımdaki tarih alanı kullanılırsa ve tarih zaten geçmişse, iş akışı başarısız olur. -**Limits & Credits**: +**Sınırlar ve Krediler**: -* **No maximum duration limit**—you can set delays of minutes, days, weeks, or longer -* **1 credit consumed** when the Delay node executes, regardless of duration -* **No credits consumed** while waiting—a 5-minute delay costs the same as a 5-day delay +* **Maksimum süre sınırı yoktur**—dakika, gün, hafta veya daha uzun gecikmeler ayarlayabilirsiniz. +* Süreye bakılmaksızın Gecikme düğümü çalıştığında **1 kredi harcanır** +* Beklerken **kredi harcanmaz**—5 dakikalık bir gecikmenin maliyeti 5 günlük bir gecikmeyle aynıdır -## Communication Actions +## İletişim Eylemleri ### E-posta Gönder -İş akışınızdan bir e-posta gönderir. This is great for templated group emails. Emails will look like the ones you send from your mailbox. -Not suited for newsletters (which require richer formatting) or automated email sequences. +İş akışınızdan bir e-posta gönderir. Bu, şablonlu grup e-postaları için harikadır. E-postalar, posta kutunuzdan gönderdiğiniz e-postalara benzeyecektir. +Bültenler (daha zengin biçimlendirme gerektirir) veya otomatik e-posta dizileri için uygun değildir. -**Prerequisites**: Add an email account in Settings → Accounts +**Ön Koşullar**: Ayarlar → Hesaplar bölümüne bir e-posta hesabı ekleyin **Yapılandırma**: -* Select the sender email account +* Gönderen e-posta hesabını seçin - You can only send emails from mailboxes synced to your own Twenty account. Sending from other team members' mailboxes (e.g., the account owner's email) is on the roadmap. + Yalnızca kendi Twenty hesabınıza senkronize edilmiş posta kutularından e-posta gönderebilirsiniz. Diğer ekip üyelerinin posta kutularından gönderim (ör. hesap sahibinin e-postası) yol haritasındadır. -For all the following steps, you can reference variables from previous steps for personalization. +Aşağıdaki tüm adımlar için kişiselleştirme amacıyla önceki adımlardan gelen değişkenleri kullanabilirsiniz. * Alıcı e-posta adresini girin. - Only one recipient is possible at the moment. + Şu anda yalnızca bir alıcı mümkündür. * Konu satırını ayarlayın. -* Mesaj gövdesini yazın. You can format links, create numbered list, bullet point lists, add attachments. +* Mesaj gövdesini yazın. Bağlantıları biçimlendirebilir, numaralı listeler ve madde işaretli listeler oluşturabilir, ekler ekleyebilirsiniz. - Adding HTML signatures is not possible at the moment. + Şu anda HTML imzaları eklemek mümkün değildir. ### Form -İş akışı gerçekleştirilirken kullanıcı girdisi toplamak için bir form açar. The responses can then be used in subsequent steps to create records, send emails, or execute any other action based on the input. +İş akışı gerçekleştirilirken kullanıcı girdisi toplamak için bir form açar. Yanıtlar daha sonra sonraki adımlarda, girdiye bağlı olarak kayıtlar oluşturmak, e-postalar göndermek veya başka herhangi bir eylemi yürütmek için kullanılabilir. - **Forms are designed for manual triggers only**. Diğer tetikleyicilerle (Kayıt Oluşturuldu, Güncellendi, vb.) iş akışlarında, formlar yalnızca iş akışı çalıştırma arayüzü üzerinden erişilebilir olup, bu beklenen kullanıcı deneyimi değildir. 2026'da formların otomatik iş akışlarını doğru bir şekilde desteklemesi için bir bildirim merkezi yayınlanacaktır. + **Formlar yalnızca manuel tetikleyiciler için tasarlanmıştır**. Diğer tetikleyicilerle (Kayıt Oluşturuldu, Güncellendi, vb.) iş akışlarında, formlar yalnızca iş akışı çalıştırma arayüzü üzerinden erişilebilir olup, bu beklenen kullanıcı deneyimi değildir. 2026'da formların otomatik iş akışlarını doğru bir şekilde desteklemesi için bir bildirim merkezi yayınlanacaktır. **Yapılandırma**: -* Configure the fields that users will be asked to fill. For each field, choose - * a type among text, number, date, a given record, a select field. Select fields from all objects are available. - * a label - * a default value under `Placeholder` (optional) -* Edit the form title +* Kullanıcılardan doldurmaları istenecek alanları yapılandırın. Her alan için şunları seçin + * metin, sayı, tarih, belirli bir kayıt veya bir seçim alanı türü. Tüm nesnelerden seçim alanları kullanılabilir. + * bir etiket + * `Placeholder` altında varsayılan bir değer (isteğe bağlı) +* Form başlığını düzenleyin **Çıktı**: Form yanıtları, sonraki adımlarda kullanılmak üzere mevcuttur. -**Example**: The "Quick Lead" workflow is available by default in all workspaces, available anywhere in the Command Menu `Cmd + K`. +**Örnek**: "Quick Lead" iş akışı varsayılan olarak tüm çalışma alanlarında kullanılabilir ve Komut Menüsü `Cmd + K` içinde her yerden erişilebilir. -**How to fill the form**: +**Form nasıl doldurulur**: -* Trigger your manual workflow from the command menu `Cmd K` -* Fill the form that is displayed in the side panel and click `Submit`. +* Manuel iş akışınızı komut menüsünden `Cmd K` ile tetikleyin +* Kenar panelde görüntülenen formu doldurun ve `Submit` düğmesine tıklayın. - The fields cannot be made mandatory. + Alanlar zorunlu hale getirilemez. - + -## Integration Actions +## Entegrasyon Eylemleri ### Kod @@ -247,24 +247,24 @@ For all the following steps, you can reference variables from previous steps for **Yapılandırma**: -* Önceki adımlardan gelen değişkenlere erişin. You can edit the variables names dynamically. +* Önceki adımlardan gelen değişkenlere erişin. Değişken adlarını dinamik olarak düzenleyebilirsiniz. - + * Düzenleyicide JavaScript kodu yazın * Sonraki adımlarda kullanılmak üzere değişkenler döndürün * Kodu doğrudan adımda test edin - If you need to use external API keys in your code, you must input them directly in the function body. You cannot configure API keys elsewhere and reference them in the serverless function. + Kodunuzda harici API anahtarlarını kullanmanız gerekiyorsa, bunları doğrudan fonksiyon gövdesine girmeniz gerekir. API anahtarlarını başka bir yerde yapılandıramaz ve bunlara serverless fonksiyon içinde referans veremezsiniz. - **Working with arrays?** Arrays from external systems or previous steps may come as strings. See [How to handle arrays in Code actions](/l/tr/user-guide/workflows/how-tos/advanced-configurations/handle-arrays-in-code-actions) for the solution. + **Dizilerle mi çalışıyorsunuz?** Harici sistemlerden veya önceki adımlardan gelen diziler metin (string) olarak gelebilir. Çözüm için [Kod eylemlerinde diziler nasıl ele alınır](/l/tr/user-guide/workflows/how-tos/advanced-configurations/handle-arrays-in-code-actions) bölümüne bakın. - Click the square icon at the top right of the code editor to display it in full screen — helpful since the default editor width is limited. + Kod düzenleyicisinin sağ üst kısmındaki kare simgeye tıklayarak tam ekranda görüntüleyin — varsayılan düzenleyici genişliği sınırlı olduğundan faydalıdır. ### HTTP İsteği @@ -275,37 +275,37 @@ For all the following steps, you can reference variables from previous steps for **Yapılandırma**: -* API endpoint URL'sini girin. Using parameters from previous steps is possible. +* API endpoint URL'sini girin. Önceki adımlardaki parametreleri kullanmak mümkündür. * HTTP yöntemini seçin (GET, POST, PUT, PATCH, DELETE) * Gerekli başlıkları ve değerleri ekleyin * Yapı önizlemesi için örnek yanıt sağlayın -## AI Actions +## Yapay Zeka Eylemleri -### AI Agent - Coming Soon +### Yapay Zeka Aracısı - Çok Yakında -Runs an AI agent within your workflow to perform intelligent tasks. +İş akışınız içinde akıllı görevler gerçekleştirmek için bir yapay zeka aracısını çalıştırır. **Yapılandırma**: -* **Agent**: Select an existing AI agent or use the default agent -* **Prompt**: Write the instruction for the AI agent -* Reference variables from previous steps in the prompt +* **Aracı**: Mevcut bir yapay zeka aracısını seçin veya varsayılan aracıyı kullanın +* **İstem**: Yapay zeka aracısı için talimatı yazın +* İstemde önceki adımlardaki değişkenlere başvurun -**What AI Agents can do**: +**Yapay Zeka Aracıları neler yapabilir**: -* Analyze and summarize data -* Classify or categorize records -* Generate text content -* Make decisions based on data -* Interact with your CRM data using tools +* Verileri analiz edip özetleyin +* Kayıtları sınıflandırın veya kategorilere ayırın +* Metin içeriği oluşturun +* Verilere dayalı kararlar verin +* Araçlar kullanarak CRM verilerinizle etkileşim kurun -**Output**: The AI agent's response is available for use in subsequent steps. If the agent has a structured output schema, the response will follow that format. +**Çıktı**: Yapay zeka aracısının yanıtı, sonraki adımlarda kullanılmak üzere mevcuttur. Aracın yapılandırılmış bir çıktı şeması varsa, yanıt bu biçimi izler. - AI Agent actions consume workflow credits based on the AI model used. See [Workflow Credits](/l/tr/user-guide/workflows/capabilities/workflow-credits) for details. + Yapay Zeka Aracısı eylemleri, kullanılan yapay zeka modeline bağlı olarak iş akışı kredileri tüketir. Ayrıntılar için [İş Akışı Kredileri](/l/tr/user-guide/workflows/capabilities/workflow-credits) bölümüne bakın. - AI agents respect role-based permissions. You can assign specific roles to agents under **Settings → Roles** to control what data they can access. See [Permissions](/l/tr/user-guide/permissions-access/capabilities/permissions) for details. + Yapay zeka aracıları role dayalı izinlere uyar. **Ayarlar → Roller** altında aracılara hangi verilere erişebileceklerini kontrol etmek için belirli roller atayabilirsiniz. Ayrıntılar için [İzinler](/l/tr/user-guide/permissions-access/capabilities/permissions) bölümüne bakın. diff --git a/packages/twenty-docs/l/tr/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities.mdx b/packages/twenty-docs/l/tr/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities.mdx index e69ebf19da..fa7949b6d5 100644 --- a/packages/twenty-docs/l/tr/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities.mdx +++ b/packages/twenty-docs/l/tr/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities.mdx @@ -1,56 +1,56 @@ --- -title: Detect Stale Opportunities -description: Automatically notify managers when opportunities haven't been updated. +title: Durağan Fırsatları Tespit Et +description: Fırsatlar güncellenmediğinde yöneticileri otomatik olarak bilgilendirin. --- -Keep your pipeline healthy by alerting managers when opportunities go stale. This workflow checks for opportunities that haven't been updated in a specified number of days. +Fırsatlar durağanlaştığında yöneticileri uyararak satış boru hattınızı sağlıklı tutun. Bu iş akışı, belirli sayıda gündür güncellenmeyen fırsatları kontrol eder. -## The Problem +## Sorun -Opportunities sitting without updates lead to: +Güncellenmeden bekleyen fırsatlar şunlara yol açar: -* Deals going cold -* Unreliable forecasts -* Lost revenue +* Anlaşmaların soğuması +* Güvenilmez tahminler +* Kaybedilen gelir -## The Solution +## Çözüm -Create a scheduled workflow that finds stale opportunities and emails their managers. +Durağan fırsatları bulan ve yöneticilerine e-posta gönderen zamanlanmış bir iş akışı oluşturun. -## Step-by-Step Setup +## Adım adım kurulum -### Step 1: Create the Workflow +### Adım 1: İş akışını oluşturun -1. Go to **Settings → Workflows** -2. Click **+ New Workflow** -3. Name it "Stale Opportunity Alert" +1. **Ayarlar → İş Akışları** bölümüne gidin +2. **+ Yeni İş Akışı**'na tıklayın +3. Adını "Durağan Fırsat Uyarısı" koyun -### Step 2: Configure the Trigger +### Adım 2: Tetikleyiciyi yapılandırın -1. Select **On a Schedule** -2. Set to run daily (e.g., every day at 8 AM) +1. **Zamanlanmış Olarak** seçin +2. Günlük çalışacak şekilde ayarlayın (ör. her gün saat 08:00'de) -### Step 3: Search for Stale Opportunities +### Adım 3: Durağan Fırsatları Ara -1. Add **Search Records** action +1. **Kayıt Ara** eylemini ekleyin 2. Alanı Yapılandır: -| Alan | Değer | -| ---------- | ----------------------------------------------- | -| **Object** | Fırsatlar | -| **Filter** | Updated At is before (today - 7 days) | -| **Filter** | Stage is not "Closed Won" AND not "Closed Lost" | -| **Limit** | 100 | +| Alan | Değer | +| ---------- | ------------------------------------------------ | +| **Nesne** | Fırsatlar | +| **Filtre** | Updated At, (bugün - 7 gün) tarihinden önce | +| **Filtre** | Stage, "Closed Won" DEĞİL VE "Closed Lost" DEĞİL | +| **Sınır** | 100 | -### Step 4: Check If Any Found +### Adım 4: Bulunup Bulunmadığını Kontrol Edin -1. Add **Filter** action -2. Condition: `{{searchRecords.length}}` is greater than 0 -3. If no stale opportunities, the workflow stops here +1. **Filtre** eylemi ekleyin +2. Koşul: `{{searchRecords.length}}` 0'dan büyüktür +3. Durağan fırsat yoksa iş akışı burada durur -### Step 5: Format the Alert (Code Action) +### Adım 5: Uyarıyı Biçimlendirin (Kod Eylemi) -Add a **Code** action to format the email: +E-postayı biçimlendirmek için bir **Kod** eylemi ekleyin: ```javascript export const main = async (params) => { @@ -88,49 +88,49 @@ export const main = async (params) => { }; ``` -### Step 6: Send Alert Email +### Adım 6: Uyarı E-postası Gönderin -Add **Send Email** action: +**E-posta Gönder** eylemini ekleyin: -| Alan | Değer | -| ----------- | ----------------------------------------------------------- | -| **To** | sales-manager@yourcompany.com | -| **Subject** | `🚨 {{code.totalCount}} Stale Opportunities Need Attention` | -| **Body** | `{{code.summary}}` | +| Alan | Değer | +| ---------- | ----------------------------------------------------------- | +| **Kime** | sales-manager@yourcompany.com | +| **Konu** | `🚨 {{code.totalCount}} Stale Opportunities Need Attention` | +| **İçerik** | `{{code.summary}}` | -### Step 7: Test and Activate +### Adım 7: Test Edin ve Etkinleştirin -1. Click **Test** to run the workflow -2. Check that the email contains the right data -3. Activate when ready +1. İş akışını çalıştırmak için **Test**'e tıklayın +2. E-postanın doğru verileri içerdiğini kontrol edin +3. Hazır olduğunuzda etkinleştirin -## Customization Options +## Özelleştirme Seçenekleri -### Change Staleness Threshold +### Durağanlık Eşiğini Değiştirin -Modify the Search Records filter to change from 7 days to your preferred period: +7 günü tercih ettiğiniz süreyle değiştirmek için Kayıt Ara filtresini düzenleyin: -* 3 days for high-velocity sales -* 14 days for enterprise deals -* 30 days for long sales cycles +* Hızlı tempolu satışlar için 3 gün +* Kurumsal anlaşmalar için 14 gün +* Uzun satış döngüleri için 30 gün -### Alert Individual Reps +### Bireysel Temsilcileri Uyarın -Instead of one manager email, use **Iterator** to send personalized emails to each rep about their own stale deals. +Tek bir yönetici e-postası yerine, her temsilciye kendi durağan anlaşmaları hakkında kişiselleştirilmiş e-postalar göndermek için **Iterator** kullanın. -### Add Escalation +### Eskalasyon Ekle -Create multiple workflows with increasing severity: +Artan ciddiyette birden fazla iş akışı oluşturun: -1. Day 7: Email to rep -2. Day 14: Email to rep + manager -3. Day 21: Create task for manager to intervene +1. Gün 7: Temsilciye e-posta +2. Gün 14: Temsilciye + yöneticiye e-posta +3. Gün 21: Müdahale etmesi için yöneticiye görev oluşturun -### Include in Slack +### Slack'e Dahil Edin -Use **HTTP Request** to post to a Slack webhook instead of or in addition to email. +E-postaya ek olarak veya yerine, bir Slack webhook'una gönderi yapmak için **HTTP Request** kullanın. -## Related +## İlgili -* [Workflow Actions](/l/tr/user-guide/workflows/capabilities/workflow-actions) -* [Send Emails from Workflows](/l/tr/user-guide/workflows/capabilities/send-emails-from-workflows) +* [İş Akışı Eylemleri](/l/tr/user-guide/workflows/capabilities/workflow-actions) +* [İş Akışlarından E-posta Gönderme](/l/tr/user-guide/workflows/capabilities/send-emails-from-workflows)