Back to Project
Installation and Resources
- Pre-requisites
- Install and Activate Yurbi
- Setup a user-friendly URL
- Explore the Demo Environment
- Change your Yurbi admin password
- Join the Yurbi Community (and other resources)
- Backup Strategy
Connect Yurbi To You Data
Security Planning and Setup
- Security Planning
- Folder and Report Security Groups - Simple Environments
- Folder and Report Security Groups - Department Environments
- Setup Data Security Groups
Report and Dashboard Building
- Report Building Planning
- Out of the Box Visualization Types
- Build Datagrid Reports (Detailed and Target)
- Build Summarized Reports
- Drill Down Reports
- Build KPIs Reports
- Build Chart Reports
- Linking Reports - Data Blending
- Advanced Reports
- Build Combo Charts
- Map Visualizations
- Using SQL Stored Procedures
- Create Dashboards
- Create Filters and Saved Views
- Dashboard Smart Filters
- Configure Dashboard FastCache
Deployment and Training
- Apply Your Branding
- Create Data Tag
- Create App Shield Security Policies
- Create Users
- User Training and Documentation
- Provide Access To Your Users
- Display In Unattended Mode
Operations and Maintenance
Configure Your Yurbi App
The Yurbi App is like a universal translator from Star Trek. It translates your raw data into information that your users can use to build reports (without the mind-reading part, we need you to build the Yurbi App as of Star Date ~73000, i.e. now).
Remember the purpose of the Yurbi App is to eliminate the need for the users building your reports to know anything about your database schema or how to write SQL code.
The role of the Architect is slightly different for database data sources than MS Excel/CSV data sources. So we’ll break the instructions down in those categories below.
Database Sources (we call them AnyDB Apps)
Add SQL Functions In The App (applies to Excel/CSV sources as well)
MS Excel/CSV Sources
Side Note: The reason my date function didn’t work on the Excel import, I was trying to use an MS SQL function but my Excel was imported into the Yurbi PostgreSQL backend. Instead of datename ( mm, call_req.open_date ) it should have been to_char ( call_req.open_date , ‘month’ )