ProcessMIX Guide
  • Platform Overview
    • Introduction
    • Platform Purpose
    • Main Concepts
      • Organization Structure
      • Visual Language
      • Project Development Environment (IDE)
      • Deployment and Integration
      • Administration and Troubleshooting
    • First Steps
    • Change Log
      • 5.0.0
      • 5.0.5
      • 5.0.5.1
      • 5.0.5.2
      • 5.0.5.3
      • 5.0.5.4
  • Language Reference Guide
    • Overview
    • Data Structures and Types
      • Core Types (pdk.core)
      • Dictionary (pdk.asset.dictionary)
      • Scorecard (pdk.asset.scorecard)
      • Blockchain (pdk.blockchain)
      • Exceptions (pdk.ex)
      • Input/Output (pdk.io)
      • JSON Web Token (pdk.jwt)
      • Networking (pdk.net)
      • HTTP (pdk.net.http)
      • SOAP/Web Services (pdk.net.soap)
      • XML/DOM (pdk.net.xml)
      • S3 (pdk.s3)
      • SQL (pdk.sql)
      • Postgres (pdk.db.postgre)
      • Util (pdk.util)
      • Default Data Structure Field Values
    • Flows
      • Variables
        • Local Flow Variables
        • Node Variables
      • Flow Node Types
        • Core Nodes
          • In
          • Out
          • Assign
          • If
          • Switch
          • Iterator
          • Function Call
          • Subflow
          • Raise Exception
          • Exception Handler
          • Validator
        • Connector Nodes
          • Database Begin Transaction
          • Database Commit Transaction
          • Database Rollback Transaction
          • Database Query Executor
          • EVM Blockchain Functions
          • EVM Blockchain Smart Contract Functions
          • REST Service Executor
          • SOAP Service Executor
          • S3 Connector
          • SMB Connector
      • Expressions
      • Built-In Functions
        • Expression functions
          • pdk.util.Any
          • pdk.util.Array
          • pdk.util.Blockchain
          • pdk.util.Cast
          • pdk.util.Codec
          • pdk.util.Crypto
          • pdk.util.Date
          • pdk.util.File
          • pdk.util.Json
          • pdk.util.JWT
          • pdk.util.Map
          • pdk.util.Math
          • pdk.util.String
          • pdk.util.Util
        • Node functions
          • pdk.flow.Any
          • pdk.flow.Array
          • pdk.flow.File
          • pdk.flow.JsonArray
          • pdk.flow.JsonObject
          • pdk.flow.HttpRequest
          • pdk.flow.HttpResponse
          • pdk.flow.Logger
          • pdk.flow.Map
          • pdk.flow.Xml
            • pdk.flow.xml.XmlAttr
            • pdk.flow.xml.XmlElement
            • pdk.flow.xml.XmlNode
            • pdk.flow.xml.XmlDocument
            • pdk.flow.xml.XmlDocumentType
            • pdk.flow.xml.XmlDOMConfiguration
            • pdk.flow.xml.XmlDOMImplementation
            • pdk.flow.xml.XmlProcessingInstruction
            • pdk.flow.xml.XmlTypeInfo
            • pdk.flow.xml.XmlCharacterData
            • pdk.flow.xml.XmlText
            • pdk.flow.xml.XmlNamedNodeMap
          • pdk.node.BlockchainEth
          • pdk.node.S3
          • pdk.node.Smb
      • Exceptions
        • Checked Exceptions
        • Runtime Exceptions
    • Assets
      • Dictionary
      • Decision Table
      • Scorecard
      • PMML
    • Connectors
      • DB Connector
        • Prepared Query
        • Dynamic Query
        • Query input parameters
        • Stored Procedure
      • REST Connector
      • SOAP Connector
      • S3 Connector
      • SMB Connector
      • EVM Blockchain Connector
    • Global Variables
    • Appendices
      • Overview of Database Transactions
      • Reserved Words
  • Project Development Environment (IDE)
    • Project Explorer Panel
    • Flow Builder
    • Flow Node Editor
    • Data Structure Builder
    • Connector Builders
      • REST Connector Builder
      • SOAP Connector Builder
      • DB (Database) Connector Builder
      • EVM Blockchain Connectors Builder
      • S3 Connector Builder
    • Asset Builders
      • Dictionary Builder
      • Decision Table Builder
      • Scorecard Builder
      • PMML Asset Builder
    • Global Variables Panel
    • Expression Editor
    • Project Deployment and Execution
    • Cron Expression Generator
    • Test Helper
    • Debugging the Project
    • DB transactions
    • Team Collaboration Tools
      • Version Control
      • Conflict Resolver
    • Selectors
    • Error Panel
    • Local History
  • Home and Administration Guide
    • Organization and Subscription
    • Organization Team
    • Repositories and Projects
    • Environments
    • Deployments
    • Database Provisioning
    • Roles and Permissions
  • Logs and Troubleshooting
    • Request/Call Logs
    • Deployment Logs
    • Application Logs
  • Appendix: Example Project
    • Risk Mitigation Solution
Powered by GitBook
On this page
  • Custom Dictionary
  • Reason Code Dictionary
  1. Language Reference Guide
  2. Assets

Dictionary

PreviousAssetsNextDecision Table

Last updated 6 months ago

In ProcessMIX, Dictionary is a tabular data set (a spreadsheet) used for storing lookup information, which you can create directly in your project for easy access and maintenance. Columns in a ProcessMIX dictionary have data types, so that they can be used for structured information storage and retrieval - an essential requirement in automated data processing.

When a dictionary is created, a corresponding backing is also automatically defined in the same project, which contains a separate property for each table column,. This way dictionary entries can be accessed programmatically from flows in a standard fashion, as any other processed data.

When you edit dictionary parameter names and values, the backing data structure is automatically updated as well, in order to keep it in sync with the dictionary settings.

There are two types of dictionaries in ProcessMIX:

  • Custom dictionary—a general-purpose lookup table, which you can use for information retrieval by adding a corresponding node in a flow.

  • Reason code dictionary—a specialized lookup list for providing explanatory reason codes and descriptions when calculating predictive scores with the help of assets.

The type is specified via a configuration property in the dictionary builder.

Custom Dictionary

Custom dictionaries can have any number of columns, but they must be of simple data types: String, Integer, Float, Boolean, or Date.

For example, you could define a custom dictionary to store a list of country codes, names and their currency codes:

Name: CountryList
countryCode (String)     countryName (String)    currencyCode (String)
971                      Afganistan              AFN
008                      Albania                 ALL
012                      Algeria                 DZD 
...

Then you can add a reference to it as a node to your flow and be able to retrieve a full or filtered list of country records to use in the rest of the flow as you wish.

It is advised not to edit the backing data structure directly, using the parameter settings in the dictionary builder itself. If you need to open and edit the data structure directly, it is important that you only use properties with simple data types, such as String, Date, Integer, Float, Boolean, from the backing data structure when selecting parameters for each column in the dictionary. Otherwise, you will see an error when you try to select such property as a column type.

Reason Code Dictionary

This dictionary type is used as a supporting tool when developing scorecards. It helps to produce a human- and machine-readable explanation of the reasons why a particular score was calculated by the model.

It is restricted in a sense that it needs have few standard columns, which are automatically added as properties to the auto-generated backing data structure:

  • Rank (Integer)

  • Name (String)

  • Code (Integer)

  • Message (String)

Additional custom properties/columns can also be added, but the above mentioned ones are required for the proper scorecard implementation.

You can learn more about creating and editing dictionaries in the section.

data structure
scorecard
Dictionary Builder