Skip to content
← Go back

Transaction status reports from Youview

June 2nd, 2014 (Revision 1), download as PDF

If your organisation uses BeBanjo to publish Metadata to YouView then we have good news for you! When the YouView systems process transactions for Metadata publications they provide detailed Transaction Status Reports; these are now displayed in the Schedule page of BeBanjo.

This note describes what has changed in full, and as usual you can contact support or your technical account manager for further clarification.

Transaction Status Reports in BeBanjo

When a Scheduling is published to YouView its Metadata status will now change to Publication sent instead of Published. Every five minutes BeBanjo will find all Schedulings for YouView whose status is Publication sent and retrieve their Transaction Status Reports from YouView.

That report includes the “life-cycle” status of the transaction in YouView, and BeBanjo uses that status to update the Metadata status of the Scheduling, like this:

YouView Life Cycle Status BeBanjo Metadata Status
Accepted Publication sent
Validating Publication sent
Quarantined Publication sent
Committing Publication sent
Failed Publication failed
Committed Publication sent
Publishing Publication sent
Published Published

How to use these reports in the Schedule page

In the Schedule page you can use the Metadata Status filter to easily find Schedulings of each status, for example: Publication failed. Examples of each are shown below.

Publication sent

Good things come to those who wait! Here’s a Scheduling that was recently published to YouView: 2014 06 02 Transaction Status Reports From Youview R1 01

Published

Here’s an example of a Scheduling whose transaction in YouView was published successfully; notice that BeBanjo provides you with useful information such as the CRID and transaction identifier values: 2014 06 02 Transaction Status Reports From Youview R1 02

Publication failed

Don’t panic! Here’s an example of a Scheduling whose transaction in YouView failed; notice that BeBanjo provides you with everything you need to investigate the problem with YouView, e.g. CRID and transaction identifier values, and BeBanjo:

2014 06 02 Transaction Status Reports From Youview R1 03

Reference

  • movida#934 YouView SDK: Handle Transaction Status Reports