HomeGuidesRecipesAPI
HomeGuidesAPILog In

Warnings

Peruse and learn

πŸ“˜

This is a list of important warnings pertaining to product use

General Warnings are only listed here, while other more specific warnings also get listed where relevant throughout the documentation

General

🚧

Save your projects regularly. Projects in design do not Autosave.

🚧

Bots that emulate user input is not a recommended use case

While we will attempt to support most customer projects, the use of bots or macros to emulate users is not recommended or expected to behave as intended with SmartIQ. This is due to having the potential to cause race conditions

🚧

SmartIQ restricts the following special characters from being used in file names and paths: semicolons, commas, carriage return ('\r'), and newlines('\n')

🚧

Custom fonts must be in the Content Library if unsupported Docx, Pptx, and Xlsx template fonts are to be used when converting templates to Pdf files. Unless the fonts are directly embedded into the content document.

🚧

If your data has text formatting in HTML then make sure to pass it to a rich text question otherwise its formatting will not be converted.

🚧

Response Metadata doesn't perform well with lots of Response Metadata fields or lots of tasks

🚧

Only fonts installed on the SmartIQ server, or added into the Content Library, can be drawn upon at generation time, unless the fonts are specifically embedded into the content document.

🚧

Only, Word, Excel and PowerPoint templates can be edited within SmartIQ

🚧

PDF templates can't be edited by SmartIQ

🚧

Produce will send the DocuSign envelope any time the template is generated. This means that you will not be able to download a document with this template type.

🚧

File names restricted characters: semicolons ;, commas ,, carriage return \r, and newlines \n

Any file that is uploaded with a filename containing any of these characters will have the character automatically replaced with an underscore _ within SmartIQ and will appear with an underscore when downloaded

Security Settings

🚧

Do NOT lose encryption key material

If SmartIQ is no longer able to contact the chosen key wrapping technology, SmartIQ will NOT be able to decrypt or unwrap the DEK. Therefore, your data will be lost.

Minimum Requirements

🚧

Behaviour may differ between different browsers and browser versions

While we try to keep SmartIQ functional between all systems, technical differences mean identical operation cannot be guaranteed when comparing operation between different systems.

Placeholders

🚧

Placeholders are not Variables

Placeholders do not act the same as variables and cannot transfer default or pre-fill information into the form. Placeholders only transfer data from the form to the various locations in the templates.

🚧

If placeholder data appears formatted incorrectly in your documents, it is suggested that your placeholders are used within rich text questions instead of a label or input question.

🚧

Range placeholders don't exist for PDF templates, so inserting repeaters or gap placeholders isn't possible.

🚧

PDF Button, FileSelect and Signature field types are not supported by placeholders.

Questions

🚧

The Action Button only works online

The Action Button is supported on mobile apps, however it can only be used in online mode. If the app is in offline mode, the Action Button will be disabled.

🚧

The Button Question Type cannot be used as a Condition

🚧

Questions should only refer to other questions which come earlier in the form structure.

References to later questions (a forward reference) may work, but can also behave unreliably; for this reason forward references are not recommended.

🚧

Javascript cannot be run from question text

Actions

🚧

Offline app Actions can't modify the Wizard object

Any action that modifies the Wizard object will not work on the mobile apps. As actions are run server side, SmartIQ only passes back the result and the action outputs.

Repeaters

🚧

It is HIGHLY suggested that designers use nested repeating sections with caution and do not layer the nesting too deeply.

Having multiple nested repeaters each containing even a small amount of data can very quickly explode out to levels that can drastically affect performance performance

🚧

If a project is designed to use nested or side-by-side repeating sections, with dependencies relating to the uploaded data, csv uploads can result in a non-linear increased time to load.

A CSV that loads easily with 10 rows may be very slow with 25 rows and not load at all with 100 rows. Best practice is to start designing with an initial set of test data that exceeds the projected maximum row count, so any performance issues are identified early in the project design process.

🚧

"Show minimum rows on startup" only works at STARTUP. The repeater will load its rows when it is created (usually when the wizard is launched).

This means if a question reference tag is linked to maximum or minimum, and the question is updated, rows will not be created/deleted from the repeater.

🚧

Question reference tags operate differently within a repeater context.

Within a repeater, question tags are only able to retrieve answer data from within their current repeat. To reference a previous repeats' question answer the previous tag is required.

🚧

The previous question reference tag will make a repeated question return 0 if the question is self referencing.

Data Sources

🚧

Questions with the data type set to 'Date' will return the date formatted in the long date format.

To change this default behaviour the use of a format string such as SHORT DATE, LONG DATE, dd/MM/yyyy must be used

🚧

Date formats must use upper case M for month as lower case m refers to the minute value

🚧

SmartIQ can only retrieve and hold up to 1000 rows of data from an a data source

Therefore filtering larger data sets solely in SmartIQ is not possible. You should first filter the data at the data source or use an enterprise service bus (e.g. MuleSoft) before importing to SmartIQ. This also limits the offline mobile app forms.

🚧

Document fragment not inserting into main document header or footer

The reason why the document fragment is not being inserted into the header/footer of the generated document, is because the content within the fragment is in the header/footer as well. A good way to think about it is that you cannot have a header within a header or footer within footer, but you can have a body within a header or footer.

🚧

SQL Server and PostgreSQL impose a limit of 2100 parameters per query

In certain cases, particularly when using Aggregate data filters, SmartIQ may exceed this limit. There is no workaround to increase the parameters, only the recommendation to limit the number of values that are passed to SQL Server as filters.

Workflow

🚧

Any conditions required to trigger the Submit Task action must be complete before Workflow Assignment occurs, during the creation of the Escalation

This means that any actions that need to input into those conditions must be run no later than "Run After Document Generation". "Run After Finish" will be too late.

🚧

Avoid using 'Current User' transitions when also using the Submit Task escalation

The Submit Task escalation submits the task as the configured Submit Task Manage Settings user, so a "Current User" workflow transition will result in a task assigned to the Connector Settings service user.


Related Content