Proof-of-service (POS) workflow customization via task extension
First Claim
1. A method of providing a task workflow extension feature in a proof of service system, comprising:
- providing at least one editable form defined using a scripting language; and
transmitting said scripting language to a client via configuration properties.
1 Assignment
0 Petitions
Accused Products
Abstract
Task extensions for a proof-of-service (POS) system allow easy customization without requiring modification to the POS application itself. Current preferences capability is used to specify new tasks, which are downloaded to the device during an administrative sync process. The new workflows are detected at runtime. This provides a way to collect additional customer-defined data associated with a given task. Ideally, task extensions could be used with both the existing tasks (delivery and pickup) and with new tasks that would be defined by a customer. Data collected by the workflow extension is returned as an XML-tagged string of data elements to the legacy system, which would be responsible for parsing the data. Some rudimentary data validation on the client may be included by adding attributes to the XML-tags that define the UI'"'"'s data collection elements.
20 Citations
24 Claims
-
1. A method of providing a task workflow extension feature in a proof of service system, comprising:
-
providing at least one editable form defined using a scripting language; and
transmitting said scripting language to a client via configuration properties. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. A task workflow extension feature in a proof of service system, comprising:
-
means for providing at least one editable form defined using a scripting language; and
means for transmitting said scripting language to a client via configuration properties. - View Dependent Claims (14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24)
-
Specification