Migration of existing PNF PnP sub-workflows to a new BB approach (probably we will be creating 4-5 new BBs).

VID Impact:

Within “old” VID macro orchestration pages, a special field to provide a pnf-id parameter (shall be actually called “correlationID” or “PNF correlationID”) has been displayed under the following conditions:

1. Service Model contains a PNF resource type.

When we migrate to BB approach, we`d keep the possibility to provide this parameter (PNF correlationID) to the SO API call as input.

How this will change with SO/BB approach, and with new VID GUI targeted at macro (GR) flows – we`d see exactly, after we execute some tests with new VID UI, and updated SO PNF BB code.
We`d have to check, what capabilities and conditions could be applied to display and process this “PNF Correlation ID parameter”.

Can the same BBs could be re-used in “standard” vCPE use-case.
We`re looking at a generic solution, and we`d probably display this additional field, when we figure out, that there is a PNF resource used in a Service Model.