Currently in workflow when we get a booking. I have it set to look at the first digits with represents the year of the the booking. For example, if the booking starts with 20 it goes into the folder year 2020, if the booking start with 19 it goes into the year 2019 etc....However, we are getting older bookings that need to be scan. The second screen shot shows booking staring with 96 which should be 1996 and not 2096. How do I fix my destination folder so it recognizes if its a 1900 folders or a 2000 folders. Any suggestions?
Question
Question
Replies
Hi Teresa,
You can add a routing decision activity where the condition in branch 1 is booking number starts with "2" and another branch doesn't start with "2" and apply the formatting to retrieve the year correctly for routing.
Thanks.
That's probably not going to work as it would turn 05 and 13 into 1905 and 1913, respectively.
But the approach is correct. You'd want to decide what date range falls into the 1900s and what date range should be in the 2000s. Maybe something like anything from 50 to 99 is meant to be 1950 to 1999. Then run your "booking year" token through a condition and decide whether to append 19 or 20 to it. You'd have to make sure the token is tagged as integer and not string so the evaluation works correctly.
Mahesh is almost there, I think. Use a routing decision where if the first number is 0-5, preface it with 20, but if it's 6-9, preface with 19. That way you're covered until 2059 and it will catch everything back to 1960.
So for branch 1, you would say "If field value "BookingNo" matches regular expression ^[0-5]\d+", then preface with a 20.