IMPORTANT: For Sea/chat message parsing to be functional, the Sea/chat integration steps must have been completed. If this is not case, please read Sea/chat integration set up and action accordingly.
Messages that have been sent via Sea/chat integration with Sea/futures are displayed on the right-hand side of the whiteboard.
The visibility of the Chat panel on the right-side of the whiteboard screen is controlled by clicking the "Feed" button in the toolbar area.
Click to display/hide the chat panel.
How does the parsing work?
Parsing functionality looks for valid terms against which to parse the information from Sea/chat in to Sea/futures.
In order for a Sea/chat message to be parsed it MUST contain all of the following:
Route / Index - the parsing functionality scans for this first before it can further proceed e.g. C5
Period - without a period the offer/bid rates cannot be assigned to the correct dashboard fields e.g. Jun or May-Jun or Q4
Bid and / or Offer rates e.g. rate/rate (9.50/9.75) or rate offer (e.g. 8.00 offer) or rate bid (e.g. 7.00 bid)
If the parsing criteria has been met the message will show 'Parsed' in the top right-hand corner.
If part of the message cannot be parsed, you will see in the message.
This shows that some but not all of the message has been parsed.
The information that could not be parsed will be highlighted in red.
In the below example, Aug try 26500 offered is not a valid period.
Some messages will NOT parse at all. When this is the case, you will see 'SKIPPED' in the message.
If the route is missing a message will not be parsed. A route is absolutely necessary for the parsing functionality to operate.
Commas are not accepted by the system. In the below example, there is a comma in the rate indicated. When entering the rate it is important to format the number using a full stop e.g. 7.00 will parse but 7,00 will not parse.
General text / chat will not be parsed.
Spreads will NOT be parsed.
Click the dot icon to Report an issue
