Request and Approval process

Using Streamlit
,
1

Hi
Im trying an implement a data sharing process using streamlit, where a person will select a data in dropdown box and request access.
and there will be approvers for this min 2. They should approve. comments added if possible
i want to see as roadmap diagram on status of approvers.
similar to this

image
image1792×742 73 KB

is it possible? can you help how i can achieve this.

1 Like
2

This is interesting, I see this app applied in online store bought product tracking, but you need to describe in detail the processes involved.

Example

  1. The person logs in on the app.
  2. The person selects data.

What is next? Where are the approvers? Who is this person?

1 Like
3

FYI, the screenshot i pasted is not streamlit app. I took one from online :stuck_out_tongue:
Data Engineer/ Developers will login and search for right data is present in datalake. I have done this part.

image
image1948×619 56 KB

if the data which they are looking is present, they have to request data share button. which will go for data owner approval - minimum 2
once the approvers approved. and then i have a set command for data share will be enabled.

there will be separate login for developer and separate login for approvers
this is my idea, im not its possible or not. i need to check with fellow community members

1 Like
4

Hi @gowthamneelakandan, try using the ‘Steps’ option (see sidebar) available at https://nicedouble-streamlitantdcomponentsdemo-app-middmy.streamlit.app/

Cheers

2 Likes
5

thanks, will have a look and try to implement

6

Streamlit can handle this. Here is a typical process behind the scene.

Terms for Each Step:

  1. Order Placed: The buyer has successfully placed the order.
  2. Processing: The order is being prepared, which includes picking and packing the items.
  3. Ready for Dispatch: The order is ready and awaiting pickup by the delivery team.
  4. Dispatched: The order has been handed over to the delivery team.
  5. In Transit: The order is on its way to the delivery address.
  6. Out for Delivery: The order is with the local delivery agent and is on the way to the buyer’s address.
  7. Delivered: The order has been delivered to the buyer.
  8. Received: The buyer has acknowledged receipt of the order.

Monitoring and Communication Enhancements:

  1. Automated Updates: Implement automated notifications via SMS, email, or in-app messages at each step.
  2. Real-time Tracking: Provide a real-time tracking link for the buyer to see the current status and location of their order.
  3. Estimated Delivery Time: Continuously update the estimated delivery time based on the real-time location and status of the order.
  4. Proof of Delivery: Require a signature, photo, or another form of confirmation upon delivery to ensure the item has been received by the buyer.
  5. Feedback Loop: Allow the buyer to provide feedback after receiving the order to ensure customer satisfaction and improve the process.

Additional Steps to Improve the Process:

  1. Order Verification: Before processing, verify the order details to avoid any mistakes.
  2. Quality Check: Before dispatch, conduct a final quality check to ensure the items are in perfect condition.
  3. Packaging Confirmation: Confirm that the items are securely packed to prevent damage during transit.
  4. Customer Support Availability: Provide easy access to customer support at all stages of the delivery process.
  5. Delay Notifications: If there are any delays, promptly notify the buyer with the reason and the new estimated delivery time.

Implementation Example:

  1. Order Placed: Buyer receives a confirmation email.
  2. Processing: Notification that the order is being prepared.
  3. Ready for Dispatch: Notification that the order is packed and ready for pickup.
  4. Dispatched: Buyer receives a tracking link.
  5. In Transit: Real-time tracking updates are available.
  6. Out for Delivery: Notification that the delivery agent is on the way.
  7. Delivered: Notification that the order has been delivered, along with proof of delivery.
  8. Received: Buyer confirms receipt, and the order is marked as completed.

Example:

  1. The buyer logs in on the app, choose an item, put item on the cart, checkout the item, and the app updates the status to Ordered Placed
  2. The store owner logs in on the app, see the notification that there was an order placed on an item. Prepares the item, etc
    .
    and so on

The app provides different views depending on the users’ role (buyer, store owner, admin, etc.). A huge app with massive database usage, but this is fun.

7

image
image1256×362 13.6 KB

thanks @Shawn_Pereira.
i had created a yaml file locally for now. and put the name and status in it. based on that i created this.
this was exactly which i wanted. i had disabled all the steps.

but i see, there are lot many antd components, which im more interested.
Steps - Ant Design

my question is the components that is available in the app which you shared will work

or other components that will also work if we pass right pamrs?

1 Like
8

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.