Job Manager Discontinuations

Previously former assignees lost participant status upon task completion, limiting their access to previously handled jobs. This functionality has been changed in version 8.0 to improve workflow visibility and user experience. User task assignees now retain participant status after completing their tasks, ensuring continued access to previously handled jobs. You cannot revert to the old behavior. See Former Assignees Automatically Added as Participants to Jobs.

Effective version 8.0 you can no longer edit the unique name for job types.

Previously, you could:

  • Edit the unique name of job types

  • Not edit the technical name of job types

  • The technical name now serves as the primary reference for job types

  • You can edit technical names at any time

  • The API now references job types using their technical names

The API endpoint for accessing job types now uses the technical name

With version 8.0, permissions have been consolidated. Instead of multiple permissions, only two are now required.

The following legacy entries have been removed:

  • MANAGE_DEFAULT_TYPES

  • MANAGE_OBJECT_NUMBERS

  • MANAGE_TYPE_CATEGORIES

  • MANAGE_TYPES

  • MANAGE_TYPE_CONFIGURATION

  • MANAGE_VARIABLE_ACCESS_AND_RIGHTS

  • MANAGE_DATASHEET_LAYOUT

  • PUBLISH_DSE_CHANGES

The following two permissions take over the functions of the removed permissions. They can be assigned to an administrator role.

  • Manage Jobs

  • Manage Products

To administer the Data Hub module, you need an administrator role with these two permissions enabled.

Note

The following previously used entries are still visible and selectable under > Permissions when editing a role, but their assignment to the role has no functional significance:

• Consume JMS Messages

• Show Blueprint Jobs

The SOAP interface for Job Manager and Marketing Data Hub has been removed. This interface was previously replaced by the REST API in versions 7.3 and 7.4.

If you were using the SOAP interface, you must migrate your integrations to use the REST API.

You can find detailed information about:

  • REST API endpoints and authentication

  • Code examples

in our API documentation.

Note

Need help with the migration? Contact our Support team through your usual support channel.

The ability to inject code before the system build process in Job Manager has been removed to improve system stability and security.

You can now add custom JavaScript code through the Job Administration interface. This provides a more secure and maintainable way to customize job processing.

If you use code injections in Job Manager, you need to:

  • Export your existing code injections

  • Move your customizations to the new JS inject field in DSE administration to run on the search page or individually in a job type on the data sheet.

Previously, it was possible to create custom Rich Text Editor configurations, including the ability to import InDesign styles, for use with Job Manager and Data Hub variables. As of version 8.0, these configurations are no longer usable with datasheet variables. As part of upgrading the Job Manager Rich Text Editor, we have replaced the previous custom configurations with a set of new configuration presets. When configuring a Rich Text Editor field on a Job Manager variable, you can now choose between the Minimal, Standard, and Full presets instead of having to set up custom configurations.

The Task Manager functionality has been removed from the product. This change streamlines our system, focuses resources on actively used features, and paves the way for a new standalone task management solution in the near future.

The Resources sub-module has been removed from the Jobs module. This change eliminates the calendar-based task management and resource allocation features.

The job type Only Briefing has been discontinued and is no longer available in the list of job types when configuring a job.