As a Content Creator, I want to track the approval status from the kebab menu of contents that I have created

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.4.3.5 CE GA5, 7.4.13 DXP U1, Master
• Component/s: Workflow
• Labels:
  • 7.4-portal-ga5
  • S
  • fc_21_11
  • qa_test_mapped
• Epic Link: Workflow Tracking

As a Content Creator, I want to track my content's approval status from the kebab menu of my content, so that I can follow the approval process within the context of my content. 

Design Deliverables

Mockup

Context

A tracking component was created by the Workflow Team that allows developers to pass an instance Id and have a complete view of the workflow of the instance (including the current step, past steps and possible future steps). This was created for Commerce use cases. However, this component has a lot of value elsewhere in DXP for assets that utilize an approval workflow.

Therefore, we are expanding this feature to other assets that support Workflow (eg. blog entries, web content, etc). Instead of just showing if the asset is pending or approved, it will be possible to open the Workflow Instance Tracker from the kebab menu of the asset and view the complete workflow of the instance. 

Acceptance Criteria

Given an asset configured with an approval workflow,
and an asset instance that was recently submitted to approval,
when a user opens the kebab menu for the asset,
then he should be able to open the Workflow tracking component and understand where in the workflow process that asset instance is.

• If the asset is approved, it should be possible to track the steps that it went through.

Definition of Done (DoD):

• All Acceptance Criteria were passed;
• Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
• Code with peer review completed;
• Validated by QA, Product Designer and/or PM;
• No critical bug related to Story scope (ex.: similar of FP4, FP5);
• Make sure that all system documentation were updated (if necessary)
•  Make sure that it has the extensions points needed to allow GS and customers to customize the feature (If applicable)