The System settings contain settings and information related to the overall workings of the system running your Dynamicweb solution, as well as high-level settings for the solution iteself.

The Solution settings (Figure 2.1) contain high-level settings related to the Dynamicweb solution.

Figure 2.1 Solution Settings - Part 1

From the first part of the solution settings page you can:

  • View/edit the solution title, the system email an the copyright information
  • Customize the login screen information - the logo, the partner information, the solution login info, and the partner email

You also have access to the settings in Figure 2.2.

Figure 2.2 Solution Settings - Part 2

With the second half of the settings you can:

  • Restrict non-administrator users (incl. admins) by:
    • Disabling save username and password
    • Locking the template folder, the system folder, the entire Settings area or the developer node or items node within the Settings area
    • Disabling edit links in layout selectors
  • Set up a custom error page for HTTP Error 404:
  • Disable logging on the shopping cart, payment gateways & checkout handlers. This may lead to a performance improvement.
  • Force ssl on /Admin to redirect all /admin calls to https://

Finally, you may set the default pdf page size for pages generated with the &pdf=true command.

The solution report lets you review solution information and purge logs and statistics (Figure 3.1) – which can be a major resource drain on large or old solutions.

Figure 3.1 The Solution Report node

The Version settings (Figure 4.1) contain read-only information about the current version and any custom license configurations pertaining to for the solution.

Figure 4.1 Version settings

Neither users, admins nor administrators are allowed to change these settings.

Please bear in mind that extended variants and language versions count as a products in regards to the product limit.

Items placed in a folder do not count towards the item limit.

The Global Settings node is available to Administrators only, and lets you access and edit the contents of the GlobalSettings.aspx file directly from the backend.

Please do not edit the Global Settings unless advised to do so by someone who knows exactly what the settings do – any changes you make can have wide-ranging consequences.

Scheduled tasks are tasks which have been configured to run at certain, scheduled, intervals.

For instance, you can set up a scheduled task for rebuilding your indexes, for scheduling emails, or for running batch integration jobs.

The scheduled tasks node gives you access to a list of all scheduled tasks created on the system (Figure 6.1).

Figure 6.1 Scheduled tasks

From the list of scheduled tasks, you can view, run or edit the tasks – or remove them altogether. You can also right-click an existing scheduled task and copy it.

If you need to use custom credentials to run a task you can use the Impersonation button to set them up – this is required if your solution is not hosted by Dynamicweb. Instead, use the credentials for the target windows server environment.

From Dynamicweb 9.3,  you can see when taskexecuter was last executed on this solution above the scheduled task list - the normal interval is every 5 minutes - and will be informed if there is a problem with the serverside scheduled task job.

Scheduled Tasks on SSL servers

You may experience problems with executing scheduled tasks on SSL servers - this is because previous implementations of Scheduled Tasks did not add the -k (--insecure) parameter to tasks on the IIS.

The solution is to delete the task scheduler in Windows Task Scheduler, and force Dynamicweb to create a new instance by creating a new scheduled task.

You can also edit existing tasks and add the -k parameter manually.

While most scheduled tasks are created automatically from other parts of the system, you can also create scheduled tasks manually by clicking Add in the toolbar to open the scheduled task configuration view (Figure 8.1).

Figure 8.1 Creating a scheduled task

Here you can define the task name, the start time and end time, and the repetition interval, and you can see the Activation URL, which can be used to trigger the scheduled task remotely.

You can check Set next run time based on end time to base the next run time on when the task has ended instead of when it was begun.

Each task must also have an action (“activation”) associated with it – your options are:

  • Trigger an URL (e.g. a data integration job URL)
  • Call a Method from the API
  • Select an add-in, such as Clean up logs or Run SQL add-in

The following scheduled task add-ins are available out of the box:

Add-in name


PIM Email Notification Add-In

Evaluates & triggers out PIM notification emails.

Build Ecommerce Assortment Items

Rebuilds assortments

Calculate users smart search results

Recalculates user smart searches

Cleanup logs

Evaluates and triggers automatic log cleaning rules

Place recurring order

Places recurring orders

Redeem expired points

Removes expired loyalty points from user accounts

Run SQL add-in

Executes the SQL query defined on the add-in


The Edit super users node allows you to edit your admin and administrator users (Figure 9.1).

Figure 9.1 Editing super users

From here, you can reset passwords and add an email to a super user account.

Only administrators may edit the administrator account, admins are limited to editing the admin account.