I do not have any particular pre-formed custom commands but if you make a custom buttom to run "cmd.exe" on Windows, you will open a command prompt which shows you the environment variables the client uses. You can use these variables in custom buttons in Integrity.
IM/Workflows and Documents variables:
SI/Configuration Management Variables:
I would say the "uglyness" is encouraged by the ugly windows batch language as well as by the way the contextual information
is presented to the user tool/script 
Just alone for an explore here user script I stumbled over a bunch of implicit use cases.
Here my ugly version (tested on Build 10.4.0.4301 API Version 4.12.4301):
Feedback and improvement suggestions welcomed
Jürgen
| SI_user_action_explore_here.bat |
|---|
echo off SETLOCAL ENABLEDELAYEDEXPANSION prompt $P$G echo @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ REM DEBUG: print out all relevant environment variables set MKSSI_ echo @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @echo WORKING_DIR:%cd% color cf if NOT "%MKSSI_WINDOW%" == "sandbox" ( echo ERROR: Window must be a sandbox pause exit ) if NOT "%MKSSI_SUBPROJECT2%X" == "X" ( echo ERROR: Multiple selection not supported pause exit ) if NOT "%MKSSI_MEMBER2%X" == "X" ( REM this can also happen if a subfolder (not subproject) is selected in the GUI REM then all members (recursive) within the subfolder are presented as selected echo ERROR: Multiple selection not supported pause exit ) color 9F REM set the default directory change targets to current directory set CD1=. set CD2=. REM the main trick to land on the desired directory without parsing REM is to pretend the project file or membername being directories REM eg cd /D "D:\sandboxes\project1\project.pj\.." will land in directory D:\sandboxes\project1 if NOT "%MKSSI_SUBPROJECT1%X" == "X" ( echo SUBPROJECT selected set CD1=%MKSSI_SUBPROJECT1%\.. ) else if NOT "%MKSSI_NMEMBER%" == "0" ( echo MEMBER selected set CD1=%MKSSI_MEMBER1_SANDBOX%\.. set CD2=%MKSSI_MEMBER1%\.. ) else ( echo PROJECT selected set CD1=%MKSSI_FILE%\.. ) echo CD1: %CD1% echo CD2: %CD2% cd /D "%CD1%" if NOT "%CD2%" == "." ( dir "%MKSSI_MEMBER1%" echo err: !errorlevel! if !errorlevel! == 0 ( REM the working file exists REM the following should also work if membername has format folderX\membername explorer /select, "%MKSSI_MEMBER1%" ) else ( REM working file missing REM the following cd may fail if for membername format folderX\membername REM also directory folderX is missing in the sandbox REM then we will land/stay in the directory %MKSSI_MEMBER1_SANDBOX% cd /D "%CD2%" REM you may want to check !errorlevel! to have folderX missing an illegal use case explorer /e, . )
) else ( cd /D "%CD2%" explorer /e, . ) REM pause REM cmd endlocal |
The problem with the environment variables (which, by the way, we use in our scripts, too) is that they have changed in the last Integrity versions AND that they differ from view to view. Sometimes, they are not available, sometimes they have a different content
.
