Platform implementation

ServiceNow App Engine

We implement ServiceNow App Engine so teams can build custom applications on the same Now Platform as their IT and employee services, reusing its users, groups, security and workflows.

Hands typing on a laptop on an oak desk beside a coffee cup

App Engine work starts with a basic question: what belongs on ServiceNow at all? Applications that route requests, track records and need approvals fit well, while large public websites usually do not. We set up App Engine Studio for guided builders and ServiceNow Studio for developers, with App Engine Management Center controlling who may create applications. Arabic forms and portals, and the language settings they need, are planned with the first application.

Each application is built in its own scope, with tables, forms, UI Builder pages, flows and access control lists that keep its data apart from other apps. Git source control integration, the Automated Test Framework and the application repository move each version from development through test to production without manual update sets.

ServiceNow App Engine and related product names may be trademarks of their respective owners.

How we implement ServiceNow App Engine

Design, build, integration and run-state support, with each decision recorded for your steering committee.

  • Blueprint and governance

    The intake process for new applications, scope naming, table design and the role and ACL model are agreed with your ServiceNow platform owner and security team before the first app is built.

  • Application intake and triage

    A request-to-build process in App Engine Management Center that checks each idea against existing apps and assigns a business builder or a developer.

  • Data model on the platform

    Tables extended from Task or created new, with relationships to users, locations and the CMDB, designed so reports and SLAs need no extra work.

  • Store-ready patterns

    Applications built to ServiceNow Store standards where you plan to share or sell them, including scoped APIs and documented configuration.

  • Hypercare and managed support

    Either of ServiceNow's two yearly releases can change UI Builder components and APIs, so we run ATF suites on each upgrade, review deprecation notes that affect scoped applications, and monitor app usage and errors.

Signs your next app belongs on ServiceNow

App Engine fits organisations that already run ServiceNow and want new request-driven applications to share its identity, data and workflow, instead of adding another platform to support.

  • An existing ServiceNow instance with an active platform owner
  • App Engine licences planned for builders and users
  • A backlog of request, tracking or approval apps suited to the platform
  • Agreement on which apps business builders may publish

Plan ServiceNow App Engine with Hosn Al Tomoh

Share your current systems, compliance themes and integration map. We will return a phased plan, a risk register and a governance model for your stakeholders to review.

Start the conversation