...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Section | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Designing forms and workflows with dashboards in mind will ensure your process is complete, efficient, productive, and manageable. Form/Workflow design should take into account the key stakeholders in the process and the reporting, monitoring, analysis, and strategic needs of the stakeholders and participants. The designer must quantify and specify those insights in terms of measurements, key performance indicators (KPIs), analytics, and data that is to be derived. This information can be roughly categorized into:
- Strategic data that is used to measure the process against set goals
- Analytical information that is more tactical and discovery in nature
- Operational and real-time process information
For example, a strategic goal in a Procure-to-Pay process might be on-time procurement. The designer would want to ensure the workflow captures data that can measure this, such as a deadline date and a calculation to determine if the procurement is early, on - time, or late.
An example of a tactical insight in the same Procure-to-Pay process is discovering volume buying and discount opportunities. The form/workflow should capture relevant information on the product/service, including category, vendor, rate, and discount information (if any) that allows a stakeholder to assess this metric.
...
Move a control into or out of a Section control
Delete a control
Rename a control
Delete the source form/workflow
Remove a control from Searchable Fields
Change control type:
Text
Email
Money
Phone
Quantity
Number
Text
N/A
Works
Breaks
Works
Breaks
Breaks
Email
Works
N/A
Breaks
Works
Breaks
Breaks
Money
Breaks
Breaks
N/A
Breaks
Breaks
Works
Phone
Works
Works
Breaks
N/A
Breaks
Breaks
Quantity
Breaks
Breaks
Breaks
Breaks
N/A
Breaks
Number
Breaks
Breaks
Works
Breaks
Breaks
N/A
Checkbox
Dropdown
Radio
Checkbox
N/A
Works
Works
Dropdown
Works
N/A
Works
Radio
Works
Works
N/A
Date
Time
Date/Time
Date
N/A
Works
Works
Time
Works
N/A
Works
Date/Time
Works
Works
N/A
Here's an example of a Column chart that was originally designed to display the average Number and Price (metrics) by widget type (dimension). If the Price control is changed from a Money control to a Text control, I see the chart displayed with a validation error in design mode. The Dashboard runs in test and use mode, but the Price calculation does not include submissions since this change. This means your Dashboard users may not know right away there is a problem, but they may see incorrect data.
...
Style properties allow the designer to customize the look and feel of the runtime dashboard and the PDF Snapshot. See the Style Settings documentation for additional details on each of the available properties.
Sharing Dashboards
...
Here is an example of a Dashboard embedded in a frevvo Space.
