JOBS

In CLOUDFLOW JOBS you can manage Jobs.

What is JOBS

JOBS is a CLOUDFLOW module that can handle Jobs. You can create new Jobs, manage existing Jobs and interact with them.

JOBS is integrated in the workflow engine. It is therefore very flexible and it can be linked with your production flow.

JOBS comes with a predefined user interface that cannot be changed.

What is a Job

A Job is a collection of different information types that belong together. It contains data and assets.

Data:
  • Job Name
  • Status
  • Description
  • Custom data (such as customer name, printing process...)
  • ...

All Jobs data are stored in the database in a dedicated Jobs collection.

Assets:
  • Files
  • Folders

How does it work?

There are dedicated nodes for the actions you want to perform with JOBS. See Jobs for an overview of all the Job nodes.

Working with JOBS comes down to three main concepts:
  • Creating a Job.

    A Job is created by the Create Job node.

    Anyone (with the right permissions) can create a Job. It is not limited to internal employees of your company. For example, you can easily set up a web portal for your customers or suppliers and give them the possibility to start a workflow that creates a Job.

  • Interacting with an existing Job.

    Interactions with an existing Jobs are also driven by specific nodes in a workflow. For example, the Update Job node allows you to update the status of a Job or add additional files.

  • Managing an existing Job.
    There are various possibilities to overview and manage existing Jobs:
    • Since Jobs are driven by a workflow, you can use KIOSK.
    • You can use the Job list.
    • You can use Form Builder or Pagebuilder to build a web portal. This way, external parties can both start and manage their Jobs.

What can you use it for?

JOBS is a very versatile module in CLOUDFLOW and can be used for many application fields. For example:

  • In a prepress environment where prepress operators use JOBS to add prepress information such as metadata, file information... to a Job. The operator can use KIOSK to browse and manage the Jobs.
  • In a more extended environment where different parties such as operators, customers, suppliers... are involved. Customers could use an external tracking portal to place an order, while internal parties could use it as an internal tracking portal.
    Important: The default JOBS user interface cannot be changed. If you want to extend the use of JOBS with custom portals, this is outside the scope of the default JOBS user interface. See Use case for a an example of a such a JOBS use case.
  • ...
Note: The API contains functions dedicated for Jobs (job.*). They are available on http://<server>:<port>/?api#job.