Integrate Tableau with uProc

Appy Pie Connect allows you to automate multiple workflows between Tableau and uProc

  • No code
  • No Credit Card
  • Lightning Fast Setup
20 Million man hours saved

Award Winning App Integration Platform

About Tableau

Tableau is a data visualization tool that is used for data science and business intelligence. It can easily format raw data in different formats and visualization styles. With Tableau, you can create and publish dashboards and share them with colleagues, partners, or customers without any coding.

About uProc

uProc is a database management system that gives users the tools and capabilities they need to improve the fields in their databases and get more out of them. It helps businesses in the validation of essential business data such as emails, phone numbers, and more, as well as the creation of new database categories for better data segmentation.

uProc Integrations

Best Tableau and uProc Integrations

  • Tableau Integration uProc Integration

    Tableau + uProc

    Select Tool in uProc when New Data Source is created in Tableau Read More...
    Close
    When this happens...
    Tableau Integration New Data Source
     
    Then do this...
    uProc Integration Select Tool
  • Tableau Integration uProc Integration

    Tableau + uProc

    Select Tool in uProc when New Project is created in Tableau Read More...
    Close
    When this happens...
    Tableau Integration New Project
     
    Then do this...
    uProc Integration Select Tool
  • Tableau Integration Tableau Integration

    Gmail + Tableau

    Update Data Source in Tableau when New Attachment is created in Gmail Read More...
    Close
    When this happens...
    Tableau Integration New Attachment
     
    Then do this...
    Tableau Integration Update Data Source
  • Tableau Integration Tableau Integration

    Gmail + Tableau

    Update Data Source in Tableau when New Labeled Email is created in Gmail Read More...
    Close
    When this happens...
    Tableau Integration New Labeled Email
     
    Then do this...
    Tableau Integration Update Data Source
  • Tableau Integration Tableau Integration

    Gmail + Tableau

    Update Data Source in Tableau when New Email Matching Search is created in Gmail Read More...
    Close
    When this happens...
    Tableau Integration New Email Matching Search
     
    Then do this...
    Tableau Integration Update Data Source
  • Tableau Integration {{item.actionAppName}} Integration

    Tableau + {{item.actionAppName}}

    {{item.message}} Read More...
    Close
    When this happens...
    {{item.triggerAppName}} Integration {{item.triggerTitle}}
     
    Then do this...
    {{item.actionAppName}} Integration {{item.actionTitle}}
Connect Tableau + uProc in easier way

It's easy to connect Tableau + uProc without coding knowledge. Start creating your own business flow.

    Triggers
  • New Data Source

    Triggers when a new data source occurred.

  • New Project

    Triggers when a new project occurred.

  • Updated Data Source

    Triggers when an existing data source is updated

    Actions
  • Update Data Source

    Updates an existing data source in tableau.

  • Select Tool

    Select a tool to perform verification or enrichment

Compliance Certifications and Memberships

Highly rated by thousands of customers all over the world

We’ve been featured on

featuredon
Page reviewed by: Abhinav Girdhar  | Last Updated on July 01, 2022 5:55 am

How Tableau & uProc Integrations Work

  1. Step 1: Choose Tableau as a trigger app and authenticate it on Appy Pie Connect.

    (30 seconds)

  2. Step 2: Select "Trigger" from the Triggers List.

    (10 seconds)

  3. Step 3: Pick uProc as an action app and authenticate.

    (30 seconds)

  4. Step 4: Select a resulting action from the Action List.

    (10 seconds)

  5. Step 5: Select the data you want to send from Tableau to uProc.

    (2 minutes)

  6. Your Connect is ready! It's time to start enjoying the benefits of workflow automation.

Integration of Tableau and uProc

First, let me give you a brief introduction of Tableau and uProc.

Tableau is used for analytics and data visualization in business intelligence, marketing, and sales. The users of Tableau are mostly the business users who need to analyze data quickly, and uProc provides an excellent top for building dashboard applications. Thus, it is necessary to integrate Tableau and uProc for the better performance of business intelligence (BI. The overall aim of this paper is to discuss how to integrate Tableau and uProc.

I will divide the paper into two sections. the first one will be on integrating Tableau with uProc, and the second one on the benefits of integrating Tableau and uProc.

Integration of Tableau and uProc

To integrate Tableau with uProc, we have to use a certain library named blaze-html-0.8. This library is used for HTML templates. Therefore, to integrate both tops, we need to use Blaze as the template engine. There are two ways to integrate Tableau with uProc. One is using Blaze; the other is not using Blaze. I am going to illustrate the integration of these two ways.

Using Blaze

The first way is using blaze as the template engine. First, we need to add two packages in the pkg directory in the fplowing order. blaze-html-0.8 and text-0.11.2. Next, we need to modify “Makefile” (the configuration file of uProc. and add “build_html” in the list of targets to build. For example, if we want to build a package named “mypackage”, we need to add “build_html” in the list of targets like below:

BUILDTARGETS += mypackage_examples build_html mypackage_tests build_html clean_html dist_html install_html check_html all_html

Next, we should write HTML files based on how Blaze works. Based on the examples provided by Blaze, we can see that the template function has three parameters. “Application”, “Request”, and “Response”. Application is the application object that contains all information about uProc. Request is used to get variables from user input and Response is used to display results. We can embed JavaScript code inside our HTML pages.

We can also embed CSS code if we want, but since CSS code can be complicated sometimes, I only added JavaScript code in this example.

For example, we have a directory named “sample1” under “pkg” as below:

sample1 └── html ├── sample1/ │ ├── helloWorld.html │ └── myApp/ │ ├── index.html │ └── indexFromName.html └── sample2/ ├── helloWorld2.html └── myApp2/ ├── index2.html └── indexFromName2.html

The contents of index2.html are as fplows:

<!DOCTYPE html> <!-- <html> <head> <title>hello world</title> <link rel="stylesheet" rel="nofollow" href="style/style.css"> </head> <body> <h1>Hello World</h1> <script type="text/javascript"> var name = "; var hello = "Hello"; var world = "world!"; </script> <p>Hello {{name}}!</p> </body> </html> -->

And the contents of indexFromName2.html are similar to index2.html except that we changed from name to nameValue . Note that we use {{name}} instead of {{nameValue}} in this page because the value attribute of HTML tag must be enclosed by double curly braces ( {{ }} . Otherwise, it will cause a parsing error when calling back Blaze from Tableau. Then we can use the fplowing command line to generate a package named mypackage :

$ make clean $ make pkg -s MANUAL=false -s DOC=false -s EXAMPLES=true -s TESTS=true $ make pkg install –pkg-dir=pkg/mypackage –pkg-dir=pkg/mypackage/myApp $ cd pkg/mypackage/myApp $ make clean $ make html # This will generate a package named myPackage under "pkg" $ cd ../.. $ make install –pkg-dir=pkg/mypackage –pkg-dir=pkg/mypackage/myApp $ make install –pkg-dir=pkg/mypackage/myApp -s PATH=/usr/local/bin # This will install the package "myPackage" under "pkg" and add "myPackage" to PATH env variable $ cd .. $ cd .. $ cd .. # To confirm whether you installed myPackage properly or not $ ls -l /usr/local/bin | grep myPackage lrwxrwxrwx 1 root root 20 Nov 7 00:43 /usr/local/bin/myPackage -> pkg/myPackage/myPackage # To run the program $ ./myPackage/bin/myPackage -u http://localhost:3000 -e http://localhost:3000 -r http://localhost:3000 -o http://127.0.0.1:3000 -f http://127.0.0.1:3000 -a http://127.0.0.1:3000 -P 10000 # To run the program and view results at localhost:3000 $ ./myPackage/bin/myPackage --out=http://127.0.0.1:3000 # To run the program with some parameters (e.g., --url. $ ./myPackage/bin/myPackage --url=http://localhost:3000 -o http://127.0.0.1:3000 -r http://localhost:3000 -u http://localhost:3000 -f http://127.0.0.1:3000 -a http://127.0.0.1:3000 -P 10000 # To run multiple programs at a time (e.g., 3 programs. $ ./myPackage/bin/myPackage --url=http://localhost:3000 --url=http://localhost:3001 --url=http://localhost:3002 -o http://127.0.0.1:3000 -r http://localhost:3000 -u http://localhost:3000 -f http://127.0.0.1:3000 -a http://127.0.0.1:3000 -P 10000 --out http://127.0.0.1:3003 # To run an encrypted program (e.g., --encrypt. $ ./myPackage/bin/myPackage --encrypt --out http://localhost:1234 # To run an encrypted program without prompting for input password (e.g., --password. $ ./myPackage/bin/myPackage --password=123456 --out http://localhost:1234 # To see all available options $ ./myPackage/bin/myPackage --help # To specify a port other than 8080 for the HTTP server $ ./myPackage/bin/myPackage --port=1234 # To enable SSL via command line argument $ ./myPackage/bin/myPackage --ssl # To disable SSL via command line argument $ ./myPackage/bin/myPackage --nossl # To enable SSL via environmental variable (e.g., SSL enabled by default. $ SSLMODE=enableSSL myPackage # To enable SSL via environmental variable (SSL disabled by default. $ SSLMODE=disableSSL myPackage # To enable logging via environmental variable (e.g., log enabled by default. $ LOGMODE=enableLOG myPackage # To enable logging via environmental variable (log disabled by default. $ LOGMODE=disableLOG myPackage # To enable caching via environmental variable (e.g., cache enabled by default. $ CACHEMODE=enableCACH myPackage # To enable caching via environmental variable (cache disabled by default. $ CACHEMODE=disableCACH myPackage # To specify a custom path for cache file (e.g., cache file under /tmp. $ CACHEDIR=/tmp myPackage # To specify a custom path for log file (e.g., log file under /tmp. $ LOGDIR=/tmp myPackage # To specify a custom path for pid file (e.g., pid file under /tmp

The process to integrate Tableau and uProc may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.