“复制分支”的动作目前尚未进入UX,因此@Paul最近挑战了我以创建解决方法。这是我相对简单的解决方案,可以通过复制列表中的“副本”中的项目来修改“分配”。应该注意的是,用户运行操作不是最佳实践,因为这可能会导致并发问题,因此在设计过程时,请考虑一下。在此模型中,我将一个部门和所有属于该部门的员工复制到新创建的部门。随着您增加层次结构的大小,复杂性显然会增加,但是逻辑仍应保持。下面的视频证明了它有效:NB: - 引用评论中的分期模块,因为简化了模型,并且分期模块的动作被移至EMP01中以进一步解释逻辑,我正在创建一个新的部门(在这种情况下为商业),这也为新部门(COMM)创建代码,并在模块中勾选要复制的分支。这使我可以过滤此视图,以充当导入我的L2部门列表的来源。它还可以进入SYS01和EMP01模块,以便我突出显示我需要复制的员工(分支项目)。反过来,这在下面勾选了副本包含的订单项。 The view can then be filtered to just the ticked items. This filtered view can then be used as an import for the relevant items into the L3 Employee List and the details—then into the EMP01 module to hold all of the required details (in this case only name and salary). I am also generating a “New” code at this point, which needs to be something distinct, especially if the same branch will be copied frequently. In this case, I have added the department #No to the name eg #13Shaila Engle. For best practice see Planual Rule 2.02-05. Once the imports are complete then the editable fields are highlighted in blue. This would be relevant in certain environments, but for others, we would be looking to list format against a flat employee module. Planual Rule 1.05-5 Display Name The new department field etc in DEP01 are filled with blanks to reset to a clean module (Action: EMP5). Action details This would be a single process button in an operational model, but I have broken it down into three processes here to demonstrate what is happening in the model. The processes create the department and filter the employees to be copied, copy the employees and then finally clear out the staging module and other temporary requirements.
... 查看更多