Query : Adding custom attributes to flows.json (tab/subflow)

Hi ,

I have a query - If i add some custom attributes to a flow (via. processing flows.json) - attrbutes which i want to use for internal housekeeping ...

example :- All flows where type="tab" or type"subflow" - say - sourceInstanceName, owner.

This will be done via. processing the flows.json on instance 1 of NR1 and deploying to instance 2 of NR via. httpAdmin API.

Query is - so long the attributes are unique - which i know will not come from core - will they be maintained or some internal mechanism will remove them ?

Can these extra attributes cause some functional issues ?

I am not expecting to see these attributes in the editor.

We are trying to assess how to move flows from one env to other and maintain some trackability aspects.

The editor will only export properties it knows about. As soon as you hit deploy in the editor it will strip all of your custom attributes.

Being able to add custom attributes is something that has been in the backlog for a long time - but without any immediate need it has never been looked at in any detail.

Thanks Nick.

Our use case is basically being able to trace the flows across environments - and automate some updates and trace what sits where.

So we would have added few attributes to the flows to do this traceability.
Will wait for future.

Hi Nick ,

In connection to this - is it possible for add for core a date attributes on tab and subflows to indicate when this was last modified - create date , last modified date ? So core itself updates . Also if work in user login mode - then last updated by.

Projects versioning etc. needs github integration. Plus as i have understood even then 1 project can be active at a time.

I want to explore an option when syncing environments programmatically to give user a signal that target is newer than source and then he may take a call.

Do let us know. Thanks.

here is a silly idea .. maybe you can utilize the info attribute of flows, subflows etc to add the additional custom attributes you want.

The info property is the one being populated when you edit the Description
but you could use that possibly by comma separating your attributes ?
(last modified, version etc)

Example :


Shows up as :

        "id": "616c0e53159c5f07",
        "type": "tab",
        "label": "Flow 2",
        "disabled": false,
        "info": "2022-02-10 22:00:00,1.0.1",
        "env": []
        "id": "2e51e9c7341d0ebe",
        "type": "subflow:faef06365fc96dd3",
        "z": "616c0e53159c5f07",
        "name": "",
        "x": 700,
        "y": 400,
        "wires": [],
        "info": "2022-02-08 04:00:00,2.2.0"

kinda hackish i know
from what i understand you doing this programmatically which is beyond my league
so i leave you to it

I must say thats a hackish idea and a good one.

This means i need to remind every user to do this once he does change. I want the core to do it and then i can "read" it programmatically.

So for a flow/subflow - system itself indicates when it was created , last changed, by whom (if user login enabled) .

Then i can simply have a flow which can compare 2 envs and indicate which is more updated env and leave it to user to take the next call.

I was under the impression that you were POSTing/updating flows programmatically/remotly with httpAdmin API. if its the user updating its going to be a tedious process .. but its the only thing that i could think of that gives you the option to tag on as many different attributes you need.

The same could be done using Environment Variables (which is even cleaner),
even if you dont use them internally in the flow, you could use them to store some attributes



1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.