...
We hope to resolve any significant errors in a timely manner, but for now please be aware that there are some workflows that we do not support, or there may be something you can do to resolve it yourself.
Please see below
Known issues
The following are known issues, and possible work arounds to get you going again
API Login Details
Make sure you have setup your API user correctly
See here Below are some possible causes if you have seen the error message “An error has occurred. Would you like to learn more?”
...
| Warning |
|---|
You have clicked the Share It button more than once |
When previewing a tax document, the Share It button can only be clicked once. The second time it is clicked there will be an error.
Solution: Close the preview window and print the report again.
| Warning |
|---|
API User credentials are incorrect |
When the Nimbus Profiler was installed, the Nimbus URL, API Login Code and API Password were saved in the AE/AO database. If the Login Code or Password for the API user are changed in Nimbus then the Profiler will not be able to authenticate to save documents.
Solution: Contact Support to update the credentials in the database.
More information: https://nimbusportals.atlassian.net/wiki/x/BYAtxw
Missing Clientcode
If you have tried to publish a document from AE or AO and there is no Clientcode in AE/AO, then sorry, but it wont work.
...
| Warning |
|---|
Client code is not provided |
The Nimbus Profiler needs to know what the client code is, in order for it to attach the document from AE/AO to that same client in Nimbus.
There are some workflows that are not supported as the client code is not known. See the Unsupported Workflows section below (https://nimbusportals.atlassian.net/wiki/spaces/CH/pages/edit-v2/3339321359#Unsupported-Workflows)
Solution: The document will need to be saved manually to Nimbus
| Warning |
|---|
Client code does not exist in Nimbus |
If the AE/AO Client code does not exist in Nimbus then the document cannot be saved.
Solution: Please make sure
...
the Client code exists in both AE/AO and
...
Nimbus. If you have just added the client in AE/AO
...
then try again soon as there is sometimes a short delay before AutoMate synchronises the client from AE/AO to Nimbus
...
Missing Client
If the Client or Contact only exists in AE/AO, but not in Nimbus, then it wont work.
Please make sure the Client exists in both AE/AO and Nimbus .
| Warning |
|---|
No internet connection |
Coming soon….
Supported Workflows
For this release, only some workflows are supported.
The following workflows are supported for the Beta Release as at the end of 2024:
Workflow | Details | |
|---|---|---|
| 1 | Publishing a Tax Return | You are in a AE/AO Tax Return, and click on “Share it” |
| 2 | Publishing from Statutory Reporter | You are in an AE/AO Statutory Report, and click on “Share it” |
| 3 | Publishing a Workpaper | You are in an AE/AO Workpaper, and then click on “Share it” |
| 4 | Publishing from PDF Manager This currently only works for Tax Returns | You are in AE/AO and have published a Tax Return to PDF Manager, and then click on “Share it” |
Unsupported Workflows
The following workflows are not currently supported for the Beta Release as at the end of 2024:
Workflow | Details | |
|---|---|---|
| 1 | Other workflows from within AE/AO | E.g. you are in PDF Manager and click on “Share it” |
| 2 | Other workflows - outside of AE/AO | E.g. you are in Excel / Word / Outlook / File Explorer, and use the existing add-in to “Share it” |
| 3 | Nimbus Profiler Files saved locally | You are in Windows Explorer and right click on a file |
Other Known Issues
We are not aware of any just yet, but we will keep you posted here if we find any.
...