Continuous jobs have more robust filtering

Created on 7 September 2021, almost 3 years ago
Updated 19 October 2023, 8 months ago

Problem/Motivation

When creating a continuous job you can only tell them to create job items based on limited settings. ex) only content types. The issue here is some translator plugins cost money per transaction as well as require time from a team to translate.

Proposed resolution

Create a submodule that people can enable if they wish to have a more advanced filtering strategy on what content is continuously sent to a translator.

This module would enable the following things:

  1. Update the continuous job form (add/edit) so that when you select a content type you can also see all fields on that content type. For now select lists and boolean fields have been added. Allowing users to specify what content they wish to send automatically to a translator.
  2. Logic for limiting the job creation based on the jobs new field configuration.
  3. Add form settings to limit the creation based on creation of new content or updating existing content.

Notes: More field support could be added going forward, but in order to keep this simpler. Only select lists and boolean fields on the content type are being added.

✨ Feature request
Status

Needs review

Version

1.12

Component

Source: Node

Created by

🇺🇸United States Dan Kolbas

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024