You can take a look at the following documentation links which details the steps on how to send profile attributes and audience membership data to Pega Customer Decision Hub for next-best-action decisioning.https://experienceleague.adobe.com/en/docs/experience-platform/destinations/catalog/personali...

Looks like vacationPacakageDetails.fullDueDate is on the experience event schema ? Accessing experience event attributes via #{ExperiencePlatform.ProfileFieldGroup.timeSeriesEvents._xxxx.vacationPacakageDetails.fullDueDate} will not work (if you are using this in a batch journey starting with a read...

right, it is a direct UPS update and won't be available in "AJO Push Profile Dataset". You can query the profile snapshot dataset to fetch the push token details.https://experienceleague.adobe.com/en/docs/journey-optimizer/using/channels/push/push-config/push-gs

There wouldn't be duplicates as only single instance of a profile can be in a journey at a given point of time and hence, it will be an union

listString will be your array xdm path and you are comparing the first parameter against the whole array (listString). If you need to check for non existence of more than one value, you can use the following syntax not(in( 'DFC', <ListString> )) and not(in( 'XYZ', <ListString> )

can you switch the parameters in the function ? second parameter will be a listString and the first one will be a string not(in( 'DFC', <ListString> ))

You will have to use it on the following lines not(in(#{ExperiencePlatform.ProfileFieldGroup.profile.person.gender}, ["male"])) https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/building-advanced-conditions-journeys/main-functions-journey/list/functionin 

You can take a look at the Business events feature if that helps solve your use case https://experienceleague.adobe.com/en/docs/journey-optimizer-learn/tutorials/create-journeys/use-case-business-event 

Yes, it is

Indeed, looks to be a documentation error which I see has been updated now.