Blueprint Enhancements

Open
Subscribe

R	Robin S

This currently works just great for what it was designed to do. That is for a White Label or Black Label account owner to push a prebuilt account (or addons) to their own sub account owners.

1 limitation is that as built now, all the original flow, pipeline, form and site etc development has to be done in the primary account. It would be a lot more practical if these builds could be done in a sub account owned by the BL/WL owner (or even a totally separate account).
The following use cases as well as the above challenge could in my opinion be satisfied with some enhancements to the current build.

1. While the FT team do take full system backups, these backups (like most SaaS platform backups), are for a major disaster where the complete platform needs to be recovered. Backups of this type do not lend themselves to the recovery of data or configurations in individual accounts in the case of either accidental or malicious corruption or loss of data etc
2. There are many cases where an account owner (be it a BL/WL or just a regular) account owner has built some solution and wants to share with other FT owners
3. An independent consultant could have their own FT account where they develop sites, flows etc for their clients.

I would speculate that the current implementation od Blueprints is comprised of 3 major components.
1. The module that allows a Blueprint to be defined
a. Runs only on a BL or WL account
2. The module that ‘sends’ a Blueprint to a sub account
a. Runs only on a BL or WL account
3. The module that receives and applies a Blueprint
a. Runs on all types of accounts

What enhancements would be required to solve the above use cases?
1. The Blueprint definition module
a. Allow this to run in all account types
b. Add a ‘Backup’ variant of a Blueprint to this module
i. In the backup variant in addition to defining the various sites, flows, pipelines etc to be included, also allow for the various sets of data from Contacts, Flows, emails, Pipelines etc to be saved
2. The Blueprint ‘send’ module
a. Add the ability to schedule these to run on a recurring schedule defined by the account admin (just like a recurring calendar event)
b. In addition to the current capability for a BL/WL account to push Blueprints to sub accounts, for all accounts provide the ability to specify a target location for these backups to be stored
i. Google Drive
ii. Drop Box
iii. One Drive
iv. Send to an email address
v. Other possible options
3. The Blueprint ‘receive’ module
a. Allow this to be manually initiated if desired
b. Allow the module to also receive the Blueprints to process from other external sources such as:
i. Google Drive
ii. Drop Box
iii. One Drive
iv. Send to an email address
v. Other possible options

01/19/2023 -

Wishlist

Voters 18

Blueprint Enhancements