Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 12 Next »

Overview:


Quantitative Data:

Data driven justification for ux/ui changes, especially necessary for organic changes that do not originate from client requests or roadmap features.

Link

Date Range

Item

Metric & Value

Assumption

00/00/2021
to
00/00/2021
(0 Days)

Metric name

  • Metric Value

HYPOTHESES

  • Lorum ipsum

REASONING

  • Lorum ipsum


Competitor Research:

Function

Findings

Image

Takeaways

EMBRACE

REJECT

TO DISCUSS


Proposal Feedback:

Stakeholder

Date

Changes

Product

17/03/23

DONE

  • ‘Connect’ sidebar item

    • This should show even if credential manager hasn’t been configured

    • If users navigate to ‘connect’ in sidebar without credential setup, the listing will be empty

  • Audit of chnages

    • Details will be on system level

  • Campaign processr < visibility for publishers

    • For v1 this should be asingle toggle to apply to all publishers

    • V2 may have ‘per publisher selection’ if required

REJECTED

  • Potentially merge management screen with ‘dashboard’ somehow, maybe new tab?

    • Instead, have indicator on dashboard that campaign is ‘connected’

NEED MORE INFO

TO DISCUSS

  • Terminology change for ‘Active Configurations’ and ‘Inactive Configurations'

    • Arunima suggested changing ‘Inactive’ to ‘Completed’ or ‘Pending Changes’ or ‘Action Required’?

  • Development things to talk to rokas about

    • Handing of updates

      • if a configuration change is made (like a job is updated, job is added, job is removed) how do we track and send this across enterprises? Via job id?

    • In mappings, can only reference fields in processr once a lead is in because the fields come from the lead data

      • Can we change behaviour so fields come from associated form on the campaign? Dropdown of fields in integrations should come from forms (value transforms is an issue?)

TO DO

  • ‘Configure’ step 2, for ‘validation lists’ values will not be shown in column because there could be too many to show

    • But if we have ‘view details’ then it could have table with pagniation of values

  • New step to include ‘integration’ configuration?

  • Listing needs ‘domain’ column and ‘advertiser’ column

  • Dashboard to have new column to show if campaign is ‘connected’

  • Step 1 select ‘existing campaign’ should have advertiser first

  • Step 1 setup, step 2 form mapping

    • Mapping is required on ‘form’ not on ‘job’

    • If select from linked enterprise then mapping is ‘done’ because sending enterprise has done this

    • If select own form, then mapping is required

  • Step 1 - ‘select existing campaign' interface should only be a 1 to 1 relationship, so cannot add more than 1 campaign to assign a configuration to

    • Then on processr we could have a feature to ‘import’ all processr jobs from another campaign

    • So ‘associated campaigns’ no longer required

  • Mocks for configuration updates, e.g. on jobs step, have column for ‘type of update’ then highlight the jobs that have been added, changed, removed (tracked based on campaign ID)


Retrospective:

To be completed after this features release. The retrospective should allow a basis for further improvements to this feature.

User Feedback

Stakeholder

Date

Description

Quantitative Data

Link

Date Range

Item

Metric & Value

Assumption

00/00/2021
to
00/00/2021
(0 Days)

Metric name

  • Metric Value

HYPOTHESES

  • Lorum ipsum

REASONING

  • Lorum ipsum

  • No labels