Entrar
Contate-nos
Suporte
BR
English
日本語
Deutsch
Français
Português (BR)
Plataforma

‍Visão geral da plataforma‍

A plataforma líder de desenvolvimento com IA

Explore a plataforma unificada, ágil e comprovada pelo mercado para todo o SDLC

Agentes OutSystems

Crie, aprimore e gerencie agentes em um só lugar, com mecanismos de proteção e controle de custos

Orquestração empresarial agentic

Geração de aplicações de IA customizadas a partir de um prompt em linguagem natural

Fluxos de trabalho agentic

Automatize e orquestre as transições entre humanos e agentes

OutSystems MCP

Leve o desenvolvimento de IA governada a qualquer agente de codificação.

Fluxos de trabalho agentic

A camada de dados virtual para potencializar todas as suas aplicações e agentes de IA

Segurança e conformidade

Suas políticas e governança empresarial integradas a cada aplicação e agente

Integração empresarial

Integre com qualquer sistema, aplicação e modelo de IA

Tabela de preços

Comece agora com planos flexíveis

Descubra mais

Descubra os principais casos de uso dos seus agentes
Explore o que você pode construir
Histórias de sucesso
Demos da plataforma
Compare o OutSystems
Guia de desenvolvimento de software de IA
Glossário de IA
Orquestre a colaboração entre humanos e IA
O que é low-code?
Casos de uso

Apps externos

Portais do cidadão
Portais de serviços bancários móveis
Portais de seguros
Portais de atendimento virtual
Portais de criação de contas de clientes
Portais de autoatendimento para clientes
Mais sobre apps externos

Sistemas Centrais

Sistemas de empréstimo digital
Sistemas de gestão de sinistros
Sistemas de serviço de campo
Sistemas de cadeia de suprimentos
Integração com Salesforce
SAP
Mais sobre sistemas centrais

Apps internos

Integração de colaboradores
Autoatendimento para funcionários
Gestão de escritórios
Gestão interna de casos
Gestão de serviços de TI
Gestão de desempenho
Mais sobre aplicativos internos
Ver todos os casos de uso
Leia as histórias dos clientes
Soluções

Soluções para sua indústria

Serviços bancários e financeiros
Seguros
Governo
Manufatura
Veja mais setores aqui
Saúde
Energia e serviços públicos
Varejo
Educação

Iniciativas empresariais

Inovação em IA agentiva
Desenvolvimento impulsionado por IA
Velocidade e agilidade de TI
Eficiência operacional
Experiência do cliente
Modernização de sistemas legados
Conheça exemplos de aplicativos
Leia as histórias dos clientes
Desenvolvedores

Descubra o nosso universo

Torne-se um desenvolvedor
Comunidade
Fóruns
Marketplace do Forge
Grupos de usuários
Tech Talks

Programas de Advocacy

Programa MVP
Programa de Campeões

Aprenda conosco

Treinamento
Documentação
Sessões de Jump Start
Certificações

Explore nossos recursos

Suporte
Atualizações de produtos
Newsletter para desenvolvedores
Conheça exemplos de aplicativos
Leia as histórias dos clientes
Sobre a OutSystems

Empresa

Sobre a empresa

Histórias de clientes

Avaliações da OutSystems

Parceiros

Blog

Webinars

Eventos

Recursos

Serviços

Carreiras

Central de Descobertas

Leia as histórias dos clientes
Explore a plataforma
Schedule demo
Schedule demo
Start free
Start free
Schedule demo
Schedule demo
Start free
Start free

OutSystems Problem Management O11 and before

At OutSystems, we use an 80/20 approach to solving the issues our customers may face with their usage of our product. This means we first aim at restoring service (and overcoming the limitations an issue brings) and then we focus on identifying the root cause so that our customers don’t have to deal with the same issue again.

For that, we handle customer issues in two different phases: Incident and Problem. Incidents are unplanned events that cause a service disruption; while Problems are their cause or potential cause.

At OutSystems we handle Incidents and Problems separately. Incident Management is focused on solving Incident tickets and unblocking our customers in real-time from any deterioration in the value they are receiving from their OutSystems platform. Incident Management is based on response times, as we define in - Support Severity Levels & Response Times. OutSystems support tickets are aligned with the Incident - we tend to close support tickets as the service is restored.

On the other hand, Problem Management is focused on preventing Incidents from occurring and reducing their impact if they do occur, which requires a longer-term and careful analysis. For that, OutSystems uses Problems shared with affected customers and identified as RPM-xxxx. Problem Management is initiated and advanced proactively by OutSystems based on its internal prioritization of business objectives and resources, and for that reason, it does not have defined response times or published service levels.

While working on Problems, our development teams need to decide on the best course of action based on criteria such as urgency to the customers, and the viability of alternatives or workarounds that minimize or even avoid the impact of the problem. Customers can keep track of the progress in a given Problem via Support Portal (in the support ticket that originated it); Any possible fixes to the product are identified in the Release Notes with the Problem (RPM) identifier as well.

Lifecycle

While working on a Problem, it goes through multiple phases depending on the activity happening. The diagram below explains the lifecycle of a Problem.

problem-management-page-graphic-2x

The possible statuses of a problem (RPM) are:

  • Waiting for Investigation
    OutSystems registered the Problem with information on how it manifests and its impact. No analysis of the cause has been performed yet.
  • Investigation On Hold
    OutSystems is waiting for additional occurrences of the same Problem to decide on further investigating it. For more details about this status, check Details on "Investigation on hold" status.
  • Investigation Started
    OutSystems started the investigation of the Problem, in order to assess the most adequate type of solution.
  • Inconclusive Investigation
    OutSystems has not been able to conclude the root cause and will proceed to investigate when additional information or new occurrences are available.
  • Fix to be Released
    OutSystems has created a software fix, which is pending release to the general public.
  • Closed - Fixed
    The Problem was addressed with a software fix that was already released.
  • Closed - Known Error
    The Problem was documented as a misbehavior, typically with a workaround, but a software fix was not produced. For more details about OutSystems not fixing a given Problem, check Known Errors.
  • Closed - Duplicated
    A duplicate of an existing problem.
  • Closed - Not applicable
    OutSystems did not consider this to be a valid Problem. The Justified Status Decision will indicate why. For more details about this status, check Details on “Not Applicable” status.

Details on “Investigation On Hold” status

Not all software fixes have a direct impact on our customers’ ability to achieve their outcomes with the platform, especially for lower-impact Problems, or when workarounds are available.

OutSystems will internally decide whether a Problem will be investigated or remain on hold until real customer data demonstrates the relevance of addressing it. In that situation, ‘Investigation on Hold’ is an intermediate state in which additional evidence is gathered to justify further attention and time investment in pursuing the Problem’s investigation and possible fix.

Even when focused on tackling the Problems that strongly impact our customer base, we may always decide to pick a lower-impact Problem for deeper investigation as additional data become available.

Details on "Not Applicable" status

Not all Problems end up being… Problems, even after being created.

Some of them are not originated as follow up of incidents but for other reasons that don’t apply, so we might not deem the Problem as one, and that will be clearly visible on the Problem page - with our justification for such a decision.

Known Errors

For as much as we would like to at OutSystems, not all problems of the world can be solved at the same time. The same goes for Problems of the OutSystems software - so we decide how to handle them to ensure the best results for our customers.

When prioritizing fixing Problems, we take a number of variables into consideration - like the impact on customers’ day to day, the effort required to fix the Problem, the risk for customers (affected or not affected by the original Problem) of possible side effects the fix might introduce, and others - to decide whether or when to fix it.

Sometimes we might identify misbehaviors in the course of Problems that, after clearer analysis, turn out to be expected behaviors that did not make sense at the time, were poorly documented, are the result of features we don’t have yet, or other similar situations.

Eventually, OutSystems may opt not to fix misbehaviors; instead, we may choose to document them, so that customers can know what to count on. When relevant, such documentation will also come with one or more workarounds visible through the Support Portal so customers can overcome that behavior.

Documenting a Problem creates an internal Known Error which might not be the end of the line - in our continuous improvement we might pick it up again for a software fix.

Find below more extensive criteria that may lead a given RPM not being fixed:

  • The fix is unfeasible;
  • The fix has a high risk;
  • There is a simple workaround;
  • The number of customers affected by the issue is low;
  • The cost to fix is too high or the Return on Investment (ROI) is too low;
  • The issue can be addressed by documentation;
  • The issue does not represent a product issue (eg. it’s a limitation of the underlying technology);
  • The desired fix is not aligned with the Product direction or vision;
  • Other unforseen situation within reasonable justification.
Plataforma OutSystems
Visão Geral da PlataformaPreçosGuia de AvaliaçãoBásico de Low CodeModelos de AplicaçõesTeste grátis
Por que OutSystems
Avaliações da OutSystemsHistórias de clientesAvaliações de AnalistasEventosServiçosParceirosFAQsCarreira & CulturaMendix vs. OutSystems
Soluções por Iniciativa de Negócio
IT speed and agilityAgentic AI innovationLegacy modernizationCustomer experienceOperational efficiency
Soluções por indústria
Banking & Financial ServicesSegurosGovernoManufaturaSaúdeEnergia e serviços públicosVarejo e atacadoEducaçãoVer todas as Indústrias
Parceiros
Visão GeralEncontre um ParceiroTorne-se um ParceiroAlianças TécnicasParceiros de TreinamentoAcessar Partner Center
Desenvolvedores
TreinamentoAtualizações de ProdutoSessões Jump StartCertificaçõesForge MarketplaceUser GroupsTech TalksDe/Coded Podcast
Comunidade
Comunidade PrincipalFórunsSugestõesOutSystems Research ProgramPrograma MVPOportunidade de Emprego da ComunidadePrograma de Campeões
Suporte Técnico
Documentação TécnicaCentro de SuporteDownloads
Recursos
Desenvolvimento de Software de IAGlossário de IATransformação DigitalDesenvolvimento de AplicaçõesEventos e WebinarsBlogRecursosCentral de DescobertasAlternativas por plataforma
Empresa
Sobre a OutSystemsContact SalesEscritóriosAssessoria de ImprensaCarreira e CulturaESG StatementSupplier Code of ConductSitemap
Menções Legais
Visão geral jurídicaPolítica de CookiesEU Co-Funded ProjectsModern Slavery ActTermos e CondiçõesLGPD na OutSystemsMaster Subscription AgreementTermos de Uso do RepositórioDeclaração de PrivacidadeCode of Business Conduct and EthicsPolítica de Notificação e RemoçãoCorruption Risks Prevention Plan
OutSystems © - All Rights Reserved
55 Thomson Place
2nd Floor
Boston, MA 02210
Tel: +1 617 837 6840
Mais escritórios
Português (BR)
English
日本語
Deutsch
Français
Português (BR)
Obrigado! Recebemos o seu envio!
Ops! Algo deu errado ao enviar o formulário.