Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workflow subaction to submit Content Analytics event #30381

Open
john-thomas-dotcms opened this issue Oct 17, 2024 · 0 comments · May be fixed by #30384
Open

Workflow subaction to submit Content Analytics event #30381

john-thomas-dotcms opened this issue Oct 17, 2024 · 0 comments · May be fixed by #30384

Comments

@john-thomas-dotcms
Copy link
Contributor

Parent Issue

No response

User Story

As a developer, I want to collect custom analytics events when users perform specific workflow actions.

Acceptance Criteria

  1. Users can add a Workflow subaction to any Workflow action to record an analytics event.
  2. The subaction allows the user to specify the following information at a minimum:
    • Event type
      • This can be any value EXCEPT the pre-defined event types we record automatically (e.g. PAGE_REQUEST).
    • Object type (e.g. WhatAmI)
      • If the user leaves this blank, the type is set to CONTENT.
    • Object ID
      • If the user leaves this blank, the id is set to the content identifier.
  3. Each time the workflow action is executed, an event is logged to the analytics data store.
  4. The events submitted via workflows may be retrieved the same as all other analytics events (e.g. via API and viewtool).
  5. No information about the event is displayed anywhere (e.g. no growl, no popups, no log messages).
    • If the user wants any messages or notificaions, they can add other subactions for those.

Proposed Objective

Technical User Experience

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Review
Development

Successfully merging a pull request may close this issue.

2 participants