CMS/Dynamic Sandbox V2.0

[emmayank]

Description

This flow involves addressing the current problems with the sandbox and implementing Sandbox 2.0 with enhanced features. The key activities include:

Current Sandbox Problems:

1. Any new addition of domain/catalog involves generating example JSONs and redeployment.
2. Some code-level changes are required.
3. Responses are static.
4. Limited catalogues are available.

New Implementation of Sandbox 2.0:

1. Adding new domains/catalogs only requires the addition of the new catalog.
2. Minor code-level changes.
3. Responses are dynamic.
4. Unlimited catalogs—users can add as many catalogs as they want.

Solution for Sandbox 2.0:

1. Take a database dump from the dev database and restore it in the Strapi instance for Sandbox 2.0.
2. Implement mock automation for auto-confirmation, auto-arrival of the driver at the pickup location, auto-start, and end ride.
3. Create one instance for the Sandbox 2.0 environment.
4. Create a Postman collection.

Steps for Implementation:

1. Document the approach.
2. Make a list of all domains available in the sandbox that need to be created in Strapi.
3. Mock automation for status in <domain> for <this> & <this>.
4. Create a catalog.
5. Deploy to the BOC environment.

Additional Points:

1. Corresponding catalogs are required. If the catalogs are insufficient, additional catalogs need to be added. A baseline of 15 catalogs per use case should be established.
2. Corresponding Postman collections for each use case are needed and should work in the new sandbox.
3. List the steps on how the evaluation will be conducted.
4. Postman collections should be available in the new sandbox.
5. Corresponding issue tickets for this flow should be created.
6. Release notes should be added.

Example Use Cases Across Domains:

• Retail: 1 use case.
• EV: Multiple use cases.
• Skilling: 4 use cases.

Goals

• [ ] Implement Sandbox 2.0 with enhanced features.
• [ ] Ensure dynamic responses and unlimited catalogs.
• [ ] Document the approach and deployment process.
• [ ] Create and deploy Postman collections for each use case.
• [ ] Ensure catalogs meet the baseline of 15 per use case.
• [ ] List evaluation steps and create corresponding issue tickets.
• [ ] Add detailed release notes for Sandbox 2.0.

Expected Outcome

• A fully functional Sandbox 2.0 with dynamic responses and the ability to handle unlimited catalogs.
• All use cases across Retail, EV, and Skilling domains are documented and deployed with corresponding catalogs and Postman collections.
• Comprehensive documentation, including release notes and evaluation steps, is available.

Acceptance Criteria

• [ ] Sandbox 2.0 is implemented with dynamic responses and unlimited catalog capacity.
• [ ] All required catalogs (15 per use case) are available in the new sandbox.
• [ ] Postman collections are created and functional for each use case.
• [ ] Deployment to the BOC environment is completed.
• [ ] Documentation, including the approach, evaluation steps, and release notes, is finalized and available.
• [ ] Corresponding issue tickets for this flow are created.

Mockups / Wireframes

NA

Product Name

Beckn

Domain

Beckn BPP

Tech Skills Needed

Node.js, Strapi, Database Management, API Development, Mock Automation, QA Testing

Complexity

High

Category

Development

Sub Category

Sandbox Environment Enhancement

Project View

https://github.com/orgs/beckn/projects/28/views/58

[yesrag2309]

@emmayank - Can you fill the missing below details and the current working status as comment.

Assignee Flow status Start Date End Date Labels Category Project

@viraj89 @faizmagic

[yesrag2309]

@emmayank - Can you fill the missing below details and the current working status as comment.

Estimation Hrs Priority Start date and End date

@viraj89 @faizmagic

[yesrag2309]

@emmayank - Please find below the current week status and next week plan.

Current week status - DHP consultation and diagnostics have been migrated from Static Sandbox to Dynamic Sandbox. Next week plan - DHP Pharmacy and ODR will be migrated from Static Sandbox to Dynamic Sandbox.

@viraj89 @faizmagic

[yesrag2309]

As discussed in today’s tech standup, versioning needs to be realigned with @faizmagic. Once he is back, we will review the details of Version 2.0.

@emmayank - Please share the status of the DHP Pharmacy and ODR migration from Static Sandbox, and provide a list of the remaining items along with the actual pending details. Additionally, include the plan for completion, specifying how many iterations are still needed to finish this task.

@faizmagic @viraj89 @vbabuEM

[yesrag2309]

@emmayank - Please update the card. If DHP Pharmacy and ODR are migrated from Static Sandbox to Dynamic Sandbox please close this card and open a new card by mentioning next set of planned migrating items/components.

@viraj89 @faizmagic

[yesrag2309]

@emmayank - As we discussed, this card allocated resource is working on the P2P energy App Google Demo moving this card next iteration by changing the status as Floated. Next week we need to look for alternate resource to pick if not this is move further to next iteration.

@viraj89 @faizmagic