FAQ

The Application ID must begin with a letter and can contain only letters, numbers, and underscores. However, the first character of an application ID can only be alphabetic (NOT a numeric or underscore). There is no limitation on the number of characters that the Application ID can contain (no length restrictions). Alphabetic characters can be upper or lower case. Some suggestions regarding how Application IDs should be created might be: – add a identifying prefix for each customer if a single customer has many Applications – add a suffix with the creation date – keep the ID as brief as possible, but still efficient and easy to identify/intelligible.

We unify all the information from all the sources into Unicode using UTF-8, and we pass it from ICE and all of our Bridges as UTF-8 and XML-encoded entities. However, we are not limited to extracting data just from UTF-8 bytes, and we should not extract bytes as UTF-8 when it is not appropriate. All our extraction in Muse is to UTF-8 but from a wide range of encodings (including UTF-8).

We accommodate this large number of encodings, detailed in the documentation, when we extract data; only then is it converted into Unicode (with UTF-8 encoding) on our side.

We unify all the information from all the sources into Unicode using UTF-8, and we pass it from ICE and all of our Bridges as UTF-8 and XML-encoded entities. However, we are not limited to extracting data just from UTF-8 bytes, and we should not extract bytes as UTF-8 when it is not appropriate. All our extraction in Muse is to UTF-8 but from a wide range of encodings (including UTF-8).

We accommodate this large number of encodings, detailed in the documentation, when we extract data; only then is it converted into Unicode (with UTF-8 encoding) on our side.