Introduction
On behalf of the team at Emersion, we would like to take this opportunity to welcome you if this is your first time here.
Our knowledge base contains tutorials, how-to articles and troubleshooting help for all users of the Emersion platform. Access to this knowledge base requires users authenticate with Cumulus user credentials for access.
Although every effort is made by Emersion to keep the content as up-to-date as possible, the size of the platform, its complexity and its rate of constant evolution means that this is not always feasible. Some information may be slightly out of date. Information pertaining to recently released modules and features may be pending publication. All articles are indexed through key words and labels (also known as tags).
If you cannot find information on a topic, module or function, please contact us via the Emersion Service Desk and we will do our best to help.
Site Conventions
To make reading and absorbing information from this knowledge base as easy as possible, we have adopted the following conventions and standards.
Document Conventions
The following conventions are used throughout this manual to describe information and procedures:
Italics | Indicates the page titles and headings, page section names, and object status (i.e. a pending invoice, or a cancelled subscription). The capitalisation and punctuation are the same as displayed on the screen. For example: Complete the Address field. |
Bold text | Bold text indicates the name of a navigation path, link, button, interactive elements and objects in the system (i.e. a report name or customer name). For example: Type the user’s name in the Customer Name field, and then click Search. |
BOLD CAPITALS | Text in bold capitals indicates the name of a key on a keyboard. For example: Type your password, and then press ENTER. |
Navigation > | Menu options or navigation paths are prefixed with 'Nav:' followed by the clickable pathway. The pathway itself in bold. This is shorthand using the following convention: Module > Functional Area > Option For example, selecting the Account Profile area can be described as: Admin > Settings > Account Profiles from the Menu. |
| Reference IDs | When referencing an actual object in the system by its proper name, bold it as per the rules above, and include the ID of the object in brackets. This is because users can use these IDs to search. i.e. Run the Smash and Grab Report (id: 001) or Open the message template for the Bulk Upload Processing Notification Event (event type id: 963) |
Monospace text in a code block | Preformatted text is used for presenting content that requires syntax highlighting. For example: -- Working API Call:
-- WSDL: Accounts
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:emersion:api" xmlns:urn1="urn:emersion:types"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/>
<soapenv:Body>
<urn:CreateAccount>
|
a warning | A warning should never be ignored. |
a note | A note is something we think is really important to consider, or to pay attention to. |
A tip a tip | A tip highlights content we consider as a life hack when it comes to Emersion. |
Examples
Example 1
Go to the Customer > Details > Trading Terms page.
click on the Edit button to put the page into Edit mode.
Scroll down until you see the Super Settings section and change the value in the Days field to the preferred value.
Press the Save button.
Example 2
Go to Reports > List and click on the Accounts tab.
Running the Smash and Grab report (id: 001) will show you a whole heap of things you wanted.
Legal Disclaimer
No part of this knowledge base, inclusive of all content, images, sound files, videos may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, recording or otherwise without express written permission of Emersion Software Systems Pty Ltd.
All content is for informational use only.
Articles found to be out of date are in no way considered a breach of the Service Level Agreement ('SLA').
This knowledge base is subject to change without notice.
Emersion Systems Pty Ltd assumes no responsibility or liability for any errors or inaccuracies that may appear in this knowledge base.