Archives for 21 Sep,2021

You are browsing the site archives by date.

← Back to Blog

Informer 5.5 Preview

Madhavi Chandra, Director of Informer Product Management, shares development details on our upcoming release Informer 5.5!

Hello (Hallo, Bonjour, Hola)! We are actively working on Informer 5.5 which will have many new features that bolster ease of use and global adoption. We showcased an early access build of Informer 5.5 to our Informer Advisory Council members, which was met with great enthusiasm and excitement for what is in store!

We can now take Version 5.5 on a world tour as it will have Internationalized UI support for Mexican Spanish, Canadian French, and German as well as support for dates and times based on the locale of a User.

A new top-level Global Search Bar makes it extremely easy to find anything in your Informer system with just a few keystrokes. The Global Search Bar searches through all entities in your entire Informer system and provides results in a categorized manner. Find what you need at your fingertips!

In addition, a new parameters bar on the Ad hoc Query page will display the parameters that back a result set along with the data. Easily interact with Ad hoc Queries by viewing the parameters that were entered on the same screen as the query results and change the parameter inputs right there. This will foster even more ease of use when interacting with Ad hoc Queries.

Query payloads are now updated at runtime to use the defined field/link definitions. This will dramatically improve efficiency as changes to fields or links made at the definition level will no longer need all references to that entity dropped and re-added for the changes to be reflected. It will also be easier to add multiple entries to User Fields assigned to a User that are then handled across the system including in Criteria and Elasticsearch Script Fields.

Dataset copying options are now more comprehensive and flexible. The User can choose which entities to copy over – Data, Visuals, Filters, and Sharing. The new parse logs based on new Log Settings provided in the Log Settings dialog enable the User to determine the specific amount and type of information that will be captured in the logs, making it easier to hone in on the exact log information desired.

Finally, we are expanding our Datasource connectors and will have a new Jbase Datasource driver (a NoSQL multivalue database) in Beta. The new driver provides the ability to scan and query a Jbase Datasource, and build Reports and Visualizations.

As you can see, much awaits you in Informer 5.5!

Read More
← Back to Blog

Using Custom Field Expressions to Enhance Informer 5

Robin Lamb, Director of Informer Client Services, discusses helpful tips on using Custom Field Expressions to enhance your Informer 5 experience.

On occasion, database-level functions need to process data fields before those fields are ready for use in reporting tools. For example, referencing a TRANS subroutine to pull Fields from one file into another on U2 databases or a SUBSTRING function on a SQL database to extract the ID of a multi-part key field. Many of these subroutine or function fields are ready and available on databases but there are times when they are not.

With Custom Field Expressions, it’s easy to create these subroutine and function fields inside of Informer 5 without having to touch the underlying database.

For instance, below is an example of creating a year field from a stored database date field. To create a Custom Field Expression, follow the steps below:

  • Go to Mappings, and then choose the Mapping where the date field lives
  • Click on Add Field
  • Name the Field (no spaces or special characters)
  • Choose the return type
  • Add the expression
    • When entering the expression, use the Insert Keyword Icon to assist with the expression language

Once you have entered the expression, use the Test Expression (checkmark Icon) to test the results.

Another example using this feature is creating a value based on a parameter of another field. In the example below, the code is creating a value for a product but this could be translating to any if/then type of statement.

CASE WHEN ${MAPPING_ALIAS}.product = 'productA' OR ${MAPPING_ALIAS}.product = 'productB' THEN .25
WHEN ${MAPPING_ALIAS}.product = 'productC' OR ${MAPPING_ALIAS}.product = 'productD' THEN .50
WHEN ${MAPPING_ALIAS}.product = 'productE' THEN .4
WHEN ${MAPPING_ALIAS}.product = 'productF 'THEN 1.5

There are many ways to use this feature to enhance the Informer 5 functionality. Other examples include creating aggregate fields, formatting output of data, concatenating fields together, and many more.

Read More