Guided flow enhancements: Telemetry

[MaunicaKolla815]

ENHANCEMENT 1

• [ ] Guided flow (pest) initiated twice (hygiene fix)

Current Behavior -

On flow start, the query in DB comes as "Guided:Pest". On the 3rd interaction where the user has to select between writing the pest name or writing symptoms, the query column in DB again shows "Guided:Pest" as the query.

Expected Behavior -

Instead of "Guided:Pest" on the 3rd interaction, the query column should include - "Select Crop Information Needed" as the question.

Screenshot attached below for better understanding -

ENHANCEMENT 2

• [ ] Guided flow isendflow not captured for guided:weather + guided:scheme

[MaunicaKolla815]

@prtkjakhar - isFlowEnd column to be made true for weather guided

User flow: Weather --> crop selection

Populate the isFlowEnd column as Weather - false Crop - true

[MaunicaKolla815]

@Amruth-Vamshi : The requirement is to identify isFlowEnd for the schemes flow.

When do we consider the flow to have ended?

Step1: User clicks on scheme Step 2: User types/selects a scheme Step 3: User picks either - About scheme, Eligibility, Benefits | End the flow here, mark isFlowEnd as true

Cases where user selects, mark isFlow end as false

1. Other questions on scheme
2. Back to home
3. Abandons at step 2

[Sreejit-K]

Enhancement 1: @MaunicaKolla815 At the third interaction on selecting pest the query coloumn is getting populated as 'pest'. We use this 'pest' string inorder to continue that particular flow with the button that is being selected. And as per the discussion with @Amruth-Vamshi changing this to "Select Crop Information Needed" would require lot of changes in flowise( Lable Classifier has to be replaced with codeRunner transformer )

[MaunicaKolla815]

Enhancement 2: Completed for AKAI, pending for KMAI @Sreejit-K