Field Components
Essential knowledge
Changed on:
23 Sept 2024
Overview
[Warning: empty required content area]Key points
[Warning: empty required content area]Field Components are a different kind of component all together.They cannot be configured via the manifest. Rather, they are automatically rendered based on the data type to be captured.Field Components are essentially form based elements. They could be as simple as a text box, or more advanced with multiple input fields and types.Field Components are key in delivering flexibility and enhanced user experience to complex user actions driven by the workflow. Workflows can require complex data input for the expected trigger event, and Field components enable full control over the user experience provided for those cases.
Example:
In the screenshot above, the Requested Quantity and the Location selection are 2 parts to a single field, which map to an Event Attribute structured as follows:Since Field Components are rendered automatically based on the User Action definition, there is no configuration reference required.Learn more about the Field Components
Example:In the screenshot above, the Requested Quantity and the Location selection are 2 parts to a single field, which map to an Event Attribute structured as follows:
1{
2
3 "name": "StockReserveDetails",
4 "value": {
5 "locationRef": "F_NSYD",
6 "requestedQuantity": 2
7 },
8 "type": "STOCK_RESERVE_DETAILS"
9}