Populate Signed Time with airSlate SignNow

Populate signed time

the flow in today's WTF episode is available on the tdg para platform bank filter the category to flow and it's this flow here happy flowing hi everyone its Benitez here welcome back to my youtube channel and today's WTF episode I'm going to show you how you can populate a date and time field based on a user's timezone and dynamics 365 and zds today's agenda is an advanced of new topic I will do a quick recap of functionality that is available today in classic dynamics v65 workflows and then we're going to jump straight into flow there are two configuration methods that will allow you to set date and time for date and time fields in a dynamic 365 workflow the first one will allow you to add and subtract month days hours and minutes because it can only do add or subtract you cannot set a specific time using this method the second method is using the default value date and time now for the time you can set it to a particular time such as 9:00 a.m. however with a date you are fixed to that date meaning you can't do add or subtract days based on the default date value that you selected if you were to continue with this method in your workflow the problem is someone who is based in another time zone such as Wyatt in New Zealand will see the time value based on their time zone so Aaron Rogers he's based in Wellington New Zealand and he's seeing the time as 11:00 a.m. and that is because 9:00 a.m. in Melbourne Australia equals 11:00 a.m. in Wellington New Zealand so why is this a problem well for any user who's in the same time zone as Eliza won't have their tasks created with a due date of 9:00 a.m. for the Melbourne Australia time zone for someone like Aaron who is based in Bryant in New Zealand his due date will be 11:00 a.m. because there's two hours ahead of 9 a.m. so you can't set the task due date and time based on the user's local timezone when you are configuring with classic dynamics 3 6 5 4 close however the good news for you is you can do this in flow and this is what I'm going to show you today let's go straight into my floor now in this flow my trigger is when the case is created and my next action is getting the user record based on the owner of the case the next step that we're going to do in this flow is we will use the same action again which is the gift record and this time the entity that we are going to cool is the user's settings excuse me I do not want Salesforce in my flow alright so back to what I was saying we are going to get the users setting and float and that is because this...