The Get Next Task control allows the user to get their next available task. You can use the Default Get Next Task Ajax service that comes with the Portal Builder Toolkit, or create your own Ajax service to fit your particular needs.
The Get Next Task control gives you the ability to implement a push client. A push client, from the user's viewpoint, presents one item of work at a time and does not allow user selection from a work list.
Without the Get Next Task control, you only have a pull client. A pull client, from the user's viewpoint, presents a list of work items and the user selects the work to be performed next.
The Get Next Task control allows you to implement any kind of client.
This control needs to be used in conjunction with the Task UI Frame control in order to display the Task UI.
Like all Portal Builder controls, you can trigger events that are fired when the user interacts with the control (see the Event and Methods sections below and the Event Handling article for more information).
Get Next Service The Ajax service that the control calls
Once the Get Next Ajax service returns a result the Get Next Task will get the taskId, so that when the Get Next Task button is clicked that task will be displayed.
These are the configuration option settings...
Note: The Control Id of the Task UI Frame is Task_UI_Frame1
The Get Next Task button has the following On Click event...
For more information on the requestNextTask method, see the Get Next Task JS Doc here.
When the page loads...
When the Get Next Task button is clicked...
With the Get Next Task control, there are 3 types of event handlers:
- On Load When the page loads, Note that this particular event is only fired ONCE per page load
- On Request Complete Event fired when the Ajax request returns a result
- On Request Error Event fired when the Ajax request returns an error
For detailed information on the available methods for this control, access the JS Doc file.
- Author: Courtney Silva
- Date Created: February 25, 2016
- Date Modified: March 9, 2016