Find commands, policies, ddas by searching by filename or text.
Open Oracular Editor (not tied to any server).
Reloads the lists used in the completion dialogs and other places.
Every command executed is saved in a file of the format host__port.mds in the History folder. This option will delete the file.
Reloads the lists used to generate the popup suggestions.
Shows all the local RP instances on your machine and allows you to open LES, a command prompt with env.bat, mtfdevice, or KevTerm.
This takes a schbat, devcod, password, useLocalForms, and your windows user/pass to start Kevterm and pick everything on the wave.
A tool to write scripts to automate common tasks (open RF to a specific screen, open GUI to a specific screen, etc)
New in 2010.4: Write Groovy code within square brackets ([[String str = "abc"]]).
To run a command, call edit.run(Command.<command>, params) (e.g. edit.run(Command.script, "putty")).
A tool to easily create DDAs by generating the CSVs needed from the given information.
This tool allows comparison of a table between two servers. Options are available to ignore date/times, ignore certain columns, and generate the insert statements needed to move data from one environment to the other.
Enter a part number in the first box and hit enter to see all the alternate part numbers.
Takes in a form name and the location of the .dat file (vehicle or handheld) and outputs the form in RDT format. This has not been put to practical use yet, so the output may not be 100% accurate.
Open a .OUT file containing ZPL and this will attempt to render an approximation of the label.
Drag files from Windows Explorer to add to the rollout. Enter a name, press Generate and a new rollout will be created in the Oracular MOCA Client\Rollouts folder.
Enter the table name and the number of primary key columns, choose a CSV file, and a dialog will pop up with the text needed.
Parse logs produced by Integrator
Parse .slexp files (Integrator exports)
Manage Oracular's issues and rollouts