Tenant Environment Setup application
Use the Tenant Environment Setup application to specify the following for your environments:
- Default time zone, language, and support of additional languages.
- Default product family and module for all newly created metadata.
- Default theme, interface design, and user interface settings.
- Service administrators.
- Activated solutions.
- Single sign on options.
- Global settings, such as default lifecycles.
Learn more in Tenant Environment Setup application, Single Sign On configuration, Support additional languages on the platform and Time zones.
API Keys
Register API keys within the system to:
- Authenticate third party endpoints, such as Google maps and weather widgets.
- Enable large language models.
Learn more in Client API keys setup and Enable AI models in your environment.
Email domain
Optionally, set up a custom email domain which the platform can send emails from.
Learn more in Email domain setup.
Automated record processing
Optionally, create automated record processing events with:
- Scheduled jobs—Specify the specific time and requirements for when a job runs to process records.
- Record patch processing—Specify a time limit or defined number of records which initiates a job to process records.
Learn more in Scheduled jobs and Record batch processing.
Support additional languages on the platform
Support additional languages across your environments to allow your users to access the platform in those languages.
When you support an additional language, users can select a different locale in their User Settings menu to see the platform's user interface and applications in the language of that locale. Additionally, some formatting elements may change to match those used in the region.
For example, setting your locale to English (United States) displays the date November 14th, 2025 as 11/14/2025, whereas the English (United Kingdom) locale would display it as 14/11/2025.
Support a language
Use the Tenant Environment Setup application to support different languages. Each Base record in the Locale Settings application step represents a language you can support. The available options are determined by your contract with Nextworld.
Use the Support Language row action on the language you need to enable, and then select Prepare Plan. After you're notified that the job is complete, there is a new Owned record in the Locale Settings application step for that language. This indicates that the language is now enabled in your environments, and you and your users can select the new locale in your user settings.
Learn more in Tenant Environment Setup application and Locale Settings application step.
Owned metadata and translations
When you support a language, all platform elements and Base metadata can be accessed in that language. If you have any Owned metadata objects, however, you are responsible for managing the translatable values for those objects. If you don't translate these objects, they display in the default language regardless of your locale setting.
Both customers and solution development partners may have Owned metadata that they may need to translate. Learn more in Metadata translations.
Time zones
Components of the platform, such as DateTime fields, logic blocks, and application settings, reference and use time zones in different ways. Time zones can be set at the tenant level, within user profiles, or dictated by the browser, depending on how an environment has been configured.
System administrators can set a default time zone for an environment within the Environment step of the Tenant Environment Setup application. The system determines what time zone is used based on the Display Preferred Time Zone checkbox for that environment. Learn more in Environment application step.
Options include:
- Display Preferred Time Zone selected—The system looks for a Custom Time Zone in the User Profile. If no Custom Time Zone exists, it uses the Default Time Zone for that environment. If no time zone is selected, the system uses the default time zone configured by the platform.
- Display Preferred Time Zone cleared—The system looks for a Custom Time Zone in the User Profile. If no Custom Time Zone exists, it uses the user's browser's time zone.
Custom Time Zone
Optionally, users can also select a custom time zone in their User Profile. If a custom time zone is selected, other time zone settings are ignored.
Learn more in Custom Time Zone.
Client API keys setup
System administrators configure API keys with the API Key Setup application. API keys authenticate third party endpoints, such as Google maps, weather widgets, and artificial intelligence that can be used in the Nextworld Platform.
To integrate with an external system with an API, you need to acquire the system's API key. The steps on how to acquire them are found in the table below.
| System | Function | User Responsibility |
Google Javascript API—Enables map visualizations based on latitude and longitudeGoogle Geolocation API—Displays map visualization when used with address as a data point. |
| |
| Open Weather |
|
|
| Global Payments |
|
|
| Open AI | OpenAIGPT API—Enables the use of:
|
|
Once the API keys are obtained, you must register them in the API Keys application. Each provider many only have one record in the application. View a list of available providers in the API Key Provider Catalog application. Learn more in API Key Provider Catalog application and API Key Setup application.
Once the API key record is created, the endpoints begin to work If the proper API key is not obtained, core functionality is not impacted, but maps, weather, and payments won't work.
API Key Setup application
System administrators use the API Key Setup application to register API keys. This allows third party endpoints, such as Google maps and weather widgets, to be used in applications and dashboards.
To integrate with an external system, you need to acquire the system's API key. Learn how to acquire system API keys in Client API keys setup.
Once you acquire the API key, you must create a new record for the provider and enter the key. Only one API key should be registered in the application for each vendor and API type combination. If the proper API key is not obtained, core functionality is not impacted, but maps, weather, and payments won't work.
To view a list of available API key providers, open the API Key Provider Catalog application. Learn more in API Key Provider Catalog application.
API Key Provider Catalog application
Use the API Key Provider Catalog application to view the external systems, also known as providers, which have endpoints available for use in the platform. Endpoints enable use of features such as Google maps, weather widgets, and artificial intelligence.
The list form of the application shows a record for each provider supported on the platform. For example, Global Payments or Google Analytics. In order to enable use of the provider's features, you must obtain the provider's key then create an API key record in the API Key Setup application. Learn more in API Key Setup application and Client API keys setup.
Email domain setup
A system administrator can set up a custom email domain. This allows Nextworld systems and applications to send emails from the custom domain.
Prerequisites
Contact Nextworld Support to request that the email domain be configured for your tenant. This configuration must be completed before proceeding to the steps below.
Complete preliminary setup in Nextworld
1. In the Email Domain Management application, Create a new domain.
| Customer Internet Domain | MyDomain, which is your custom domain name. For example, nextworld.net. |
|---|---|
| Primary Customer Domain | Optional. Set to True if you have multiple custom domains and the current domain represents your primary, default domain. |
| Verification Email Address | Optional. Enter an email address that should be used to test the domain setup with the Send Test Email form action. |
2. Save the record, then use the Generate Verification DNS Tokens action to update the DNS records for the new domain.
3. If you exited the domain record during your save, reopen the record. Verify that the Domain Identity Verification Token field has been populated, and that the Easy DKIM CNAME Records subtable includes at least one Easy DKIM CNAME Record.
Configure your domain server
In your DNS provider, modify the DNS records:
1. Add the Nextworld Domain Identity Verification Token to your domain name:
| Host/Name | _amazonses |
|---|---|
| DNS Record Type | TXT |
| TTL | 1 hour (recommended) |
| TXT Value / Data | "record"where record is the Easy DKIM CNAME Record name. For example: Note that the quotation marks are required. |
2. Add each of the Easy DKIM CNAME Records in the subtable to your domain name’s DNS:
Verify configuration in Nextworld
1. In the Nextworld Email Domain Management application, use the Update Verification Status action to determine whether the DNS records have been updated. Depending on your domain provider, DNS records can take up to 48 hours to update.
When the Domain Verification Status is Verified for the domain record, the DNS has propagated and the domain is ready for use in Nextworld.
2. Optionally, use the Send Test Email action on the domain record to send an email to the address specified in Verification Email Address. If the domain setup is complete and a test email address was specified, Nextworld sends a confirmation email from no_reply@MyDomain. For example, no_reply@nextworld.net.
Record batch processing
System administrators can enable record batch processing to efficiently process records regardless of the volume of transactions in a table.
Record batch processing is similar to a scheduled job to process records. However, rather than running at a specific time, processing occurs either when a defined number of records are ready to be processed, or when a defined time limit is reached.
Each record batch is created with certain parameters, including the:
- Table—Where to retrieve records from.
- Filter Criteria—Which records should be processed.
- Target Batch Record Count—The number of records that causes a batch to begin processing.
- Maximum Delay—The maximum amount of time which should elapse before the batch begins processing, regardless of the number of records that are ready to be processed.
For example, a batch definition over the General Ledger table could filter for records with a status of Ready for Batch Processing, a target record count of 1000, and a maximum delay of one hour. This would ensure the records are processed whenever 1000 records with a status of Ready for Batch Processing exist in the table, or hourly if the record volume is not reached.
System administrators must create setup records for record batches within their tenants. Learn more in the following topics:
- Record Batch Setup application
System administrators use the Record Batch Setup application to debug and activate record batch definitions.
- Record Batch Status Inquiry application
System administrators use the Record Batch Status Inquiry application to review the status of batch definition records which have been processed.
Application developers create record batches in the Record Batch Definitions application. Learn more in Record Batch Definitions application.
Record Batch Setup application
System administrators use the Record Batch Setup application to debug and activate record batch definitions.
Select the Populate form action to load records for every batch definition record created in the Record Batch Definitions application. Enter the lifecycle you want the batch to process in, the user the batch job should process as, then activate the record.
Optionally, select the Run Now row action to process the batch definition.
Review the status of batch records which have processed in the Record Batch Status Inquiry application. Learn more in Record Batch Status Inquiry application.
Batch definitions are created by application developers in the Record Batch Definitions application. Learn more in Record Batch Definitions application.
Record Batch Status Inquiry application
System administrators use the Record Batch Status Inquiry application to review the status of batch definition records which have been processed.
Open a record to view information about the batch, such:
- How many records were processed.
- The filter criteria used to select the records.
- Diagnostic information, such as success or failure, about the processed batch.
Batch definitions are created by application developers in the Record Batch Definitions application. Learn more in Record Batch Definitions application.
System administrators create a record in the Record Batch Setup application to debug, activate, and run the batch definition. Learn more in Record Batch Setup application.