Hello,

Can you please share screenshot of what happens when you open this application in lifetime? Or explain more about the issue.

And please check application permission documentation which may help you, may be someone applied permissions to this application

https://success.outsystems.com/documentation/11/managing_outsystems_platform_and_application_lifecycle/manage_it_users/grant_permissions_for_specific_applications/

The community can help you with this. You may try to log a support call with OutSystems. 

Hey Ren,

Not sure if this is the same problem but from your description, it looks like. 

Google just launched a new version of Chromium that impacts how browsers validate Custom Protocols. This is making some of our Service Studio URLs invalid, like the comparison one in LifeTime. 

As this depends on the browser version, it would justify that some people can keep using it but others don't.

We are already on top of it to release new versions with the fix.

In the meantime, as a workaround, you can disable this Chrome feature as stated here.

Hope it helps!

We are also experiencing the same issue in our environment. Basically its throwing an javascript exception irrespective of the browser when we click on 'Compare module in Service Studio'.

Workaround is to copy the highlighted text below and replace  space with %20 and paste in browser url and it opens Service Studio and shows the comparision.

to 'servicestudio://-mergeModules%20headfitted-dev.outsystemscloud.com%20be63c3a1-f64b-465f-809d-20411f2eb31c%20headfitted-dev.outsystemscloud.com%2030355%201%20headfitted.outsystemscloud.com%2029995%202%20%22Development%22%20%22Production%22%200'

Thank you for your help！

I was able to do both methods, replacing the URL text and adding the Chrome option.

I'd say the real solution is not to manually replace spaces in links or add startup flags to Chrome, but to start using Firefox for LifeTime and ServiceCenter.
Chrome has gotten too powerful and we're entering the same era as with Internet Explorer again, in which one single browser forces their own 'standards' to all of us.

@Miguel Rebelo any chance other (non-Chromium) browsers can be selected for debugging in the future? Because when kept following Chrome's own standards and forced update policies could eventually result in a future risk for OutSystems.

The fix will work if you also remove the single quote on both ends of the text that you copy to open Service Studio, otherwise it does not work.

As for today no browser works well - except Microsoft Edge working in Internet Explorer mode.

Regards

Tomasz

Hi everyone,

Just saw the latest comments and seems you are still using a old LifeTime version without the fix for this problem. We have released 11.25.0 of LifeTime back in Oct 31st, 2024 that includes a fix to overcome this issue:
Fixed ServiceStudio links in LifeTime to make them compatible with Chrome browser policies. (RPM-5292)

I would like to recommend the update of LifeTime environment to overcome this issue and if you have any further problems please reach out to our Support so that we can keep evolving the product to better service you :)

Cheers,
Jose Ramalho