When you clone a page, shouldn’t the Notes indicator on each object/workflow/step clone also?
Current Behavior:
Notes are app-based, not page-based.
On a cloned page, notes from the source page are only visible via “see all (#x) notes” link in the top-right corner of the notes pane. So the notes are not really cloned, but the Notes pane will have this list of “hard-links” to the original/source object.
No note indicators are cloned, ie, an object on the source page that has a note attached will have a “full” note indicator. On a cloned page, the note indicator for the corresponding/cloned object will be “empty”.
Problems:
If you have lots of notes, and use cloning of pages for version control or to copy core features, on the new copy you end up with a very long list of notes that you have to manually scroll through to find a note.
The list of “other notes” on a cloned page are actual hard-links back to the original/source object. When you click on one of these notes (like say, to edit it), you are taken back to the source page and source object where you may mistakenly continue with other edits on THAT page. Best case, you realize the page has changed and must then navigate back to your clone to continue working.
Constantly clicking the notes pane on a cloned page and scrolling through its list of other notes to see if you already have a note about that object.
Suggested Behavior:
Clone the notes with the objects so each object will retain its note AND note indicator.
Workaround:
Clone the whole app for version control. This seems like a silly waste of resources, but you will end up with a copy that will have the notes properly attached to each object. Cloning a page was supposed to solve the problem of copying objects and workflows so the new page would work the same as the original, but leaving notes out of the cloning process means you really should clone the whole app whenever you need a working & documented copy of anything?