Skip to main content

IMPORTANT - Product End of Life Statement - IMPORTANT

Request RE, Survey, and Calendar 1.5 Support Ending December 31, 2020
Contact Kinetic Data Support with Questions
Kinetic Community

The Fulfillment KAPP Update Actions Tree

Taking action on a work order, ie changing priority, status, assignment, work order due date, acknowledgement, are more than just visual changes to a record. These items need to be able to affect real changes, like sending notifications or completing the work order.

Status Changes

Status changes, in addition to triggering any workflow (like notifications), may need to perform key functions like complete the work order or additional desired functionality like requiring work information entries or questions at certain status. These actions are tied to the back end statuses, and can fire on various visible/text statuses (see configuration file).


Changing the status of an item to pending, automatically prompts for (requires) a work information entry.


In Progress, Assigned

These statuses don't initiate any additional actions (other than the tree indicated in the section below).


Closing the work order (often visibly called "Completed"), adds a section to the work order that includes the submit button and any questions that have been added to the section. If information is required on completion of this work order, for example to be passed on to a future work order, a question could be added into this section and made required. 



Cancelling a work order adds a section to the work order that prompts for cancellation comments and includes the submit button.


Fulfillment Update Tree

When any of the actions are triggered on an item with the attribute "Fulfillment Update" containing a valid tree, such as the one available in the install package:

Work Order::Air_Fulfillment_Development_Catalog::Fulfillment Update v1

This fulfillment tree processes the action (priority, status, assignment,  or work order due date) for the submission (work order).


Retrieves the work order, and performs the configured actions. In the displayed (and downloadable) example, the actions are all echos. The actions desired will depend on company policies and procedures.