Jarvis guide
Try “supplier bill”, “overdue invoice”, “approval”, or a feature name.

Learn how your custom app is used

Use the Custom App Learning Agent to create business-facing Wiki pages from selected, trusted apps.

For
Admin
Availability
For users with access to the related records
Reading time
2 min
Verified
2 August 2026

Outcome

Jarvis can explain the business workflows in a trusted custom app without filling Chat with source code.

Main feature: Learning and review

The situation

Your company uses a custom app called dealer_claims. New team members know the screens but not why a claim is held, who approves it, or which documents are created. The original developer is no longer available.

Before you start

This is an administrator task. Review the app ownership and code source. The selected source is sent to the AI provider connected to the site. Do not select an app you do not trust or have permission to analyse.

Run the learning Agent

  1. Open Agents and find Custom App Learning.
  2. Read the overview and install it.
  3. Open Skills > Analysis.
  4. In Learn from custom apps, choose Choose apps and run.
  5. Select only dealer_claims for the first run.
  6. Read the consent text and start learning.
  7. Follow the run from the Agent’s Runs tab.
  8. Open the company Wiki pages the run created or updated.

Review the result as a business user

Ask whether a page explains the event, people, decision, record, and exception in normal business words. Correct anything that describes code but not work. Re-running the Agent updates the same pages rather than creating another copy.

Do not treat generated documentation as permission to change the app. It is an aid to understanding its workflow.

Done when

A new operations user can read the Wiki page and explain how a dealer claim moves from submission to approval, including the hold conditions and responsible role.

Source comments can be wrong or outdated. Compare the generated page with one real case and a current process owner before sharing it widely.

Use it again

Run one app at a time until the review process is trusted. Re-run after a meaningful workflow change, not on every small code update.