Jobs and processes

In iDMS, jobs and processes define how data is handled, transformed, and moved within iMIS. Understanding how jobs and processes work together is essential for building efficient, reliable data workflows.

Whether you are importing data, updating records, or integrating with external systems, all work in iDMS is performed through jobs.

In This Article 

What is a job?

A job is a configured task that performs a specific action on data. Jobs are created and executed within iDMS modules such as iImport, iUpdate, iTransfer, and iWorkflow.

Each job defines:

  • The source of the data (file, query, or API)
  • The action to perform (insert, update, delete, transfer)
  • The mapping of data to iMIS fields
  • The matching criteria used to identify records

Jobs can be run manually or scheduled to run automatically.

What is a process?

A process is a sequence of one or more jobs working together to achieve a larger outcome. Processes often involve multiple steps and may span across different iDMS modules.

Processes are commonly implemented using iWorkflow or by combining jobs with iSchedule.

Working together: Jobs and processes

Jobs are the building blocks, while processes define how those jobs are connected and executed.

Example process

The following is an example process:

  • Import data from a spreadsheet using iImport
  • Update records using iUpdate
  • Schedule the job to run nightly using iSchedule
  • Send data to an external system using iTransfer

In this example, each step is a job, and together they form a complete automated process.

Job lifecycle

Jobs in iDMS follow a general lifecycle:

  • Create – Configure the job, including source, mapping, and matching
  • Test – Run the job with a small dataset to validate results
  • Execute – Run the job manually or schedule it
  • Monitor – Review job status and results in the dashboard
  • Maintain – Update the job as data or requirements change

Types of jobs

The following are the available types of jobs in iDMS.

Manual Jobs

Jobs that are triggered directly by a user.

  • Used for one-time imports or updates
  • Common during setup or testing

Scheduled Jobs

Jobs that run automatically using iSchedule.

  • Run at defined times or intervals
  • Common for recurring data updates or integrations

Triggered Jobs

Jobs that run based on an event or external trigger.

  • Triggered by iWorkflow actions
  • Triggered by webhooks using iHook
  • Often used for real-time integrations

Monitoring jobs and processes

iDMS provides tools to track job execution and performance:

  • Dashboard – Displays high-level metrics and recent activity
  • Task History – Shows results of recurring jobs
  • History – Displays all job executions and statuses

Each job run includes status information such as:

  • Completed
  • Partial
  • Failed
  • Pending

Designing effective processes

When building processes in iDMS, consider the following:

  • Order of operations – Ensure jobs run in the correct sequence
  • Dependencies – Confirm required data is available before execution
  • Error handling – Plan for failures or partial results
  • Performance – Schedule large jobs during off-hours

Best practices

The following are best practices:

  • Break complex workflows into smaller jobs
  • Use clear naming conventions for jobs and processes
  • Test each job independently before combining into a process
  • Monitor job history regularly to identify issues
  • Document your processes for future reference

Common pitfalls

The following are common pitfalls related to jobs and processes:

  • Combining too many actions into a single job
  • Not testing jobs before scheduling them
  • Overlapping jobs that affect the same data
  • Lack of visibility into job failures