Jobs application

Jobs in Nextworld can include logic block or application generation, data imports, background tasks, report generations and others. After jobs are created and submitted in their respective builder applications or scheduled through the Job Scheduler application, they can be viewed in the Jobs application. View information such as job errors or the current job statuses and use row actions in the application to stop, or terminate, a job.

Learn more about what jobs are and what you can do with them in the Jobs topic.

Summary page

View general information about a job, such as who created it, when it was created, and in what zone.

Details page

View the job input parameters, or the specific information that was used to run a job.

Dependencies page

View any dependencies the job may have and the data mappings from those dependencies. 

Results page

View the job output information, or the specific information that resulted from the job. 

Errors page

View the encountered errors if the job failed. 

Steps page

Some job types, such as Gen All App or Gen All LB, are comprised of many steps that you must run across multiple servers at the same time to increase performance. For those types, detailed information about each step appear on this page.

Scheduled jobs

For example, the chart of accounts account hierarchy must be flattened each time a change is made. Instead of requiring users to manually do this, you could create a scheduled job that runs nightly which contains a job to flatten the chart of accounts table.

Scheduled jobs are comprised of one, or many, jobs that you create using the Jobs page in the Job Scheduler application. There are different job types you can create within a scheduled job, including logic blocks, data exports and imports, migrations, and reports. You can control the sequence of when each job should process and what environment they should be submitted in. 

When the scheduled job is configured, it can be submitted to process. When it is submitted, any individual jobs you created within the scheduled job are submitted together as batch jobs. View the status of the submitted jobs in the Jobs application. 

Dependencies

If your scheduled job has more than one job, you can sequence the jobs by defining dependencies. This ensures other jobs are completed before the specified job starts. If a job has another job defined in the Dependencies field, you can use the Data Mapper tool to map outputs from that job into the current job's fields. 

For example, if you have a scheduled job that contains both a Data Export and Logic Block job, you could specify the Data Export Job Nickname in the Dependencies field of the Logic Block job. Then, you could map outputs from the Data Export into the logic block driver table fields. Those outputs then become available as values within your logic block. 

Configuration options

The following scheduled job configurations apply to every job that you create within a scheduled job record:

• Run Environment—The context in which the jobs in a scheduled job are run. This contextual information includes the user account under which all job steps execute, the associated permissions and access rights that determine what resources the jobs can access, the users who receive notifications about running jobs, and the environment and lifecycle that the jobs run in.
• Recurrence—How often the jobs of a scheduled job should run. You must define one of the following recurrence types for each scheduled job record on the Recurrence page:
  • Manual—Run when someone executes them. They are not tied to any start date or end date, timezone, or recurrence rules.
  • Single Run—Run once at a specified start date and start time. Use the Run Now action to manually initiate the job additional times. 
  • Recurring—Run jobs on a designated, consistent schedule. You must define a start date, start time, and timezone. You can optionally specify an end date and end time after which the scheduled job stops running.

If the recurrence type is Recurring, define one or more recurrence rules using the fields in the Recurrence Rules subtable. For example, you can schedule a report job to run every other Friday and on the last day of each month by defining two recurrence rules in the Recurrence Rules subtable.

Learn more in Job Scheduler application.

Job Scheduler application

Use the header region to define the name, description, product family and module, and Category. Once your scheduled job is submitted, you can also view the time of the last submission, when it is scheduled to run next, and whether or not it is active. Only active scheduled jobs have the ability to run.

After the header information is entered, you can further specify your scheduled job using the application's pages.

General page

Specify the environment and lifecycle that the job should be run in, and the run as user. The run as user is used to apply security to the jobs that are executed, and receives notifications about the jobs.

Use the Notifications section to monitor scheduled jobs execution, and to automatically send alerts based on completion status. When a scheduled job finishes, the system can emit events for both successful and failed jobs. These events can then trigger message events that send email notifications to specified individuals. Learn more about creating message events in the Messages topic.

Recurrence page

Define how often the scheduled jobs should run. Options include:

• Manual—Run when someone executes them. They are not tied to any start date or end date, timezone, or recurrence rules.
• Single Run—Run once at a specified start date and start time. Use the Run Now action to manually initiate the job additional times. 
• Recurring—Run jobs on a designated, consistent schedule. You must define a start date, start time, and timezone. You can optionally specify an end date and end time after which the scheduled job stops running.

If the recurrence type is Recurring, define one or more recurrence rules using the fields in the Recurrence Rules subtable. Each recurrence rule requires a frequency interval and a frequency type, such as every two weeks or every five days. You can add multiple recurrence rules to have the job run at different intervals. 

If your scheduled job has more than one job, you can sequence the jobs by defining dependencies. This ensures other jobs are completed before the specified job starts. If a job has another job defined in the Dependencies field of the subtable, you can use the Data Mapper tool to map outputs from that job into the current job's fields. 

The data source type can be a constant value, a system defined value, or the result of another job action run:

• Constant—Any value defined by the user that matches with the destination data type.
• System Value—Any system defined value, such as current time or current user, that matches with the destination data type. 
• Table Record—The name of a record in the Jobs subtable that the data mapper is on. Choosing one of these options selects another job that you want to map a result value from. 
  • The result value options for the Source Field are dependent on the job Type of the selected record. For example, if the type is Logic Block, then the field options are populated with fields from the Logic Block table. 

Jobs page

Create jobs and job dependencies that you want to run in the scheduled job. If your scheduled jobs have more than one job, you can define dependencies for each one that specify any other jobs that must be completed before the current one starts.

Recent Submissions page

View information on a scheduled job that you have submitted to the Jobs application. Each time a scheduled job is run, an entry is created on the Recent Submissions page that includes the submission type, the data and time the job was submitted, the status, and the Scheduled Job Submission Id. An application link is provided for each Scheduled Job Submission Id allowing the job details to be viewed.

Job Status card

You can create a job by:

• Selecting the Submit action in applications such as Data Import Definitions, Planner Definition, or Advanced Migration Utility. 
• Selecting the Generate action in applications such as Application Builder.
• Using the Job Scheduler application where you can initiate one or many jobs on demand or a at a scheduled time. 
• Creating a logic block that calls another Background Task type logic block.

When you submit a job, you can perform other tasks while the job runs in the background. A record is created in this application with information on the job's current status. After a job is finished processing, you receive a notification with an updated Success or Failed job status. Open the Job Status record to review additional information, such as why a job failed. 

Scheduled Jobs

Scheduled jobs are background tasks, such as test suites, logic blocks, data syncs, or orchestrations, which run independently without a user interaction. A scheduled job can be created to run at a specific time, or when certain requirements have been met. 

For example, when changes are made to the chart of accounts hierarchy in the general ledge, you must rebuild a flattened view of the relationships between the accounts. Rather than manually performing this action, you can have a scheduled job that runs ever night to address any changes made throughout the day. 

Learn more in Scheduled jobs.