What is the best practice to keep copies of the entire apps page in a periodic manner in case of reference required in the later period.
Duplicate App and store it with date mentioned.
One point for consideration is the retention period, as the underlying/linked models change the relevance of an duplicated UX pages may be impacted. Cards may no longer work as originally designed.
This will vary by use case but from my experience the utility of these duplications have a limited shelf life.
@BlessyDube - While creating your duplicate app, you can provide instructions in the app with the date you created and also the app name can also include the date created.
Hi @BlessyDube , One more point worth noting is to remove the access to the older/copied app pages for the user so they don't end up in the wrong/outdated pages.
Hi - I cannot seem to create a migration for Assignment 3 and it will not allow me to update the hierarchy and proceed further. It seems to think that a link has already been created, but I don't see anything. Any ideas?
There was an error rendering this rich post.
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-yearβ¦
