Who is this article for?

Advanced Administrators seeking access to Module Builder

An Active Support package or Success Plan and a Module Developer license is required. Reporting authorities, roles, and record access controls restrict data visibility.

The platform framework is supported by advanced tools that support the functionality, improve user web and mobile experience, enable customizations, and improve performance optimization.

• API Services: Applications are designed to be part of a company's larger ecosystem. Whether connecting to third party Cloud software or on-premises systems of record, the ability to exchange data with other technologies is a vital part of the equation. Applications connect by calling the REST API. REST is the de facto standard for interfacing web-based technologies. It is easy to learn, human-readable, and has tremendous support in the form of libraries for every major programming language.
• Data & Analysis Tools: Data & analysis tools allow users to import, export, examine, and interpret large datasets to extract meaningful insights, identify trends, and make informed decisions by transforming raw data into usable information through various analytical methods.
• Module Developer Guide: Applications are created and maintained using the Module Builder screen, a browser-based environment that configures fields, workflow, business rules, and more. The Module Developer Guide is a resource for Module Developers and establishes configuration guidelines and protocols. A programming background is not required to use Module Builder, but knowledge of relational concepts like SQL joins, Excel formulas, and a logically understanding of application structures and workflow requirements contribute to the success of a Module Developer. Users interested in performing Module Builder changes to the system should contact their Technical Account Manager (TAM). A Module Builder workbook is available to test a user's skills.
• Module Developer Guide Advanced: The Advance Module Developer Guide offers configuration troubleshooting and gotcha tips and tricks, move to production checklists, translation/internationalization support, and Miramar conversion guidance.
• Mobile Developer Guide: The Mobile Developer Guide describes how in certain use cases an application can be extended to a mobile tablet or smartphone. Users who perform a large amount of work away from their desks could work digitally, rather than having to capture data on paper and manually enter it into the system. The Mobile App is an extension of an application. It is used to capture data or execute work, but the workflow, approval, and reporting happen in the application on the desktop.
• Mobile Testing: Administrators are encouraged to test module developer changes to the system in a pre-production User Acceptance Testing (UAT) area. When it comes to testing these changes, there is no such thing as a mobile-UAT area. Testing of the mobile app must be performed using a preproduction-release version of the application, on the same device (phone or tablet) that the user already uses. For access to the Mobile Testing preproduction-releases, contact your Technical Account Manager (TAM).
• Metrics and KPIs: Metrics and KPIs is a robust application that allows an organization to define, track, monitor, and report on its Key Performance Indicators. KPIs can be populated by manual input or automatically from other applications. KPIs can be generated each month or quarter.
• Managing Checklists: The Checklist Guide outlines settings available to module developers or administrators who work with checklists connected to various modules or business processes, such as inspections, industrial hygiene (IH) checklists, supplier management checklists, etc.

These advanced tools all play a significant role in enabling custom configuration and highly functional platform features that administrators and module developers can use to ensure a user-friendly experience.