Links are a common way to open documents, files, tools, videos, websites, email applications, or phone someone. Many of us are familiar with tel:, mailto:, and https:. You can make a custom URL scheme for Studio to simplify automating business processes.
Imagine embedding links in an Omnis report and emailing them to a business associate or client. Those URL’s can:
- open a Studio application (if it’s not already open),
- log you in (if you’re not already), and then
- open a specific data record inside Studio (if you have permission).
Some useful examples are:
- Emailing a client an invoice (PDF) which they return with a bank transfer. Clicking the invoice number on the PDF then opens Studio to a payment window for the specific order to entering payment details, eliminating navigation.
- Clicking on a client in an ‘action-item’ report of the top 10 recent support requests or sales prospects to see all the data.
- Nagios registeres services of a clientare down: with a link you added, you can directly open the data of the client so you can respond quickly
- Bug report in Sentry: With a link you included you can directly open a method editor in Omnis at the position where the issue is triggered.
What you’ll learn:
This session will show you concepts using links in reports to access data from the database. This includes
- what the links look like
- how to process them
- making the links work within a report
- making links that will open Omnis to the specific data from the OS, browser, URL, eblast, or any web page
- addressing logging in, if Omnis is opened from scratch
- addressing security, should the user not be permitted to access the data.
- discussing some ancillary use cases for this idea
Why you should attend:
The implementation combines use of features that have existed in Studio for a long time, in conjunction with a new capability in Studio 11.2 that permits adding links external to Omnis.
This session provides the how-to to let you access a path to data in your application, especially if it is not open, using URL Schemes
This topic will demonstrate how easy it is to make your application time zone aware. This could be especially useful of you have offices in multiple time zones, travel for work, need to have global calendaring, enable time-based sales and discounts online, time synchronize logs from multiple systems (eg for purposes of PCI or regulatory compliance) and more.
The topics include all you need to do such as:
- Settings for time zone support within the Postgres server
- Retrieving a list of valid time zones that Postgres supports
- A one-time Database conversion process
- Time zone fields
- Options and ramifications
- Database defaults for new data
- Possible Changes to your application
- Meaning of some built in Postgres date functions
- Data retrieval in foreground & background
- Implicit time zone fetches and session variables
- Explicit time zone fetches
- Mixing time zones in your data for retrieval
- Determining your computer time zone if you want to make changing automatic based on locale