Working with Data Types

Avatar

By Alina Panaite

updated about 1 month ago

Each process variable has a data type.  PROCESIO supports the following data types:

Primitives: string, integer, float, boolean, date-time, JSON

Custom: data model (a custom data type that can contain one or more attributes)

Examples of data types

  • Primitive Value (type string)

John

  • List of Primitive Values 

John

Mary

George

Daniel

  • Data Model 

John 

Doe

31

  • List of Data Models

John 

Doe

31

Mary

First

24

George

Tahoe

29



File” data type

The “File” is a data model that contains the following attributes:

  • path: the file path set automatically to the file location when it’s being uploaded to the PROCESIO platform

  • name: the name of the file

  • mime-type: the file type

  • size: the file size

Use a “File” variable type as process input to be able to create processes that use dynamic files as attachments in the “Send email” action. Or use it as an output variable to map to it a file that you get from the “Call API” action.

How to work map variables

Be mindful of the data types compatibility when passing values from one process variable to the property of an action. Each action property expects a given data type. This means that the variable type must match with the expected property type of the action. We refer to this as data mapping.

The variables used at a process level are called process variables. Each process may have:

  1. input process variables (optional)

  2. output process variables (optional)

  3. process variables used within the process (optional)

If the process needs certain dynamic data in order to start, you need to configure process variables that have the “Input” tag enabled. Declare variables as “Output” if there’s certain data that you expect to get back from the process once the process has executed successfully.

 You need to consider the following when mapping input/outputs to process variables:

  • PROCESIO does not support mapping of data from one type to another thus you need to map data of same data types. You can always create a new process variable of the corresponding data type if needed.

    • Exception: conversion from Integer to Float is allowed, as well as conversion from any primitive data type to String. 

  • Pay attention to <list> type of a process variable. Even though 2 process variables may have the same data type, you cannot map a process variable declared as single value to a process variable declared as a list.

  • String: properties that expect a string data type will accept any type of variable and concatenations.  

    • Exception: A data model cannot be mapped to a String property. Mapping of a data model attribute to a String property is allowed.

  • Integer property: you can map only integer variables

  • Float property: you can map both float and integer (conversion from Float to Integer is allowed)

  • Boolean property: you can map only boolean variables

  • For Date-Time: you can map only Date-Time variable and hardcoded value with the format: dd/MM/yyyy hh:mm:ss (UTC).

  • Data model: you can map to a data model property only a data model variable of the same type. For example, a “Customer” property accepts only the “Customer” data type as a variable. 

  • File: you can map to a “File” property only a “File” data model variable


Related links

Working with Process Variables

Creating a basic process

Did this answer your question?