Shared auths and data (Static Slots)
For some Embedded Solutions it may be that you want to use shared authentications or set project config data to be the same value across all solution instances, without allowing the End User to set or change them. In this you can use what we call 'Static Slots'.
This is useful in cases where you wish all the End Users of your Solution to make use of the same authentication for a particular service, rather than having to administer multiple personal authentications.
An example of this might be if you have an FTP server with a company login, and you wish all your End Users to make use of this. Or you might have a company login for a service like Hubspot or Salesforce.
1. Setting a static authentication
In order to set a static authentication you need to:
- In the source workflow that your solution is based on, create the 'master' authentication for the service in question
- In the solution editor, move the authentication to 'hidden' and tick the 'make static' box:
Drop-down lists associated with a static auth
Note that any drop-down lists associated with the service that your solution statically authenticates to will be connected to the same static authentication.
For example, if you have used config data to allow the End User to choose from a list of Salesforce record types or Slack channels, then the record types or channels available will depend on what the static authentication has access to.
2. Setting static config
In order to set project config data as static you need to:
- Set the config data and give it a default value
- In the solution editor, move the config data to 'hidden' and tick the 'make static' box:
Updating static slots
If you need to update a static slot (e.g. creating a new authentication or changing the default value for config data), then you will need to change this in the source workflow and then publish a new solution release