Installed Applications
How to use Installed Applications in Platform Settings: access, working steps, fields, related records and troubleshooting.
Purpose and access
Review platform defaults and dependencies within the administrator’s authority. Record the reason and tested impact of changes. Authentication, session settings and security-sensitive configuration need a controlled change process.
This page is a settings page in System Admin → Platform Settings. Use the link above to open the configured destination; permissions are checked by the destination service.
Before you start
Review the current settings or existing records and prepare the information needed for the change.
Confirm the company, party, dates, units and source references that apply. Select existing links carefully and check for an existing record before creating a duplicate.
Working steps
- Open Installed Applications from System Admin → Platform Settings, or use ERP Search.
- Review the existing configuration before editing.
- Complete the editable fields described below. Required fields and validation conditions must be satisfied; read-only values are set by the system or their source records.
- Add the required child rows. Review each row’s identifiers, linked records and values, using the child-table field reference below.
- Save the record and address validation messages. Reload and verify the saved values and relationships.
- Use any additional workflow actions only when the record and your role provide them. Saving this record does not automatically complete a related transaction or external action.
Field reference
These fields come from the installed ERP definition. Hidden fields and password inputs are omitted. Additional conditions, custom scripts and workflow rules can make a field required or read-only in a particular context.
| Field | Type / behavior | How to use it |
|---|---|---|
Installed Applicationsinstalled_applications | Table Optional · Read-only | Add the relevant child rows and review required columns, quantities and references before saving. Linked record: Installed Application |
Child tables
Installed Applications — child-row fields
| Field | Type / behavior | How to use it |
|---|---|---|
Application Nameapp_name | Data Required · Read-only | Enter the identifier or short text requested by the label. Preserve external reference numbers accurately. |
Application Versionapp_version | Data Optional · Read-only | Enter the identifier or short text requested by the label. Preserve external reference numbers accurately. |
Git Branchgit_branch | Data Optional · Read-only | Enter the identifier or short text requested by the label. Preserve external reference numbers accurately. |
Has Setup Wizardhas_setup_wizard | Check Optional | Enable or disable the named option only when it matches the intended record behavior. |
Is Setup Complete?is_setup_complete | Check Optional | Enable or disable the named option only when it matches the intended record behavior. |
Troubleshooting
- Not permitted: verify the account, role and source-document permission. Do not share an administrator login.
- Missing record or address: inspect the relevant Link or Dynamic Link fields; a matching title alone does not establish a relationship.
- Cannot save or change status: review required fields, read-only values, document status and the configured approval transition.
- Unexpected report or portal result: review company/date filters, source-document submission and the approved party or Employee link.