2025.4.3

Flow - New Allocation and Condition Steps

We developed new Allocation and Condition steps.

Allocation step allows you to divide a transaction amount and allocate the partial amounts based on a selected criterion, such as cost centre, department, product, etc.

The way this works in Fynapse is the input Transaction Event from the Input step is divided into multiple Transaction Events with partial amounts divided based on the defined driver attribute from a Reference Entity, e.g. department, cost centre. 

Condition step allows you to define conditions for your processing rules. Using this step you can generate multiple outputs going into different subsequent steps.

For more details, refer to Flow Steps.

1
"flows": [
2
            {
3
                "versionStatus": "Published",
4
                "name": "ConditionalAllocation",
5
                "graph": {
6
                    "edges": {
7
                        "2230feee-76db-48dd-bb90-30171ece1206:0": [
8
                            "638a4aed-1acd-43e5-9a88-0f60bb1211b3"
9
                        ],
10
                        "2230feee-76db-48dd-bb90-30171ece1206:1": [
11
                            "7a40a4eb-bd7b-4146-95cf-00316da86f41"
12
                        ],
13
                        "2230feee-76db-48dd-bb90-30171ece1206:2": [
14
                            "5af4fb62-5c23-4c4a-aee3-cfaa1f7f09d8"
15
                        ],
16
                        "5af4fb62-5c23-4c4a-aee3-cfaa1f7f09d8:0": [
17
                            "edf44cd0-1964-40c2-964e-3e6a1b1b3b21"
18
                        ],
19
                        "638a4aed-1acd-43e5-9a88-0f60bb1211b3:0": [
20
                            "35aa4a57-af6a-4381-8135-25771c280dd4"
21
                        ],
22
                        "741a2ec1-5d9e-494c-8d74-61e14187208a:0": [
23
                            "45bd8b34-6e24-4f9a-a717-4abd1129711d"
24
                        ],
25
                        "7a40a4eb-bd7b-4146-95cf-00316da86f41:0": [
26
                            "741a2ec1-5d9e-494c-8d74-61e14187208a"
27
                        ],
28
                        "edf44cd0-1964-40c2-964e-3e6a1b1b3b21:0": [
29
                            "d17901e1-ba74-42bd-aadc-a2245a62a602"
30
                        ],
31
                        "fb923048-50a2-4120-b30a-6151f9dcd136:0": [
32
                            "2230feee-76db-48dd-bb90-30171ece1206"
33
                        ]
34
                    }

Flow - New Mapping Feature

We added a new Map by name feature that is available in the Attributes Mapping tab in all steps which require attributes’ mapping. This feature allows you to automatically map input attributes with target attributes with the same name.

REST API New Statistics Endpoints

We implemented new Statistics endpoints that allow you to gather different metrics:

• Get ingestion metrics - provides information about ingestions, both API-sourced and from ingestion files, in a defined period
• Get Journal metrics - provides information about the status of ingested Journals in a defined period
• Get Journal metrics by day - provides information about the status of ingested Journals per day
• Get processing metrics - provides information about Business Event processing metrics and the total number of records generated by a Flow
• Get throughput metrics - provides information about the daily average processing speed of ingested Journal Lines per day

For more details, refer to API Changelog, Statistics via API and API Reference Guide.