Custom Fields for Custom Connectors

Custom fields can be added in account configuration and then later used with custom connector the same way as email, username, domain, password, etc. There can be exactly 5 fields with editable values (but immutable names).

These values can be added while creating a new account, but they cannot be edited directly in the table. Instead, a new way to edit an account was introduced. Each row has a “pencil” icon that opens the account editing form with populated fields.

If there were any custom fields already saved, the panel is automatically expanded, and the user can see their values right away.
The custom field can hold any value: a single digit, some random text, an authentication token, etc. It accepts any string shorter than 1024 characters.

To be able to use saved custom field values together with the custom connector, users will need to update their launchers. 

From then on, user can add custom fields as arguments that will be passed when starting a new custom connector process during a test, for example:

CustomConnector.exe --custom1 "{custom1}"

Users can also change the command line and tell the test to take username, email, domain, and other values not from their dedicated field, but from custom fields. 

So, for example:

CustomConnector.exe --username "{username}" --password "{password}" --domain "{domain}"--resource "{resource}" --email "{email}" 

Can become:

CustomConnector.exe --username "{custom1}"--password "{custom2}" --domain "{custom3}" --resource "{custom4}" --email "{custom5}"

In some cases, users might want to test with an additional username and password, or an authentication token. Custom fields allow for this additional customization.

Custom fields can also be added when creating accounts in Swagger (API v5 and v6). Since it is optional, the property can be equal to null, or omitted altogether.