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.

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/about-journey-building/condition-activity It can be branched out based on a specific criteria (say for example, if the preferred channel is email, then email can be configured and if it sms, then sms node can be ...

It shouldn't affect the SMS action ideally. If there are any failures, you can see the corresponding event in message feedback dataset

You can use the below expression assuming you have a date time field in the event payload which is a future date (in the custom wait) in journey canvastoDateTimeOnly(toDateTime(((toInteger(<your_date_time_field>))) - (toInteger(5*24*60*60*1000)))) 

Correct, existing Org's won't be impacted.