This module focuses on creating mobile applications in ServiceNow. Developers will learn the essentials of building custom applications tailored for mobile devices.
1. Course Prerequisites
Before embarking on this course, it's essential to fulfill the following recommended prerequisites to ensure a smooth learning journey.
1. Familiarize Yourself with Mobile Basics
To grasp the ins and outs of mobile apps and their features, including the terminology employed in this course, we recommend completing the course "Mobile: Introduction." This course assumes a foundational understanding of mobile concepts.
2. Access Your Instance
For the practical activities, make use of the "Open My Instance" feature in the course. Be sure to take note of the expiration date to keep your experience uninterrupted.
3. Utilize Admin Impersonation
Use the personas of Beth Anglin or Tyree Courrege for testing configurations. Log into the mobile app as an admin and impersonate Beth or Tyree as needed.
4. Download the Mobile Apps
Download the mobile apps on the device where testing will take place. You can do this through your device's app store or your organization's mobile device management. For detailed guidance and assistance with barcodes, refer to the "Mobile: Configure Mobile Apps and Instances" course within the "Mobile: Additional Resources" section.
5. Harness the Power of Update Sets
Leverage update sets to save the configurations you make during the training. In case your instance needs to be reclaimed before completing all modules, update sets allow you to reconstruct applets and reconfigure settings.
6. Ensure Icon Compatibility
Review and bookmark the "Mobile Icons ServiceNow" documentation page to confirm that the icons you use are supported for mobile apps. If an unsupported icon is selected, it will be represented by a question mark.
As you progress through the lessons, you may encounter slight discrepancies between the screenshots or videos of the configurations and what you observe. These variations may arise from differences in the mobile device's operating system or the use of different app versions, or due to configurations completed in prior lessons.
Once you have met these prerequisites, click on "Next: Why This Course" to discover the objectives and goals for this lesson.
2. Purpose of This Course
This course is designed to provide an understanding of how ServiceNow's mobile development can be tailored to meet the specific needs of different organizations. While ServiceNow offers pre-configured base system applications for various business lines, these applications are generic and not tailored to individual organizational requirements.
As an Application Developer within the ServiceNow ecosystem, your role involves harnessing the platform's capabilities to create applications that streamline work, enhance manageability, and increase productivity. To unlock the full potential of mobile capabilities, creating mobile-specific applications is necessary.
While base system applications like Now Mobile, ITSM Mobile, and Field Service Management Mobile come pre-configured, they can be customized to better align with your organization's unique processes. This course explores the flexibility of modifying screens, functions, and other configurations within these applications, as well as adding new elements to meet your organization's requirements.
Alternatively, you can opt to create entirely new applications from scratch, configuring screens, functions, and other features. This approach can be particularly beneficial in avoiding issues like skipped records during system upgrades or complications when updating Store applications to the latest versions.
Throughout this course, we offer two methods for creating new applications:
App Engine Studio (AES): This method is preferred for creating mobile applications, but it comes at an additional cost as a Store app. Not all organizations may have access to it. Even if your organization doesn't have AES, understanding its configuration can lay the groundwork for promoting its adoption within your organization.
Guided Application Creator (GAC): An alternative to AES, GAC is available within Studio on the instance and doesn't incur an additional fee.
By the end of this course, you will have the opportunity to create a new application using both methods, allowing you to choose the approach that best aligns with your interests and your organization's needs.
3. Differences Between AES and GAC
The creation of mobile applications is possible using both App Engine Studio (AES) and Guided Application Creator (GAC). However, there are notable distinctions in the end products between these two methods:
Both AES and GAC create the following elements:
Launcher Screen(s)
In AES, the launcher screen is part of an experience and is a vertically-oriented icon section with a feed count. It uses the name set for the experience.
In GAC, the launcher screen is created with the same name as the application and is a horizontally-oriented icon section. The name of the data item matches the application name.
Data Item
In AES, a data item is created for each list screen, and conditions can be set to control the returned records. The name matches the screen's name.
In GAC, a data item is generated for each selected table, and all records are returned. The name of the data item matches the application name with the table name appended.
Screen(s) and Necessary Card(s) and Icon(s)
In AES, a list screen with a record screen, or a webpage screen (depending on the selection) is created. The number of screens depends on the configuration, and the name matches the screen's name.
In GAC, a list screen and record screen are created for each selected table, named according to the table. It uses the data item with the same table appended, and the name is based on the table.
Functions - New, Edit, Delete
All three functions (New, Edit, Delete) are created for each table or screen configured, with the table name or screen name in parentheses.
Notable Differences to Be Aware of:
With GAC, all created elements follow a naming convention based on the names of the tables, which often require updates and may not be concise or valuable.
AES allows initial configuration to be added to Mobile Agent, Now Mobile, or both, while GAC always adds configuration to Mobile Agent. Edits are needed to add or delete configuration to and from the apps if a different assignment is desired.
AES provides the flexibility to select either a list screen or mobile web screen, but GAC always starts with a list screen as the first screen.
AES allows conditions to be set for data items, while GAC does not, resulting in the retrieval of all records.
GAC permits the selection of multiple tables at once, but it only creates one screen for each table. In AES, each table selection requires screen creation within the Experience, allowing the same table to be used multiple times with different conditions set.
GAC offers an option to create the application in the Global scope, whereas AES doesn't.
GAC requires a specific role for operation, which is not a requirement for AES.
There is no option to publish the application in GAC.
In exceptional cases, GAC may be preferred over AES (e.g., when creating the application in the Global scope is necessary). However, in most cases, AES is the preferred choice, and GAC should only be considered when an organization lacks access to AES.
This course provides the opportunity to learn about both AES and GAC, allowing you to complete both sections if desired or focus on the one most relevant to your needs:
App Engine Studio (AES): Learn about AES and create a new application using its features, which is a for-fee application.
Guided Application Creator (GAC): Work through creating a new application using GAC, a feature that doesn't require an additional fee but has limitations on feature capabilities.
4. App Engine Studio Overview
Before we delve into the intricacies of crafting a mobile application within App Engine Studio, it's pivotal to commence with a thorough exploration of the App Engine Studio Overview. This comprehensive introduction serves as the cornerstone for comprehending the multifaceted capabilities of this powerful tool, allowing you to wield it effectively to build tailored mobile applications. Let's take a closer look at what this overview encompasses and how it equips you for the journey ahead.
Understanding App Engine Studio
App Engine Studio is an instrumental component within the ServiceNow ecosystem, designed to streamline the process of creating custom applications. It is particularly valuable for constructing mobile applications that align seamlessly with your organization's unique requirements. The overview demystifies the various facets of App Engine Studio, shedding light on its functionalities and how they can be harnessed to your advantage.
Building a New Application
One of the core aspects covered in the overview is the process of building a new application. It offers step-by-step guidance, taking you through the key stages of application development within App Engine Studio. By the end of this section, you'll be well-versed in initiating a new application project, configuring its features, and customizing it to cater to specific organizational needs.
Leveraging ServiceNow Documentation
In line with ServiceNow's commitment to providing comprehensive resources, this overview directs you to relevant documentation. These resources are a treasure trove of insights and guidance, allowing you to explore App Engine Studio in-depth. By referencing ServiceNow's official documentation, you gain access to the latest updates, best practices, and expert insights to make your application development journey even more seamless.
Unlocking the Power of Customization
App Engine Studio empowers you to create applications that are finely tuned to your organization's requirements. This means you can not only build applications from the ground up but also customize existing ones to better serve your needs. The overview highlights the flexibility of App Engine Studio, emphasizing how it can be tailored to align with your organization's unique processes.
A Valuable Foundation for Your Learning Journey
By immersing yourself in the App Engine Studio Overview, you'll acquire a solid foundation upon which to build your knowledge and skills. This knowledge will prove indispensable as you embark on the journey of creating customized mobile applications within the App Engine Studio environment. It's a gateway to unlocking the full potential of ServiceNow's mobile development capabilities.
In your learning journey, don't hesitate to turn to ServiceNow's extensive documentation, which serves as a dependable companion on your quest for mastery. These resources are designed to offer clarity, guidance, and expert insights, ensuring that you have everything you need to succeed in building exceptional mobile applications within the ServiceNow platform.
5. Using AES to Build a Mobile Application
Developing mobile applications primarily takes place within the Mobile App Builder. However, when initiating a new application, an initial set of data items, screens, cards, launcher screens, and functions is created. This guide walks you through the process of creating a new mobile application in App Engine Studio (AES), offering insights into the essential steps involved.
Step 1: Create App
Begin the process by selecting "Create App," located in the upper right corner of the welcome window. This action launches the application creator, providing various options for crafting and customizing a new ServiceNow application. For this purpose, focus on "Basic Info" and "Experience." It's worth noting that the first time AES is opened, a "Getting Started" window may appear, which can simply be closed to proceed.
Step 2: Name the App
Give your application a descriptive name. This name will be visible not only in App Engine Studio and Mobile App Builder but also in the Application picker in the Platform and the My Company Applications. It's important to choose a recognizable name, especially if you need to manage or delete the application outside the mobile scope. The chosen name is also utilized when applications are published to the ServiceNow Store. Consider including the word "Mobile" in the name to distinguish it from other applications. The application is created as a new Scoped application, offering data protection and mitigating conflicts with core functionality during upgrades. Additionally, you can add an optional description and thumbnail image.
Step 3: Add Roles
Roles can be added to define who has access to the application, although this is not mandatory and can be configured later as needed. After defining or modifying the roles, proceed to the app dashboard.
Step 4: Configure an Experience
With the new application created and the app home page open, it's time to create a mobile experience. Click on "Add" next to the Experience header or "Add to interface" in the corresponding box. Select "Mobile experience" and click "Begin" in the bottom right of the modal. This step is crucial, as it marks the selection of a mobile experience.
Step 5: Add Experience - Select Mobile Apps
Choose the mobile app(s) to which this experience will be added. This addition configures the initial screen(s) within a launcher screen in the selected mobile app(s), appearing with the lowest priority on the navigation bar. You can select one or both apps, and any newly added launcher screens can be modified or deleted from the navigation bar later.
Step 6: Add Experience - Configure Launcher Screen
Here, configure a launcher screen that will be added to the navigation bar of the selected mobile app(s). Select an icon for the navigation bar, enter a distinct name for the experience (displayed on the navigation bar or within the More menu), and optionally select roles with access to this navigation item. If you selected "Mobile Agent," an "Available offline" checkbox is displayed, which applies only to the screens in Mobile Agent. The preview provides an approximate representation of the configured settings.
Step 7: Add Experience - Select Screen
In AES, you have two screen options available for the initial build: "List screen" or "Mobile web." The "List screen" typically includes a list of records and a record screen, along with pre-configured functions (New, Update, Delete). "Mobile web" simply displays a web page of a provided URL.
Step 8: Add Experience - Configure Data Item
If you selected "List screen" in the previous step, you'll need to select a table to determine the records displayed within the screen of the mobile app(s). This configuration sets the Data Item applied to the screen. Configure the conditions for the data to be displayed to pre-filter results and enhance output value.
Step 9: Add Experience - Configure Screen
For each screen, select an icon and color to customize the appearance within the launcher screen list. Enter a distinct name for the screen label, and if you selected "Webpage" in the previous step, enter the URL for the webpage. This step is crucial to proceed to the next.
Step 10: Add Experience - Finish Configuration
If you need to add more screens, you can do so using the "Add more screens" option. The configuration process for additional screens is similar to the one you've just completed. When you're satisfied with the configurations, click "Done adding screens."
Step 11: Add Experience - Success
After successfully adding the experience, you have two options:
"Edit in Mobile App Builder," which opens a new tab with Mobile App Builder and the new application.
"Done," which returns to the home of the application, where additional configuration options, including Experiences, can be tailored for the application. Additionally, this screen provides barcodes for downloading the mobile app(s) on the testing device. Note that only the apps selected during development are available under "Select app," and both iOS and Android platforms are accessible under "Select platform."
Application Created
At this stage, your new configurations can be tested within the mobile app(s). Remember to swipe down from a launcher screen within the mobile app to see the changes. You can further edit the configuration and add additional screens, functions, and features using Mobile App Builder.
This intuitive step-by-step process ensures a seamless transition from application creation to testing, offering a valuable introduction to mobile application development within the App Engine Studio. If you ever need to navigate backward during the configuration, you can use the step line at the top of the screen, which indicates the current status of the configuration, along with an arrow to navigate to the previous steps.
6. Additional AES Configuration Items
In the application created using App Engine Studio (AES), there are several additional settings that can be configured to enhance management and collaboration. These settings provide greater control and security for your application development.
Manage Collaborators:
The "Manage Collaborators" feature, represented by a round icon featuring a person and a plus sign, allows you to assign owner and editor designations for the application. This feature serves to restrict access and editing rights to the application, ensuring that only authorized individuals can view and make modifications to it. This can be especially valuable for safeguarding sensitive applications from unauthorized access.
Application Properties:
Application Properties offer a set of customizable settings and options to fine-tune the behavior and functionality of your application. You can configure various properties to align the application with your specific requirements. This includes defining the application's behavior, permissions, and other critical parameters that affect its performance and user experience.
Source Control:
Source Control enables you to manage and track changes to your application's source code and configurations. It provides version control and collaboration capabilities, allowing you to monitor and revert changes, collaborate with other developers, and maintain a record of all modifications made to the application. This is crucial for ensuring the stability and integrity of your application throughout its development lifecycle.
Publish:
The "Publish" feature allows you to share your application with a wider audience. It provides the means to release your application to users, making it accessible and usable. This step is essential when your application is ready to be deployed and used by the intended audience, whether it's within your organization or for public consumption.
These additional configuration items within AES empower you to manage collaborators, fine-tune application properties, maintain source control, and publish your application effectively, ensuring that it meets your development and security requirements.
7. AES Application Building Activity
Congratulations on successfully creating a new mobile application in AES! This practical exercise allowed you to apply your acquired knowledge and skills to configure a mobile application.
Here's what you achieved:
Application Name: You named the application "Work Orders Mobile."
App: It's designed for the "Mobile Agent" app.
Experience Label: You labeled it as "Work Orders."
Screen: The application features a "List" screen.
Table: It's linked to "Work Order Task."
Conditions: You set specific conditions: only work orders assigned to you and with a scheduled start date before today will be displayed.
Screen Label: The screen is aptly named "Past Start WO Tasks."
With these configurations, you've laid the groundwork for effectively managing past-due work orders. The conditions you've set ensure that the application displays relevant information tailored to your needs.
Your newly created application is now ready for further customization and enhancement in Mobile App Builder. In this platform, you can add more features and functionality to meet the specific requirements of your business.
You've successfully completed this activity, demonstrating your ability to create applications in AES. If you're ready for more challenges, you can explore how to create applications using Guided App Creator (GAC) or test your knowledge with a Knowledge Check to reinforce your understanding.
Guided App Creator (GAC): Learn how to create new applications using Guided App Creator.
Knowledge Check: Test your knowledge by taking the course's knowledge check to solidify what you've learned.
Great job, and keep up the excellent work as you continue your mobile development journey with the Mobile Development Essentials path.
8. Guided App Creator Overview
While the preferred and more versatile method for creating a new mobile application is App Engine Studio (AES), it is also possible to build an application in Guided App Creator (GAC). GAC offers a simplified approach to application development and is directly accessible within Studio in your instance.
Here are the steps to get started with Guided App Creator:
Step 1: Access Guided App Creator
Access Guided App Creator by navigating to the Studio in your ServiceNow instance.
Step 2: Explore "Getting Started with Guided Application Creator"
To familiarize yourself with the capabilities and workflow of Guided App Creator, explore the provided resource titled "Getting Started with Guided Application Creator." This guide provides a comprehensive overview, offering valuable insights into the process of building a new application using GAC.
Guided App Creator (GAC) serves as an alternative method for mobile application development, offering simplicity and ease of use. It can be a suitable choice when App Engine Studio (AES) is not available or when a rapid, uncomplicated application is needed.
By following these steps and exploring the provided resource, you can acquire a solid understanding of GAC and make informed decisions about your mobile application development strategy within ServiceNow. For detailed instructions and references, please consult the ServiceNow documentation.
9. Using GAC to Build a Mobile Application
If App Engine Studio (AES) is not available or you prefer a simpler method for creating mobile applications, you can use the Guided App Creator (GAC) within Studio. Here's how you can create a mobile application using GAC:
Step 1: Access Guided App Creator
Begin by opening Studio from your ServiceNow instance.
Step 2: Define Application File
When in Studio, you'll have access to existing applications as well as the option to create new ones. Choose "Create Application" to initiate GAC.
Assign a name to your application. This name will serve as the container for your application and will be used throughout the development process. It will also be used in the ServiceNow App store if you choose to publish the application.
You can opt for a Scoped application (recommended for avoiding conflicts with upgrades) or a Global application (provides more accessibility but may lead to conflicts). If you select Scoped, the scope will be auto-populated. Edit the Scope value if conflicts arise.
Optionally, provide a description and logo.
Click "Create" to proceed.
Step 3: Add Roles
Define and assign roles that will be used within the application. Roles help define tables and user experiences. It's recommended to add these roles at this stage for easier development.
Click "Continue."
Step 4: Select Application Format(s)
Define the format for your application. For mobile development, select the "Mobile" format.
Click "Continue."
Step 5: Identify Tables
Choose one or more tables to define the data to be included in the application. You can also create new tables.
Note that, in GAC, you cannot set conditions, meaning all records for selected tables will be included. You can edit this later in Mobile App Builder.
Click "Done with tables."
Step 6: Start Designing
Initiate the development of your application by clicking "Start designing."
Step 7: Customize Design
Review and edit the general information provided earlier, such as the Name, Description, Tables, and Roles.
Select an App Icon and color to be used in your application.
Configure whether the application should be available offline (GAC automatically adds new applications to Mobile Agent).
Click "Create" to proceed.
Step 8: Complete Application Configuration
If you have configured multiple application formats, you'll need to complete the design step for each one. However, for mobile development, the "Mobile" format is sufficient.
After finishing the design for the last step, click "Done with apps."
Configuration Complete
Your application is created. You can select "Go to Studio" or "Done" to return to Studio. Mobile App Builder is the preferred tool for editing mobile configurations.
To test the configuration, use Mobile Agent.
Please note that you can't go back to edit previous configurations once the build process is complete. However, you can edit selections during the "Start design" review before finalizing the application.
10. Building an Application in GAC Activity
Great! You've learned how to create a mobile application using the Guided App Creator (GAC). Now, it's time to test your understanding by completing an activity. Follow the guidelines below:
Activity Instructions:
Open Studio in your ServiceNow instance.
Create a new application using the "Create Application" option.
Configure the application with the following details:
Name: End User Apps Mobile
Advanced Settings: Scoped
Roles: admin
Format: Mobile
Tables: Incident
Once you've configured the application, test it within the mobile app.
Remember, you can refer to the information you've learned in the previous lessons, but try to complete the activity without a step-by-step guide to reinforce your learning.
If you need a step-by-step guide, you can refer to the PDF provided. The application can be further configured in Mobile App Builder, which is covered in more detail in other courses within the Mobile Development Essentials path.
Before proceeding to the next courses, you have the option to learn about application creation in App Engine Studio (AES) or take the Knowledge Check.
Learn to create a new application using App Engine Studio (AES)
11. Knowledge Check
AES is a for-fee Store app.
True
False
What is generally the preferred application development environment?
App Engine Studio
Guided App Creator
A new application in the Global scope can be created with AES.
True
False
Which screen types can be created using AES (select all that apply)?
Input form
List
Webpage
Record (only)
Conditions for a data item can be set during creation in which environment?
AES
GAC
Multiple screens can be created using the same table with GAC.
True
False
12. Congratulations!
You've completed the course, and you're now ready to begin creating new mobile applications in ServiceNow. To continue learning about mobile development, you can do the following:
Continue with Other Trainings: Explore other courses in the Mobile Development Essentials on-demand series to further enhance your skills.
Review ServiceNow Product Documentation: Visit the ServiceNow Product Documentation site to access detailed documentation and resources that will help you master mobile development in ServiceNow.
Feel free to exit the course module and start building innovative mobile applications on the ServiceNow platform. If you have any more questions or need assistance in the future, don't hesitate to reach out. Good luck with your mobile development journey!
Key: ServiceNow Mobile Development, Mobile Application Creation, ServiceNow Mobile App Builder, Guided App Creator (GAC), App Engine Studio (AES), Mobile App Configuration, Creating Mobile Applications, ServiceNow Mobile App Design, Mobile Development Course, ServiceNow Training Series, Mobile App Development Skills, ServiceNow Learning Path, ServiceNow Mobile Development Tutorial, ServiceNow Course Modules, Mobile App Building Techniques, ServiceNow Documentation Reference, ServiceNow Training and Certification, ServiceNow Developer Resources