...
Page content:
...
Select Component (exit back to card)
...
Start/Stop - (link out to Dev)
...
...
Pull Changes from an upstream repo
Revert changes, see change history
...
Script Execution
...
Accessing Help in the Translator - rename to Help Index (link out to Admin)
Keep both ways to access
...
The Translator’s Toolbar, located at the top of the screen, provides access to key functions such as developing against multiple samples, running tests, and managing projects.
...
Expand | ||
---|---|---|
| ||
From the Translator, you can control the status of the component to test what you are working on. Depending on the current status of the component you can START, STOP, or KILL a component in a pending state. The status light will indicate the current state of the component:
|
Expand | ||
---|---|---|
| ||
The Translator is a data driven environment, meaning you can use real Sample Data to develop and test your integration logic. Use the toolbar to:
|
Expand | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
The Translator’s Source Control tools help you manage your projects, saving changes locally and in connected remote git repositories for the rest of the team to access. In order, to leverage the source control features, you must configure your IguanaX Git settings and ensure your project is connected to a repository.
|
Expand | ||
---|---|---|
| ||
When working in the Translator, one of the many great benefits is the auto-execution of the script, enabling you to develop and test your code at the same time. However, sometimes you may want to control when your script executes, for example when working with large data sets, testing one-time executions or debugging an error.
|
Expand | ||
---|---|---|
| ||
The Help Index can be accessed in the Translator to search and view Iguana’s Translator API documentation. This documentation provides information on how the API works, how to use it along with an example. |
Expand | ||
---|---|---|
| ||
The Translator employs syntax highlighting to colour code functions, keywords, and variables to improve code readability and help developers quickly navigate scripts. The Language dropdown controls how the Translator does code syntax highlighting. The Language is set to Lua by default, but can be changed if you are working in the Translator with different types of data. For example, if you open a sample HL7 message, the Translator will auto detect the HL7 and change the language bar to the appropriate HL7 setting so the data is highlighted correctly. You can manually select the language if needed. |