For the project I am working on we have an entity called Task. Each task has a list of Subtasks and each Subtask has a list of resources that it requires. Our clients want a page where they can create/edit a Task and modify it's subtasks and the resources used by each subtask. However, they also want the ability to click cancel to revert everything (including any subtasks or resources that were deleted) Currently I have implemented edit/save microflows which create a NP clone of all the entities when editing and when the user click saves it replaces the exiting persistent version in the database. However, the tasks can contain a long list of subtasks and we are starting to notice performance issues due to too many NP entities and the time it takes to create them all. Are there any other ways to do something like I have descrived?
asked
Jacob Whyte
1 answers
1
Hi Jacob,
You can use persistent entities for subtasks and resources. Use associations as the data source to display subtasks and resources. When saving, make sure to commit all objects. If the user cancels, any unsaved changes will be discarded automatically.