For masking jobs we are using some powershell scripts which contains API call to TDM portal. One of the step is to import masking options usin API which is working fine. Although, for the LOGDIR option the API won't get the filepath specified as E:\DATA\TDM\PROJET\<project_name>\AUDIT_LOG
When we run the powershell script and let the masking job complete. We do not see the execution log in that specific folder. I think it gets ignored and then uses the default FDM execution log path instead.
But if we do the masking directly from the TDM Portal GUI and we specify the LOGDIR option , then it works fine.
Why can't the API call accept the filepath specified in LOGDIR option?
If you guys need a webex to see the issue, just let us know.
API call is like this:
$url = "https://"+$global:adressePortailSelection+"/TDMModelService/api/ca/v1/datamodel/maskSettings/" + $optionId + "?projectId=" + $projectId + "&versionId=" + $versionID
Release : 4.9.1
Component : TDM Web Portal
If it fails for them when updating the LOGDIR option then I'm afraid that they don't send doubled \\ character which causes an invalid JSON format - in this case we can't do anything on the server side and they need to modify their client (Powershell script) to replace \\ characters in the log path with \\\\ (so it gets escaped). So for example C:\\\\AUDIT_LOG (or C:\\\\AUDIT_LOG\\\\) needs to be used.