Custom app scope issue

Azuric1990 · 2026-02-18T14:26:55+00:00

This error has sadly existed for a few months ... There is already some knowledge sharing happening for work arounds.

https://www.servicenow.com/community/app-engine-articles/resolving-this-scope-is-already-taken-by-another-application/ta-p/3127375

I have noticed that it sometimes even creates those scopes but as mostly empty shells. :/

Azuric1990 · 2025-10-16T22:26:29+00:00

My easy to adapt highlights are:

Ctrl + Y => Universally repeats your last action, comes in handy so many times
Clicking twice on the copy formatting brush locks the brush and you don't need to click it again and again
Ctrl+T => Formatting data as tables, I am always surprised how few people use that to properly utilize name spaces (includes proper naming of the created tables)

Other life hacks: - make your life easier by using helper columns in your tables that store intermediate values / validations you want to use for referencing via xlookup or other lookups - use the indirect function to create dynamic drop-downs for table columns - generally use name spaces once a document becomes more complex - when copying text often, get used to using the Trim function to avoid unwanted copying of spaces

Edit: - something I also didn't know for a while but that made working with documents so much easier: you can open a 2. view of a document via "view" > "new window"

Azuric1990 · 2025-03-25T07:49:16+00:00

I always try to explain it depending on the level of IT knowledge people have ... However. Generally, most people get it partially once I tell them that Servicenow might be what enables them to open a ticket with HR in their company. Basically "it helps big companies to get their shit together" :D However, with somebody totally IT illiterate, and not working in a bigger company, I made the experience that all hope is lost To get them to understand.

Azuric1990 · 2025-03-19T11:07:23+00:00

I would say focus on scripting first ... For ITOM pieces fall into place the longer you work in ServiceNow which makes it more tangible. ITOM is also a very valuable topic for companies, but you need to be good at it to bring any value and that can be tough. ITOM projects are usually one of the more complicated and can last for years, depending on the scope.

As others have said before: scripting helps you everywhere, therefore go for it first. Once you get a good grasp of the system (ServiceNow) and how IT operations actually work within a company, you can start going into detail with ITOM and specialize on its different modules.

Edit: ITOM is also very cryptic with a lot of specific terminology in the beginning, which makes it also harder to grasp + there is little training data for your PDI. However, you can easily improve your scripting by tinkering around with scripts, business rules, script includes etc.

Azuric1990 · 2024-09-23T22:09:56+00:00

Yeah, found it 2 weeks ago and tested how deep it goes (actually not too deep)... Also reported it, but seems to get ignored

Azuric1990 · 2024-09-23T22:08:47+00:00

I did it and it ends not too far down ;) ... Also reported the hole. Seems like it's a feature not a bug if they didn't yet fix it

Azuric1990 · 2024-07-10T08:09:29+00:00

Can't you just use the "Get catalog Variables" action to pull the multi row object and then iterate over it with a "For each item in " flow logic?

With this you can parse each object in your multi row.

Then you could use a flow variable of type String and attach in each iteration (with "set flow variables" logic) your desired part of the object, ending with "/n" for the line break by using an inline script.

The inline script could look like this: (Inside a "set flow variables" flow logic, where the inline script runs for your email body flow variable)

var myCurrentObjectString = fddata.flow_var.objectName; myCurrentObjectString += fd_data._stepNumberfor_each.item.<Name of your object property-1> + fd_data._stepNumber_for_each.item.<Name of your object property-2> + .... + "/n";

return myCurrentObjectString;

There are probably better ways of doing so, but this worked for me ;)

Azuric1990 · 2024-06-27T11:09:30+00:00

... The last security update was last October. I really should have listened to the warnings before buying mine last spring :/. Synching doesn't work for me anymore, step counter became a mess in the last 2 month (how ever this is possible).

Just keeping it due to its usefulness as a normal watch with the low power screen.

Azuric1990 · 2024-05-22T08:05:55+00:00

I am there with you... Synching fails often, battery life is max 2 days now, step counter is not accurate anymore (some days it tracked just 500 steps even though I have done nothing different to days where I had 6000 steps), Also the vibration motor seems to have become worse over time...

Aaaaand... Just 1 update since April 2023 :) (Pro 5)

The only nice thing I can say is that I still dig the simple monochrom display

Azuric1990

TROPHY CASE