1.LLodi Help Center #

LLodi Helps
Create a FREE Account now

LLodi Step by Step

LLodi Helps is the best way to find updated documentation about the LLodi Platform.
If you need assistance and you currently have an account, you can contact our team by completing the support form in the bottom menu in the platform. If you don’t have an account yet, you can get more info by reaching us through the Contact Form at LLodi.com.

Yes No

1.1.What is LLodi? #

LLodi is a Cloud Service that allows all the company members to use their favorite apps within QlikView® or Qlik® Sense, through the creation of Data-Driven Forms that Integrate Workflows into your Analytic Apps


Yes No

1.2.LLodi Step by Step #

LLodi Step by Step


  • Create a FREE account
  • Log in to LLodi Platform
  • Navigate to LLodi Forms and and select your prebuilt form and Workflow or, on the contrary, create your own form in Custom Forms and create your workflow with Zapier, Scribe Online, Workato, IFTTT, Stamplay or Custom Integration Platform.
  • Start with Zapier easily creating your first workflow. (Review the section on integration platforms)
  • Complete the installation of the LLodi Widget:
    • Qlik Sense Extension
    • Qlik View Extension
    • Power BI Custom Visual
    • Tableau LLodi Form
  • Register End Users (Account Settings)
  • Start Take Actions on your Data Analysis.
  • Monitor the Apps taken with our Apps Monitor.
Yes No

2.Form Management #

Give your business the innovate app it deserves


In most cases companies work differently. For this reason, LLodi offers you the possibility of using preconfigured forms that automate some business processes or create your own forms and workflows that adapt to the needs of your business.

It doesn’t have to be hard, though. Use LLodi to build an app that’s a perfect fit for your business. You can even make analytics mobile apps to complete tasks on the go.

Yes No

2.1.LLodi Forms #

Our Llodi forms allow you to take actions directly from your BI application. Natively embedded in Qlik®, the form interacts seamlessly with the associative power of Qlik®. These forms have a flexible design that let you create a myriad of solutions.

The forms defined in the LLodi platform, can be used in two ways:

Qlik Sense® & QlikView® Extension

Embedded in Dashboards, Mashups or Applications, our extension turns analytic dashboards into bidirectional interactive systems, letting you combine the logic defined in LLodi with Qlik® scripting. This provides an advanced environment for customization and complexity for consultants and, yet, a visual and user friendly appearance for the end user.

LLodi forms can also be triggered directly from Qlik® script with our.

Qlik Sense® & QlikView® Connector

so you can develop automatic actions from script every time the application is reloaded and taking profit of the scripting capabilities provided by Qlik®.

Yes No

2.1.2.Building your own Forms #

If you already have a Workflow (Zapier, Workato, Scribe Online or Custom Integration), you can create your own forms to be used with LLodi.

This LLodi App lets you register new workflows just by adding a name and URL (WebHook, endpoint) and choosing a form type. You can also fill a description for the form or add tags to manage your forms easily.

Once you register a new form, you will be guided to the page to create/edit your LLodi Fields, in the option “Show form fields”.

At first the URL field can be empty, until the workflow has been created in the chosen tool. At that time, it will be mandatory to enter the WebHook address or the endpoint.

Yes No Types #

Form Simple Forms

Input Text (the field number is defined as text)
Text Area
Input Select Combo
Check box
Read Only
Screenshot ( Save a screenshot as a base64 string)

For multi line forms:

Text (the field number is defined as text)
Text Area

Form Table Forms:


All Select type fields (Input Select, Input Select Combo, Multi Select) have the following feature:
Make name-id pairs with the separator “|”. In any select type field only the first subfield will be displayed, allowing to send additional info under the covers

eg: Name1|id1,Name2|id2
eg: Name|id|value

Combine this field type with the split formula to build a selector out of a csv list. Check out our Useful Formulas.

All Check type fields (Input Check, Multi Check) are default false.

You can edit the Placeholders for every text and area type field.

You can edit the Labels for every field that is not hidden.

Yes No help setting up an advanced form #

Log in and complete this quick form if you don’t find a LLodi Form that meets your requirements or if you have some cool ideas you want to request and you do not have the time to customize your own form and worflow.

We offer managed services to build, run and support your Business Apps.

Yes No

3.Integration Platforms #

Workflow Integration

LLodi can connect to most webhooks and endpoints of the available cloud services, either using integration and automation tools (like zapier, workato or scribe) or directly to the target application. Thanks to that, the circle is close, performing operations that act directly on the main data origin.

Connect your Qlik App with more than 1.000 applications: Salesforce, Sugar CRM, Microsoft CRM, HubSpot, MailChaimp, and much more!

Yes No

3.1.Zapier #

Zapier “Connect Your Apps and Automate Workflows” www.zapier.com

Zapier is one of the leading applications to automate easy-to-use cross-application workflows for both business and IT users. Ideal for developing simple processes (Zaps) with more than 1,000 applications.

Zapier offers a free trial for 14 days, which allows you to create any process without limits of steps or applications. https://zapier.com/signup

After creating the account, you have access to the platform in order to create your first Zap. In the Explore option, all possible applications that can be used are displayed. If you select Salesforce, you will see some pre-configured zaps and if we keep scrolling down, a box appears with the different actions that this connector allows.

A Zap can take several steps. If you create a Zap to be integrated into a LLodi form, in the first step you will always have to select the “Webhooks by Zapier” app.

In the “Choose Trigger” section mark the “Catch Hook” option – Continue
Set up Webhooks by Zapier Hook – Continue
The following screen appears, with the address “webhook url”. When you press OK, Zapier will wait for a test.

The address “Webhook URL” should be copied in the URL field of the Custom Forms that we are going to create. Add the name, the type, in this case Zapier and click on the insert button

If you know the fields to create the action, you can click on the icon and enter “Show form Fields” to add and configure the different fields that will later be used in the form and sent to Zapier.

If you know the fields to create the action, you can click on the gear and enter “Show form Fields” to add and configure the different fields that will later be used in the form and sent to Zapier.

If you do not know the fields, access the Zap in Zapier and select App in the second step, choose Salesforce and all available actions appear. Tag “Create Task”, click on the continue button (Zapier will ask you to connect your Salesforce account) and later a screen with all fields that you need in Salesforce will appear to create the task.

Cool, now you have all the information to create the form. It’s been quite easy, hasn’t it?

After creating the fields in LLodi, return to the Custom Forms screen and click again on the gear, on this occasion you will have to access the “Test Form” option of the gear to run the test. This process will connect LLodi and Zapier, and in the previous screen, you will be able to join each Salesforce field with a field of LLodi.

More help “Creating a Zap” in Zapier.

Yes No

3.2.Scribe Online #

Designing a LLodi Map

The Scribe Online Request-Reply Map
Create a Request-Reply map. The only thing you need to know is what fields you want and how you want them to behave.
As of the response, LLodi Widgets expect one single field named “Respuesta”. This field supports basic HTML to display whatever response you want to the end user.

LLodi Widgets already send some fields that you may want to use in your map:
– OSUser: BI End User that triggered the action.
– pn_guid: GUID of the LLodi Map.
– App_name: Field built in the Widget for monitoring purposes.
– App_id: Field built in the Widget for monitoring purposes.
– Selections: Field built in the Widget for monitoring purposes. You can use this to register the selections in specific fields in the BI dataset.

The LLodi Map
Check the different Field types available.

Assigning the target
– LLodi fields: (up to 9) make this the target whenever you want the widget to fill up this field in the form with data from the BI app.
– Console: make this the target of a field if you want to set the value directly from LLodi Platform.
– No target: make this the target of Text and Area fields.

Choosing a formula (for Select field types)
– senseField: in Qlik Sense, this formula will retrieve the content of a field and fill up the selector with the data from that field, you will also make selections directly into your app. In any other BI tool, this field will behave as if it had the split formula.
– split: use this formula to fill up the selector from a csv list.
– No formula: use this formula if you want the widget to leave the field as it is.

Yes No

4.Analytic Widgets #

Download: Put decision-making and action-taking LITERALLY in the same page with the LLodi Widgets, natively designed for:

Qlik Sense
Qlik View

Yes No

4.1.Qlik Sense Extension #

Qlik Sense Extension

Download the extension
Install the extension in your server or your desktop version.
Drag and drop the extension into the dashboard.
Introduce the GUID of the LLodi Map you are going to use.
Fill up the LLodi Fields.
Fill up the monitoring fields.
Custom the style of the LLodi Form.
Check out some Useful Formulas

You have the possibility to use the same extension for different forms. Ask our support team.
SenseField Feature: With Qlik Sense you can just select one existing field to fill up a selector.

Keep in mind:

The default value for the fields Enter App Name,Enter Title and Enter Context are DocumentName(), DocumentTitle() and GetCurrentSelections(). Make sure you check it before you start working with your LLodi Workflow. You may need to select it and press Enter to force Qlik Sense to evaluate those formulas.

In some cases a Workflow may get you back a selection. In those cases a button “Select” will be displayed besides your Response.

Yes No

4.2.QlikView Extension #

Qlik View Extension

Download the extension
Install the extension in your server or your personal edition.
Go to web edition mode.
Right-click to add the extension into the dashboard.
Introduce the GUID of the LLodi Map you are going to use.
Fill up the LLodi Fields.
Fill up the monitoring fields.
Check out some Useful Formulas.

Yes No

4.3.Power BI Custom Visual #

Power BI Custom Visual

Download the custom visual.
Install the custom visual in your desktop application.
Drag and drop the extension into the dashboard.
Create a measure with the GUID of the LLodi Form you are going to use and drag it into the GUID field.
Create some more measures to fill up the LLodi Fields.
Fill up the monitoring fields.
Custom the style of the LLodi Form.
Check out some Useful Formulas.

Yes No

4.4.Useful Formulas #

Make a Concatenated list

LLodi Widgets use comma separated lists to build the selectors and to send several values in one shot.

Qlik Sense and Qlik View:
eg: concat(region,’,’,regionid)

Power BI:
eg: CONCATENATEX(regions,regions[name],”,”,region[name])

Remember to use single quotes in Qlik and double quotes in Power BI

Make lists of pairs

In most cases you will want to make pairs name-id so LLodi can display the name while uses the id to make the operations under the covers. In those cases you just need to go one step further:

Qlik Sense and Qlik View:
eg: concat(region&’|’&regionid,’,’,regionid)

Power BI:
eg: CONCATENATEX(regions,regions[name]&”|”&regions[id],”,”,region[name])

Make lists with additional info attached

Once you’ve got started you may think of new LLodi Form that you want to request. For example, you may want to send additional info beside the name and id, such as the total sales amount of one particular client.

Qlik Sense and Qlik View:
concat(distinct aggr(only(name)&’|’&id’|’&sum(value),aggregatedby),separator,sortby)
eg: concat(distinct aggr(only(region)&’|’&regionid’|’&sum(amount),regionid),’,’,region)


Certain LLodi Forms allow you to choose the date format for your users to input.
The DateFormat value is composed by dateparts sort and separator.

DateParts sort:
mdy: mm/dd/yyyy
dmy: dd/mm/yyyy
ymd: yyyy/mm/dd

Separator: choose the symbol your users will use.
eg: dmy/
eg2: mdy-

Yes No

5.Monitoring Dashboard #

Actions Monitor

Use our built-in app to monitor the decisions that have been taken with your LLodi Maps.
If you prefer, you can retrieve the data with our REST API and build a fancy BI app with it.

Yes No

6.Account Settings #

Account Settings

Yes No

6.1.Register End Users #

Registration of end users who will use analytic applications with LLodi Forms.

Yes No

6.2.Security Console #

Usually there is only one admin user to manage the LLodi environment. In case it is necessary to have more users, you can request their creation to the support team. In cases that multiple users exist, it will be possible to confirm the access to the different options through the creation of labels and their subsequent allocation to the user.

Yes No

6.3.Stand Alone Users #

LLodi has a generic widget that can be used for BI tools for which there is no native widget.

In case of using this widget, it is necessary to register the users who will be able to access the forms.

Yes No

6.4.Rest Api Client #

This part of the help page describes the LLodi REST API specifications for developers and some general guidelines you may need in order to use the API. For all your requests you will need en API key that will be assigned to you once you have a LLodi account. Below it is described how to obtain the key via an API request.


Base URL: https://platform.llodi.com
Response: All API responses are given in JSON format so make sure your client accepts JSON. Usually your request will need to add the header “Accept” with “application/json” value
All REST API responses contain the header “Content-Type” : “application/json” and are in UTF-8 format.
HTTP method GET is used to te retrieve info from the API. HTTP method POST is used to insert info via API
Response Codes:
Success: 200
– 400 for bad request (requirements are not met)
– 404 for not found request (data is not found )

In order to get your API key you must have an active LLodi account and make an HTTP request to the REST API with following requisites:
Endpoint: https://platform.llodi.com/api/rest/v1/security/apikey
Method: POST

– Parameter name: Authorization
– Parameter value: base64(username:password) where base64(username:password) referes to your LLodi username (email) and password coded in base64 format. Base64Encoder E.G. base64(millodiusername@mycompany.com:myllodipassword)

If all requirements are correct you will get your API key with the following model:
“Api_key” : “YourApiKey”

Below there is a list with all endpoints available and their specifications.

Get all decisions
Description: Get your decisions from LLodi Decision Monitor. These request can be filtered by several fields.
Method: GET
Path: /api/rest/v1/decisions/{apiKey}
– user (optional)
– type (optional)
– startDate (optional)
– endDate (optional)
– app(optional)
– foreign_parent(optional)
– foreign_child(optional)
– limit (optional)
– offset (optional)

Response model:
“pn_guid”: “”,
“pn_name”: “”,
“api_key”: “”,
“decisions_guid”: “”,
“created”: “”,
“decisions_type”: “”,
“decision”: “”,
“description”: “”,
“app_name”: “”,
“user”: “”,
“n_rows”: 0,
“foreign_parent”: “”,
“foreign_child”: “”

Description: Get your KPI from LLodi Decision Monitor. These request can be filtered by several fields.
Method: GET
Path: /api/rest/v1/decisions/{apiKey}/kpi
– user (optional)
– type (optional)
– startDate (optional)
– endDate (optional)
– app(optional)

Response model:
“types”: 0,
“decisions”: 0,
“details”: 0,
“users”: 0,
“rows”: 0

Get field
Description: Get fields values from LLodi Decision Monitor field.
Method: GET
Path: /api/rest/v1/decisions/{apiKey}/field/{field}
URL: {field} represents the field you want to get data from.

Response model:

Create a decision
Description: Creates a decision in LLodi.
Method: POST
Path: /api/rest/v1/decisions/create/{apiKey}
Headers: Authorization : base64(username)

Request body model:
guid: “” , (required,unique),
description: “” ,
foreign_identifier: “”,
closed :0,
value :0,
comments: “”,

Response model:
response: “Record created”

Create decision details
Description: Creates decision details in LLodi.
Method: POST
Path: /api/rest/v1/decisions/create/{apiKey}/details
Headers: Authorization : base64(username)

Request body model:
decisions_guid: “” , (required)
description: “” ,
details: “”,
foreign_identifier: “”,
closed :0,
value :0,
comments: “”

Response model:
response: “Record created”

Yes No

6.5.Time Balance #

Check how many support hours you still have available for your customizations and in what actions they have been used so far.

Yes No

7.QvLLodiConnector #

QvLLodiConnector allows you to develop automatic actions from script every time the application is reloaded and taking profit of the scripting capabilities provided by Qlik.

Installing your connector

To install Custom connectors, you have to copy the files from the zip into the directory:

C:\Program Files\Common Files\Qlik\Custom Data\QvLLodiConnector.

Using this path, the connector will be available both for QlikView and Qlik Sense.

Restart Qlik and begin to use QvLLodi Connector!

*Some versions of QlikView may not work in that path, in that case use:

C:\Program Files(x86)Common Files\QlikTech\Custom Data\QvLLodiConnector.


Create new data connection in Qlik Sense

Once you have unzipped the files in your directory you have to add the connector as a new Data Connection.

Select QvLLodi Connector from the list, a modal will be opened where you can login into LLodi.

Give to the connection your preferred name and complete your login credentials, check the connection and then you can finally create it.

Now the connector is available on your sidebar as a Custom Connector, insert your connection string and select your data to create and copy the generated script.

Create new data connection in QlikView

To be able to use QvLLodi Connector in QlikView you must turn on WebView from View Menu. Then enter on Edit Script and choose our connector in Database.

Use your username and password to connect with LLodi. Test connection and then you can give LLodi access to QlikView.


Now your new data connection is ready to use within data load editor.


Using your connector

Once you have connect with the QvLLodi Connector you can use within your data load editor.

Just connect with the connector, complete the fields and copy the generated script.

Everytime you reload your app the connector will work, remember that you can apply the logic from Qlik to the connector and use variables to complete your Form Fields in the data load editor or the script.

Advanced Options: Override Request

In addition to WITH FIELDS (), you can add the sentence “WITH CONNECTION ()”, that will override URL, Headers and/or query parameters using the keywords: “URL”, “HTTPHEADER” y “QUERY”. This works the same way as REST Connector.


  • URL: Using this keyword you can replace the URL define in form settings in LLodi Platform.
  • HTTPHEADER: We can use this keyword to add as many headers as we want to the payload. We must define key and value.
  • REQUEST: With this keyword we can add parameters to the URL, we can also add as many parameters as we want. We must define key and value.


Select * from Slack
with fields (“text” “value”, “channel” “value2”)
WITH CONNECTION (URL “https://www.llodi.com”, HTTPHEADER “Content-type” “application/json”, HTTPHEADER “Accept-Language” “*”, QUERY “id” “1234”, QUERY “OLDIE” “1952”);


In this case the details of our request will be:





Content-Type: application/json.


Yes No