iridize groups guides together into applications. An application is simply a logical grouping of guides; On any given application only guides from the same application can be shown. In the iridize dashboard you can administrate and configure each application independently.
If you need to setup iridize on multiple applications in your organization or on multiple versions of the same application it is recommended that you use separate iridize applications.
To see what is your appId simply visit the account setup page
iridize supports deploying in both your staging and production environments. In your production environment iridize will only serve published revisions of your guides. In staging, on the other hand, iridize will also display draft revisions of your guides.
Using this paradigm will allow you to create walk-through guides in your staging environment before a new feature is released to production without having to worry about affecting your production environment. You will then be able to publish these new guides only after they were tested and the feature was rolled out to production.
To enable iridize in your staging environment use the following code
iridize.env = “dev”;
If iridize.env is defined to any value other than “dev” or not defined at all, iridize will assume that this is a production environment.
On Premise Runtime Installation (Hybrid Setup)
Iridize fully supports on-premise runtime installations. To install iridize in an environment without access to the internet you will need to do 2 things.
1) export your guides from your iridize account. This will provide you with a ZIP archive with all the necessary files in the proper directory structure. Unzip the contents of this archive into a web server of your choice.
NOTE: your web server must be configured to serve files with the name index.json when a request is made to a directory. For example, in apache this can be achieved by adding the following line to your conf file.
The default iridize behavior is to send guide usage and error reports to the iridize cloud servers at https://iridize.com. This behavior may be overridden by adding the iridize.reportPrefix property override to the iridize embed code. For example, if the following line is added to the embed code, the reports will be sent to the base url https://foo.com/bar/
iridize.reportPrefix = 'https://foo.com/bar';
When this property is used it is common to setup a webserver that simply logs all requests to the base url or its nested paths into log files which can later be used for counting guide activations, step activation and checking for guide error reports.
Some times it is desired to disable usage and error reporting altogether, for example when deploying iridize runtime on-premise installations to environments without internet connectivity. In such cases it is possible to do so by setting the iridize.enableReport property to boolean false in the iridize emebed code.
iridize.enableReport = false;
Normally iridize uses the browser's local storage to store information about which walk-through guides are active. Users may wish to open several views of your application in multiple browser tabs. Potentially a different guide/s may be open in each tab. For this reason iridize scopes the local storage per browser tab.
However, some web applications use multiple tabs as part of the navigation scheme. In order to permit a walk-through guide to be continued in another browser tab you should use the useSessionStorage setting. This tells iridize to store state information in the browser's session storage. As a result this copies the user's state from one tab to the next.
Set the preferred language for the Iridize guides. This should be set dynamically based on the currently logged in user.
The value of this setting should be the language code of the relevant language as provided by this standard.
for example, to set the language to French,
Use this setting to disable the help widget on certain pages. This is sometimes required if your application uses popups or iframes.
iridize.showStartPanel = false;
Use this setting to enable Iridize integration with Salesforce Classic. This setting allows Iridize to extract the user_id directly from Salesforce.
Use this setting to enable Iridize integration with Salesforce Lightning. This setting allows Iridize to extract the user_id directly from Salesforce.
Use this setting to to have Iridize create a random user identifier for the current logged in user. This allows you to use the user conditions without having to do any integration whatsoever. The down side is that if the end user changes browser or computer the information they will be assigned a new user_id.
The iridize JS API
The API can also be used to attain granular control over the activation of iridize guides within your web application. Using the API you can start or stop guides based on your custom business logic, as well as monitor the progress of a specific customer through your guides, by binding to guide-level or step-level events.
To read more about our API visit this knowledge-base article
iridize on-page guidance solution is compatible with any application that can be used with a standard web browser.
Iridize technology can offer instructions on any element in the DOM tree.
Iridize can be used to provide instructions on embedded objects such as java applets, Flash and Silverlight. However, iridize cannot inspect elements within these embedded objects.