Understanding Halt Tasks

A Halt task stops the JD Edwards EnterpriseOne workflow process and specifies a period of time that must pass before the process can continue.

For example, suppose you have a process for submitting a contract proposal to a client. The client has two weeks to accept the proposal or the contract is voided. After the contract is entered, the system activates a JD Edwards EnterpriseOne workflow process, using a Halt task, that puts the contract on hold for two weeks. At the end of the two weeks, when the JD Edwards EnterpriseOne workflow process resumes, a Business Function task checks the status of the contract. If the contract has been accepted, nothing happens. If the contract has not been accepted, the status is changed to Void and a notification is sent to the client.

When you set up a Halt task, you specify either hours and minutes or the date and time at which you want the process to resume.

If you add Halt tasks to the JD Edwards EnterpriseOne workflow process, you must run the Start Escalation Monitor batch process (R98810) regularly. You can run it manually or set up the JD Edwards EnterpriseOne Workflow Scheduler to run the batch process automatically. If you do not run the Escalation Monitor regularly, the workflow process will remain halted. The Escalation Monitor resumes the process after the date and time are met.

You can run the Escalation Monitor manually from Object Management Workbench. The Start Escalation Monitor button is located on the Workflow Operations tab in Workflow Design.