You have reached the support section of Enfocus.com. This content is only available in English.
You have reached the support section of Enfocus.com. This content is only available in English.
From this version onwards, you are no longer obliged to use the Switch Designer on your Switch Server. Now that we implemented the Remote Designer, you have the possibility to administer your Switch Server wherever you want. You can use only one Designer at the time (local or remote), but you can install it as often as you like, on a MAC and a PC.
How to set up Remote Designer
How to launch Switch remotely, i.e. using Remote Designer
In earlier versions of Switch, the Users pane was only used to set up access rights for users accessing Checkpoints or Submit points in Switch Server for SwitchClient. Hence, it was only available if you activated the SwitchClient module.
From this version onwards, the Users pane is always available and has an extra functionality: it allows you to set up the user rights for Switch Remote Designer.
The Users pane has been fully redesigned. It is now easier to configure users and user groups and to assign them the permissions they need.
In the left part of the pane, you can configure users and user groups, and assign them permissions for SwitchClient and Remote Designer.
In the right part of the pane, you can grant users and user groups access to particular Submit points and Checkpoints.
About users and user groups
In the previous version, there were a number of predefined user roles linked to certain permissions/access rights. From Switch 12 onwards, “roles” are no longer used.
You are now free to configure your users and user groups, and assign them the permissions they need.
Remark:
When upgrading from an earlier version, all users (including users with an “Operator role”) will be converted to regular users. You will have to reconfigure their access rights.
How to configure users and user groups
Proceed as follows:
If you want to use Switch Remote Designer:
Configure access rights for Switch Remote Designer:
Depending on what the user is allowed to do with Remote Designer, select:
How to configure access rights for SwitchClient Submit points and Checkpoints
For each Submit point/Checkpoint used in your Switch flows, you must define which users/user groups have the right to access it.
Proceed as follows:
What can users do in the Submit points or Checkpoints they have access to?
This depends on:
Only Administrators can unlock jobs.
From this version onwards, you can assign access rights based on your existing Active Directory users and user groups. In that case, you don’t need to create new users or groups in Switch, you can easily import them from your Active Directory.
How to set up Active Directory in Switch
1. Open the User preferences dialog in Switch
2. Select Active Directory settings.
3. Enter the address of your AD (Active Directory) server, and the user name and password to log on to your AD server.
How to import users and user groups from your Active Directory:
If you selected an AD group, the group name and the group members are displayed in the Groups category in the Switch Users pane.
If you selected an AD user, the user name, full name and email address are displayed in the Users category in the Switch Users pane. Note that these details are read-only.
5. Configure the permissions for SwitchClient and Remote Designer if necessary. This is done in the same way as for other Switch users and user groups.
With the introduction of the Remote Designer, we changed the default behavior of the preference “Start Switch Server automatically at login” to “YES”. Note that the preference “When exiting the flow designer” is only taken into account when “Start Switch Server automatically at login” is “No”.
We added a menu item to be able to stop the Switch server completely e.g. for maintenance reasons. This applies only to Local Designer.
In earlier versions of Switch, we stored enormous amounts of messages in the message database. The amount of messages was so big, that complex installations could have problems with the large number of messages and it could happen that Switch slowed down or even crashed. Therefore we changed the message handling.
Switch now stores only messages about the Server that are independent of individual jobs or elements. Switch stores as well all error and warning messages about jobs and elements.
When logging to text files is enabled, all messages (including job/element related messages) are stored in the text files.
“Logging ftp interaction” will still be done in separate files.
When enabling debug logging, assert messages are also stored in the Switch message database. All other debug logs are only written to text files.
When exporting to xml logs, only messages stored in the message database are exported.
When logging to text files is enabled, we create a new file every 10000 messages and every day. The file name of the text files contains the date in form YYYYMMDDHHmmss to make it easy to search for logs of a certain time. The cleanup log messages preference will also clean up the text files older than x number of days depending on this preference.
Note: As a scripter you still have access to all messages to be able to debug your script.
Split PDF and Merge PDF now support concurrent instances.
Those are the most important bugs fixed:
Number
|
Description |
27463 |
In some cases Switch Service crashes when updating XMP info. |
28155 |
Files are cut off at 1 GB when Switch sends them via FTP to certain FTP servers. |
28677 |
Memory corruption after licensing issues. |
28887 |
Rename is not working when there is a + in the file name. |
29050 |
Designer crashes on flow update when multiple flows are selected. |
29257 |
Server crash after unsuccessfully stopping a script process. |
29620 |
Switch Server on Windows doesn't clean up subfolders if they only contain hidden Mac system files. |
29746 |
Crash when using finalize Processing function in combination with certain external scripts. |
29624 |
The Inject job tool creates a new job ticket every 30 seconds when not set up to do so. |
29924 |
The Job.FailMessage variable is not filled in when a job is moved to the Problem jobs folder, because Switch terminated the script. |
30114 |
Service is closed by the Watchdog when a crash happens in PitStop Server. |
30194 |
Switch is not able to restart after it started an external process . |
30323 |
Can't connect to a certain SFTP server . |
30456 |
Random Server crash on communication with SwitchClient |
30461 |
Random Server crashes when multiple clients connect to the same server. |