Skip to main content

Idea pipeline (top 25)

Filter by idea status

Filter by product

1967 Ideas

SuleymanVanguard

Delegate / proxy feature to transfer user rights in case of holidays or sicknessOpen

Not sure whether Thinkwise should deliver this feature or not, but just wanted to post this Idea to see if other TW-customers needs these kind of functionality too.Delegation functionalityA feature in a software system that allows users to define their holiday or sickness period and transfer their user rights to a dedicated colleague is typically referred to as "delegation" or "proxy" functionality. This feature is crucial for ensuring business continuity and workflow efficiency in an organization.Key Components and FunctionalityUser Interface for Setting Delegation: Period Definition: Users can specify the start and end dates for their holiday or sickness period. Select Delegate: Users choose a colleague to whom their rights and responsibilities will be transferred during their absence. Reason/Notes: Optionally, users can provide a reason for the delegation (e.g., holiday, medical leave). Delegation Rules and Permissions: Granular Permission Control: Users should be able to select which rights and responsibilities are transferred. For example, they might delegate the ability to approve certain workflows but retain access to sensitive information. Temporary Access: The system should ensure that the delegate only has access for the specified period and automatically revoke access once the period ends. Optional: Notification and Confirmation: Notifications: Both the original user and the delegate should receive notifications about the delegation setup, including any changes or cancellations. Confirmation: The delegate may need to confirm acceptance of the delegated responsibilities. Audit and Security: Audit Logs: The system should log all delegation activities for security and compliance purposes. Security Checks: Regular checks to ensure that delegations do not create security risks or conflicts of interest. BenefitsBusiness Continuity: Ensures that critical tasks and approvals are not delayed due to a user's absence. Maintains workflow efficiency by allowing colleagues to handle responsibilities seamlessly. Improved Flexibility: Users can take time off without worrying about pending tasks or responsibilities. Provides flexibility in managing unexpected absences due to sickness or emergencies. Enhanced Collaboration: Promotes a collaborative work environment where colleagues can support each other. Helps in distributing workload effectively during peak times or staff shortages. ConclusionA well-implemented delegation feature enhances productivity, ensures continuity, and provides flexibility in managing absences. It is a vital component for modern software systems, particularly in organizations that require constant workflow and decision-making processes. Ensuring security, ease of use, and seamless integration are critical factors for the success of this feature.

Freddy
Thinkwiser
FreddyThinkwise Local Partner Brasil

Model actionbar elementsCompleted

Especially with the introduction of the actionbar component, where you can freely position the actionbar it has become more a necessity to model the action groups of the actionbar. I see the taskbar has the following main groups:Filter Pre-filter Tasks Reports CRUD actions (incl. import/export) RefreshIt's not uncommon that you have a grid, form and for example a preview/cube/ or other element not being a reference.. If you put them all on a separate tab all the component gets all the action bar items. Functionally and personally this is unwanted. the filter, pre-filter and mass update for example do not make sense on a form level (exceptions are there of course) because you are looking at a single entity.  In the U-GUI we use the previewer to load external apps.. Basically you don't want to have search, filter, CRUD actions there (again exceptions are possible)It would be really great if the option to hide action bar could be extended by modelling at screentype level which action-bar items you would like to see.  Example: If you put a form on a separate tab, the search /filters are most likely unwanted because it will most like likely changes your context if you (accidentally) fill something in the searchbar or activate a pre-filter.  If you have, like we external components that base themselves like a form on a single entity you have the same situation.. you probably only want to see tasks/reports and a refresh button here..  Especially when you are not familiar with the concept of Thinkwise it's odd to see have search / CRUD actions here.  @tiago @Yara