Yeah, would be great to have some customization, like they already have on their own website :)

You can create your own custom 404 page but you have to use HTML.

Just wondering how?

And is that available for Outsystems cloud instances?

A generic 404 would be great with an option to upload 404 images with some custom text.

I believe this is a basic thing that need to be supported by platform.

Hi All,

Yes, I was also facing the same issue. and OS Team,Please start works on this ASAP.

Thanks

Hi All, 

I see that this was opened two years ago, was it ever picked up?

Hi,

It has been a while since this was posted and since this was put on "OutSystems radar".

Is there any update or foreseen date for this new feature to be released?

Cheers,

João

Hi João,

Thank you for your interest. We may look into this soon (no promises though), in the context of another initiative (SEO Friendly URLs for reactive apps), but we can't still commit to a date on any of it.

Cheers,
Tiago Simões

Hi,

I am also interested in knowing if there is any progress on this.

At the moment the alternative they gave me was to use Amazon CloudFront.

Cheers,

Jose

I agree with this initiative. Is necessary for implement a good protection practice.

Upvoting this to help push this request to being implemented!

Please do this.  

This is the basic one must have in the newer version as this post is been more than 2 years people shown interest to have feature on the platform.

Yes Please. We would definitely use this in cloud apps.

Yes please! We are currently facing this need for a cloud environment. App specific custom 404 pages would be a great added value in comparison to the built-in error page, which is absolutely not something you can serve to an end user. 

The default IIS 404 is not realy looking very professional for a customer-facing application. Please put this on the radar again.

So this is stated as a best practice (see documentation) and has been requested for over 4 years. Please make it happen.

That will be useful. Please do this.   

What is the hold up on this? Seems like a fairly basic request. 4 years for a feature that will stop cloud apps looking like they were created by a dude in his basement!

There isn't a reason for not doing it!

I think we need this, It's a customization that should be made easily by any developer.

This feature is a most to have and a great UX improvement. Would be great if we could define a custom "404 page not found" per application.  Please do it! Thx

Please, let's not lose this idea, it is necessary.

Any news on this?

Any update on this?

Hi an update on this would be very useful, we are also facing the same issues. I was very surprised to learn we are not able to customise 404/Page Not found screens.

This idea is really important. Outsystems should implement it asap.

any update please

Hi (Landing.Jobs) Dawud Menzed,

I think it is confusing to call a reactive application like the one you published on the Forge a plugin.

The work "Plugin" is used for OutSystems Mobile Apps that wrap a Cordova Plugin github project.

Regards,

Daniel

Hi All. I know this thread is a bit old now, but I have news to share.

We are thrilled to announce the launch of our brand new plugin on Forge, designed to empower our customers with the ability to create their own unique "404-Not Found" pages directly within Service Studio.

You can access the plugin at the following URL: https://www.outsystems.com/forge/component-overview/15534/custom-404-plugin.

You will find comprehensive documentation in the dedicated tab, providing step-by-step instructions on enabling and utilizing this new feature. We've also included a demo application showcasing its seamless integration.

This plugin works for both on-premise and cloud infrastructures.

Thank you.

Outsystems team: Please do not consider this implemented.

We attempted to use the Forge component as prescribed, but are getting tons of errors with no response on a resolution.

This should not be such a difficult request for the OS Cloud base to support.

@Doug Kantor if you have problems with the plugin, you need to post on the support page of the component, for the proper visibility of your issue. Posting it here on an Idea with status implemented will not give visibility to OutSystems.

Hi Doug,
Thanks for raising the issue. 
Daniel's advice is correct: adding to the discussion of an already implemented idea does not guarantee the attention you were looking for. But it worked this time ;-) 

I noticed you went to the support page but didn't get a reply.
This is not a formally supported component, and so support should be best-effort. The reality is that, so far, this didn't meet the best-effort target. I'll follow it up.

As a generic disclaimer, any Forge component is open-source. If you can understand the code and troubleshoot to pinpoint the language construct or platform API that is misbehaving, as if you had developed it yourself, you get full access to the standard OutSystems Support.

I do have to agree with Doug then that if the solution is "not a formally supported component" then this Idea hasn't really been "Implemented" has it? It just has a third party, open source workaround? 

If this is an implemented feature of the platform I would think OutSystems would take over support of the component? Make it first party and keep it working? 

I believe we have a number of customers using this successfully. There's obviously a problem that affected more than one customer, but let's not conflate that with "the capability does not exist".

Think we just have different definitions of "Implemented". Mine includes OutSystems fully supporting the feature.

We use it succesfully

Thanks for the feedback, Jordan. 

A new version of the component was just released precisely to address the problem you found, Doug.

This hasn't been "Implemented." Come on, guys. Someone found a solution and posted it as a Forge component, yet as it has been stated, it's not even a supported or verified component. So it's not a native OutSystems capability and needs quite a bit of tweaking (including another separate Forge component, Factory Configuration) to make it work. 

I would like to clarify that this Forge component was created by an OutSystems team.
I respect your concerns about the support model and ease of configuration and your disagreement with the idea's status.

If it is a first party OutSystem component, can you get the Supported tag added? It probably would go a long way to get people to trust it more. Right now "Vanguard Labs" does not mean anything to anyone. It sounds like another OutSystems partner agency. 

It does not even have the "Trusted" flag, so there is no way for folks to know if this follows good practices. 

I am still very confused how this is acceptable for OutSystems as a solution. Seems other people are still concerned as well.

Unfortunately I cannot mark my own idea not solved.

If you're pitching to a client who has used something like WordPress, and they ask if you can make custom 404 pages, and the answer is "Yes but you have to install 2 extra bits of software and make complicated configurations to make it work", it is most definitely not implemented into the platform.  

Something implemented I imagine would be similar to the Invalid Permissions screen, where you can handle an exception of the type PageNotFound and redirect there.

Hi Jordan,
My impression is that customers for whom the 404 experience is important are implementing the solution based on this Forge component. Hence, I feel that we have resolved the most important problem.
Addressing the remaining issues on this topic, which you describe, is still a valid idea. However, that is not in our short-term priorities.
I understand your discomfort and respect your decision not to mark the idea as Solved.