Hi Sudhir,
Instead of cloning the module you can make it multi departmental by adding a Department entity and linking it to Users and Tasks. Use XPath constraints and access rules to restrict visibility per department. using this way you reuse the same module logic for all departments and reduce maintenance and duplicate logic.
But If your application is already on prod and have lot of data created. You need to map the older data to suit the new logic as well by using microflow scripts which you can run.
Hope this helps!
Thanks
Reusing a Module for Multiple Departments Without Cloning – Best Approaches
Instead of cloning the module, consider the following scalable options:
1. Add Department Entity & Association
Introduce a Department
entity.
Associate it with Task
, Activity
, and User
entities.
This allows you to filter data by department dynamically.
2. Use Roles with Constraints
Define Admin_User and User_User roles per department, or manage access via XPath constraints using the department reference.
Avoid duplicating role logic by designing reusable microflows and pages.
3. Parameterize Pages & Microflows
Design pages/microflows to work with a department parameter.
Load data conditionally using [%CurrentUser%]
and associations.
4. Use App Store Modules (e.g., User Management)
Combine your module with existing generic modules to manage users and permissions centrally.
5. UI Filters & Navigation
Add a department switcher/filter for admins.
Dynamically show only relevant tasks per user’s department.
Avoid cloning as it leads to maintenance issues. A dynamic, association-based design makes your app easier to extend and scale across departments.
Regards ,
Menta Raju