SJEaton

Okey doke

Hi @Ehsan which build was this in? Sam

Oh ok, all PCs are active but I guess I have to save/activate again! Thanks guys

Hi This works great for business processes but when i go into a PC the download a process defiinition file is not active. Why is this? Sam

Thats helpful thanks @Ehsan Where do you change this? Sam

OK, can this be put forward as a suggestion then as they display nicely in email templates but not in authorisation node tasks (or other tasks) so that would be a nice improvement, thanks

Hi @Ehsan, so basically, date/time custom fields will always display like this if pulled into authorisation nodes? Sam

Yes, thank you @Victor

Hi @Ehsan, do you have any further thoughts on how I rectify this? Thanks Sam

Thanks @Bob Dickinson!

Hi Is there a RegEx validation to limit a monetary amount e.g we don't want them a customer to enter more than £1500 in a field. Is this possible? Are there any regex examples /guidance published on wiki?? Sam

Thanks @Bob Dickinson, I can see where this could be useful so will get this switched on and inform our users its there. Sam

Hi @Ehsan, nope still not working for me. Must still be doing something wrong. This is what I've entered: Original Payment Start Date: [&[global["flowcode"]["customField22"]]] Original Payment End Date: [&[global["flowcode"]["customField23"]]] Proposed New Payment End Date: [&[global["flowcode"]["customField24"]]] This is what displays: Original Payment Start Date: [2019-02-26 00:00:00] Original Payment End Date: [2019-04-03 00:00:00] Proposed New Payment End Date: [2019-04-05 00:00:00] Sam

Hi @Paul Alexander, the get request details node didnt make any difference. I ended up deleting and reconfiguring it and it all seems ok now so must've been some kind of bug?! Thanks both for your assistance. Sam

Thanks @Martyn Houghton I'm liking your logic but the one's with '&' and '/' in are working fine. 'Volunteering Leave' is the one that isn't. I've also tried changing the 'No Match' option with a custom expression to no avail. I might just reconfigure it again just in case there's just a bug in it somewhere but other than that, this is definitely a head scratcher! Sam

Hi @Martyn Houghton, but I know the decision node is doing its job because the PC goes on to the relevant forms in the Volunteering Leave PC that it switches too. The issue lies when it hits the 2nd decision node in the BPM, which is based on CustomA Sam

Hi @Martyn Houghton, sorry, what would I have in this custom form?

Yes it does switch based on Catalog ID. Attached are some screenshots showing the ProCap, the request types and then the BPM and whats configured for the No option from the decision. Basically anything other than these two request types should go through the no match route. All others work except Volunteering Leave Sam

Great, thanks @Ehsan

I need some help with a workflow that isn't routing as I expect. I've configured a ProCap called 'TEST My HR Absence/Leave Transaction (with Switch)' that includes 2 x switch capture nodes based on 2 options selected in a request type field (Custom A). These all work perfectly and then trigger the 'TEST My HR Absence/Leave Transaction Request Process (with Switch)' BPM . The BPM has a decision early on based on Custom A so that it sends a different email dependant on what request type is entered for this custom field but for the no match route, all work fine except the 'Volunteering Leave' request type. This is one of the switch capture options but the other no match, switch capture option works fine. I therefore don't understand why the Volunteering Leave option routes the wrong way?? SR00099083 and SR00099091 are requests where it routed the wrong way and sent the wrong email. (I know that Custom A is working fine for Volunteering Leave as its pulled into the Summary and email subject as it should, its just the no match decision that isn't routing it correctly) Can someone please help me investigate and resolve this? Thanks Sam

Thanks @Ehsan, hope to get a fix soon

I'd really appreciate it @Victor as I really do need to get this process finished. Thanks Sam

Hi @Ehsan I wrapped the variable inside [date: ] but its not quite worked. I have [date:&[global["flowcode"]["customField22"]]] but its outputting as [date:2019-02-26 00:00:00] Can you advise how to amend? Thanks Sam

Hi @James Ainsworth It is happening to me in Chrome and also IE. No-one else has reported it to me but as the wording that I entered has disappeared from the node itself in the ProCap I am assuming it will be everyone who cant see it. I'm going to have to enter the wording back in as this is a live process and it needs to be there. If it happens again I will let you know. Sam

Hi I have pulled in custom fields into one of my views and then want to export into excel. Seemed simple enough but 2 of the custom fields are date/time fields and although they display in the request list for the view, they don't pull through into the excel spreadsheet, see attached. Any ideas why? Sam