Configurations in your app can be used to set authentication for web services, containing app specific values, or mailbox credentials. Configurations are environment dependent, which means their value will be different in each of your apps. This includes copies or “sandboxes” of your apps. You can access the configurations screen by going to Settings > Configurations.
The navigator is the black bar at the top of your screen.
Here’s what everything does:
+New: This button opens a window where you can create a new template.
Question mark [ ? ]: By clicking this button, a new panel pops-up. This panel has a small video that shows you how to create a new configuration, as well as links to some helpful articles.
Search bar: Here you can search for templates by description, kind or HTML contents.
Creating a new configuration
You can create a new configuration by pressing the + New button on the navigator.
Here you can define your configuration by selecting its type, entering its name, and filling in the required values.
Kinds of configurations
There are 11 kinds of configurations that you can create in Betty Blocks, and each serves their own purpose.
You can use these to connect to web services that require you to use a client certificate to connect to them. You can choose between a
Pem certificate or a
Pkcs12 certificate. How to set up a Client Certificate Authentication can be found here: HowTo create a Client Certificate set-up
You can use custom configurations to save environment specific values. This means it can hold different values throughout your entire application development street. When a new Custom Configuration is merged to a new environment, it holds no value. More information about Custom Configurations can be found here: What are sandboxes?
Exact Online XML
This type of configuration can be used as authentication to send and receive XML data through an Exact Online integration. After creating one, you are redirected to Exact Online's login screen, prompting you to enter your credentials. If done successful, you are then redirected back to your application with the authentication in place.
If the webservice you want to use uses HTTP Basic to authenticate, you can use this. You’ll need to pass along a username and a password. This will generate a Basic Auth token in
You can use this kind of configuration to configure a mailbox service. You’ll need to enter the mail service's address, its port, and your username and password. More information about mailboxes can be found here: What is a mailbox and HowTo create one?
You can use this kind of configuration to set up web services using OAuth1 to authorize access. You’ll need to enter a client key and secret, as well as a token key and secret.
You can use this kind of configuration to set up web services using OAuth2 Basic. You have to enter a token credential uri as well as a client. You can also add extra attributes or use an authorization uri or a client secret.
This type of configuration should be used when trying to authorize with an OAuth2 app using JWT as its token protocol. If you don’t know what any of this means, you probably won’t need to use it. You have to fill out all of these fields if you’re planning on using an OAuth2 JWT web service.
This type of configuration should be used when you want to authenticate with Signhost, using the (soon to be deprecated) Sign document action event. If you're using our Http request action event, use normal authentication, as mentioned in their API documentation. More information about Signhost integrations can be found here: HowTo create a Signhost integration in Betty Blocks
If you want to use an SFTP server integration, you'll need SSH authentication. You can decide to use key auth or a plain password, as well as use a generated key or a custom one.
This configuration is used for the (soon to be deprecated) Twinfield action event. If you're using normal Http request events, stick to the method explained here: HowTo create a Twinfield integration in Betty Blocks.
Editing or deleting a configuration
You can edit a configuration by clicking on it and pressing Edit. Here you can change the contents of your configuration, such as usernames and passwords or API keys.
You can also delete a configuration by pressing the Delete button in the bottom left of the screen while you’re editing it.
Before you delete a configuration however, you’ll want to make sure nothing important depends on it, or it might break! Thankfully, Betty Blocks has an integrated tool to help you check. You can find more about it on the What are Dependencies? page, but in short; when you press the edit button on a configuration, you can see what depends on it by clicking on the dependencies button.
Using a configuration
You can use a configuration by selecting it inside of your web service, or other feature. Make sure to select the proper authentication type, or you won’t be able to select it!