VNTG Core Service

VNTG Core Service offers significant advantages by providing essential, pre-built system management features. This is expected to reduce the initial time and effort required for projects by providing foundational functionalities for menu configuration and permission management. Furthermore, it allows for more efficient management by business users, who can directly adjust user permissions and view historical records without relying on IT staff.

This solution addresses several key challenges in enterprise system development:

• System user permissions: It provides features to manage user permissions, which are often difficult to handle with default OutSystems roles or static entities. It allows for user and group-based access control, as well as the ability to check the permissions a specific user has.
• Common code management: Instead of creating separate entities for each code classification, the module offers a centralized way to define and manage common codes.
• Compliance: The module provides a change history feature to record who granted a user system access and when, addressing requirements for internal accounting controls and audits.
• Efficiency: It eliminates the need to rebuild common management features for every project, which is inefficient
  
  

Key features include:

• User Management: Manages user information, including extensions for employee details like department and position.
• Group Management: Allows administrators to create groups and manage group members.
• Menu and Authorization Management: Provides a tree structure for menus and the ability to register programs and set menu permissions for both groups and individual users.
• Common Code Management: Provides screens to define common codes and a Code Dropdown block for use in screens.
• Change History: Most system management entities are read-only, with changes recorded in a separate history table via public actions, which can be viewed in a dedicated screen.
• Reusable Blocks: Includes reusable UI elements such as Code Dropdown and Confirm Popup.
• Client/Server Actions: Offers various actions to retrieve user information, menu permissions, and common codes for use in business screens.
  
  

• Architecture: The Core Service architecture is composed of several modules: VNTG_Admin (End-User UI), VNTG_CW (reusable UI Blocks), VNTG_BL (business logic), VNTG_CS (data entities), VNTG_Lib (utility functions), and VNTG_Th (UI theme).
• Requirements: It is recommended to review the components of the Core Service and either customize or directly develop parts that do not align with the project's specific needs. The module currently uses 55 AO (Application Objects), but this can be reduced to around 50 by removing unnecessary demo screens. It is advisable to have a buffer of +10 AO for potential