Run a Job

Learn how to run a job to generate a new data version in a project or for production.

Overview

When you add new data to Visier or change your transformation logic, you can run a job to generate a new data version. Depending on your needs, you can run a job in the production project or a draft project. Alternatively, you can set up a recurring job schedule to run jobs regularly. For more information, see Schedule a Job.

Note: Analytic tenants can have a maximum of 500 active processing jobs at any time, except free trial tenants, which have a maximum of 5 active processing jobs. Administrating tenants can have a maximum of 50,000 active processing jobs across all tenants. An active processing job is running, pending, or rescheduled. These maximums are the default, however, contact Visier Technical Support to request limit adjustments.

Run a job in a project

Who can use this feature?

Users with the following:

  • Profile capabilities: Data (Write, Detailed)

Users with the following can access the Jobs room in a project:

  • Additional capabilities: Manage Jobs

Not sure if you have this feature or capability? Reach out to your administrator.

Depending on your needs, you can run a job in the production or draft project. For example, quickly resolve a scheduled job failure by uploading a new file and running a job in production. When updating transformation logic, such as changing an extraction rule, run a job in your draft project to validate the data version before releasing it to users.

Jobs can be run in the Data Categories or Jobs room. When running a job in the Data Categories room, you can generate a partial data version and enable features such as alerts and the normalizer cache.

Note:  

  • Generated data versions may cause issues and warnings. For more information, see Data Issues.
  • Data versions generated in a draft project will not be published to production. To make the data version available in production, you must publish the project.
  • Run job for partial data version is a special data load job that allows you to select specific analytic objects to include in the job, rather than all the data in your tenant. This is useful for faster data testing because you can select only the data you're interested in validating. Partial data versions are only valid in a project; they cannot be published to production.

Run a job in the Data Categories room

  1. In a project, on the navigation bar, click Data > Data Categories.
  2. On the data category you want to create a new data version, click the More button .
  3. Click Run job or Run job for partial data version.
  4. In the Run job dialog, do the following:
    1. In Generate debugging info, select one of the following:
      • None: No debugging information is generated about the job. This is the default behavior.
      • For stages and records: Debugging information is generated at the end of each stage and provides the final result of a stage.
      • For stages, records, and rules: Debugging information is generated for all rules in each stage: business rules, system rules, and multi-subject rules. Jobs set to For stages, records, and rules run for longer because there is more information to generate.
    2. If For stages and records or For stages, records, and rules, select one of the following to define the level of detail to return about the debugging information:
      • Show file and line: Returns the file and line values for the data in the debugging information.
      • Show mapping: Returns the mapping names that correspond to the data in the debugging information.
    3. Enable or disable Use alerts. If enabled, all enabled alerts check the data in the job. For more information, see Data Alerts.
    4. Enable or disable Enable normalizer cache. If enabled, the normalizer cache minimizes source upload processing to improve job performance. We recommend always enabling the normalizer cache.
  5. If running a partial job, click Next and then select the analytic objects to include in the job.
  6.  Click Run Job.

    Result: After a job processes data successfully, a new data version is available. To view the new data version in a project, you may need to change the project's data version. For more information, see Set the Data Version.

Run a job in the Jobs room

  1. In a project, on the navigation bar, click Data > Jobs.
  2. In the Schedule tab, click Schedule job.
  3. In the Run job dialog, do the following:
    1. Enable the Run now toggle.
    2. Enable the Process data toggle.
    3. Select the data category you want to create a new data version for.
    4. Set debugging options by expanding the Advanced section:
      1. In Generate debugging info, select one of the following:
        • None: No debugging information is generated about the job. This is the default behavior.
        • For stages and records: Debugging information is generated at the end of each stage and provides the final result of a stage.
        • For stages, records, and rules: Debugging information is generated for all rules in each stage: business rules, system rules, and multi-subject rules. Jobs set to For stages, records, and rules run for longer because there is more information to generate.
      2. If For stages and records or For stages, records, and rules, select one of the following to define the level of detail to return about the debugging information:
        • Show file and line: Returns the file and line values for the data in the debugging information.
        • Show mapping: Returns the mapping names that correspond to the data in the debugging information.
  4. Click Schedule.

    Result: After a job processes data successfully, a new data version is available. To view the new data version in a project, you may need to change the project's data version. For more information, see Set the Data Version.

Run a job in the global workspace

Who can use this feature?

Users with the following:

  • Profile capabilities: Data (Write, Simple)

Not sure if you have this feature or capability? Reach out to your administrator.

Select administrators have access to the Jobs room in the global workspace. They can upload new files and run jobs to resolve scheduled job failures without the help of Visier Technical Support. If you don't see the Jobs room in the global workspace, you may have the ability to run jobs within a project instead. For more information, see Run a job in a project.

Note: Jobs in the global workspace will follow the release behavior defined for your scheduled jobs. For more information about your settings, see Release Behavior.

  1. On the global navigation bar, click Data > Jobs.
  2. Click Run Job.

    Result: A data load job starts. If successful, the data load job generates a new data version. If your release behavior is set to Auto-release latest, the new data version is immediately available in production.

You can monitor the progress of your job in the Jobs room. For more information, see Jobs. If the Jobs room doesn't list a job that you just started, the job may still be in the queue. Wait a few minutes and then refresh the Jobs list. When the job begins running, it will appear in the list.

Run a data load job for analytic tenants

Who can use this feature?

  • This is available to Embedded Partners

Not sure if you have this feature or capability? Reach out to your administrator.

To run jobs for your analytic tenants, open a project and navigate to Data > Jobs.

The Run Jobs button is located in the top-right of the screen, as shown next.

You use Run Jobs to run data load jobs for:

  • Production: End users see this data version when logged in.
  • Testing: The data version can only be previewed from the Jobs room. No other users see changes in the solution.

When the Run Jobs function is used to run a data load job, it uses the most recently uploaded data files, based on the current data load job definition. If the intention is to refresh the data in Visier with the latest updates from your external data systems, then we recommend that the SFTP mechanism is used to first transfer the latest data files, and then the jobs are triggered through the API request.

Tip: After a job runs successfully, you can preview the new data version in your tenant or analytic tenants. For more information, see Preview a Data Version.

There are several scenarios, which are described next, where you may want to use the Run Jobs functionality from within Studio in Visier.

Run a data load job and publish to analytic tenants

To run a job that immediately publishes a new data version to production and is visible to your end users, follow these steps.

  1. Open the production project.
  2. Navigate to Data > Jobs.
  3. Click Run Jobs.
  4. In the Job configuration dialog, do the following:
    • Optional: To run a data connector extraction job, select Extract data. If running an extraction job, select the Connectors to run jobs for and the extraction options. For more information, see Run a Data Connector Extraction Job.
    • Select Process data.
    • Set the Data category to the data category that you want to run the job. For more information, see Data Categories.
    • Select Make available for analytic tenants.

      The following screenshot shows running an extraction job in the production project to deploy immediately to end users.

  5. Click Next.
  6. Select the analytic tenants that are to have the new data version and run the jobs.
    • Select from list: Select tenants from the list of available tenants. You can select all tenants or a subset of tenants.
    • Enter as plain text: Type or paste a list of tenants in plain text. Separate each tenant with a comma or space; for example, WFF_j1r~c7o,WFF_j1r~i1o.
  7. Click Next.
  8. In Confirmation, review your selection, and then click Run Jobs.
  9. In the Jobs room, view the progress of these jobs.

Run a data load job without publishing to analytic tenants

To run a job that doesn't publish to production, follow these steps. This allows you to verify that the data load job included the intended data updates without exposing the data version to end users.

  1. Do one of the following:
    • Open the production project. This allows you to run a data version on the production version without exposing the data version to end users.
    • Open a draft project. This allows you to review the changes in one or more analytic tenants without changing the production version.
  2. Navigate to Data > Jobs.
  3. Click Run Jobs.
  4. In the Job configuration dialog, do the following:
    • If using a draft project, select one of:
      • Run job for the latest production version. This runs a job in the project based on the latest production version. If selected, you can optionally make the data version available to analytic tenants.
      • Run job for the current project. Requires at least one project revision and no uncommitted changes.
    • Optional: To run a data connector extraction job in production, select Extract data. If running an extraction job, select the Connectors to run jobs for and the extraction options. For more information, see Run a Data Connector Extraction Job.

      Note: Only available if Run job for the latest production version is selected.

    • Select Process data.
    • Set the Data Category to the data category that you want to run the job. For more information, see Data Categories.

      The following screenshot shows running a processing job in a project based on the latest production version without deploying to end users.

  5. Click Next.
  6. Select the analytic tenants that are to have the new data version and run the jobs.
    • Select from list: Select tenants from the list of available tenants. You can select all tenants or a subset of tenants.
    • Enter as plain text: Type or paste a list of tenants in plain text. Separate each tenant with a comma or space; for example, WFF_j1r~c7o,WFF_j1r~i1o.
  7. Click Next.
  8. In Confirmation, review your selection, and then click Run Jobs.
  9. In the Jobs room, view the progress of these jobs.