Alisha

Hi @Steve Giller, I stored the date in h_custom_e but in the Email Template, it outputs the date as 2023-06-07 (for today's date). Is there anyway to change the output to something less confusing, e.g. 7 June 2023, as it's not always clear if the date format is 7 June or 6 July, depending on which country you're from! Many thanks, Alisha

Good afternoon, Which role enables users to search for Archived Co-Workers please? We've had a look at the roles but can't find anything obvious. Many thanks, Alisha

We are using some of the Integer Custom Fields, but we also have the same problem with needing more Custom Fields.

We can see the first name and last name in the Connections panel, but no User ID.

Good afternoon, In my Business Process, I am using a Capture Outcome Field in a Human Task. I have used h_custom_p for the Field ID, but this doesn't appear to be updating. When checking Custom P in a report, the field is blank. Is there something else that I need to do to store this information in Custom P please? Many thanks, Alisha

Sorry @Steve Giller, I wasn't too clear. We can see the User ID, like in your screenshot, but when it's added to the Timeline, the User ID is missing - we only see the first and last name.

Good morning, Is there any update on being able to see the User ID when Impacting customers please? Being able to see the User ID as well as their first and last name would really help when searching for the customer as we use the User ID to help identify them. Many thanks, Alisha

Good morning, When linking Problems to an Incident, please could we see the date that the Problem was Resolved so we can see how recent it is when linking? Many thanks, Alisha

Hi @James Ainsworth, If we toggle the 'Reason Required' setting off, then there's no field to enter any comments when needed. Many thanks, Alisha

Good afternoon, Before Service Manager update (2853), we were able to set a sub-status and have the 'Reason Required' field appear but this wasn't mandatory so we could skip this when not needed. Now the 'Reason Required' field is always mandatory. Please could completing the 'Reason Required' field be optional per sub-status? Many thanks, Alisha

Hi @Steve Giller, We are trying to create a quick call, so the new request would be unrelated to the request that's currently open on the screen. Clicking on the custom button would log the request with all the necessary details, without having to go through the longer process via the Raise New button. Many thanks, Alisha

Good morning, When someone leaves the organisation and their account is Archived, it still shows their status as 'Available'. Please could a new status be created to 'Archived' or something similar, so we know that an account has been archived at a glance? Many thanks, Alisha

Good afternoon, Please could we have some date only custom fields. I have used h_custom_21 for the Date Control in a capture, but when I use h_custom_21 in an email template, it inputs the time as well as the date. We would only like the date to show please. I have tried to use Cloud Automation Utilities to convert h_custom_21 to Date only (which seems like a complicated way to just display the Date), and put the result on the Timeline to check it and it does display the date only. I then update result in the custom field, but when using h_custom_21 in the email template, it still shows the time. A date only custom field would be really helpful here. Many thanks, Alisha

+1 of for us please. This would be a really time-saving feature!

Hi @James Ainsworth, Do you have an update on this please? In addition to sending bulk emails within Request Actions, we would also like to be able to put the requests on hold in bulk as well please. At the moment we're having to manually email lots of different customers on their requests and then put them on hold individually, which is becoming a time consuming task. It would be good if we can speed up this task please. Also taking off hold in bulk would be handy as well. Many thanks, Alisha

Thanks Steve, that makes sense. We'll create an additional outcome like you suggested.

Good morning, Please could we have the option of deleting tasks when required. An example scenario is when the customer has raised a request incorrectly - we would resolve the request and advise the customer instead of cancelling it and the task is therefore not required. Although there is a delete button, this does not work and presents the below error. Many thanks, Alisha

Hi @James Ainsworth, Please could this be reconsidered as an enhancement as we do still have a need to link multiple sites. If it can't be done during the capture, it would be helpful if we could link them once the request is raised. Many thanks, Alisha

@Steve Giller @Victor Now that I have got the Analyst User ID from the source email and updated the Owner, is it possible to update the Resolved By to the Analyst if the value stored in a custom field is the same as the Owner? We would like to request to be resolved by the Analyst and not by the System AutoResponder. Many thanks, Alisha

It would help if I checked the ? - I will try to remember this in future! I appreciate all your help, thank you @Steve Giller

I'm slowly getting there... If I remove the first and last name and just keep the User ID, it has updated the Owner! (Our Handle contains the first name, last name and User ID.)

Hi @Steve Giller, I now have the Analyst's details output to the Timeline using the Regex Substring. However, when I try to update the Owner with that result, it doesn't work. Is this the correct variable that should be used? &[global["flowcoderefs"]["stringUtilsRegexSubstr"]["result"]] Many thanks, Alisha

Not a big issue, but noticed that when there is an apostrophe in a username, it shows the HTML code.

Hi @Bob Dickinson @Steve Giller, We have now run out of spare custom fields. Is there any progress on us getting additional custom fields please? Many thanks, Alisha

Hi @James Ainsworth, Alternatively, if there is a setting to leave the Customer part of the summary panel expanded throughout the whole capture, that would also work for us. Many thanks, Alisha