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.
We’re working on modeling inventory consumption at the lot level, accounting for shelf life considerations, since we need visibility into which lots may not consume—both for risk reporting and E&O analysis. Each item may have customers with different shelf life requirements. For example, item A may need 270 days for some…
Hi, Can you help me, how can we get row data into columns using Unique ID? Per attached below first snapshot, I want to bring rountingOrder 4, RecipientName, Sent and Completed dates in 1 row as show in sanpshot 2. Do I need to create Hierarchy list and Map?
Hi Anaplan Community, I'm working on a simulation planning model where users need the flexibility to input pricing adjustments at any level of the product hierarchy, and I’d love your guidance on best practices. 📌 Scenario Overview: We have a 4-level product hierarchy: Brand Category Sub Category SKU (lowest level) The…
