A bit of back story here, may help to outline why I need what I need.
Part of our ERP system requires a "costing operation" to be completed on a regular basis, this is for general ledger transactions, journal postings etc etc. This costing process needs to be run a lot... and it takes roughly 5 hours to complete.
Not that someone is hammering keys for 5 hours every day, more like open window, press save, wait an hour, and then keep going on.
Problem is that you can't "side load" this, as while the process is going about its work the computer on which it is running is pretty much useless.
This is where this lovely product comes into play, thank you MacroScheduler!
Now, onto what I'm trying to get done here:
As part of this costing process, I need to have the macro logged, so that if it fails somewhere through the process, the log can be reviewed to see exactly where it stopped functioning. Multiple people can access this log.
The macro connects to the ERP system database to run checks to see if it should run certain SRTs, and run a procedure that may actually run deletes if it's required. The other catch to this is that I have to connect and run these processes as a system admin.
In the macro I must specify this admin user name and password and of course it's in plain text, because of logging this admin user is exposed.
I'm trying to find a way to hide or mask this connection string from the logs and I cannot find anyway to achieve this.
I tried putting the database connection in a separate macro, and then call it through the use of Macro> and using the system variable MACRO_RESULT, but you cannot return the database connection through the variable, all that is returned via MACRO_RESULT is a numeric value of 1.
If anyone has any thoughts on either:
- masking the username and password in the script log
- externally calling the database connection and returning the connection
- disable/enable logging output as the script progresses
If anyone has any other ideas I'd really appreciate it.