PI UFL Connector Event Frame Generator enhancement and bugfixes
Currently it is not possible to create an event frame from the PI UFL Connector linked to an existing element, despite the documentation does not specifically mention this restriction, you can only link the new event frame to an element created within the current capture ( #902422 )
This is really a bad limitation and a really bad practice.
For an equipment I'm getting csv files at the end of its batch run, and it would be extremely helpful to create for every file loaded by the UFL a specific event frame directly linked to the equipment , so I can get them easily from PI Vision in the equipment displays.
This is not possible as the only element I can link this event frame is one generated inside the capture, that has its own automatically generated element template and so on.
In addition if I even want to generate an element, I cannot create one from an existing template, and I cannot specify a full path where I want to place this element.
Carlo Pedroli commented
"You can still create an EF to an element that already exist, but you will need to define it in your INI" is it true, but if the required element was created by UFL itself in another datasource with static attributes, the "EF .ini" sets all these attributes as Excluded
Gabriel Verreault commented
The connector can only write to AF and not read. Thus, it is not aware of the context.
You can still create an EF to an element that already exist, but you will need to define it in your INI. As if you were creating it (although it already exist), then you will be able to store your event frame.