Skip to main content
  • 4,045 Posts
  • 13,979 Replies
4045 Posts
Using Scripted parameter to return password or environment variable. fme string encoding help

I have a workspace which uses input user credentials to do stuff. I also want the workspace to work during testing by using System environment variables. This is working great for things like DBNAME, HOST, PORT etc where the user inputs are strings (text user parameters). I can simply just enter in ${PORT} for example and FME will look for a set environment variable. Where I'm having trouble is with the password. I can't do the same thing for the password so I've created a simple scripted parameter which first checks if there is a user password set and if not try and see if there is an environment variable. In most cases it works well, however, I've discovered that some special cahrachters are getting encoded by FME - So something like @ becomes '<at>'. Does anyone know a way to 'decode' these encoded strings. Ideally it'd be done in the scripted parameter, however, if it has to be done in the workspace so be it.Short from using

Badge Winners

  • Welcome Back
    okainunoohas earned the badge Welcome Back
  • FME Flow Certified Professional
    kruti_811has earned the badge FME Flow Certified Professional
  • FME Certified Professional
    bkjhas earned the badge FME Certified Professional
  • Expert (Bronze)
    timatsafehas earned the badge Expert (Bronze)
  • FME Form Advanced Training
    mike_greshhas earned the badge FME Form Advanced Training
Show all badges

Community Stats

32,431
Posts
123,238
Replies
40,558
Members