Schedule supported database work in IFS Cloud
Documentation-based guide draft · Reviewed against sources on 2026-09-27 · Not executed in an IFS environment. IFS references use 26R1 unless stated otherwise. Confirm available APIs, components, and permissions in your installed release.
Schedule an approved database task once, inspect its background job, and only then make it recurring. The IFS scheduler runs registered tasks; it is not a general-purpose box for pasting arbitrary SQL against production tables.
Before you start
Section titled “Before you start”Use a development environment and a registered database task with a small, reversible test scope. If the requirement starts as custom PL/SQL, have the development owner package it as a supported task with reviewed parameters, permissions, transaction behavior, and repeat-run behavior before following these steps.
Record the task name, parameter types, expected business effect, execution owner, and how to reverse the lab data change. For the initial run, choose one fictional record rather than an unbounded company-wide selection.
1. Confirm the task and its inputs
Section titled “1. Confirm the task and its inputs”Open the database task selection in New Database Task Schedule. Locate the registered task by name and inspect its parameters. If the method is not registered or its required parameters are absent, fix the task definition through the approved development process first.
Prepare a worksheet:
| Item | Value to record |
|---|---|
| Task | Exact registered task name |
| Scope | One lab record/company/site |
| Owner | Intended service/business user |
| Parameters | Name, data type, and test value |
| Expected result | Observable business output and maximum row count |
| Repeat behavior | No duplicate effect, or explicit repeat rejection |
Do not replace a missing task with a direct DBMS_SCHEDULER job that bypasses the application framework.
2. Create an inactive one-time schedule
Section titled “2. Create an inactive one-time schedule”- Open New Database Task Schedule and select the task.
- Enter a Schedule Name such as Lab task acceptance 041.
- In Set Parameters, enter the prepared narrow values.
- In Set Schedule, choose Date and a time a few minutes ahead.
- Check the displayed time zone and the resulting planned execution time.
- In Set Options and Streams, select the required language and leave the task inactive until you have reviewed all inputs.
- Save, reopen the schedule, and compare every value with the worksheet.
Only the creator or an administrator can edit schedules under the documented rules. Use the intended ownership model from the start rather than relying on a departing consultant’s account.
3. Activate and follow the background job
Section titled “3. Activate and follow the background job”Activate the schedule. After the planned time, open it and use View Background Jobs. This action becomes available after the schedule has been saved.
Inspect the actual job state, start/end times, and error text. Then verify the business output through its normal application page or an approved read query. A Finished status is not enough if the task’s selection matched zero rows unexpectedly.
If you use the action to run the task as soon as possible, remember that it overrides normal schedule timing for that execution. Do not also leave a near-future one-time run that unintentionally repeats the same work.
4. Test safe repetition and failure
Section titled “4. Test safe repetition and failure”Repeat the same lab task with the same parameters only if its repeat-run contract permits it. Confirm it either leaves the already-correct state unchanged or rejects the duplicate visibly. Then test an invalid reference and inspect both the background-job error and persisted data.
A job can fail after partial work depending on the task’s transaction implementation. Reconcile what changed before retrying; do not assume the scheduler wraps every method in one reversible transaction.
5. Configure recurrence deliberately
Section titled “5. Configure recurrence deliberately”After acceptance, change the plan to Daily, Weekly, Monthly, or Interval as appropriate. Confirm the next execution time. Use Custom only when the standard choices cannot express the requirement and the task owner can review the expression.
A documented Oracle calendaring-style example is:
FREQ=WEEKLY;INTERVAL=2;BYDAY=FRITreat this as syntax to validate in your installed schedule editor, not as an exact promise about time-of-day or time-zone defaults. Preview/check the next run and daylight-saving implications using time-zone guidance.
6. Diagnose and clean up
Section titled “6. Diagnose and clean up”No job usually means inactive/incorrect scheduling or a queue problem. A permission error points to the executing identity. Repeated overlap indicates the task duration and recurrence are incompatible; fix task locking/claiming or the interval rather than allowing duplicate processing.
Deactivate the lab schedule and confirm no job is still waiting or running before removing it. Retain the parameters, job ID, observed result, and rollback evidence. Do not delete application scheduling tables directly.
Sources and scope
Section titled “Sources and scope”Older IFS Applications examples are historical context, not evidence of Cloud compatibility. No third-party code, screenshots, or downloadable workflows are reproduced.