Application lookups provide an easy way to access custom types in your Andi skills. Custom application types are often hard to utilize without context. For example, a PrecisionLender rate type may be in the event data you interact with as the number 4. Without application lookups, it is hard to know that rate type 4 equals adjustable rate type in the context of the PrecisionLender application. This article will cover using and requesting application lookups.


In this Article


What are Application Lookups?

Application lookups are defined key-value pairs relevant to PrecisionLender and your organization. You can view these key-value pairs in two places.

  • By selecting the Builder tab > Resources > View Application Lookups
  • By selecting the Admin tab > Application Lookups

These two views are read-only and serve as a quick reference for usage in skill writing. You can leverage application lookups in your skills through skill configuration or using the Lookup Powers in the Andi Web Skills Builder.


Using Application Lookups in Skill Configs

Application lookups can be configured directly into skill configuration to help simplify configuring a skill.

To add application lookups in skill configuration, add a new skill configuration with option type and select Map to an application lookup?. You can also check multi-select if you would like to have an array of values in your skill.

In the image below, we want to allow multiple rate types to be configured. Like normal skill configs, your key name can be used in code. If only selecting a single application lookup type, the value will be a string or a number. If selecting multiple, there will be an array available for you to use.

shows the app lookups

With this setup, your skill configuration now becomes a multiselect for application lookups in your organization.

shows the app lookups status


Lookup Powers

In addition to skill configuration integration, application lookups can be accessed with lookup powers.

These powers allow for a more direct usage of organization and application mappings. For example, in the below code, the should I run criteria is determined based off the hard-coded region names matching the pricing region. In event data, the pricing region is often represented by a GUID. Lookups provide an easy way to map this to expected human-readable values:

shows the lookup

Note that the “Regions” was determined by referencing the available lookups in the Andi Skills Manager. The “Regions” text is one of the lookup names.


Sample Lookups JSON and Type Definitions

shows a sample lookup

{ "name": "RateTypes", "valueType": "number", "values": [ { "name": "Fixed", "value": 1 }, { "name": "Float", "value": 2 }, { "name": "Adjustable", "value": 3 }, { "name": "Swap", "value": 8 } ] }

Notice the id or type value will always be listed under “value”. The human-readable label for a lookup will always be name.


Requesting Additional Lookups

By default, some of your organizations’ types may already be synced. Check the relevant lookups pages in the Andi Skills Manager to be sure.

If you feel like something is missing or would be helpful, please reach out to our support team at support@andi.com for assistance.

Was this article helpful?
0 out of 0 found this helpful