Skip to main content

Context: This may be harder to explain but let's say I have interlinking tabs in a LucidChart. Tabs A, B, C, D, E .... There are shapes in each tabs, and the shapes will link to other tabs. For example, Tab A -> D, B->D, C->D, E->D.

 

I'd like to implement a "Back" functionality.

Scenario 1) User navigates from Tab A -> Tab D. Then user clicks the "back" button/shape. The user goes back to Tab A

 

Scenario 2) User navigates from Tab C -> Tab D. Then user clicks the "back" button/shape. The user goes back to Tab C

 

Request: A “back” shape/function that knows where it came from, i.e., the back button on a browser or a smartphone.

Hi, thanks for this idea! We encourage anyone else who’s interested in this to upvote this post and share any additional details about your use case or what you’d like to see in this experience. For more information about how we manage feedback in this community, please take a look at this post:

 


I’ve commented on a couple of Idea threads along this same line: Would really like “links” to be object-based and reciprocal.

Using the OP’s example: User clicks shape on Tab A -> shape on Tab D. Then user clicks the “landing” shape on Tab D to return to clicked shape on Tab A.


Hi ​@k8siegel, thank you for contributing to this idea! I noticed your comment on this similar post regarding bi-directional links between objects/shapes. 

We’re very interested in your feedback! Would you be willing to share more details about your use case? 


Sure! Here are some screen shots from Visio, where this functionality works as desired. (We document call flows, mapping out the logic of IVR systems to illustrate possible caller journeys. Some documents are 500+ pages.)

You’ll see that we label incoming links with the corresponding outgoing location, so users can “track back”. Having the two objects linked makes navigation much easier, especially when the pages aren’t near each other. Currently in LucidChart, we need to manually create the object on the “destination” page with its own additional link back, doubling our work and introducing the possibility of error.

With subroutines, there could be dozens of connected pages. And there can be multiple “entry points” between one page and another, so having a link connected to an OBJECT rather than the overall PAGE would help ensure that users are following the correct path.

links coming to the same page from different locations; sometimes logic picks up at a point other than top of page
another link FROM the same page (35511) TO the same page, but at a different logic point. also, link to subroutine ~200 pages away
return from subroutine links to various locations (some on same page)
subroutine links returning to different logic points on the same page

 


Hi ​@k8siegel, Thank you once again for this excellent feedback and for providing more details of your use case! I can understand how this would make navigation much easier for you. The detail about what you'd like to see in this experience is very helpful for our team! 

We encourage anyone else who’s interested in this to upvote this post. For more information about how we manage feedback in this community, please take a look at this post.