In the context of our fundraising automation products, RaiseNow interacts with target systems in order to translate data from various sources according to the requirements of the target system. The integration layer is called RICE (RaiseNow Intermediary for Customer Engagement).
We refer to the original data as a notification. The translation and data transfer of a notification to the target system is referred to as a business process.
Though we handle most errors automatically, especially when wrong data is submitted to RaiseNow manual intervention is sometimes required.
The business process monitor provides customers with an overview of all processes, their status and their edit history.
You can login to the Business Process Monitor here: https://merchantadmin-app.rnw.io/ with your RaiseNow Hub credentials. If you do not have a login yet, please contact support@raisenow.com
Process List
The business process view can be filtered by search-term, time, data category, status, and process type. Additionally the metrics for the data categories can be viewed.
Search
Identifiers
It is possible to search for identifiers. Best results can be achieved by using quotation marks (""). Example identifiers to search for:
- payment/transaction identifier:
"c1e2c16880q2698" or "bc240568-fe50-4f2e-a6c5-faf579f9528b"
- Business Process identifier:
"1188b8e6-97e4-446d-ba92-0ff1db636a08"
Errors
You can also search for Error Messages, for example to get all BPs with the same error.
Example error message:
Message: Path "stored_campaign_id" is not reachable
Example search:
"stored_campaign_id"
You can also filter BPs with that error, for example to get all BPs with a different error:
!"stored_campaign_id"
Status Categories
| Name | Description | intermediate status | action |
| Execution Succeeded | Final status for successful BP | no | Can't be edited or re-executed |
| Failed Permanently | Final status for failed BP | no | Try to fix it by re-execution or by editing the BP notification data |
| Failed Transiently |
Failed BP with automatic-retry | yes | wait |
| Failure Ignored | Explicitly ignored failed BP | no | Can be edited and re-executed if needed |
| Manipulation Failed | BP Specification differs from a previous version, thus the manipulation (edit, re-execution) failed | no | Let RaiseNow Support know, if transfer to target system is needed |
| Non Executable | BP in testmode in production or other way around | no | nothing |
| Execution Pending | BP is just in processing | yes | wait |
| Update Requested | BP update was requested (after editing notification data) | yes | wait |
| Resumption Requested | BP re-execution was requested (without editing notification data) | yes | wait |
Data Categories
Usually you will get two RICE Instances for your integration with the target system. The "Production" data category will be preselected by entering the Business Process Monitor.
The data category only decides which notification should be processed and which not.
By setting up the instances you decided to which target system data should be transferred:
- Production
- UAT
- Sandbox
- Dev
- Test
| Name | Description |
| Non Production | Shows all BPs processed in your Non Production instance. BPs in this instance only accept notifications which state a test mode otherwise BPs will end in status Non Executable. We explicitly avoid (and don't recommend) sending test mode data to your production target system. |
| Production | Shows all BPs processed in your Production instance. BPs in this instance only accept notifications which state a production mode otherwise BPs will end in status Non Executable. It is possible to send production data to your test target system. |
Process Types
Process Types vary between different target systems RaiseNow is supporting. A process type defines how to process a specific case to your target system. Nevertheless you can filter by process types.
Process details
The process details show the original notification on the left-hand side. The right-hand side shows the steps that were executed by RICE. If the process caused an error the last step executed will show the error message that was triggered. On the upper right corner, you can edit the original notification, ignore the failure or view the history of that process.
Edit Notification (before re-execution)
The original notification can have various forms depending on the source. Standard notification from the E-Payment platform (EPP) will be query strings. When editing these, please be sure to retain the required format where parameters are always divided by '&'. For example:
parameter1=value1¶meter2=value2
Re-Execution
In edit-view use the button below the notification to update the notification and request re-execution from the last failed step in the business process: Update and Request Execution.
Re-Execution happens automatically, usually within a couple of seconds. If you reload the business process you will either see a status indicator Update requested or Resumption Requested.
Reload the business process until you see a non-intermediate status again:
- Failed Permanently
- Manipulation Failed
- Non Executable
Ignore Business Process failure
In details-view of a failed permanently process you can also choose to ignore the failure. For example you decided to import the case manually to the target system, then we recommend to set the BP to failure-ignored and give it a reason why. This way nobody will simply retry the process, which prevents creating a duplicate in your target system.
Simply provide a reason why this BP should be ignored. Click OK to save it or Cancel to get back to the details-view.
Screencast
Comments
0 comments
Article is closed for comments.