Custom App Discovery
Capture and operationalize support for an application that is not part of a standard catalog.
Custom App Discovery is used when an organization needs support for an application that is not already part of a standard catalog or predefined onboarding pattern.
What a custom discovery request does
A discovery request helps teams:
- capture the need for a custom application
- document requirements and context
- assign ownership
- track progress
- add comments and attachments
- convert the request into a real application when ready
Common statuses
Typical discovery statuses may include:
- pending
- in progress
- needs info
- completed
- rejected
Converting discovery into an application
When discovery is complete and the team is ready to operationalize the application, the discovery request can be converted into a real application record with onboarding artifacts and workflow setup.
Why discovery matters
Not every operational platform can be defined up front. Discovery makes it possible to bring custom, customer-specific, or unusual applications into the same governed operational model as standard apps.
Best practice
Use discovery comments and attachments to capture real implementation context. This makes conversion to a full application much smoother.