Kindly take a look at the following links https://experienceleague.adobe.com/en/docs/journey-optimizer/using/content-management/personalization/functions/dates#age https://experienceleaguecommunities.adobe.com/t5/journey-optimizer-questions/getting-age-field/m-p/675449  

It will be in the existing datasets (message feedback and email tracking datasets). You can filter with  _experience.customerJourneyManagement.messageProfile.channel._type='https://ns.adobe.com/xdm/channel-types/whatsApp'

profileID corresponds to the namespace value configured in the starting node of the journey. If you have used crmId as the namespace, then the corresponding crmId values will show up against this column.

You can use the expression example similar to the one posted in this thread https://experienceleaguecommunities.adobe.com/t5/journey-optimizer-questions/5-days-wait-on-journey/td-p/763236 

It's strange to see that there are multiple words in first name. Below is a simple example and you can expand on it using additional functions like listSize (if needed)if ( indexOf("MOHAN DUGGANABOIENA"," ")>=0 ) then ( (upper(substr(getListItem(split("MOHAN DUGGANABOIENA"," "),0), 0, 1))) + (lowe...

You can look at some of the examples in the playground here https://experienceleague.adobe.com/en/apps/journey-optimizer/ajo-personalization?lang=en# for displaying it in the message content and apply conditional logic within the loanDetailsObject where activeLoan = true and simultaneously, incremen...

You can create a batch segment leveraging attributes from ajo_email_tracking_experience_event schema (https://experienceleague.adobe.com/tools/ajo-schemas/schema-dictionary.html?lang=en) and use it accordingly in the condition as an inAudience check as creating expressions using experience events ha...

I ran a test and shows up correctlyExpression - (upper(substr('MOHAN', 0, 1))) + (lower( substr('MOHAN', 1))) + ' '+ (upper(substr('DUGGANABOIENA', 0, 1))) + (lower( substr('DUGGANABOIENA', 1))) Result -  

Hopefully, you have validated with the latest expression as I see the right result being returned.

That's the expected behavior.