Wrigley HUB – Reapplication Workflow Glitches

1. Wrigley HUB – Reapplication Workflow Glitches

2. To analyze and determine system issues that are preventing Wrigley and Agency users from properly completing Reapplication Requests on the HUB. To recommend bug fixes to BBDO NY to improve the existing reapplication process on the Wrigley HUB Objective

3. Issue #1: Non-working Required Fields Issue #2: Form inconsistencies when ‘Est. with LA’ Issues to Discuss

4. There are two Reapplication Workflows in place for Finished Work assets . These workflows are triggered based on the following criteria: Workflow #1 – If the asset that has been selected for reapplication is an ‘Original’ asset (ie. If the ‘Adapting Market’ field is blank), then Workflow #1 is triggered Workflow #2 – If the asset that has been selected for reapplication is a ‘Reapplied’ asset (ie. If the ‘Adapting Market’ field is populated), then Workflow #2 is triggered. Workflow Review – Finished Work Assets

5. After the client initiates a request, the Local Agency is responsible for filling out the Detailed Request form. There are multiple fields marked as required, however the only field that is truly required is First On-Air Date. Backend Status = ActivatingAgency Workflow 1 – Issue #1: Non-working Required Fields Red Asterisks imply that field is required

6. If the Local Agency tries to submit the form without populating a value in the ‘First On Air Date’ field, they receive the following validation. If the Local Agency tries to submit the form without populating a value in any of the other required fields (ie. Airing Period, Invoice To, Contact Name, Agency Address, Telephone Number). They are able to submit the request without being stopped. This is a problem. Workflow 1 – Issue #1: Non-working Required Fields

7. In Workflow #1, there are 3 backend statuses that cause the status to the end user to show as ‘Est with LA’: ActivatingAgency – This status will occur when the Client initiates the request and forwards to the LA. ReturntoActivatingAgency – This status will occur if the request is initiated by the client, returned by the LA back to the client, and then re-forwarded back to the LA. ReturnfromOA – This status will occur if the client initiates the request, the LA fills out the form and submits to the PA, then the PA clicks ‘Return with Comments’ to send the request back to the LA. Workflow 1 – Issue #2: Form Inconsistencies when Est with LA

8. ActivatingAgency The form shows multiple required fields (Consumer Benefit, Brand, Airing Period, First On-Air Date, Invoice To, Contact Name, Agency Address, Telephone Number) Workflow 1 – Issue #2: Form Inconsistencies when Est with LA

9. ReturntoActivatingAgency Red asterisks for the Required fields are missing from the form First On-Air Date is still required. It’s just not shown. Workflow 1 – Issue #2: Form Inconsistencies when Est with LA

10. ReturnfromOA Red asterisks for the Required fields are missing from the form Now only ‘Comments’ are required. The ‘First On Air Date’ is no longer required. Workflow 1 – Issue #2: Form Inconsistencies when Est with LA

11. Recommended Fix All 3 forms tied to the 3 statuses should work consistently Consumer Benefit, Brand, Airing Period, First On-Air Date, Invoice To, Contact Name, Agency Address, Telephone Number, and Comments should ALL be required fields on 3 forms The Required Fields should show with a red asterisk on all 3 forms Workflow 1 – Issue #2: Form Inconsistencies when Est with LA