@pdfbutler/migration-cli 0.0.27 → 0.0.29

package/README.md

@@ -6,38 +6,87 @@
 
 v0.0.11 updates: <br/>
 
-- '-b' flag disables backend export. If specified, the export operation doesn't use a PDF Butler backend process for exporting the configuration. By default, backend export is enabled.
-- '-l --logs' flag. Use this flag to enable a more detailed log of the migration process.
-- '-p --partial' flag. Use this flag to ignore invalid document configurations and allow the export of document configuration files with the backend part.
+- `-b` flag disables backend export. If specified, the export operation doesn't use a PDF Butler backend process for exporting the configuration. By default, backend export is enabled.
+- `-l | --logs` flag. Use this flag to enable a more detailed log of the migration process.
+- `-p | --partial` flag. Use this flag to ignore invalid document configurations and allow the export of document configuration files with the backend part.
 
 v0.0.14 updates: <br/>
 
-- The '-i --id' flag has been added to the import command to specify the IDs of the PDF Butler document configurations that require importing. This is a required flag.
+- The `-i | --id` flag has been added to the import command to specify the IDs of the PDF Butler document configurations that require importing. This is a required flag.
 
 v0.0.17 updates: <br/>
 
-- The '-c' or '--clone' flag has been added to the import command. Use '-c' or '--clone' to allow inserting new DocConfigs instead of updating existing ones.
+- The `-c | --clone` flag has been added to the import command. Use `-c | --clone` to allow inserting new DocConfigs instead of updating existing ones.
 
-v.0.0.18 updates: <br/>
+v0.0.18 updates: <br/>
 This release introduces several new commands to enhance the management and deployment of PDFButler Packs and administrative settings in your org. Here’s a breakdown of the new commands and their functionality:
 
-- 'exportpack'. Allows you to export a PDFButler Pack from the org to an external file.
-- 'importpack'. Facilitates importing a previously exported PDFButler Pack into your org.
-- 'adminsettings'. Allows you to configure critical PDFButler settings such as the service URL, region, and stage.
-- 'admincredentials'. Enables you to securely provide or update the PDFButler admin credentials.
+- `exportpack` — Allows you to export a PDFButler Pack from the org to an external file.
+- `importpack` — Facilitates importing a previously exported PDFButler Pack into your org.
+- `adminsettings` — Allows you to configure critical PDFButler settings such as the service URL, region, and stage.
+- `admincredentials` — Enables you to securely provide or update the PDFButler admin credentials.
 
-v.0.0.20 updates <br/>
+v0.0.20 updates: <br/>
 This release introduces an alternative authentication method to enhance flexibility when connecting to Salesforce. The new functionality includes support for session-based authentication, allowing users to connect without relying solely on username.
 Additionally, two new optional flags, --session and --instance, have been added to all commands to support this authentication method:
 
-- '--session'. Allows you to provide a Salesforce Session Id for authentication.
-- '--instance'. Specifies the Salesforce Instance URL for authentication.
+- `--session` — Allows you to provide a Salesforce Session Id for authentication.
+- `--instance` — Specifies the Salesforce Instance URL for authentication.
+
+v.0.0.24 updates: <br/>
+This release introduces enhancements to filename handling, improving compatibility and usability when working with zipped files, particularly in Windows environments.
+
+- `--cut` — Trim filenames to a maximum of 150 characters to prevent issues when extracting a zipped file on Windows, as Windows Explorer cannot support file paths longer than 255 characters.
+- `--shortpaths` — The filename is just the DC name (drop the Stage and long DC Id in the filename).
+
+v0.0.28 updates: <br/>
+DocConfigs with Templates — Export & Import Support
+
+- Export and import operations now support DocConfigs together with their associated template DocConfigs.
+- Use `-m | --templates` to include templates during both export and import.
+
+DataSource — Export & Import Support
+
+- DataSource import requires PDF Butler package version v1.505 or higher.
+- `exportdatasource` — Exports PDF Butler DataSources from the org.
+- `importdatasource` — Imports PDF Butler DataSources into the org from JSON
+
+SB Sign Request Template — Export & Import Support
+
+- `butler:sb:export:signtemplate` — Exports Sign Request Templates from the org and saves them as JSON files for backup or migration.
+- `butler:sb:import:signtemplate` — Imports Sign Request Templates into the org from previously exported JSON files
+
+v0.0.29 updates: <br/>
+Export Pack — DocConfig Export Modes
+- `exportpack` now supports DocConfig export modes via `-d | --docconfig`:
+  - `none` (default) or without flag: export only pack JSON.
+  - `lead`: export only leading DocConfig (without pack JSON).
+  - `pack`: export only pack DocConfigs (without leading and without pack JSON).
+  - `full`: export both pack JSON and all related DocConfigs.
+
+Export Pack — Backend Bundle Support
+- `exportpack` now supports backend bundle export for DocConfigs with:
+  - `-a | --auth-env-var`, `-e | --endpoint`, `-s | --stage`
+  - `-u | --unzip` to extract backend files instead of writing zip archives
+  - `-m | --templates` to recursively export template DocConfigs
+
+Import Pack — DocConfig Import Modes
+- `importpack` now supports selective DocConfig import mode via `-d | --docconfig`:
+  - `pack`: import only pack DocConfigs.
+  - `lead`: import only leading DocConfig.
+  - `full` (default): import DocConfigs and then import the pack.
+
+Import Pack — Backend Bundle Support
+- `importpack` backend/template import enhancements:
+  - `-a | --auth-env-var`, `-e | --endpoint`, `-s | --stage` for backend upload.
+  - `-m | --templates` to include template dependency DocConfigs.
+  - `-c | --clone` to insert new DocConfigs instead of updating existing ones.
+
+Backend Export Modes
+- `-b | --backend` now supports modes: `full` (default, export SFDC + backend), `only` (backend only), and `none` (SFDC only).
+- Backward compatibility: using `-b` without a value is interpreted as `--backend none`.
 
-v.0.0.24 updates <br/>
-  This release introduces enhancements to filename handling, improving compatibility and usability when working with zipped files, particularly in Windows environments.
 
-- '--cut'. Trim filenames to a maximum of 150 characters to prevent issues when extracting a zipped file on Windows, as Windows Explorer cannot support file paths longer than 255 characters.
-- '--shortpaths'. The filename is just the DC name (drop the Stage and long DC Id in the filename).
 ## About
 
 @pdfbutler/migration-cli is a Salesforce plugin designed to simplify and automate the process of migrating configurations within the PDF Butler system in the Salesforce environment. PDF Butler is a powerful tool for generating and automating documents in the Salesforce platform, and the use of this CLI plugin allows users to easily manage configurations and transfer them between different Salesforce instances or projects.
@@ -62,7 +111,7 @@ If you've installed Node.js on your computer, you can use npm to install Salesfo
 npm install @salesforce/cli --global
 ```
 
-For install the plugin run:
+For installation the plugin runs:
 
 ```
 sf plugins install @pdfbutler/migration-cli
@@ -105,6 +154,9 @@ $ sf butler pb exportpack [options]
 $ sf butler pb importpack [options]
 $ sf butler pb adminsettings [options]
 $ sf butler pb admincredentials [options]
+
+$ sf butler sb export signtemplate [options]
+$ sf butler sb import signtemplate [options]
 ```
 
 ## Recommended CLI Shell:
@@ -119,13 +171,59 @@ One of the common errors in Windows Command Prompt is incorrectly parsing comman
 
 ## Commands
 
+## butler sb export signtemplate
+
+Export Sign Request Template records from your organization.
+
+```
+USAGE
+$ sf butler sb export signtemplate -i <value> -f <value> [--json] [-t <value>] [-l] [--session <value>] [--instance <value>]
+
+FLAGS
+    -t, --target=<value>         The Salesforce org username credentials to connect to the target org.
+    -i, --id=<value>             The Customer Template ID to export. For bulk export, enter multiple IDs separated by whitespaces. (Required)
+    -f, --folder=<value>         The output root folder path. Files will be saved to the signRequestTemplates subfolder. (Required)
+    -l, --logs                   Enable detailed logs for the export process.
+    --session=<value>            Salesforce Session ID for authentication.
+    --instance=<value>           Salesforce Instance URL for authentication.
+
+DESCRIPTION
+    Export Sign Request Template records from your organization.
+
+EXAMPLES
+    $ sf butler:sb:export:signtemplate -t my-org -i "a0Bxx0000000011 a0Bxx0000000012" -f "./export/sb"
+```
+
+## butler sb import signtemplate
+
+Import Sign Request Template records into your organization.
+
+```
+USAGE
+$ sf butler sb import signtemplate -i <value> -f <value> [--json] [-t <value>] [-l] [--session <value>] [--instance <value>]
+
+FLAGS
+    -t, --target=<value>         The Salesforce org username credentials to connect to the target org.
+    -i, --id=<value>             The Customer Template ID to import. For bulk import, enter multiple IDs separated by whitespaces. (Required)
+    -f, --folder=<value>         The export root folder path that contains the signRequestTemplates subfolder. (Required)
+    -l, --logs                   Enable detailed logs for the import process.
+    --session=<value>            Salesforce Session ID for authentication.
+    --instance=<value>           Salesforce Instance URL for authentication.
+
+DESCRIPTION
+    Import Sign Request Template records into your organization.
+
+EXAMPLES
+    $ sf butler:sb:import:signtemplate -t my-org -i "a0Bxx0000000011" -f "./export/sb"
+```
+
 ## butler pb export
 
 Export PDF Butler configurations.
 
 ```
 USAGE
-$ sf butler pb export [--target | -t <value>] [--id | -i <value>] [--out | -o <value>] [--stage | -s <value>] [--auth-env-var | -a <value>] [--endpoint | -e <value>] [--backend | -b] [--unzip | -u] [-l | --logs] [-p | --partial] [--session <value>] [--instance <value>]
+$ sf butler pb export [--target | -t <value>] [--id | -i <value>] [--out | -o <value>] [--stage | -s <value>] [--auth-env-var | -a <value>] [--endpoint | -e <value>] [--backend | -b <value>] [--unzip | -u] [-l | --logs] [-p | --partial] [-m | --templates] [--session <value>] [--instance <value>]
 
 FLAGS
     -t, --target=<value>         The Salesforce org username credentials to connect to the target org. (Required)
@@ -142,9 +240,10 @@ FLAGS
                                  CA: https://ca1.pdfbutler.com
 
     -u, --unzip                  Use this flag to unzip the exported configuration. (Optional)
-    -b, --backend                Use this flag to disable PDF Butler backend export. (Optional)
+    -b, --backend=<value>        Backend export mode: full | only | none. (Optional, default: full)
     -l, --logs                   Use it to get a more detailed log of migration process. (Optional)
     -p, --partial                Use this flag to ignore invalid document configurations and allow the export of document configuration files with the backend part. (Optional)
+    -m, --templates              Include template DocConfigs in the export. (Optional)
     --session=<value>            This flag is used to provide a Salesforce Session ID for authentication.
     --instance=<value>           This flag specifies the Salesforce Instance URL. The Instance URL corresponds to the specific Salesforce environment (e.g., production, sandbox) you are connecting to.
 
@@ -163,34 +262,39 @@ DESCRIPTION
     get a more detailed log of migration process and even choose to unzip the exported configuration.
 
 EXAMPLES
-    Run with --backend flag
+    Run with --backend full (default)
 
         $ sf butler pb export -t sfusername@sandbox.com -i 'document_configuration_id'
             -o 'export_folder_name/archive_or_folder_name' -s 'TEST' -e 'https://eu1.pdfbutler.com'
-            -a 'pdf_butler_user_name-ADMIN:admin_password' -b
+            -a 'pdf_butler_user_name-ADMIN:admin_password' --backend full
 
         # Console output:
             Connected to sfusername@sandbox.com (00D06000001aXGkEAM) with API version 58.0
 
         # Created:
-            Directory 'export_folder_name/archive_or_folder_name/sfdc'{
-                file 'docconfig_id.json'
+            Directory 'export_folder_name/archive_or_folder_name'{
+                Directory 'sfdc'{
+                    file 'docconfig_id.json',
+                },
+                zip file'docconfig_id.zip'{
+                    Directory 'ConfigTypes',
+                    Directory 'DataSources',
+                    file 'doc-config.json',
+                    file 'TemplateName.docx'
+                }
             }
 
-    Run without --backend flag
+    Run with --backend only
 
         $ sf butler pb export -t sfusername@sandbox.com -i 'document_configuration_id'
             -o 'export_folder_name/archive_or_folder_name' -s 'TEST' -e 'https://eu1.pdfbutler.com'
-            -a 'pdf_butler_user_name-ADMIN:admin_password'
+            -a 'pdf_butler_user_name-ADMIN:admin_password' --backend only
 
         # Console output:
             Connected to sfusername@sandbox.com (00D06000001aXGkEAM) with API version 58.0
 
         # Created:
             Directory 'export_folder_name/archive_or_folder_name'{
-                Directory 'sfdc'{
-                    file 'docconfig_id.json',
-                },
                 zip file'docconfig_id.zip'{
                     Directory 'ConfigTypes',
                     Directory 'DataSources',
@@ -199,6 +303,20 @@ EXAMPLES
                 }
             }
 
+    Run with --backend none
+
+        $ sf butler pb export -t sfusername@sandbox.com -i 'document_configuration_id'
+            -o 'export_folder_name/archive_or_folder_name' -s 'TEST'
+            --backend none
+
+        # Console output:
+            Connected to sfusername@sandbox.com (00D06000001aXGkEAM) with API version 58.0
+
+        # Created:
+            Directory 'export_folder_name/archive_or_folder_name/sfdc'{
+                file 'docconfig_id.json'
+            }
+
     Run with --unzip flag
 
         $ sf butler pb export -t sfusername@sandbox.com -i 'document_configuration_id'
@@ -211,7 +329,7 @@ EXAMPLES
         # Created:
             Directory 'export_folder_name/archive_or_folder_name'{
                 Directory 'sfdc'{
-                    file 'docconfig_id.json',
+                    file 'docconfig_id.json'
                 },
                 Unziped directory 'docconfig_id'{
                     Directory 'ConfigTypes',
@@ -352,8 +470,8 @@ FLAG DESCRIPTIONS
         It is a required parameter.
 
     -b, --backend
-        Disables backend export. If specified, the export operation doesn't use a PDF Butler backend process for exporting the configuration.
-        By default, backend export is enabled.
+        Controls what to export: full (SFDC + backend), only (backend only), none (SFDC only).
+        Default value is full. For backward compatibility, using -b without a value is treated as --backend none.
 
     -u, --unzip
         Use this flag to indicate that the exported configuration should be unzipped.
@@ -365,9 +483,12 @@ FLAG DESCRIPTIONS
     -p, --partial
         Use this flag to ignore invalid document configurations and allow the export of document configuration files with the backend part.
 
+    -m, --templates
+        Include template DocConfigs in the export.
+
     --session
         This flag is used to provide a Salesforce Session ID for authentication.
-    
+
     --instance
         This flag specifies the Salesforce Instance URL. The Instance URL corresponds to the specific Salesforce environment (e.g., production, sandbox) you are connecting to.
 ```
@@ -378,7 +499,7 @@ Import PDF Butler document configurations and related DataSource files.
 
 ```
 USAGE
-$ sf butler pb import [--target | -t <value>] [--id | -i <value>] [--auth-env-var | -a <value>] [--endpoint | -e <value>] [--stage | -s <value>] [--config | -f <value>] [-c | --clone] [--session <value>] [--instance <value>]
+$ sf butler pb import [--target | -t <value>] [--id | -i <value>] [--auth-env-var | -a <value>] [--endpoint | -e <value>] [--stage | -s <value>] [--config | -f <value>] [-c | --clone] [-m | --templates] [--session <value>] [--instance <value>]
 
 FLAGS
     -t, --target=<value>          The Salesforce org username credentials to connect to the target org. (Required)
@@ -396,6 +517,7 @@ FLAGS
     -f, --config=<value>          The path to the directory containing configurations to import. (Required)
     -l, --logs                    Use it to get a more detailed log of migration process. (Optional)
     -c, --clone                   Use this flag to disables the update of existing docconfigs and allows to create new ones. (Optional)
+    -m, --templates               Include template DocConfigs in the import. (Optional)
     --session=<value>            This flag is used to provide a Salesforce Session ID for authentication.
     --instance=<value>           This flag specifies the Salesforce Instance URL. The Instance URL corresponds to the specific Salesforce environment (e.g., production, sandbox) you are connecting to.
 
@@ -412,7 +534,7 @@ EXAMPLE
     Import configurations with --clone flag to the organization:
 
     $ sf butler pb import -t sfusername@sandbox.com -i 'document_configuration_id' -f .export_folder_name/archive_or_folder_name
-        -e 'https://eu1.pdfbutler.com' -a 'pdf_butler_user_name-ADMIN:admin_password' -s 'UAT' -c
+        -e 'https://eu1.pdfbutler.com' -a 'pdf_butler_user_name-ADMIN:admin_password' -s 'UAT' -c -m
 
     #Imported:
         Insert a new Doc config with a unique 'customerDocumentConfigId'.
@@ -465,13 +587,96 @@ FLAG DESCRIPTIONS
     -c, --clone
         Use this flag to disables the update of existing docconfigs and allows to create new ones. (Optional)
 
+    -m, --templates
+        Include template DocConfigs in the import.
+
     --session
         This flag is used to provide a Salesforce Session ID for authentication.
-    
+
     --instance
         This flag specifies the Salesforce Instance URL. The Instance URL corresponds to the specific Salesforce environment (e.g., production, sandbox) you are connecting to.
 ```
 
+## butler pb exportdatasource
+
+Export PDF Butler DataSource files.
+
+```
+USAGE
+$ sf butler pb exportdatasource [--target | -t <value>] [--id | -i <value>] [--folder | -f <value>] [--stage | -s <value>] [--auth-env-var | -a <value>] [--endpoint | -e <value>] [-l | --logs] [-p | --parents] [--session <value>] [--instance <value>]
+
+FLAGS
+    -t, --target=<value>         The Salesforce org username credentials to connect to the target org. (Optional)
+    -i, --id=<value>             The DataSource ID(s) to export. For bulk export, enter multiple IDs separated by commas or spaces. (Required)
+    -f, --folder=<value>         The output folder where DataSource JSON files will be saved. (Required)
+    -s, --stage=<value>          The CADMUS stage. (Required)
+    -a, --auth-env-var=<value>   The PDF Butler credentials for backend authentication. (Optional)
+    -e, --endpoint=<value>       The URL PDF Butler endpoint for export. (Optional)
+    -l, --logs                   Use it to get a more detailed log of migration process. (Optional)
+    -p, --parents                Automatically export parent DataSources recursively when detected. (Optional)
+    --session=<value>            This flag is used to provide a Salesforce Session ID for authentication.
+    --instance=<value>           This flag specifies the Salesforce Instance URL. The Instance URL corresponds to the specific Salesforce environment (e.g., production, sandbox) you are connecting to.
+
+DESCRIPTION
+    Export DataSources from your organization into JSON files.
+
+    The command writes files into:
+    ./<folder>/sfdc/<DataSourceId>.json
+
+EXAMPLES
+    Export a single DataSource:
+
+        $ sf butler pb exportdatasource -t sfusername@sandbox.com -i '00Dxxxxxxxxxxxx' -f 'export' -s 'TEST'
+
+    Export multiple DataSources:
+
+        $ sf butler pb exportdatasource -t sfusername@sandbox.com -i '00Dxxx, 00Dyyy' -f 'export' -s 'TEST' -l
+
+    Export with parent DataSources:
+
+        $ sf butler pb exportdatasource -t sfusername@sandbox.com -i '00Dxxx' -f 'export' -s 'TEST' -p
+```
+
+## butler pb importdatasource
+
+Import PDF Butler DataSource files.
+
+```
+USAGE
+$ sf butler pb importdatasource [--target | -t <value>] [--id | -i <value>] [--folder | -f <value>] [--stage | -s <value>] [--auth-env-var | -a <value>] [--endpoint | -e <value>] [-l | --logs] [-p | --parents] [--session <value>] [--instance <value>]
+
+FLAGS
+    -t, --target=<value>         The Salesforce org username credentials to connect to the target org. (Optional)
+    -i, --id=<value>             The DataSource ID(s) to import. For bulk import, enter multiple IDs separated by commas or spaces. (Required)
+    -f, --folder=<value>         The folder that contains exported DataSource JSON files. (Required)
+    -s, --stage=<value>          The CADMUS stage. (Optional)
+    -a, --auth-env-var=<value>   The PDF Butler credentials for backend authentication. (Optional)
+    -e, --endpoint=<value>       The URL PDF Butler endpoint for import. (Optional)
+    -l, --logs                   Use it to get a more detailed log of migration process. (Optional)
+    -p, --parents                Resolve and import parent DataSources first, then child DataSources. (Optional)
+    --session=<value>            This flag is used to provide a Salesforce Session ID for authentication.
+    --instance=<value>           This flag specifies the Salesforce Instance URL. The Instance URL corresponds to the specific Salesforce environment (e.g., production, sandbox) you are connecting to.
+
+DESCRIPTION
+    Import DataSources from JSON files into your organization.
+
+    The command reads files from:
+    ./<folder>/sfdc/<DataSourceId>.json
+
+EXAMPLES
+    Import a single DataSource:
+
+        $ sf butler pb importdatasource -t sfusername@sandbox.com -i '00Dxxxxxxxxxxxx' -f 'export' -s 'TEST'
+
+    Import multiple DataSources:
+
+        $ sf butler pb importdatasource -t sfusername@sandbox.com -i '00Dxxx, 00Dyyy' -f 'export' -s 'TEST' -l
+
+    Import with parent DataSources first:
+
+        $ sf butler pb importdatasource -t sfusername@sandbox.com -i '00Dxxx' -f 'export' -s 'TEST' -p
+```
+
 ## butler pb exportpack
 
 <span style="color: red;">Important!</span> Make sure you have installed PDF Butler version equal or higher than v1.440. <br/>
@@ -480,7 +685,7 @@ Export PDF Butler Pack.
 
 ```
 USAGE
-$ sf butler pb exportpack [--target | -t <value>] [--pack | -p <value>] [--out | -o <value>] [--logs | -l] [--session <value>] [--instance <value>]
+$ sf butler pb exportpack [--target | -t <value>] [--pack | -p <value>] [--out | -o <value>] [--logs | -l] [--docconfig | -d <none|pack|lead|full>] [--auth-env-var | -a <value>] [--endpoint | -e <value>] [--stage | -s <value>] [--unzip | -u] [--templates | -m] [--session <value>] [--instance <value>]
 
 FLAGS
     -t, --target=<value>         The Salesforce org username credentials to connect to the target org. (Required)
@@ -488,6 +693,13 @@ FLAGS
                                  For bulk export, enter multiple Customer Pack Ids separated by commas.  (Required)
     -o, --out=<value>            The value specifies the path to the folder with the exported configuration and archive name. (Required)
     -l, --logs                    Use it to get a more detailed log of migration process. (Optional)
+    -d, --docconfig=<none|pack|lead|full>
+                                 Export mode for related DocConfigs. (Optional, default: none)
+    -a, --auth-env-var=<value>   The PDF Butler credentials for backend authentication. (Optional)
+    -e, --endpoint=<value>       The URL PDF Butler endpoint for backend export. (Optional)
+    -s, --stage=<value>          The CADMUS stage for backend export. (Optional)
+    -u, --unzip                  Unzip backend export instead of saving DocConfig archives as zip files. (Optional)
+    -m, --templates              Include template DocConfigs for recursive export. (Optional)
     --session=<value>            This flag is used to provide a Salesforce Session ID for authentication.
     --instance=<value>           This flag specifies the Salesforce Instance URL. The Instance URL corresponds to the specific Salesforce environment (e.g., production, sandbox) you are connecting to.
 
@@ -523,7 +735,7 @@ EXAMPLES
             Directory 'export_folder_name/folder_name/sfdc'{
                 file 'customer_pack_id.json'
             }
-    
+
     Export multiple packs:
 
         $ sf butler pb exportpack -t sfusername@sandbox.com -p 'customer_pack_id1, customer_pack_id2'
@@ -554,6 +766,49 @@ EXAMPLES
                 file 'customer_pack_id2.json'
             }
 
+    Export only leading DocConfig (without pack JSON):
+
+        $ sf butler pb exportpack -p customer_pack_id
+            -t sfusername@sandbox.com -a pdf_butler_user-ADMIN:admin_password
+            -e https://eu1.pdfbutler.com -s TEST -o ./export/pack -l
+            --session <session_id> --instance <instance_url> -u -m -d lead
+
+        # Created:
+            Directory './export/pack/sfdc'{
+                file 'leading_docconfig_id.json'
+            }
+
+    Export only pack DocConfigs (without leading and without pack JSON):
+
+        $ sf butler pb exportpack -p customer_pack_id
+            -t sfusername@sandbox.com -a pdf_butler_user-ADMIN:admin_password
+            -e https://eu1.pdfbutler.com -s TEST -o ./export/pack -l
+            --session <session_id> --instance <instance_url> -u -m -d pack
+
+        # Created:
+            Directory './export/pack/sfdc'{
+                file 'pack_docconfig_id_1.json'
+                file 'pack_docconfig_id_2.json'
+            }
+
+    Export full content (pack JSON + DocConfigs + backend zips):
+
+        $ bin\dev butler:pb:exportpack -p customer_pack_id
+            -t sfusername@sandbox.com -a pdf_butler_user-ADMIN:admin_password
+            -e https://eu1.pdfbutler.com -s TEST -o ./export/pack -l
+            --session <session_id> --instance <instance_url> -u -m -d full
+
+        # Created:
+            Directory './export/pack'{
+                Directory 'sfdc'{
+                    file 'customer_pack_id.json'
+                    file 'docconfig_id.json'
+                    file 'template_docconfig_id.json'
+                },
+                file 'docconfig_id.zip'
+                file 'template_docconfig_id.zip'
+            }
+
 FLAG DESCRIPTIONS
     -t, --target <value>
         Specifies the Salesforce org username credentials to connect to the target
@@ -571,7 +826,7 @@ FLAG DESCRIPTIONS
 
     --session
         This flag is used to provide a Salesforce Session ID for authentication.
-    
+
     --instance
         This flag specifies the Salesforce Instance URL. The Instance URL corresponds to the specific Salesforce environment (e.g., production, sandbox) you are connecting to.
 ```
@@ -584,7 +839,7 @@ Import PDF Butler Pack.
 
 ```
 USAGE
-$ sf butler pb importpack [--target | -t <value>] [--pack | -p <value>] [--folder | -f <value>] [-logs | -l] [--session <value>] [--instance <value>]
+$ sf butler pb importpack [--target | -t <value>] [--pack | -p <value>] [--folder | -f <value>] [-logs | -l] [--docconfig | -d <pack|lead|full>] [--auth-env-var | -a <value>] [--endpoint | -e <value>] [--stage | -s <value>] [--templates | -m] [--clone | -c] [--session <value>] [--instance <value>]
 
 FLAGS
     -t, --target=<value>         The Salesforce org username credentials to connect to the target org. (Required)
@@ -592,6 +847,14 @@ FLAGS
                                  For bulk export, enter multiple Customer Pack Ids separated by commas.  (Required)
     -f, --folder=<value>            The value specifies the path to the folder with the exported packs. (Required)
     -l, --logs                    Use it to get a more detailed log of migration process. (Optional)
+    -d, --docconfig=<pack|lead|full>
+                                 Import mode for related DocConfigs. (Optional, default: full)
+                                 Note: if mode is not full, only DocConfigs are imported and pack import is skipped.
+    -a, --auth-env-var=<value>   The PDF Butler credentials for backend upload. (Optional)
+    -e, --endpoint=<value>       The URL PDF Butler endpoint for backend upload. (Optional)
+    -s, --stage=<value>          The CADMUS stage for backend upload. (Optional)
+    -m, --templates              Include template dependency DocConfigs during import. (Optional)
+    -c, --clone                  Insert new DocConfigs instead of updating existing ones. (Optional)
     --session=<value>            This flag is used to provide a Salesforce Session ID for authentication.
     --instance=<value>           This flag specifies the Salesforce Instance URL. The Instance URL corresponds to the specific Salesforce environment (e.g., production, sandbox) you are connecting to.
 
@@ -617,7 +880,7 @@ EXAMPLES
             [INFO] Retrieving items from the directory
             [INFO] Files found in folder: 1
             [INFO] Successfully imported  export_folder_name/folder_name/sfdc/customer_pack_id1.json
-    
+
     Import multiple packs:
 
         $ sf butler pb importpack -t sfusername@sandbox.com -p 'customer_pack_id1, customer_pack_id2'
@@ -634,6 +897,23 @@ EXAMPLES
             [INFO] Successfully imported  export_folder_name/folder_name/sfdc/customer_pack_id1.json
             [INFO] Successfully imported  export_folder_name/folder_name/sfdc/customer_pack_id2.json
 
+    Import only pack DocConfigs (skip pack import):
+
+        $ bin\dev butler:pb:importpack -p customer_pack_id
+            -f ./export/pack -t sfusername@sandbox.com -l -d pack
+
+    Import only leading DocConfig (skip pack import):
+
+        $ bin\dev butler:pb:importpack -p customer_pack_id
+            -f ./export/pack -t sfusername@sandbox.com -l -d lead
+
+    Import full content with templates and clone mode:
+
+        $ bin\dev butler:pb:importpack -p customer_pack_id -f ./export/pack
+            -t sfusername@sandbox.com -a pdf_butler_user-ADMIN:admin_password
+            -e https://eu1.pdfbutler.com -s TEST -l --session <session_id>
+            --instance <instance_url> -m -c -d full
+
 FLAG DESCRIPTIONS
     -t, --target <value>
         Specifies the Salesforce org username credentials to connect to the target
@@ -652,7 +932,7 @@ FLAG DESCRIPTIONS
 
     --session
         This flag is used to provide a Salesforce Session ID for authentication.
-    
+
     --instance
         This flag specifies the Salesforce Instance URL. The Instance URL corresponds to the specific Salesforce environment (e.g., production, sandbox) you are connecting to.
 ```
@@ -713,7 +993,7 @@ FLAG DESCRIPTIONS
 
     --session
         This flag is used to provide a Salesforce Session ID for authentication.
-    
+
     --instance
         This flag specifies the Salesforce Instance URL. The Instance URL corresponds to the specific Salesforce environment (e.g., production, sandbox) you are connecting to.
 ```
@@ -744,7 +1024,7 @@ DESCRIPTION
 EXAMPLES
     Set settings:
 
-        $ sf butler pb admincredentials -t sfusername@sandbox.com -u 'username' 
+        $ sf butler pb admincredentials -t sfusername@sandbox.com -u 'username'
              -p 'ADMIN_password' --user-password 'USER_password' -l
 
         # Console output:
@@ -773,7 +1053,7 @@ FLAG DESCRIPTIONS
 
     --session
         This flag is used to provide a Salesforce Session ID for authentication.
-    
+
     --instance
         This flag specifies the Salesforce Instance URL. The Instance URL corresponds to the specific Salesforce environment (e.g., production, sandbox) you are connecting to.
 ```
@@ -919,3 +1199,10 @@ SOLUTION: When using the --stage flag, make sure to provide a valid CADMUS stage
 SOLUTION: When using the --config flag, ensure that you specify a valid directory path to docconfigs.
 
 ```
+
+- Error (1): DataSource import failed. Check the JSON and try again.
+
+```
+SOLUTION: Ensure PDF Butler package version is at least v1.505 and validate the DataSource JSON files.
+
+```