- handbook
- Company
- Company
- Board
- Communications
- Decision making
- Guides
- KPIs and OKRs
- principles
- Remote Work
- Security
- Asset Management Policy
- Business Continuity & Disaster Recovery Policy
- Information Security Roles and Responsibilities
- Operations Security Policy
- Risk Management Policy
- Third-Party Risk Management Policy
- Human Resources Security Policy
- Access Control Policy
- Incident Response Plan
- Cryptography Policy
- Information Security Policy and Acceptable Use Policy
- Secure Development Policy
- Data Management Policy
- strategy
- values
- Operations
- Product
- Feedback
- Market Segments
- Metrics
- Node-RED Dashboard
- personas
- Pricing Principles
- Principles
- Responsibilities
- Strategy
- Versioning
- Customer department
- Customer
- Customer Success
- Hubspot
- Marketing
- How we work
- Marketing
- Video
- Customer Stories
- Social Media
- blog
- Community
- Marketing - Website
- FlowFuse Messaging
- Webinars
- Sales
- Engineering & Design Practices
- Design
- Engineering
- Certified Nodes
- contributing
- Front End
- Packaging Guidelines
- Platform Ops
- Deployment
- Incident Response
- Observability
- Production Environment
- FlowFuse Dedicated
- Staging Environment
- Project Management
- Releases
- Security Policy
- tools
- Website A/B Testing
- Internal Operations
- People Ops
# Services
The frontend contains two helper services that can be called anywhere in the UI. Each of the services control components built into the main Platform.vue
.
# Alerts
Alerts should be used to reinforce the completion of an action, or to alert a user that something has gone wrong.
The important piece to note here is that alerts should be for information only, and should not require any actions on the user's part.
import Alert from '@/services/alerts'
/*
* msg - The text to be displayed in the alert.
* type - 'info' | 'confirmation' | 'warning'
* countdown - (optional) If provided, the alert will disappear
* after this duration (ms), defaults to 3000.
*/
Alert.emit(msg, type, countdown)
The service is built from the ff-notification-toast forge-ui-component.
# Dialog
The Dialog service should be used when user confirmation is required, after an action has been taken. For example, if a user attempts to delete a resource, a confirmation Dialog should be shown to ensure this was not an accidental action.
import Dialog from '@/services/dialog'
/*
* msg - {
* header: '<header title>',
* kind: 'danger` | `primary` | `secondary` | `tertiary', (default = 'primary')
* text: 'show this message in the dialog',
* html: 'instead of "text", you can provide html for more custom appearance and content',
* confirmLabel: '<confirm-label>'
* }
* callback - function to run when the user confirms the dialog
*/
Dialog.show(msg, callback)
The service is built from the ff-dialog forge-ui-component.
More complex ff-dialog
instances, where you can use the component directly, can also be used for forms.