Versions Compared

Old Version 3

changes.mady.by.user Thomas Timbul

Saved on

compared with

New Version 4

changes.mady.by.user Thomas Timbul

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

By parsing the exit code and these lines you will be able to take further action in your automation script, depending on the outcome of the run/job.

Basic Windows Example

Code Block
breakoutModewide
languagebash
rem Example Windows batch file

rem run the command:
"C:\Program Files\Price Checker 2\pc2cmd.exe" -silent -auto "C:\MyFile.xlsx"

rem When complete the exit code will be accssible in the %errorlevel% variable
if %errorlevel%==200 (
   echo "Success"
) else if %errorlevel%==204 (
   echo "Suceeded, but no output file was created."
) else if errorlevel 400 (
   echo "There was a problem with your command."
) else (
   echo "Internal error - Something went wrong"
)

Basic MacOS Example

Code Block
breakoutModewide
languagebash
#!/usr/bin/sh

# This is an example shell script for MacOS

# Run the command:
"/Applications/Price Checker 2.app/Contents/Resources/app/pc2cmd" /Users/Me/Documents/MyFile.xlsx

# When complete the exit code will be acecssible via the $? variable
exitcode=$?
if [ $exitcode == 200 ]
then
  echo "Success"
elif [ $exitcode == 204 ]
then
   echo "Suceeded, but no output file was created."
elif [ $exitcode == 400 ]
then
   echo "There was a problem with your command."
else
   echo "Internal error - Something went wrong"
fi

While the actual implementation of automation software is beyond the scope of this article, feel free to contact support for assistance with Price Checker CLI integration.

...