For overnight processes RCP may generate errors. There are 2 types of possible alerts:

  1. Alerts linked to data and processes: These are refreshed every night. Two types of alerts exist:
    1. Alert which can be deleted by the user
    1. Alert which must be resolved to disappear
  • System Alerts: These alerts are generated every time a process returns an error.

The Alert Screen shows all alerts for the entity the user is currently logged onto.


The approval manager lists all approval requests. Approval is required for the creation/modification/deletion of data which has an influence on the calculation result or which can lead to significant business risk.

During the creation/modification/deletion of data, the user can already see if the data requires 4 eyes approval:

In the above example the agreement status was modified from ‘In negotiation’ to ‘Signed`. This modification will take place only after approval from another user.

The list of approval requests can be viewed in the approval manager. Here all requests in whatever status are stored.

Filters are available to ease the search of approval requests:

For each request it is possible to define the priority and enter a comment. The default priority is normal.

Search an approval request:

  • From the controls menu select ‘ Approvals’
  • Use  filters :

The below filters are available:

UserName of the requesting user
Approval UserThe user who approved the request
Entity definitionEntity area for which the request applies. Exemple : Agreement, product group etc.
Approval StatusStatus of the modification : PendingApprovedCancelledRejected
PriorityPriority of the request NormalUrgent
EntityThe entity for which the change was made
SubEntity  InstanceTable in which the request would take effect The exact name of the table is required.
  • Press Search button

The search result will return the following information:

PriorityPriority of the request NormalUrgent (shown in result list with exclamation point)
Entity DefinitionEntity area in which the modification took place. Example : Agreement, agent, portfolio, product, etc…
Entity InstanceReference of the object. Example : Code and name of agreement for which the modification took place.
SubEntity DefinitionSubEntity area in which the modification took place.
SubEntity  InstanceSub entity instance for which the modification took place.
EntityThe entity for which the change was made.
RoleThe role of the person requesting the modification
Approval StatusStatus of the modification : PendingApprovedCancelled
UserName of the requesting user
Approved byThe user approving the modification
Create Time stampDate and Time when request was created
Update Time stampDate and Time when request was handled
Approval Time StampDate and Time when the request was approved.

The user can define additional filters in the search criteria or sort the rows in the result list with the arrows

Validation 4 eyes – banner

In the RCP banner it is possible to view the number of requests awaiting approvals.

The requests which the user approves himself are ‘to be validated’.

The ones that the user has initiated and which are awaiting validation from another user are labelled ‘changes awaiting validation’.

If the user clicks on the counter the approval manager opens up to show the requests.

Session Monitor

The session monitor provides an overview on imports, export and synchronisations. It shows if these processes were run successfully or not. Most of the issues will lead to an alert (see chapter Alerts).

A successful process will show 0 Errors.

A process which has either failed or raised errors will show the number of errors raised.

In the session details, the user can see which process is concerned as well as the number of errors. To access more details the user needs to click on the number of error(s).

From the next screen it is again possible to extend the details of the error(s):

These details are quite often technical. AMS can clarify the information contents for you.


Upon RCP Installation, the dashboard area is empty.

By clicking on ‘Manage Portlets’ the list of available portlets appears.

By clicking on ‘Add this portlet’ the portlet is added to the portlet view of the user. To add other portlets the user needs click on ‘Manage portlets’ again. Inside the portlets the user can click on the gears to manage the details of the portlet or delete the portlet from the dashboard.

The + and – can extend or collapse the portlet.

Drop down lists allow the user to select from multiple values. The underlying data within the dashboard is accessible by clicking on the detail the user wishes to extend. To go back to the initial page the user needs to click on ‘Back’.

In case the portlet contains a pie chart, the user must click on the part of the pie he wants to extend. It is possible to further extend the following screen by doing the same operation again.

In the portlet ‘Payments Breakdown’ the user can retrieve the list of related agreements with this approach: In the list of pending payments the first level of details shows the payment status, the second the reason for pending (= attribute) and the third level provides the list of agreements by status and pending reason (=attribute).

Audit trail

An audit trail is created during creation, modification and deletion of data.

Information available in the audit trail:

  • Date of processing ( the date when the modification/action took place)
  • Time of processing (the time when the modification/action took place)
  • User name (the name of the user performing the modification/action)
  • Type intervention (Can be Insert/Update/Approve/Reject/Sent/Cancel)
  • Detail of modification/creation/deletion/cancellation

The audit trail becomes accessible by clicking on the clock icon. The icon is available in each area where a creation/modification/deletion is possible.

Another way to access audit trails is via the menu Controls/Audit Trails. In this screen the users can access the complete audit trails. Filters can be used to search for specific data:

Audit trails are available

  • On top of a list to cover the content of the list with addition, edit and delete within the list (example Agreements list below)
  • For each item on the list separately (will cover modifications within the agreement)

By clicking on ‘view report’ the search is launched and the report will be displayed. The report can be exported in various formats.

There is also a report ‘Audit Trails’ available under Controls – Audit trails.

It is possible to filter the report based on the following criteria:

  • Start date
  • End date
  • Object type (by default all types are selected but selection can be modified)
  • Operation type (by default all types are selected but selection can be modified)

Via the ‘search’ button the user can launch the search and the results with come up in the result area.

Most recent trails are shown on top of the report. Date is sorted by log date from most current date to start date of report.

The report can be printed and or/exported in various formats.