The term "service account" as used in the assembly editor is equivalent to a named app connection:
So the above 123FormBuilder app has 3 service accounts named "Default", "another test", and "bobtest".
The first connected account is always named Default.
End users must enter unique names for any additional connected accounts.
Accounts are associated with credentials needed to access API endpoints on the user's behalf.
Certain modules in the Assembly Editor need to reference API credentials. They are:
- OAuth modules
- Service Credential modules
By default the Assembly Editor's settings has the "show service account fields" setting disabled:
When the Show service account fields setting is disabled, modules that have service accounts don't show the service account field:
Typically when building triggers and actions in the Assembly Editor, development and testing is done using a single connected account, the Default account. Service account fields are unused and their presence is distracting since they are always empty.
Checking the Show service account fields setting causes them to appear:
When the fields are blank they reference the Default account.
Entering any other value will cause the modules to attempt to load credentials for the specified app using that entered name.
If the credentials are not found, an error occurs.
Entering service accounts manually in the Assembly Editor can be needed when troubleshooting, in the case where a user is having trouble with a certain connected account.
Service account fields also make it possible to build assemblies that reference multiple accounts.
The Automation Editor does not know if a trigger or action references multiple service accounts.
It is up to the developer of the trigger/action to inform users that they must connect certain named accounts that the assemblies expect to exist.