During our testing we have encountered an issue with the SO not resolving the CONTROLLER BLUEPRINT NAME and VERSION. Can you please look into this. Here are the logs.       aseaudi 2:17 PM it's because this parameter name is in the BPMN context, but it's not set by the BPMN in the catalogdb, the CDS_BLUEPRINT_NAME is OK in the so code, i see the code that reads the sdnc_artifact_name from CSAR and updates the vnfresourcecustomization table in CDS_BLUEPRINT_NAME but i don't see in the code where it sets CDS_BLUEPRINT_NAME in the BPMN context is alexis patch for this specfic item, or was it for something else ? i am asking about the java, not the bpmn the bpmn patch, i understand, and now it stops the flow, due to the same issue we had with configdeploy null exceptionHi     2019-06-03T16:16:02.799Z|| o.o.s.b.i.flowspecific.tasks.ConfigAssignVnf - Start preProcessAbstractCDSProcessing  2019-06-03T16:16:02.878Z||  onap.so .client.exception.ExceptionBuilder - Exception occurred java.lang.NullPointerException: null at org.onap.ccsdk.cds.controllerblueprints.common.api.ActionIdentifiers$Builder.setBlueprintName( ActionIdentifiers.java:633 ) at  org.onap.so .client.cds.AbstractCDSProcessingBBUtils.constructExecutionServiceInputObject([AbstractCDSProcessingBBUtils.java:84|https://urldefense.proofpoint.com/v2/url?u=http-3A_ abstractcdsprocessingbbutils.java-3A84 &d=DwMF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=4IIOMdJjMRUSnNTEG5jeUQ&m=2jCJOoIBwagSQsq4JDVqrNAuAnkGvXcaw-951xRDYoo&s=_3RJGi1EXwW5ZzZMlLTwS5HLNRwlDw0W4NkowL2r1ag&e=]) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) after modifying the bmpn, we now call the configassignvnf java, and we get the same error, as i mentioned earlier