Jitterbit Cloud Studio Project Reporter¶
The Jitterbit Cloud Studio Project Reporter assists in the creation of Jitterbit Cloud Studio projects by providing a report that describes an exported Cloud Studio project as a single web page. The Project Reporter can be used to both review and modify a project so that a consistent naming scheme can be used for project variables and other project components.
The tool available from this page is supplied without warranty or support, and is used under license from Jitterbit, Inc. See the tool installer for the license for the tool.
The Project Reporter is available for the Windows operating systems. Download the installer package from:
The macOS version of the tool is currently unavailable. A fix is being developed and a new version with support for the macOS will be released.
The application is packaged using an installer appropriate for the operating system. Open the installer and follow its prompts to install the application.
Intent of the Tool¶
The intent of the tool are these functions:
- Cloud Studio project reporting, including overall project, schema, and project variable reports
- Project component standardization, particularly the naming and defining of project variables
- Project JSON file editing, expansion (pretty-printing), and compression
The first part of the report lists any warnings or suggestions. A report’s warnings do not affect the project’s capability with respect to its validity as a Cloud Studio project. They reflect the project’s compliance with our standards for the naming of components such as project variables. If an endpoint has an encrypted value in a “password” type field, a warning will be issued. Warnings and suggestions should be reviewed and implemented as appropriate for a particular project.
The schema report is a separate report that is saved as a Markdown file. It lists all the different schemas used in a project and the fields used in the mappings.
The project variable report is a separate report that is saved as a Markdown file. It lists all project variables used in a project and their definitions. A more comprehensive report is included in the HTML project report.
Operating the Tool¶
Start the tool as you would any other application. The tool runs in a single window. Help in the tool links to this documentation. Menus are not used in the application except for an “About” dialog, help link, and exiting the tool. Everything is done by clicking the buttons as shown in the introductory illustration.
When you first start the tool, no project is opened by default, and there are no items listed in the program’s Favorite Projects drop-down menu:
The typical workflow is to specify a project and then create a report for the project.
Once a project has been specified and a report created, additional actions (such as cleaning or editing a project, saving reports) are available.
The tool consists of two panels with relevant buttons underneath:
The top panel (Specify Project) is where you specify the current project. Though only one project can be specified at a time, you can add a project to the Favorite Projects drop-down menu and save its path for reuse.
The bottom panel (Project Report) is from where you create the project report and manipulate a project.
You specify the current project either by browsing for the project JSON file or by selecting from a saved favorite.
Current Project: The current project’s filename is shown in bold text, with the complete path of the project file listed underneath.
Use the Browse for File button to select a Cloud Studio project file (a JSON file exported from Cloud Studio).
Once a file has been specified, you can add it to the Favorite Projects menu.
Use the Remove as Favorite or Clear Favorites buttons to edit the menu.
Create Project Report: Creates an HTML-formatted report on the current project and opens it in the default web browser.
Clean Source Project: Rewrites the current project to remove email addresses and deployment records and pretty-prints the JSON.
Copy Report Corrections Over Source Project: Copies the report corrections (suggestions) over the source project.
Save Project Report: Saves the project report as an HTML-formatted file.
Save Schema Report: Saves the project schema file as a Markdown file.
Save Project Variable Report: Saves the project variable report as a Markdown file.
Edit Source Project: Opens the current project in the system default JSON file editor.
Pretty-print Source Project: Rewrites the current project to be expanded (pretty-printed) JSON.
Compress Source Project: Rewrites the current project to remove whitespace from the JSON.
- When the application starts, it checks online to see if a newer version of the application is available for download. If so, it asks if you’d like to go to the download page. This same test can be initiated from a menu item in the application.
- Updates have been made to the recommended project variable naming conventions.
- The version of Python embedded in the application has been updated to version 3.9.0.
- Fixed errors with a project that does not have a description or components such as scripts or project variables. The report now correctly lists these items as not being present.
- Fixed an error when a file saved as a favorite is no longer available.
- Added handling of other errors that caused the program to become unresponsive.
- Fixed an issue with creating a mapping rule from an incomplete rule.
- Fixed an issue with reviewing projects that had a password in an endpoint configuration.
- Connectors and activities are displayed grouped by endpoint and connector, alphabetically.
- Bug fixes related to warnings that prevented reports from being created for certain projects.
- A warning is issued if an endpoint has an encrypted value in a “password” type field.
- The endpoints are now described in detail about their field names and values.
- Components are displayed by order of importance.
- New application icon using a bright color makes it easier to identify the application when it’s in use.
- Added spellchecking for many usages of known endpoints in names. If a known endpoint is found to be misspelled, a warning is issued at the start of the report. Correcting these errors is not automatic and must be performed manually.
- Initial release of the application.
For More Information¶
Though this tool is unsupported, we are happy to receive any feedback, questions, or concerns. You can reach the Jitterbit Documentation Team at firstname.lastname@example.org.