e
evi mattil
Snapshots should be usable for various purposes.
  1. To start the business in a new, empty account
  2. For the transfer of individual work processes — e.g. to set up an automated webinar with all the trimmings for an existing customer. (Then it is important to pass on EVERYTHING, i.e. automation with all CustomFields, tags, forms, trigger links, mail templates, etc. and links)
  3. To back up entire accounts before importing (e.g. entire snapshots; -), customers, etc.)
In case 1 + 3, the entire account is cloned (for 3, also gladly with all customer data)
Case 2 requires a smart import. We can't assume that we're the only ones developing the account. Perhaps there is already data from another agency; perhaps the account owner has already developed workflows himself and created tags and field names himself...
This requires a smart import for the snapshot. When importing, a matching process must take place for customFields, tags (tags then receive a unique ID, then the problem that nothing works anymore when the tag is renamed; -), trigger links, forms, custom values, etc. also disappears.
Why is that important?
Importing workflow snapshots currently results in a very complex adjustment process after the import, extensive testing is necessary and additional copying work is required, e.g. for mail templates. All of this effort can be significantly minimized. This makes it possible or significantly simplified to offer individual workflows
________________________________________
Snapshots should be usable for various purposes:
  1. To start a business in a new, empty account.
  2. To transfer individual workflows—for example, to set up an automated webinar with all the necessary components for an existing client. (In this case, it's important to transfer EVERYTHING, including automation with all custom fields, tags, forms, trigger links, email templates, etc., and links.)
  3. To back up entire accounts before importing (e.g. hole snapshots; -), clients, etc.).
In cases 1 + 3, the entire account is cloned (for case 3, should also include all client data, etc.).
Case 2 requires a SMART IMPORT. We can't assume we're the only ones developing the account. There might already be data from another agency; the account owner might have already developed their own workflows and created their own tags and field names. In this case, a smart import for the snapshot is necessary. During the import process, a matching process must be performed for custom fields, tags (tags then receive a unique ID, this eliminates the problem of renaming a tag and causing it to malfunction; -), trigger links, forms, custom values, etc.
Why is this important?
Currently, importing workflow snapshots leads to very complex adjustment processes after the import, extensive testing is required, and additional copying work is necessary, for example, with email templates. All of this effort can be significantly minimized. Furthermore, it becomes possible, or at least considerably easier, to offer individual workflows.
·