I'm new to ServiceNow and have been following the Learning Path on the Developers site. I created a Jakarta Instance and have been making my way through the tutorials. However, I have been consistently running into problems where I am missing configuration options when creating application files. I can't properly set up UI Policies, Events, Notifications, etc. because I'm missing specific options like being able to write scripts and more. I have switched to the "Advanced View" in the "Related Links" but to no avail. The account is an Administrator account and has not been modified at all since the creation of the Instance. Is there something I am missing? Other developers following this track with me currently do not have the same problems so I'm wondering if its account specific or something with configurations. I've attached my Notification file; even in Advanced View, it is missing "Send When" and "Advanced Condition" script.
An example of options not loading: Notification Application File Example
Double check that you are under the Advanced view for these sections.
These should be there for you, Send when and Advanced condition are under the When to send tab within the Advanced view.
If you don't see these under the Advanced view, you should be able to manually add the fields using the Form Designer.
Take a look at the documentation at Form design.
In short
Go to your instance and go to Settings Gear > Developer and change Application to Global
Right click the header and go to Configure > Form Design.
Verify you've selected the Advanced view
Drag the missing fields to the form.
Click Save
Change the Application back to the one you are working with
Related
Since a few days ago, I noticed a new button “Update” in my deployed custom models. I don’t recall having seen this documented anywhere or having received any notification about this new functionality. Can anyone explain what exactly this new button does?
The change of the Undeploy button to an Update button was made in order to better indicate that, once deployed, you can update the deployment settings of your deployed model rather than just undeploying the model. If you press update, you are now presented with a list of regions you can deploy to or undeploy from. Setting all regions to undeployed is the equivalent of undeploying the model.
I have built a Google App Maker application and published it. However, I only want users in a Google Group to be able to access the application (view UI elements) via the deployment link. How do you do this? I referenced this solution to another post: https://stackoverflow.com/a/49577258/9878092. I cannot seem to find where the Application access section that is mentioned in the solution is. Thank you!
Here are the steps you can follow to go to 'Application Access' screen.
From your appmaker window click on 'Setting' icon.
Go to Deployments tab.
Publish new deployment if you haven't done already. If you have already deployed your changes then click on the deployed version and "Edit" button.
This will open the Application Access screen. Select option "Only allow to specific" users. Provide user names who should be able to access the app.
I'm building a Chrome kiosk app that will be in a public space. Users can interact with the app, but there are a variety of settings (server addresses, timeouts, etc.) that need to be set. I'm looking for a strategy on how to allow access to that administration config.
On first run - This is straightforward, but I want administrators to be able to pull it up again.
Detect if the app ran as a kiosk app or manually - This would kind of work, not sure if it's the greatest
Detect some key combination - Ctrl + Alt + Something switches over to the settings page, this feels like people could stumble on it accidentally.
Is there another approach I'm missing?
If your Chrome device(s) is managed you have a further option which is to use the Chrome App Management area within the Google Apps admin interface.
To do this you code your app to use the storage.managed API and this should allow a Configure section for your app within Chrome App Management.
I haven't tried this myself yet but this appears to be the way the Chrome Sign Builder app is configured with its schedule.
Another approach would be to have an administrator login button in a corner of the app. You can set a default password for administrators, which could then be changed in the settings dialog.
You can also think of combining suggestions you have made, first run and then a key combination, and this could bring up a password prompt as also suggested. For an example of this see the Zebradog Kiosk app which is in GitHub so you can see code of how this could be done.
I use ctrl-alt-S at boot. This allows me to login and make changes. I know you have to do a couple of reboots, but it is out of service during admin time anyway.
Is it possible, to deactive an app (all requests will get a error answer from the app42 service) for a while (or even better, for all except one special user), update the database and after everything is valid again, reactivate the app again?
You can easily deactivate your app through dashboard.
Follow just simple steps:
Login to your AppHQ Management Console
Click on View Apps under App Manager section
Click on Disable to deactivate your app
Same you can follow when you have to activate click on enable.
Let me know if it helps.
i would like to distribute an access front end to some people and i want to make sure that they do not edit anything in it; however when i change the extension to ACCDR it makes all the forms and tables disappear. what settings do i have to change in order for them to be able to open forms but not view them in design view or make any changes to the forms?
The accdr extension puts your Access application into the "runtime" mode of Access, meaning the end user does not have the ability to see the built in navigation tools within Access. You would need to provide the navigation mechanism within the application yourself (for example, a startup form with links to the forms \ tables you want the users to be able to interact with).
The accdr extension hides objects from the user, but it does not prevent them from changing the file extension back to accdb and modifying your code \ objects.
To completely "lock down" the application you need to create an accde file instead. This prevents the user from being able to open a form in design view and make changes.
The following two links provide additional information about the file types and ways to deploy your application:
Intro to the Access 2007 file format
Deploy and Access 2007 Application